Difference between revisions of "HIE Participant Onboarding Process and Best Practices"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
Line 7: Line 7:
  
 
''Answer:'' Yes, we use HL7Spy to anonymize data.  Open your HL7 files in HL7Spy.  Once you have your messages in context, navigate to the 'View' dropdown and select the option 'Custom Code'.  A Custom Codes workspace will populate.  Navigate to the option 'Anonymize Messages', and click run.
 
''Answer:'' Yes, we use HL7Spy to anonymize data.  Open your HL7 files in HL7Spy.  Once you have your messages in context, navigate to the 'View' dropdown and select the option 'Custom Code'.  A Custom Codes workspace will populate.  Navigate to the option 'Anonymize Messages', and click run.
 +
 +
'''Do you see FHIR replacing ITI transactions?'''
 +
 +
''Answer''I have yet to work on a FHIR implementation but I remember a conference from a few years ago someone of the HL7 board said that FHIR does not actually solve any new interoperability use cases.  I’m of the mindset that if it’s not broken then don’t fix it, XDS.b has pretty well defined standards and is widely adopted today so I don’t see FHIR replacing ITI transactions anytime soon.  I think what most environments will look like in the next 5 years or so will be a hybrid setup that utilizes HL7, XML based transactions, and FHIR.

Revision as of 17:43, 12 September 2016

Webcast Slides

Questions

You mentioned that Production level data is best for testing, are you anonymizing data somehow?

Answer: Yes, we use HL7Spy to anonymize data. Open your HL7 files in HL7Spy. Once you have your messages in context, navigate to the 'View' dropdown and select the option 'Custom Code'. A Custom Codes workspace will populate. Navigate to the option 'Anonymize Messages', and click run.

Do you see FHIR replacing ITI transactions?

AnswerI have yet to work on a FHIR implementation but I remember a conference from a few years ago someone of the HL7 board said that FHIR does not actually solve any new interoperability use cases. I’m of the mindset that if it’s not broken then don’t fix it, XDS.b has pretty well defined standards and is widely adopted today so I don’t see FHIR replacing ITI transactions anytime soon. I think what most environments will look like in the next 5 years or so will be a hybrid setup that utilizes HL7, XML based transactions, and FHIR.