What is the Relationship Between the Continuity of Care Record (CCR) and HL7 2.X Messaging?

October 18th, 2006 by Dave Shaver

2 Votes | Average: 4 out of 52 Votes | Average: 4 out of 52 Votes | Average: 4 out of 52 Votes | Average: 4 out of 52 Votes | Average: 4 out of 5 (2 votes, average: 4 out of 5)

Loading ... Loading ...

Posted in CCR, HL7 Standards

In a prior post, I briefly described the CCR. One obvious follow-up question is: What is the relationship between the CCR and the HL7 standards? How does the CCR relate to HL7 2.X?

At a very high level, both the CCR and HL7 are used for moving clinical data. The CCR happens to be using XML tags and HL7 2.X uses an “old school” format known as “encoding rules seven” (ER7). I often call HL7’s format “pipe-and-hat” for its use of vertical bars (|) and caret (^) characters.

The most interesting difference between the two standards is the context in which the standards are used. As noted previously, the CCR was designed to move data between facilities while HL7 grew up moving data within the four walls of hospitals. Thus, the CCR is focused on inter-facility communication while HL7 is focused on the intra-facility messaging.

HL7 2.X is a “triggered” and real time protocol. That is, systems within the hospital want to know where a patient is right now. They want to receive lab results within seconds of them being entered. The pharmacy system needs notification when new prescriptions are written. And so on.

Contrast that with a document like a patient referral or discharge summary. Such a document is a summation of many real time events — a history of illness, a list of current medications, prior lab results, etc. There is little “real time” about a document that summarized prior data.

Clearly you could build a history of a patient’s record by listening to a non-stop stream of HL7 messages. But you would need to piece them all together to make a summary. For example, there would be no single HL7 2.X message that contains all current medications the patient is taking. Instead, there would be a stream of pharmacy orders that each indicate a new or updated prescription.

In summary, the difference between the standards boils down to the facts that HL7 is focused on intra-facilty, real time data movement — what is happening now? — while the CCR is focused on inter-facilty, “summarized” data movement — what happened before now?

Last 5 posts by Dave Shaver
11 Responses to “What is the Relationship Between the Continuity of Care Record (CCR) and HL7 2.X Messaging?”
  1. NeoTool says:

    […] In addition, you may want to read the posting in this blog that answers the question, How are HL7 2.X and CCR related? […]

  2. NeoTool says:

    […] What is the Relationship Between the Continuity of Care Record (CCR) and HL7 2.X Messaging? […]

  3. NeoTool says:

    […] In prior posts I described the Continuity of Care Record (CCR) and the relationship between HL7 2.X and CCR. This article addresses a need to mix the two formats. Specifically, the desire to move a CCR document via HL7. […]

  4. NeoTool says:

    […] As mentioned in previous posts, the Continuity of Care Record (CCR) provides a way to send data between clinics, hospitals, labs, etc that are using various EMR, HIS, RIS, PACS, dictations, etc systems. The CCR is an XML-based standard that is related to and different from the HL7 2.X messaging standard. […]

  5. NeoTool says:

    […] What is the Relationship Between the Continuity of Care Record (CCR) and HL7 2.X Messaging? […]

  6. Sending images or formatted documents via HL7 messaging - NeoTool Healthcare IT Blog says:

    […] In a prior post about how HL7 2.X and the CDA compare, I described that HL7 2.X messages provide a view of data movement “right now.” Typically ADT, scheduling, order, result, and financial data are moved using HL7 2.X. The HL7 CDA standard is typically used to move documents. The catch is that CDA documents are typically marked up lines of ASCII text — XML tags with lots of clinical content rather than a pretty look-and-feel. So, neither standard solves the “moving pretty reports between systems” problem easily. […]

  7. What Is the Continuity of Care Record (CCR)? says:

    […] In addition, you may want to read the posting in this blog that answers the question, How are HL7 2.X and CCR related? […]

  8. Who Uses HL7? says:

    […] You may have read about how HL7 relates to various healthcare IT initiatives like ELINCS, CCR, and HL7 CDA. You may also be aware of the sea-tide change among clinics and their EMR systems as they now are actively building integration solutions to exchange clinical information between various healthcare providers (e.g., hospitals, imaging centers, labs, etc.). […]

  9. Formal Article / Publication Comparing CDA and CCR says:

    […] various EMR, HIS, RIS, PACS, dictations, etc systems. The CCR is an XML-based standard that is related to and different from the HL7 2.X messaging […]

  10. How Do CCR and CDA Compare? says:

    […] What is the Relationship Between the Continuity of Care Record (CCR) and HL7 2.X Messaging? […]

  11. Embedding or Sending a CCR Document Inside an HL7 2.X Message says:

    […] prior posts I described the Continuity of Care Record (CCR) and the relationship between HL7 2.X and CCR. This article addresses a need to mix the two formats. Specifically, the desire to move a CCR […]

Leave a Reply

Discover the NeoTool Healthcare Integration Solution for Your Market.