Difference between revisions of "6. Emergency Access Procedure"
Bradymiller (talk | contribs) (→Links) |
Bradymiller (talk | contribs) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
Permit authorized users (who are authorized for emergency situations) to access electronic health information during an emergency. | Permit authorized users (who are authorized for emergency situations) to access electronic health information during an emergency. | ||
== | == Emergency Login == | ||
The individual facility can describe the guidelines for an emergency situation. An emergency access solution should be used only when normal processes are insufficient (e.g. the helpdesk or system administrator is unavailable). | The individual facility can describe the guidelines for an emergency situation. An emergency access solution should be used only when normal processes are insufficient (e.g. the helpdesk or system administrator is unavailable). | ||
| Line 20: | Line 20: | ||
== Technical Requirements == | == Technical Requirements == | ||
1. | 1. "Emergency Login" acl creation will handled in two ways | ||
1. During installation | |||
2. | 2. Use acl_upgrade.php | ||
2. When the Emergency Login policy is chosen while user creation, a message "Emergency Login ACL is chosen. The user is still in active state, please de-activate the user and activate the same when required during emergency situations. Visit Administration->Users for activation or de-activation." is display and request users to disable the Emergency user account. The usernames should be of the format "breakglassxxx" or "emergencyxxx" | |||
4. Irrespective of the log level, all activities during emergency access should be logged | 3. When the Emergency Login account is activated (during emergency situation), an automatic mail should be sent only if $GLOBALS['Emergency_Login_email'] is set 1 and $GLOBALS['Emergency_Login_id'] is set to mail id. | ||
4. Irrespective of the log level, all activities during emergency access should be logged. | |||
5. After the emergency period, the account should be deleted and the audit trail should take place [Administrative requirements] | 5. After the emergency period, the account should be deleted and the audit trail should take place [Administrative requirements] | ||
''' Where: ''' | |||
1. Administration -> Users | |||
2. Administration -> ACL -> User Memberships | |||
3. Administration -> ACL -> Advanced -> ARO Group Admin | |||
== Status == | == Status == | ||
Completed | Completed and checked in to the Sourceforge CVS | ||
== Links == | == Links == | ||
Sourceforge Communication - http://sourceforge.net/projects/openemr/forums/forum/202506/topic/3532189 (second) | * Sourceforge Communication - http://sourceforge.net/projects/openemr/forums/forum/202506/topic/3532189 (second) | ||
Sourceforge Communication - http://sourceforge.net/projects/openemr/forums/forum/202506/topic/3397800 (first) | * Sourceforge Communication - http://sourceforge.net/projects/openemr/forums/forum/202506/topic/3397800 (first) | ||
* Break Glass/Emergency User Test Report - http://www.openmedsoftware.org/mw/images/b/ba/BreakglassTestReport_Updated_apr17.tar | |||
[[Category:Certification]][[Category:Certification Stage I]] | |||
Latest revision as of 02:47, 9 September 2012
Owner of this task
ViCarePlus HealthCare IT Services & Support
6559, SpringPath Lane, San Jose, CA, USA
Website: http://www.vicareplus.com
Email: services@vicareplus.com
Meaningful Use Requirements
Permit authorized users (who are authorized for emergency situations) to access electronic health information during an emergency.
Emergency Login
The individual facility can describe the guidelines for an emergency situation. An emergency access solution should be used only when normal processes are insufficient (e.g. the helpdesk or system administrator is unavailable).
Technical Requirements
1. "Emergency Login" acl creation will handled in two ways
1. During installation
2. Use acl_upgrade.php
2. When the Emergency Login policy is chosen while user creation, a message "Emergency Login ACL is chosen. The user is still in active state, please de-activate the user and activate the same when required during emergency situations. Visit Administration->Users for activation or de-activation." is display and request users to disable the Emergency user account. The usernames should be of the format "breakglassxxx" or "emergencyxxx"
3. When the Emergency Login account is activated (during emergency situation), an automatic mail should be sent only if $GLOBALS['Emergency_Login_email'] is set 1 and $GLOBALS['Emergency_Login_id'] is set to mail id.
4. Irrespective of the log level, all activities during emergency access should be logged.
5. After the emergency period, the account should be deleted and the audit trail should take place [Administrative requirements]
Where:
1. Administration -> Users
2. Administration -> ACL -> User Memberships
3. Administration -> ACL -> Advanced -> ARO Group Admin
Status
Completed and checked in to the Sourceforge CVS
Links
- Sourceforge Communication - http://sourceforge.net/projects/openemr/forums/forum/202506/topic/3532189 (second)
- Sourceforge Communication - http://sourceforge.net/projects/openemr/forums/forum/202506/topic/3397800 (first)
- Break Glass/Emergency User Test Report - http://www.openmedsoftware.org/mw/images/b/ba/BreakglassTestReport_Updated_apr17.tar
