FHIR Document to C-CDA Conversion

[Sumathi Reddy]

I am trying to Generate C-CDA Document using HAPI-FHIR but I could not find any references or APIs. I searched in GitHub other projects, I found few examples to convert C-CDA to FHIR Document but not FHIR to C-CDA. 

I am wondering whether HAPI- FHIR has any implementation to convert FHIR Document to C-CDA. if yes, can anyone  please provide me references or guide me how to Generate C-CDA with HAPI-FHIR APIs.

[aditya.j...@gmail.com]

Hi Sumanthi,

You can use HAPI FHIR API to parse FHIR resources and get the data into Java objects. Same way, can use MDHT java library to generate CCDA-CCD. Set data from FHIR resources to CCD elements. 

Here you have to do the mappings by yourself (FHIR resource elements to CCD elements like recordTarget.patientRole.patient.name.given would map to Patient.name.given). 

The same mechanism can be used to convert V2 to FHIR or vice versa or CCD TO FHIR. 

For FHIR to CCD, you will need multiple FHIR resources in order to build CCD Header and Body (with multiple sections where 5 of them are mandatory sections).

Regards,

Aditya Joshi

[arunku...@kctechservices.com]

Hi,

Node JS sample

https://github.com/amida-tech/fhir2ccda 

https://www.npmjs.com/package/cda-fhir

Java

https://github.com/srdc/cda2fhir

using MDHT library.

Mapping document available.

https://docs.google.com/spreadsheets/d/15Kv6PFyPh91sH1JMYwLH7D2yjh4HOTy5pjETjQNRyaU/edit

Thanks & Regards

Arun VR

[Sumathi Reddy]

Thank you Arun VR.

[julious...@gmail.com]

Hi all, 

Good day, what is C-CDA?

[aditya.j...@gmail.com]

C-CDA stands for Consolidated CDA. It is simply Implementation Guide based on CDA standard. 

Problem with CDA is that it is too generic, it can hold any healthcare data. For implementations, we need more constrained document or specification, so that it can be implemented (receiver must know clearly what sender can send). To be practically useful in exchanging a specific kind of clinical document with CDA, it's necessary that the sender and the receiver of the CDA document agree to use a relatively narrow subset of everything that CDA offers. In addition, the sender and receiver must establish a more detailed alignment regarding additional semantics (beyond the base semantics provided by CDA), of what is going to conveyed in the documents they exchange.

CCDA is made up of such 9 different constrained documents. The most common is CCD (continuity of Care Document). 

One simple example to understand difference between CDA and CCD-

CCD can only have 15 sections (15 different type of clinical data like results, medication, family history, problem etc.) but CDA XML can hold any sections (there are hundreds of such sections defined, each defined and determined by section LOINC codes). 

you can say that CCD is kind of sub set of CDA. In constraining, CCD also put conditions on which element must be present and cardinality of elements. Whereas CDA would have mostly everything optional. 

You can download CCDA spec from HL7.org:

http://www.hl7.org/implement/standards/product_brief.cfm?product_id=258

HL7 Implementation Guides for CDA Release 2: IHE Health Story Consolidation, DSTU Release 1.1 - US RealmExpiration Sep 2017

(Download) (7.10 MB)

Regards,

Aditya Joshi

HL7 SME & Trainer

[Hassan Saeed]

Hi Arun , 

Is there any updated mapping that supports R4 and US Core 3.1.1 

The repository has also been archived in 2022 . 

Please help if you can , 

Regards , 

Hassan