This Article Full Text Full Text (PDF) All Versions of this Article: M1888v1 13/1/30    most recent Submit a response Alert me when this article is cited Alert me when eLetters are posted Alert me if a correction is posted Services Similar articles in this journal Similar articles in PubMed Alert me to new issues of the journal Download to citation manager Citing Articles Citing Articles via HighWire Citing Articles via Google Scholar Google Scholar Articles by Dolin, R. H. Articles by Shabo (Shvo), A. Search for Related Content PubMed PubMed Citation Articles by Dolin, R. H. Articles by Shabo (Shvo), A.

HL7 Clinical Document Architecture, Release 2

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 for publication: 06/12/05; accepted for publication: 09/20/05.

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.

This article has been cited by other articles:

				P. D. Stetson, F. P. Morrison, S. Bakken, S. B. Johnson, and eNote Research Team Preliminary Development of the Physician Documentation Quality Instrument J. Am. Med. Inform. Assoc., July 1, 2008; 15(4): 534 - 541. [Abstract] [Full Text] [PDF]

				S. B. Johnson, S. Bakken, D. Dine, S. Hyun, E. Mendonca, F. Morrison, T. Bright, T. Van Vleck, J. Wrenn, and P. Stetson An Electronic Health Record Based on Structured Narrative J. Am. Med. Inform. Assoc., January 1, 2008; 15(1): 54 - 64. [Abstract] [Full Text] [PDF]

				R. Kush, L. Alschuler, R. Ruggeri, S. Cassells, N. Gupta, L. Bain, K. Claise, M. Shah, and M. Nahm Implementing Single Source: The STARBRITE Proof-of-Concept Study J. Am. Med. Inform. Assoc., September 1, 2007; 14(5): 662 - 673. [Abstract] [Full Text] [PDF]

				A. Munoz, R. Somolinos, M. Pascual, J. A. Fragua, M. A. Gonzalez, J. L. Monteagudo, and C. H. Salvador Proof-of-concept Design and Development of an EN13606-based Electronic Health Care Record Service J. Am. Med. Inform. Assoc., January 1, 2007; 14(1): 118 - 129. [Abstract] [Full Text] [PDF]

				P. M. Yellowlees, M. Hogarth, and D. M. Hilty The Importance of Distributed Broadband Networks to Academic Biomedical Research and Education Programs Acad Psychiatry, December 1, 2006; 30(6): 451 - 455. [Abstract] [Full Text] [PDF]

				G. M. Saadawi and J. H. Harrison Jr Definition of an XML Markup Language for Clinical Laboratory Procedures and Comparison with Generic XML Markup Clin. Chem., October 1, 2006; 52(10): 1943 - 1951. [Abstract] [Full Text] [PDF]

				T. H. Payne and G. Graham Managing the Life Cycle of Electronic Clinical Documents J. Am. Med. Inform. Assoc., July 1, 2006; 13(4): 438 - 445. [Abstract] [Full Text] [PDF]

				J. M. Ferranti, R. C. Musser, K. Kawamoto, and W. E. Hammond The Clinical Document Architecture and the Continuity of Care Record: A Critical Analysis J. Am. Med. Inform. Assoc., May 1, 2006; 13(3): 245 - 252. [Abstract] [Full Text] [PDF]