Many Healthcare Payer and Providers have been using BizTalk Server for both HIPAA and HL7 messaging

Healthcare Payers are being mandated to achieve Interoperability with HL7 FHIR by CMS. In addition they need to be able to provide healthcare records to their Subscribers. CMS has established the claims data for Personal Health Records(PHR) Blue Button project for this.

More information can be found here

Other initiatives are Other initiatives are

Durable Medical Equipment Electronic Order Project Durable Medical Equipment Electronic Order Project

The Centers for Medicare & Medicaid Services (CMS) has initiated the Durable Medical Equipment Electronic Order (DME eRx) project to support the CMS Promoting Interoperability initiatives. This project will define exchange methods, use of other interoperability standards and specific uses of Fast Healthcare Interoperability Resources (FHIR) to effectively exchange orders for Durable Medical Equipment (DME) and associated supplies, medications, and supporting clinical information (to qualify the order or establish medical necessity) between the ordering provider and the intended supplier.

Electronic Medical Documentation Interoperability (EMDI)

Electronic Medical Documentation Interoperability (EMDI) Program Guides and Pilots The Centers for Medicare & Medicaid Services (CMS) EMDI Initiative develops use cases, pilot protocols, implementation guides, and other documents identifying necessary standards and specifications based upon business scenarios and system functional requirements. The primary goal of the EMDI Initiative is to reduce provider burden through effective piloting and implementation of nationally recognized health IT standards. The EMDI Initiative includes voluntary participation by healthcare providers to adopt Health IT standards and develop pilot activities. EMDI Guides

CMS Advances MyHealthEData with New Pilot to Support Clinicians

Pilot program gives clinicians direct access to claims data, putting patients over paperwork and at the center of their care


They keyword is Interoperability In order to comply everyone must be able to speak the same language They must be able to understand each other; both machine readable and human readable.

Now that you know what is required, let’s take a look at how it can be implemented using Microsoft BizTalk Server. Assuming that you have been using BizTalk for HIPAA and/or HL7 processing.


The first tutorial will be based upon a POC I did for a Payer. You can view it it here

Use Case 1

The first Use Case is to be able to receive a HL7 FHIR Bundle

  1. Validate the Resources
  2. Transform the Resources
  3. Persist the Resources to a Repository
  4. Query the Resources

I have already started integrating the HL7 FHIR XML Resources as schemas. I only needed to make a few modifications to the schemas compared to what we did over six years ago.

Business Case

  • You will,be learning that BizTalk can be used with the Azure open source HL7 FHIR Server
  • If you are currently using BizTalk, it would eliminate the need to purchase or build a separate FHIR Server.

You will be able to send and receive any message type that contains healthcare data,

This includes HL7 V. 2.x, 3.0. CCD, Dicom, HIPAA, Medical Device output, PDF, Office 365 documents, binary attachments and transform them to and from HL7 FHIR Resources.

Using the BizTalk 2020 REST Adapter to communicate with the Open Source HL7 FHIR Sever.

In Part 2, we will continue with our first use case.

Last modified: March 21, 2020



Leave a Reply