A Pragmatic AE-EHR Audit Environment
Business Need/Problem Statement
Some of our clients have recently expressed the desire for a limited, read-only view in to the AE-EHR to extend access to audit entities. For instance, the requirements of one organization included a limited patient-access read-only environment to be in compliance with FDA Research Part 11 restrictions for clinical trials. Another organization needed it for insurance audit purposes. And still again, others desired to provide an extended environment to allow hospitalists, ED physicians, and critical care physicians access to selective patient charts.
Approach
One of the more popular approaches has been to segment out a separate read-only organization in the Allscripts Enterprise Electronic Health Record (AE-EHR). The AE-EHR handles organizations quite nicely and facilitates an approach of segmenting out entities – the following Galen Wiki article covers a scripted means of deploying a new organization in v10 AE-EHR.
Once the organization has been created, patients can then be “bulk-loaded” to the organization via SQL scripts. New AE-EHR users can then be created and associated to this organization. Finally, to setup the read-only portion, security gates can be implemented.
Extendability
An additional requirement of one of our clients included an approach that offered the capability to dynamically add/remove patients to the “Audit” organization real-time. We facilitated this via creation of a file-based interface from ConnectR to the AE-EHR. The interface accepted its input from a well defined flat-file (comma-delimited, including MRN, Action – Add or Remove, and OrganizationID) and utilized that data to add/remove patients to the org via a custom stored procedures – the de facto application programming interface (API) to the AE-EHR clinical database.
And still further, another client requested that the audit/read-only entities (users of the system) be granted the ability to create tasks . For example, the client desired a specific, high priority task, identifiable as originating from the audit/read-only entity – in this case hospitalists which could be assigned to the patient’s PCP. In this case, the clients’ hospitalists could communicate high priority continuity of care tasks, which require prompt reaction, to the PCP at discharge. However, the PCPs should not be able to task back to the hospitalists, and this can be achieved by setting the EnableOrgFilterFlag preference in the AE-EHR.
If your organization needs assistance in setting up a audit environment to provide limited, read-only access to the AE-EHR, please contact sales@galenhealthcare.com and visit our website for more information regarding our technical and professional service offerings.
