Does Salesforce Do HL7 or X12 Integration?

Recently during a webinar (recording available), I was asked if Salesforce.com can integrate with/via HL7.  

The answer is yes.

But naturally, there are caveats…

Salesforce.com supports integration via several different application programming interfaces (APIs), and, in particular, via SOAP and REST.  Salesforce.com is one of the easiest applications/platforms to integrate with because of these open standards - more details are available on the Salesforce.com website.

However, Salesforce.com does not natively support HL7 version 2.X (or, for that matter, X12/EDI) delimited messaging. In other words, it won't be ready to interface via HL7 right out of the box.

Instead, you need to integrate via some “middleware” (software that sits between systems to mediate their connectivity and data formats) to convert the HL7 format to SOAP or REST, XML or JSON.  Middleware comes in many varieties:

• HL7-focused “interface engines” like Orion Rhapsody, iNTERFACEWARE Iguana, Mirth Connect, etc
• Heavy-duty SOA (service oriented architecture) ESBs (enterprise service buses) like IBM Integration Bus
• iPaaS / Cloud Integration Services like JitterBit

Is this need for middleware a bad thing?  No, and here’s why:  

1. If you’re working with multiple systems / endpoints, integrating through middleware provides centralized control, logging, and monitoring/alerting.  Middleware facilitates aggregating and intelligently routing and filtering data between systems.  There are lots of benefits to avoiding “point-to-point integration,” so you probably should already be using middleware of some sort.
2. Most providers (at least larger providers) and payors already have some form of middleware in place - there is rarely something new to buy or learn.
3. Almost all (but NOT all) middleware that supports HL7 (or X12) is also going to support XML or JSON data formats and SOAP/REST based integration.

Conclusions:

1. It’s really easy to integrate with Salesforce.com.
2. If you’re going to integrate Salesforce.com and HL7 or X12, you’re going to need some mechanism to translate the data and switch transport mechanisms - that’s what the “middleware” is for.
3. Assess your particular HL7/X12 + Salesforce.com integration requirements and ensure the middleware you are considering meets your needs; if you need help, contact us.
4. As always - before integrating PHI (protected health information), ensure your endpoints, as configured, meet your specific BAA (business associate agreement) requirements as well as what is mandated by HIPAA!

Read more about our healthcare solutions:

• Is Salesforce HIPAA Compliant?
• 4 Step Strategy for Engaging Today's Healthcare Customer
• Maximizing the Capabilities of Health Cloud
• I'm the Patient, Remember Me?
• Interoperability & Quality Process Supporting EHRs
• 5 Steps to an Effective Data Governance Plan

Connect with us for a complimentary 1:1 call with our healthcare expert.