Difference between revisions of "HIE Connect"
Matt.Leyva (talk | contribs) |
Matt.Leyva (talk | contribs) |
||
| Line 6: | Line 6: | ||
'''Do you need to be on a specific EMR to be hooked into the HIE?''' | '''Do you need to be on a specific EMR to be hooked into the HIE?''' | ||
| − | ''Answer:'' | + | ''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?''' | '''What is the implementation timeline?''' | ||
| − | ''Answer:'' | + | ''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?''' | '''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:'' | + | ''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?''' | '''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:'' | + | ''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??''' | ''' Aren't HIEs set up to be able to accept CCDs from various EMRs? What is better about this solution??''' | ||
Revision as of 19:47, 15 October 2015
Webcast Slides
- Slides Presented 10/7/15
Questions
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: I will post the answer to this shortly.
Typically EMR vendors charge for interface to HIE. How is your solution different??
Answer: I will post the answer to this shortly.