Recent posts:
Recent replies:

The soon to be released HealthShare Message Transformation Service running on AWS takes HL7v2 messages placed in a folder of an AWS S3 bucket, and converts the messages to FHIR in an output bucket of your choosing or AWS HealthLake. In the future, we may have an adapter to consume HL7v2 messages directly from a business operation. 

The soon to be released HealthShare Message Transformation Service running on AWS takes HL7v2 messages placed in a folder of an AWS S3 bucket, and converts the messages to FHIR in an output bucket of your choosing or AWS HealthLake. In the future, we may have an adapter to consume HL7v2 messages directly from a business operation. 

Muhammad,

 

The principal difference is the healthcare interoperability features engineered into IRIS for Health, which are not relevant to other users of IRIS. These features include a full FHIR (Fast Healthcare Interoperability Resources) server, and the ability to receive, transform, and route HL7v2 messages, which are widely used by healthcare providers. There are also other interoperability features in IRIS for Health such as handling different IHE profiles (Integrating the Healthcare Enterprise),  which help healthcare professionals share information.

 

There are additional healthcare specific interoperability protocols, to learn more visit:

https://www.intersystems.com/resources/detail/intersystems-iris-for-health-technology-brief/

 

 

If you have a specific question about IRIS for Health, please reach out to me.

 

 

Open Exchange applications:
Followers:
Following:
Patrick has not followed anybody yet.
Global Masters badges: