The NCCoE’s first use case within the Secure Exchange of Electronic Health Information Demonstration Project focuses on securely exchanging information through the use of mobile devices. In this use case, a hypothetical independent primary care physician is using her mobile device to perform a variety of reoccurring activities such as:
• Sending a referral (e.g., clinical information to another physician)
• Sending an electronic prescription
• Receiving a lab result
• Sending a patient lab results and instructions to see a specialist
• Checking a patient into a hospital under Dr. Smith’s care
• Sending or receiving consultation information
• Requesting that a hospital discharge a patient
• Viewing hospitalized patients’ charts
• Ordering an imaging test
At least one mobile device is used in every transaction, each of which interacts with a certified electronic health record (EHR). When a physician uses a mobile device to push clinical information to an EHR, it allows another physician to access the clinical information through a mobile device as well.
Architecture
The high-level abstract architecture involves a four-step information transfer process:
1. Physician uses a mobile device application to send a referral to another physician
2. Application sends the referral to a server running a certified EHR application
3. Server routes the referral to the referred physician
4. Referred physician uses mobile device to receive the referral
Components
As we consider how a physician makes use of electronic health records, we are taking into account the following components on:
Mobile devices
• Mobile device*
• Mobile device management client*
• Intrusion detection system (IDS)*
• Firewall software*
• Provisioning system for mobile devices client*
• Healthcare mobile device application*
• Storage encryption*
• Antivirus*
Networks
• WiFi*
• Cellular
• Bluetooth
The back end
• Certified electronic health record system*
• Storage encryption*
• Antivirus*
• Intrusion detection system (IDS)*
• Provisioning system for mobile devices server*
• Mobile device management server*
• Auditing mobile device*
• Mobile device identity management*
• Web server
• Email server
• Session initiation protocol (SIP) server
• LDAP
• Active directory
• Policy manager
A secure infrastructure
• Firewall*
• VPN Gateway*
• Authentication, authorization, and accounting (AAA) server*
• CA and Enrollment*
• Switches
* required security component
How to Participate
If you are interested in participating in this project, please contact us.