HL7 Clinical Document Architecture, Release 2
- Robert H Dolin,
- Liora Alschuler,
- Sandy Boyer,
- Calvin Beebe,
- Fred M Behlen,
- Paul V Biron,
- Amnon Shabo Shvo
- Affiliations of the authors: Kaiser Permanente, Pasadena, CA (RHD, PVB); Alschuler Associates, LLC, East Thetford, VT (LA); Consultant, Laguna Beach, CA (SB); Mayo Clinic, Rochester, MN (CB); LAI Technology, Homewood, IL (FMB); Amnon Shabo (Shvo), IBM Haifa Research Lab, Haifa, Israel (AS)
- Correspondence and reprints: Robert H. Dolin, MD, 411 N. Lakeview Avenue, Anaheim, CA 92807; e-mail: <robert.h.dolin{at}kp.org>
- Received 12 June 2005
- Accepted 20 September 2005
Abstract
Clinical Document Architecture, Release One (CDA R1), became an American National Standards Institute (ANSI)–approved HL7 Standard in November 2000, representing the first specification derived from the Health Level 7 (HL7) Reference Information Model (RIM). CDA, Release Two (CDA R2), became an ANSI-approved HL7 Standard in May 2005 and is the subject of this article, where the focus is primarily on how the standard has evolved since CDA R1, particularly in the area of semantic representation of clinical events. CDA is a document markup standard that specifies the structure and semantics of a clinical document (such as a discharge summary or progress note) for the purpose of exchange. A CDA document is a defined and complete information object that can include text, images, sounds, and other multimedia content. It can be transferred within a message and can exist independently, outside the transferring message. CDA documents are encoded in Extensible Markup Language (XML), and they derive their machine processable meaning from the RIM, coupled with terminology. The CDA R2 model is richly expressive, enabling the formal representation of clinical statements (such as observations, medication administrations, and adverse events) such that they can be interpreted and acted upon by a computer. On the other hand, CDA R2 offers a low bar for adoption, providing a mechanism for simply wrapping a non-XML document with the CDA header or for creating a document with a structured header and sections containing only narrative content. The intent is to facilitate widespread adoption, while providing a mechanism for incremental semantic interoperability.
Footnotes
-
It is impossible to acknowledge all those whose foundational work has led to the development of the HL7 Development Framework and the HL7 Reference Information Model, from which CDA R2 derives. That CDA R2 is even possible is thanks to the years of work that have gone into the creation and consensus around these foundational components.
The authors acknowledge and thank the HL7 organization and membership for providing challenging use cases, for striving toward greater and greater semantic interoperability, and for creating an atmosphere of camaraderie where people work together to solve real health care challenges that benefit from interoperability solutions.









