This is my first blog post about our FHIR (Fast Healthcare Interoperability Resources) development. In this post, I would like to share with you the toolsets that we developed to help promoting the FHIR to the healthcare community.
Three years ago, I learned FHIR via a Coursera course (www.coursera.org), instructed by Mark Braunstein, MD at Georgia Institute of Technology. Since then, I have been convinced that FHIR specification provides better support of electronic health record (EHR), such as allergies, medications, conditions, immunizations, and lab results. As a result, FHIR is a better approach to facilitate interoperation between various healthcare systems.
Since the legacy HL7 have been used for more than a decade for patient information (ADT), observation results (ORU), etc., there will be a need to convert those existing HL7 data to the FHIR specification. My company, Redix International, Inc, (www.redix.com), has been in the HIPAA business for more than 20 years. Two years ago, I decided to modify our flagship product, Redix AnyToAny Format Converter Engine, and our HL7 module to support the conversions between HL7 2.x and FHIR. As a result, we have developed a toolset that converts HL7 2.x (including 2.3, 2.4, 2.5, and CDA) to FHIR STU3. The HL7 2.3, 2.4, and 2.5 messages that we supported are ADT, ORU, MFN, PPP, REF, SIU, and VXU.
You can test the conversions by going to:
| Conversion Type | URL |
| HL7 2.3, 2.4, 2.5 to FHIR | https://www.redixhipaa.com/HL7/mapping |
| HL7 CDA to FHIR | https://www.redixhipaa.com/HL7/CCDA |
Once you are in the above web-page (see below), you can select an HL7 file from your system and the file will be automatically converted to FHIR STU3 specification, providing the file is a legit HL7 file.
Feel free to use the tools and please let us know if there is anything that we can do to improve the tools. Feel free to reach out or connect with me at @redixfhir.
In the future, I will elaborate more on the conversion tools and our future developments in FHIR.
