HL7 Continuity of Care Document Quick Start Guide

[...] additional information on getting started with CCD, please read the post on the quick start guide provided by [...]

[...] implementing CCD will be readily compatible with new technology, while simultaneously opening the doors to greater [...]

Can you send me a example xml of HITSP Summary Documents Using HL7 Continuity of Care Document (CCD) Component

The link above to the “Quick Start Guide” seems to be misdirected.

Dan

Thanks, Dan. It looks like they changed their URL. It has been updated.

Is there interoperability between HL7 V2 messages and CCD(CDA)?

Thank you for your question. We checked with one of our integration specialists and have the following response:

The short answer is “yes” with the long answer being “it depends.”

There are different levels of CDA/CCD documents. It probably would be possible to create a Level-1 CDA document from an HL7 v2 message, assuming you had a fairly robust HL7 v2 report of some flavor (MDM or ORU type of message most likely).

It would be harder to take an HL7 v2 message and convert it into a Level-2 or Level-3 CDA document. More data is required in those formats, and that data needs to be structured, not just free form text.

The CDA is based on the HL7 v3 RIM, and compliant CDA documents will follow that data model. Mapping from one data model to another can be challenging.

All CDA documents need to have a responsible party or person who ‘signs’ the document. At a minimum, the HL7 v2 message would have to have this information.

Converting a CDA document into an HL7 v2 message is possible, but you run the risk of losing the ‘context’ of the data that is in the original document if it is a highly structured Level-2 or Level-3 document. If the CDA contains nothing more than a textual report and some patient demographic information, then it can be converted into a comparable v2 message.

Hi All,

Is there any way to validate the CCD document ?

Thanks,
Prakash