Using Macros to Set Privacy Rules in Cases
2 min
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);