Processing HL7 and FHIR in the Cloud

This Tutorial is now deprecated. This video replaces it.
• Introduction to proces...
In this tutorial, we step you through getting Integration Host running under your Azure account allowing processing of HL7 or FHIR in the cloud.
The package file is available for download at: hl7soup.com/integrationhostcl...

[@sravankumar-zg3tv]

Could you explain how can we post hl7 message to a rest api via postman and parse the results in the backend? this question was initially asked and redirected from HealthcareIT channel

[@Hl7soup]

Hi Sravan. If you create an HTTP receiver like we did in this video then you can receive HL7 Messages. Once the message is received, Integration Host workflow can parse the message, and either convert it to another message type or store the values in your database. Take a look at our Getting Started tutorials for integration host to get the basics of processing a message. You can test the message via a sender Hl7 Soup as we did in this video. I'm not a Postman user for this purpose sorry.

[@prateekagarwal6493]

Hi Jason,
Could you please tell which field in HL7 message is considered as Date of Service (DoS)

[@Hl7soup]

Hi Prateek. I assume that would be the MSH-7 as that is the date the action was performed.
Cheers, Jason

[@prateekagarwal6493]

@@Hl7soup
Lol,you have increased my confusion. I have seen some systems using Date of Service from PV1-44 or PID-33. I'm really confused. Please help.

[@Hl7soup]

@@prateekagarwal6493 I'm not really sure that I understand the question sorry. PV1-44 is the visit admit date, while PID-33 is the last update date for the patient details. You can spot these in the HL7 Soup editor.

[@prateekagarwal6493]

@@Hl7soup
Yes,as per standards you are right. My question is: is it possible to consider PV1- 44 as Date of Service?

[@Hl7soup]

@@prateekagarwal6493 Yeah, it is the date the patient went and visited the hospital.