CCDA & HL7v2 to FHIR Validation Reports

When you send your data to 1upHealth for conversion to FHIR and ingestion into the 1up FHIR Server, we complete two validation phases and generate two reports. At the end of the first validation phase, which occurs when we transform your data into FHIR, we generate the first report: the Ingestion Report.

The Ingestion Report includes information about errors in your data that prohibits its conversion to FHIR format. This is a separate report from the FHIR Validation Report, which is generated after your data is converted to FHIR format. The Ingestion Report is a file in CSV format, which includes a list of the data that couldn’t be converted to FHIR resources because of missing elements or data that didn’t match your data contract elements.

After the ingestion process has completed, this report is uploaded to your Amazon S3 bucket so you can review it and make any necessary changes to your data before you submit it for ingestion again. Ingestion reports cannot be customized.

The Ingestion Validation report only includes errors from the data validator, which only shows problems in the data that you submitted for ingestion and conversion to FHIR. Each error includes the location of the error in the submitted data and the name of the data file. One report is generated for each file (CCDA) or message (HL7v2) that is submitted for ingestion. The schema of these reports includes the error, the location of the error (path), the resource type, and the source file name.

To review an ingestion report, you can retrieve it from your S3 bucket and open the CSV file in any application that supports CSV-formatted files.

Example CCDA-to-FHIR CSV File

Error

Path

Source Name

The node '@extension' does not exist at the expected path

/ClinicalDocument[1]/component[1]/structuredBody[1]/component[1]/section[1]/entry[1]/act[1]/entryRelationship[1]/observation[1]/id[1]

resources/ccda170.315_b1_toc_inp_ccd_r21_sample1_v5.xml

The node '@extension' does not exist at the expected path

/ClinicalDocument[1]/component[1]/structuredBody[1]/component[1]/section[1]/entry[1]/act[1]/entryRelationship[1]/observation[1]/entryRelationship[1]/observation[1]/id[1]

resources/ccda170.315_b1_toc_inp_ccd_r21_sample1_v5.xml

The node '@extension' does not exist at the expected path

/ClinicalDocument[1]/component[1]/structuredBody[1]/component[1]/section[1]/entry[2]/act[1]/entryRelationship[1]/observation[1]/id[1]

resources/ccda170.315_b1_toc_inp_ccd_r21_sample1_v5.xml

The node '@extension' does not exist at the expected path

/ClinicalDocument[1]/component[1]/structuredBody[1]/component[1]/section[1]/entry[2]/act[1]/entryRelationship[1]/observation[1]/entryRelationship[1]/observation[1]/id[1]

resources/ccda170.315_b1_toc_inp_ccd_r21_sample1_v5.xml

The node '@extension' does not exist at the expected path

/ClinicalDocument[1]/component[1]/structuredBody[1]/component[4]/section[1]/entry[1]/act[1]/entryRelationship[1]/observation[1]/id[1]

resources/ccda170.315_b1_toc_inp_ccd_r21_sample1_v5.xml

The node '@extension' does not exist at the expected path

/ClinicalDocument[1]/component[1]/structuredBody[1]/component[4]/section[1]/entry[2]/act[1]/entryRelationship[1]/observation[1]/id[1]

resources/ccda170.315_b1_toc_inp_ccd_r21_sample1_v5.xml

The node '@extension' does not exist at the expected path

/ClinicalDocument[1]/component[1]/structuredBody[1]/component[4]/section[1]/entry[3]/act[1]/entryRelationship[1]/observation[1]/id[1]

resources/ccda170.315_b1_toc_inp_ccd_r21_sample1_v5.xml

The node '@extension' does not exist at the expected path

/ClinicalDocument[1]/component[1]/structuredBody[1]/component[4]/section[1]/entry[4]/act[1]/entryRelationship[1]/observation[1]/id[1]

resources/ccda170.315_b1_toc_inp_ccd_r21_sample1_v5.xml

The node '@extension' does not exist at the expected path

/ClinicalDocument[1]/component[1]/structuredBody[1]/component[4]/section[1]/entry[5]/act[1]/entryRelationship[1]/observation[1]/id[1]

resources/ccda170.315_b1_toc_inp_ccd_r21_sample1_v5.xml

The node '@extension' does not exist at the expected path

/ClinicalDocument[1]/component[1]/structuredBody[1]/component[4]/section[1]/entry[6]/act[1]/entryRelationship[1]/observation[1]/id[1]

resources/ccda170.315_b1_toc_inp_ccd_r21_sample1_v5.xml

The node '@extension' does not exist at the expected path

/ClinicalDocument[1]/component[1]/structuredBody[1]/component[5]/section[1]/entry[1]/encounter[1]/entryRelationship[1]/act[1]/entryRelationship[1]/observation[1]/id[1]

resources/ccda170.315_b1_toc_inp_ccd_r21_sample1_v5.xml

The node '@extension' does not exist at the expected path

/ClinicalDocument[1]/component[1]/structuredBody[1]/component[6]/section[1]/entry[1]/act[1]/entryRelationship[1]/observation[1]/id[1]

resources/ccda170.315_b1_toc_inp_ccd_r21_sample1_v5.xml

In this example CCDA-to-FHIR Ingestion Report, the Error column indicates that the specified source file (Source Name) is missing the expected @extension at the point indicated by the Path field. To resolve this error, you can correct the errors indicated by the report and then send your CCDA file again.

Example HL7v2-to-FHIR CSV File

HL7v2 Field

Control ID

Message

Filename

Resource

IN1.3.1

EPIC-FTZ-3347000.361842841

The IN1.3.1 field is empty.

981f4e21-3e5c-47cd-895c-2ab0e2f8280b

Coverage

IN1.3.1

EPIC-FTZ-3347000.361842841

The IN1.3.1 field is empty.

981f4e21-3e5c-47cd-895c-2ab0e2f8280b

Coverage

In this example HL7V2-to-FHIR Ingestion Report, the Message indicates that the IN.1.3.1 field is empty, which means that it’s missing data. To resolve this error, you can send your data again with the correct values included in the IN1.3.1 field.