Some of the STU3 resources are renamed or removed from R4. Therefore, instead of "default" templates we provide you with some sample templates that you can use as a starting guide for you to modify and customize.)įHIR STU3 to R4: Name of the root template that is the same as the STU3 resource name e.g., "Patient", "Observation", "Organization". JSON does not have any standardized message types, unlike HL7v2 messages or C-CDA documents.
( These JSON templates are sample templates for use, not default templates that adhere to any pre-defined JSON message types. JSON to FHIR: "Stu3ChargeItem", "ExamplePatient" It accepts the following parameters in the command line: Option The tool converts a folder containing input messages (HL7v2, C-CDA, JSON or FHIR STU3) into FHIR R4 resources. The command line tool is another way of converting data, as well as managing templates. Using Command line tool Supported parameters
After enabling $convert-data in your server, you can make API calls in the form of >/$convert-data to the server to convert your data into FHIR. The $convert-data operation is integrated into Azure Health Data Services, Azure API for FHIR and FHIR server to run as part of the service. It is also available as a command line tool. NOTE: FHIR STU3 to R4 conversion is only available in the open-source FHIR Server as a $convert-data operation. The converter is integrated into both Azure Health Data Services and Azure API for FHIR, as well as in the open-source FHIR Server as a #using-convert-data-in-fhir-server) operation. If needed, you can create a new template, or modify existing templates to meet your specific conversion requirements.įHIR Converter with DotLiquid engine transforms the input data into FHIR bundles that are persisted to a FHIR server. The converter comes with a few ready-to-use templates. The templates are written in Liquid templating language and make use of custom filters. The converter uses templates that define mappings between these different data formats. For the Handlebars converter, please refer to the Handlebars branch.Ĭurrently, FHIR Converter supports four types of conversions, HL7v2 to FHIR, C-CDA to FHIR, JSON to FHIR and FHIR STU3 to R4. ⚠ Rest of this document is about the Liquid converter. $convert-data operation in both Azure Health Data Services and Azure API for FHIR $convert-data operation in FHIR Server for Azure (OSS)ģ. The following table shows the differences between two converter engines:Ģ. We strongly recommend using the Liquid converter for a better alignment with Azure Healthcare APIs, Azure Health Data Services, FHIR Server for Azure, and Microsoft Logic Apps. Net runtime.Ĭurrently, Microsoft supports two types of converter engines, Handlebars engine and Liquid engine, along with templates and filters. A new converter engine was released on that uses Liquid templating language and. It used Handlebars template language and Javascript runtime. The first version of the FHIR Converter released to open source on Mar 6th, 2020.
FHIR Converter is an open source project that enables conversion of health data from legacy formats to FHIR.