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.

Underutilization of glucose data and lack of easy and standardized glucose data collection, analysis, visualization, and guided clinical decision making are key contributors to poor glycemic control among individuals with type 1 diabetes. An expert panel of diabetes specialists, facilitated by the International Diabetes Center and sponsored by the Helmsley Charitable Trust, met in 2012 to discuss recommendations for standardization of analysis and presentation of glucose monitoring data, with the initial focus on data derived from CGM systems. The panel members were introduced to a universal software report, the Ambulatory Glucose Profile (AGP), and asked to provide feedback on its content and functionality, both as a research tool and in clinical settings. This paper provides a summary of the topics and issues discussed during the meeting and presents recommendations from the expert panel regarding the need to standardize glucose profile summary metrics and the value of a uniform glucose report to aid clinicians, researchers, and patients.