Convert HL7v2 & CCDA Data to FHIR
The 1upHealth Data Ingestion service is a robust service that converts data from other formats to FHIR®. If your data is currently in HL7v2 format or CCDA format, 1upHealth can transform your data into a FHIR-compatible format to enable the 1upHealth FHIR Server to consume it.
Before we ingest your data, we complete two validation phases. The first validation phase occurs when we transform your data into FHIR. After the data is transformed, we again validate that the conversion was successful, before we ingest the data to the 1up FHIR Server.
Limitations
Because your data file is not already in a FHIR data format, we can’t guarantee that all of the data in your file will be converted to FHIR.
We use the sample files that you provide to create a mapping template (data contract) of your data that will apply to the majority of your data. If your data format changes, it can cause your data to not be correctly converted. Make sure to contact your Customer Support Manager or Implementation Manager to provide us with your updated data files so we can update your mapping template.
If there are errors mapping your data, and there haven’t been any discernible changes in your data that would affect the mapping, you can review your data file and resolve any invalid or missing fields. After the issues are resolved, we can retry the conversion and ingestion process.
HL7v2 to FHIR Conversion
To convert your HL7v2 data to FHIR, we first convert your HL7v2 data to JSON and then convert the JSON to FHIR bundles, which are validated to determine which data can be ingested by the 1up FHIR Server. The 1upHealth Implementation team uses mapping templates to translate your HL7v2 data to FHIR. After the data is mapped and validated, the validation processor creates a validation report that specifies the resources that weren’t processed because of issues with the data.
The data conversion process includes the following steps.
-
You upload your HL7v2 data file to the 1upHealth Implementation team over SFTP.
-
1upHealth’s Implementation team creates templates to map your data to the FHIR format.
-
The 1up conversion service converts your HL7v2 data file to JSON.
-
The 1up conversion service converts the JSON to FHIR bundles, which include all of your resources.
-
1up validates that your data was transformed correctly.
Any data that fails validation is specified in the validation report (CSV).
-
Your converted data is ingested into the 1up Platform.
1up validates the structure of your FHIR bundles during ingestion.
If any of your data fails validation, you can review the validation report to find the data that failed and identify any problems with your data. You can then correct any errors and resubmit the data to 1up for conversion.
CCDA to FHIR Conversion
To convert your CCDA data to FHIR, we first analyze your sample files and create data contracts based on your data. We then apply those data contracts to the CCDA processor and validator, which converts your data to FHIR and generates a validation report of any data that failed validation and conversion.
The data conversion process includes the following steps.
-
You upload your CCDA data files to the 1upHealth Implementation team over SFTP.
-
1upHealth analyzes your sample XML files to determine what data is available and creates a data contract (mapping template).
-
The 1up conversion service processes your CCDA files using the data contract and converts them to FHIR.
-
1up validates that your data was transformed correctly.
Any data that fails validation is specified in the validation report (CSV), which is uploaded to the 1upHealth S3 bucket.
-
Your converted data is ingested into the 1up Platform.
1up validates the structure of your FHIR bundles during ingestion.
If any of your data fails validation, you can review the validation report to find the data with issues and identify any problems with your data. You can then correct any errors and resubmit the data to 1up for conversion.