A Practical Guide to Understanding HIE, Assessing Your Readiness and Selecting HIE Options in Minnesota
Plan and Select: Understanding HIE Options in Minnesota
On this page:
Minnesota’s Approach to HIE
More about the State Certification of HIE Service Providers
Do I have to use a State-Certified HIE Service Provider?
What are the State-Certified HIE Service Provider Options in Minnesota?
What other options do I have for exchanging health information?
Another role the Minnesota Department of Health has is to certify HIE Service Providers operating in Minnesota (providing clinical meaningful use HIE transactions or services). The certification process is intended to also promote seamless connections - providers or provider organizations using any of the State-Certified HIE Service Providers could exchange health information because the certification process requires the HIE Service Provider comply with specific requirements such as: ENHAC certification; establish data sharing agreements between the State-Certified HIE Service Providers, and compliance with national standards for exchange. The statewide shared services described above will also support the secure exchange of health information and interoperability between the State-Certified HIE Service Providers.
The intent of the oversight process is so that:
- Fragmentation of health information is prevented and information can follow the patient across the full continuum of care.
- HIE Service Providers properly protect patient privacy and security.
- HIE Service Providers are adhere to nationally recognized standards.
- Minnesota has a reliable health information exchange infrastructure in place to allow Minnesota providers and hospitals to achieve meaningful use incentives and Minnesota’s 2015 mandate for interoperable electronic health records.
- Transparent knowledge of services offered and that the services are in accordance with national standards.
- The ability, over time, to exchange health information with other State-Certified HIE Service Providers, providing greater interoperability statewide.
- The HIE Service Provider has attested its policies and procedures are in compliance with both federal and Minnesota privacy laws, and it has confirmed it has privacy and security policies and procedures in place for protecting PHI (personal health information).
The most important thing you can do is choose an HIE Service Provider, or other type of intermediary, that best suits your needs and matches your HIE priorities.
Health Information Organization (HIO) is a not-for-profit entity that offers a robust set of HIE options
Health Data Intermediary (HDI) is a for-profit entity that may offer a more limited set of HIE options
One of the best ways to learn about the different State-Certified HIE Service Providers is to talk to other provider organizations that are already using them. You can also contact them to request more information and pricing information, visit the current State-Certified HIE Service Providers webpage for contact information.
Both types of HIE Service Providers typically offer nationally recommended services available throughout many parts of the country including:
- Nationwide Health Information Network (NwHIN): A set of standards, services and policies to support the nationwide exchange of health information. These specifications were developed into an open-source software, called CONNECT, that organizations can use to securely link their existing health IT systems into health information exchanges. Many HIE vendors (or HIE service providers) have adapted the CONNECT software for their own needs and offer it as a service that is compatible with the federal specifications for robust HIE.
- Direct secure messaging: Direct secure messaging refers to using a set of protocols, known as the Direct Protocols, to securely push health information to a known receiver. It is commonly described as a type of secure email between two known entities; information is exchanged by way of the actual message or an attachment to the message. This is a more simple form of HIE that is useful for providers who do not yet need the more robust options such as the ability to query for patient records from unknown locations.
The following is an example of how a provider might utilize one type of HIE service provider, an HIO, that offers more robust HIE options such as query.
|HIO Scenario||Patient Arrives at Emergency Room Without Critical Medical Information
A critically injured patient arrives at the emergency room without bringing essential medical information. To locate the information, the provider may send a query (through the HIO they have contracted with for HIE services) to local hospitals, pharmacies and doctors' offices who are also connected to that same HIO. These organizations’ EHRs would identify records belonging to this patient and send information back to the HIO. The HIO may respond to the provider’s initial query with a response noting which other providers in the HIO network have records for this patient, or it may send a response with the aggregated patient medical information. The provider can then review the patient’s information and provide necessary lifesaving treatment.
The following example shows how a provider might utilize another type of HIE service provider, an HDI, that offers Direct secure messaging services, a more simple form of HIE.
|HDI Scenario||Patient Discharged from Hospital and Sent to a Rehabilitation Center
A patient at a hospital is being discharged and sent to a rehabilitation center. The nurse identifies the care center the patient is being sent to, confirms that the care center can receive Direct messages, and compiles a secure message using the Direct protocols (that can be embedded in the hospital’s EHR system) attaching the patient care summary in standardized or PDF format. The rehabilitation center receives the message and incorporates the care summary information into their EHR (or other patient record system).
Print-friendly version of Practical Guide to Understanding HIE (PDF 1.98MB/ 36pg)