Medicine:Clinical Document Architecture
Status | Published |
---|---|
Year started | 1996 |
First published | November 2000 |
Latest version | 2.0 2005 |
Organization | Health Level Seven International |
Committee | Structured Documents Group |
Base standards |
|
Related standards | |
Domain | Electronic health records |
Abbreviation | CDA |
Website | CDA® Release 2 |
The HL7 Clinical Document Architecture (CDA) is an XML-based markup standard intended to specify the encoding, structure and semantics of clinical documents for exchange. In November 2000, HL7 published Release 1.0. The organization published Release 2.0 with its "2005 Normative Edition."[1]
Content
CDA specifies the syntax and supplies a framework for specifying the full semantics of a clinical document, defined by six characteristics:[2]
- Persistence
- Stewardship
- Potential for authentication
- Context
- Wholeness
- Human readability
CDA can hold any kind of clinical information that would be included in a patient's medical record; examples include:[1]
- Discharge summary (following inpatient care)
- History & physical
- Specialist reports, such as those for medical imaging or pathology
An XML element in a CDA supports unstructured text, as well as links to composite documents encoded in pdf, docx, or rtf, as well as image formats like jpg and png.[3]
It was developed using the HL7 Development Framework (HDF) and it is based on the HL7 Reference Information Model (RIM) and the HL7 Version 3 Data Types.[citation needed]
The CDA specifies that the content of the document consists of a mandatory textual part (which ensures human interpretation of the document contents) and optional structured parts (for software processing). The structured part relies on coding systems (such as from SNOMED and LOINC) to represent concepts.[citation needed]
Consolidated Clinical Document Architecture
In 2012, in response to conflicting CDAs in use by the healthcare industry, the Office of the National Coordinator for Health Information Technology (ONC) streamlined commonly used templates to create the Consolidated-CDA (C-CDA).
Transport
The CDA standard doesn't specify how the documents should be transported. CDA documents can be transported using HL7 version 2 messages, HL7 version 3 messages, IHE protocols such as XDS, as well as by other mechanisms including: DICOM, MIME attachments to email, http or ftp.
Standard certification and adoption
The standard is certified by ANSI.[1]
CDA Release 2 has been adopted as an ISO standard, ISO/HL7 27932:2009.[4]
Country-specific implementations
Australia
Australia's Personally Controlled Electronic Health Record (PCEHR), known as "My Health Record," uses a specialized implementation of HL7 CDA Release 2.[5]
United Kingdom
In the UK the Interoperability Toolkit (ITK) utilises the 'CDA R2 from HL7 V3 - for CDA profiles' for the Correspondence pack.[6][7]
United States
In the U.S. the CDA standard is probably best known as the basis for the Continuity of Care Document (CCD) specification, based on the data model as specified by ASTM's Continuity of Care Record. The U.S. Healthcare Information Technology Standards Panel has selected the CCD as one of its standards.[citation needed]
See also
- EHRcom
- Health Informatics Service Architecture (HISA)
- Gello Expression Language
- Fast Healthcare Interoperability Resources
References
- ↑ 1.0 1.1 1.2 "FAQs". http://www.hl7.org/about/FAQs/index.cfm.
- ↑ "CDA® Release 2". http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7.
- ↑ "HL7 Attachment Supplement Specification Release 2 Version 3.5". http://www.hl7.org/special/committees/projman/searchableprojectindex.cfm?action=edit&ProjectNumber=1155.
- ↑ "ISO/HL7 27932:2009 - Data Exchange Standards -- HL7 Clinical Document Architecture, Release 2". http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=44429.
- ↑ "PCEHR Medicare Overview - CDA Implementation Guide v1.1". 27 September 2013. https://www.digitalhealth.gov.au/implementation-resources/clinical-documents/EP-1469-2013/NEHTA-1467-2013.
- ↑ "The Interoperability Toolkit". https://digital.nhs.uk/article/776/ITK-Toolkit.
- ↑ "ITK FAQs". NHS CFH. http://systems.hscic.gov.uk/interop/itk/faqs/index_html. See 'What standards does ITK utilise?'
Further reading
- Spronk, René (13 November 2007). HL7 version 3: message or document? (Whitepaper). Ringholm bv. http://www.ringholm.de/docs/04200_en.htm.
- Boone, Keith W. (2011). The CDA Book. Springer Science & Business Media. ISBN 978-0-85729-336-7. https://books.google.com/books?id=rwa6DDB4jY8C.
External links
- "Structured Documents Group". http://www.hl7.org/Special/committees/structure/.
- "CDA". http://hl7book.net/index.php?title=CDA.
- "What is HL7® CDA™?". http://iehr.eu/standards/hl7-cda/.
- "C-CDA to SQL app and API". https://www.cda2sql.com/.