...
Once the user clicks the "Epic Queue" button, there are 3 tabs on the page displayed: Current, Past, and Protocol Update tabs.
Figure 5 shows the "Current" tab, where the current queued protocols are listed and waiting to be pushed to Epic. These queued protocols can be pushed or deleted from the queue, and there are URLs linking back to the individual protocols.
Figure 5
When adding
...
or editing
...
authorized users on studies chosen to be pushed to Epic, there is an
...
"Epic EMR Access
...
" choice that authorizes whether a user
...
should have access to
...
Epic (Figure 6). This field is interfaced with Epic real-time, and only allows the choice of "Yes" when the user has a valid EMP record in Epic.
Figure 6
- When user rights have been changed for protocols that have already been pushed to Epic successfullly
Figure 7
Previously pushed protocols are listed in the "Past" tab, showing the detailed information about the previous Epic pushes that happened to the protocols, such as PI, last queued date, status, source of the push, and by whom.
There are three types of Epic pushes: Overlord Push, Protocol Update and Admin Push. The Overlord Push is push from the Epic Queue page, Admin Push are the ones done from SPARCDashboard Admin Edit section, and Protocol Update are the automatic protocol information update pushes triggered by user updates (Figure 8).
Figure 8
On
...
the "Past" tab, users can also attach notes to a Epic push with corresponding information if desired (Figure 9).
Figure 9
Technical Specs.
- Format: Health Level Seven (HL7) messaging, based on an XML encoding synt
- Protocol: Simple Object Access Protocol (SOAP)
- The API can be used for other Electronic Health Record (EHR) Systems as a template
- For more details, please check the links below to the GitHub codes and the screenshot:
...