---
title: Using Macros to Set Privacy Rules in Cases
slug: portal-sub/using-macros-to-set-privacy-rules-in-cases
docTags: 
createdAt: 2026-03-04T12:03:15.455Z
---

Cases are recommended to be used for specific use cases, rather than as a wholesale approach to all activities; they are designed especially for use in sensitive areas – transgender, sexual health, etc. where there is particular privacy requirements (perhaps even within the staff working at the clinic / medical facility – e.g. the clinician in a small rural community clinic dealing with a teen that has significant sexual health issues, where a clinic staff member is a family member of the teen).

Privacy settings can be set using the **Configuration Options** in the Profile.

Using macros lets you set advanced rules including:

- Is the case visible?
- Can the case be seen, but not opened?
- Can the case be opened after a challenge?
- Can the case be opened with no challenge?

Cases can have actions associated with it, including:

- Is a case view available?
- Can an action be performed?

Case permissions, via roles, can be set:

- Can data be read?
- Can data be added, altered or deleted?

### 


### When using cases, be careful not to duplicate clinical information in the EMR. 

Cases can be configured to be completely invisible to some users; so unless a user has permission to see the content the existence of the case may not appear anywhere in the user interface. This can lead to cases where a user without permission to see the case will created duplicate clinical information in the EMR (e.g. they are treating a patient for severe and chronic pain and do not see a prescription for pain management, so prescribe Oxycodone – not seeing that the patient already has a prescription for another drug in the case);