Health Information Exchange

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search

HIE Participant Onboarding Resources

This is Your Patient Record. This is an HIE. This is your Patient Record in an HIE.

This webcast provides an overview in how the nationwide health information exchange is being designed and how your patient data will be utilized to provide real-time interoperability and access to key data that will improve the overall safety and quality of health care.

View slide presentation

HIE Participant Onboarding Process and Best Practices

Webcast Slides


Webcast Slides


Do you need to be on a specific EMR to be hooked into the HIE?

Answer: No, our HIE Connection solution is compatible for all EMR types. To date we have implemented practices using 10 different EMR types and are currently in development for three others.

What is the implementation timeline?

Answer: Some of that depends on the EMR type, if it is an EMR type we have already developed we can have your files ready to send in approximately two weeks. If it is an EMR system that we are still developing it takes us about 5 weeks which includes the installation of GalenETL, creating the views, and going through validation.

What steps do we (as an individual practice) have to take in order to grant Galen with the necessary permissions to begin implementing their HIE Solution?

Answer: The setup and access is actually one of the easiest parts of the process and only requires you (as the practice) to take one action, which is to set up Securelink. That install process takes no more than 10 mins, we validate the credentials and then you are done and we run with it from there.

How do you handle provider environments where the EHR is hosted and cloud based and the server environment includes multiple provider organizations and not all will submit data to the same HIE?

Answer: There is not currently a solution for practices which have their clinical data hosted in the cloud. We are currently exploring options to have an HL7 interface sent from the EMR to a local server, which would allow extraction. This is in the early discussion and discovery phase however.

Aren't HIEs set up to be able to accept CCDs from various EMRs? What is better about this solution??

Answer: HIEs are setup to accept CCD/CCDA as well as HL7, but they have to work with each vendor individually and in many case practice by practice to setup an interface to receive this data into the HIE. Our solution has the ability to deliver CCDA and HL7 from various EMR (20+) and gives the HIE a single source vendor to work with. Rather than having to work with 20 different vendors and getting data 20 different ways we are delivering a consistent feed to the HIE regardless of which source system the data is coming from. This enables many gain efficiencies and allows for a lower cost interface and rapid deployment.

Typically EMR vendors charge for interface to HIE. How is your solution different??

Answer: We charge the HIE per connection and the typical cost is more than half of the costs from the vendors.