Blog

Rhapsody Health Solutions Team

Fun Facts About CCD and Consolidated CDA

As many of our customers know, our user conference Corepoint Connect 12 kicked off today in Plano, Texas. More than 100 of our customers from around the country have gathered to learn about our product and healthcare interoperability, which means there is going to be a lot of talk about HIEs, HL7, CCD, CDA, XML, etc.

Here are some interesting FAQs about CCD and Consolidated CDA that Product Manager Rob Brull and Senior Implementations Engineer Mick Stockemer shared to a full room:

Here are some random, yet interesting facts shared during the presentation:

The 3 Cs of healthcare document standards are: CCR (continuity of care record), CDA (clinical data architecture), and CCD (continuity of care document).

CDA, created by HL7 International, was targeted to cover many different scenarios. 

CCR + CDA = CCD.

HL7 now governs the CCD document.

CCD is just one type of CDA documents. 

CDA documents are exchanged via secure email. CDA documents are also portable by patients; meaning they can physically carry them to the next point of care.

CDA documents can be shared directly btw EMRs via web services or secure email protocols. 

EMRs can send and store CDA documents in an HIE repository.

CDA is used world-wide.

CDA documents must show: persistence, stewardship, potential for authentication, wholeness, human readability, and context. 

CDA documents are human readable and can be displayed on a web browser.

A CDA document is encoded in XML. 

What can be included in a CDA docuement? The same things that are included in a Word document: text, images, sounds, or other multimedia content.

CDA is the document structure for HL7 version 3.

CDA documents can be exchanged electronically the same way HL7 v2 messages can be exchanged – in an integration engine.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
First Name*
Last Name*

Related Blogs

Sameer Sule, Chief Information Security Officer

Rhapsody® Axon Security: What Healthcare CISOs Need to Know 

This FAQ is designed to help security and compliance teams understand how Rhapsody Axon works, what data it touches, and what controls are in place.

Read More >

Read more

Rhapsody Health Solutions Team

How to Reduce EHR Integration Costs Without Compromising Data Quality 

Learn how to reduce EHR integration costs by building scalable architectures that minimize rework, improve data quality, and simplify long-term maintenance.

Read More >

Read more

Rhapsody Health Solutions Team

Beyond the EHR Connect: What Enterprise Electronic Health Record Integration Actually Requires 

Enterprise EHR integration requires more than APIs and HL7. Learn how governance, identity, data quality, and monitoring create scalable healthcare interoperability.

Read More >

Read more