FHIR Converter
An open-source utility that converts healthcare data between legacy formats (HL7v2, C-CDA, JSON) and FHIR using Liquid templates.
What is FHIR Converter?
FHIR Converter is an open-source tool developed by Microsoft that transforms healthcare data from legacy formats like HL7v2, C-CDA, and JSON into the FHIR standard. It solves the interoperability challenge by enabling health systems to modernize their data for use with FHIR-based applications, APIs, and services. The conversion is driven by customizable Liquid templates, providing flexibility to adapt to various data structures and requirements.
Healthcare IT developers, system integrators, and data engineers working on interoperability projects, EHR migrations, or FHIR-based application development. It is also suitable for organizations needing to convert legacy clinical data for analytics, reporting, or integration with modern health platforms.
Developers choose FHIR Converter for its template-driven approach, which offers greater control and customization compared to fixed conversion tools. Its support for multiple formats, containerized deployment, and Azure integration makes it a scalable and enterprise-ready solution for FHIR data transformation.
Overview
Conversion utility to translate legacy data formats into FHIR
Use Cases
Best For
- Migrating legacy HL7v2 messages to FHIR for EHR integration
- Converting C-CDA clinical documents to FHIR resources for patient data exchange
- Transforming custom JSON health data into standardized FHIR formats
- Upgrading FHIR STU3 resources to R4 for compliance with newer specifications
- Building interoperable health data pipelines with customizable mapping rules
- Self-hosting a conversion service for on-premises or cloud deployment
Not Ideal For
- Projects requiring FHIR to HL7v2 conversion in production (currently in preview)
- Organizations not using Azure for template storage or deployment
- Teams converting HL7v2 messages from versions other than 2.8 without template modifications
- Simple, out-of-the-box conversions without custom mapping logic
Pros & Cons
Pros
Supports conversions between HL7v2, C-CDA, JSON, and FHIR (including STU3 to R4), with a preview for FHIR to HL7v2, enabling versatile healthcare data transformations as highlighted in the Key Features.
Uses the Liquid templating language with custom filters, allowing users to create or modify templates for specific conversion needs, as emphasized in the Philosophy and Templates section.
Offers REST APIs via a Docker container, deployable on platforms like Azure Container Apps, facilitating scalable and portable deployment, as described in the Architecture section.
Includes post-processing validation steps to ensure output conforms to FHIR standards, improving data quality and interoperability, as noted in the Key Features.
Cons
Tight integration with Azure Storage and deployment platforms complicates use in non-Azure or multi-cloud environments, adding vendor lock-in concerns, as seen in the Template Store Integration and deployment guides.
Requires knowledge of Liquid templating and custom filters, with pre-built templates based only on HL7 v2.8, making other versions or custom formats challenging without manual modifications, as admitted in the Templates & Authoring section.
FHIR to HL7v2 conversion is marked as preview, indicating it may be unstable or incomplete, limiting its reliability for production use in bidirectional conversions.
Frequently Asked Questions
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.