This document provides an overview of the HL7 Clinical Document Architecture (CDA) standard for exchanging clinical documents. It describes what CDA is, the components of a CDA document, how CDA documents can be rendered and exchanged in messages, and examples of use cases for CDA. The key points are that CDA specifies an XML format for clinical documents to enable their structured exchange between systems, CDA documents have human-readable and machine-processable parts, and CDA relies on other HL7 standards for semantics.
Theera-Ampornpunt N. HL7 Clinical Document Architecture: overview and applications. Presented at: HL7 CDA Workshop at the Faculty of Medicine Ramathibodi Hospital; 2013 Jun 20-21; Bangkok, Thailand. Invited speaker, in Thai.
In this tutorial participants will learn the history of the RIM, the method by which the RIM is maintained, and key characteristics of the RIM that make it the premier information model in healthcare.
Topics Covered:
1. Introduction to HL7: who, what, and why
2. Introduction to HL7 v3: what and why
3. History of the HL7 Reference Information Model
4. HL7 RIM Subjects, Core Classes, and Structural Attributes
5. State Machines of RIM Core Classes
6. HL7 v3 Datatypes
7. HL7 v3 Vocabulary
This tutorial will assist in preparation for the HL7 v3 Certification exam.
An overview of the interoperability standard - Health Level 7
In partial fulfillment of the requirements for
MI 224: Coding, Classification, and Terminology in Medicine
MS Health Informatics
UP Manila College of Medicine
Full lecture with narration: https://www.youtube.com/watch?v=hjUy6k328gk
Theera-Ampornpunt N. HL7 Clinical Document Architecture: overview and applications. Presented at: HL7 CDA Workshop at the Faculty of Medicine Ramathibodi Hospital; 2013 Jun 20-21; Bangkok, Thailand. Invited speaker, in Thai.
In this tutorial participants will learn the history of the RIM, the method by which the RIM is maintained, and key characteristics of the RIM that make it the premier information model in healthcare.
Topics Covered:
1. Introduction to HL7: who, what, and why
2. Introduction to HL7 v3: what and why
3. History of the HL7 Reference Information Model
4. HL7 RIM Subjects, Core Classes, and Structural Attributes
5. State Machines of RIM Core Classes
6. HL7 v3 Datatypes
7. HL7 v3 Vocabulary
This tutorial will assist in preparation for the HL7 v3 Certification exam.
An overview of the interoperability standard - Health Level 7
In partial fulfillment of the requirements for
MI 224: Coding, Classification, and Terminology in Medicine
MS Health Informatics
UP Manila College of Medicine
Full lecture with narration: https://www.youtube.com/watch?v=hjUy6k328gk
A seminar made to the Tennessee Department of Health in July 2015. An introduction to HL7 standards with a focus on HL7 v3 messaging and clinical document architecture standards.
Presentation given at HL7 Norway on april 1st, 2014. Subjects are: why a new standard? what are the basic building blocks of FHIR? What are profiles? How do we make documents out of resources? Also contains some example architectures.
HL7
Health level 7
What is HL7?
What does it stand for
HL7 Mission
HL7 contains message standards
HL7 in HealthcareManagement System
Standards
Limitations of HL7
A presentation about the role of informatics standards in facilitating electronic data interchange, and a framework for service-oriented semantic interoperability among data systems.
The presentation talks about the components of FHIR, its distribution and use. Scenarios for the introduction of FHIR in the country using HL7 V3 are also offered.
A seminar made to the Tennessee Department of Health in July 2015. An introduction to HL7 standards with a focus on HL7 v3 messaging and clinical document architecture standards.
Presentation given at HL7 Norway on april 1st, 2014. Subjects are: why a new standard? what are the basic building blocks of FHIR? What are profiles? How do we make documents out of resources? Also contains some example architectures.
HL7
Health level 7
What is HL7?
What does it stand for
HL7 Mission
HL7 contains message standards
HL7 in HealthcareManagement System
Standards
Limitations of HL7
A presentation about the role of informatics standards in facilitating electronic data interchange, and a framework for service-oriented semantic interoperability among data systems.
The presentation talks about the components of FHIR, its distribution and use. Scenarios for the introduction of FHIR in the country using HL7 V3 are also offered.
Understanding clinical data exchange and cda (hl7 201)Edifecs Inc
On top of simple needs for doctors to be connected and be able to efficiently exchange information, there is a lot of external factors driving standardization of information exchange from market to various government initiatives and as the industry moves toward a population health model, there is more need for wider applicability of standards. This Slide share covers an introduction to CDA and establishes the importance of clinical documentation for claims and prior authorization attachments
Morning session at Vitalis 2016 - giving a high-level overview of the why what and how of HL7 and FHIR. These slides combine background information on the principles that shaped FHIR and the components of FHIR.
Presented at the 8th Healthcare CIO Certificate Program, Hospital Administration School, Faculty of Medicine Ramathibodi Hospital, Mahidol University on March 21, 2018
Presented at the 7th Healthcare CIO Certificate Program, Hospital Administration School, Faculty of Medicine Ramathibodi Hospital, Mahidol University on September 15, 2016
What are 3 of the main functions of the HL7 StandardDiscuss the i.pdfrbjain2007
What are 3 of the main functions of the HL7 Standard?
Discuss the importance of standards for exchanging health care data. Provide three examples of
standards used to exchange medical information.
Briefly describe each of the three standards you mentioned in question 2.
What is the difference between semantic and platform interoperability?
Match the standard to the description
Match the definition below with the standard name
Standard Name
Matching Standard Definition
RxNorm
HTTPS
CDA
HL7v2
HL7v3
CCR
XML
LOINC
SNOMED
CCD
HTML
ICD-10
A version of HL7 that is based on XML
Secure protocol to transfer web pages from a web server to a web browser
An open standard used to format web pages
An open standard for encoding data in a structured way
A standard that provides a set of universal codes and names to identify laboratory and other
clinical observations
Standard for EMRs from the HL7 Group
The current version of HL7 in use
A comprehensive clinical terminology, originally created by the College of American
Pathologists (CAP) and, as of April 2007, owned, maintained, and distributed by the
International Health Terminology Standards Development Organization (IHTSDO)
The new version of a standard that is used for coding of diseases and signs, symptoms, abnormal
findings, complaints, social circumstances and external causes of injury or diseases, as classified
by the World Health Organization (WHO).
NLM standard for standardized drug names
EMR standard from ASTM competing with CDA
US version of CDA standard for EMRs
Standard Name
Matching Standard Definition
RxNorm
HTTPS
CDA
HL7v2
HL7v3
CCR
XML
LOINC
SNOMED
CCD
HTML
ICD-10
Solution
1) 3 of the main functions of HL7 are:
2) Importance of standards for exchanging health care data
3)Examples:
Identify and maintain a patient record Identify and maintain a single patient record for each
patient:
Key identifying information is stored and linked to the patient record. Static data elements as
well as data elements that will change over time are maintained. A lookup function uses this
information to uniquely identify the patient.
Manage patient demographics Capture and maintain demographic information:
Where appropriate, the data should be clinically relevant, reportable and trackable over time.
Contact information including addresses and phone numbers, as well as key demographic
information such as date of birth, sex, and other information is stored and maintained for
reporting purposes and for the provision of care.
Manage summary lists Create and maintain patient-specific summary lists that are structured and
coded where appropriate:
Patient summary lists can be created from patient specific data and displayed and maintained in a
summary format. The functions below are important, but do not exhaust the possibilities.
4)Difference between semantic and platform interoperability:
Semantic interoperability is the ability to automatically interpret the information exchanged
meaningfully and accurately in order t.
Semantic Web Technologies: A Paradigm for Medical InformaticsChimezie Ogbuji
Some common needs for the patient registries, Electronic Health Record (EHR) systems, and clinical research repositories of the future are: semantic interoperability, adoption of standardized clinical terminology, adhoc and distributed querying interfaces, and integration with extant databases and web-based systems. A suite of standards has recently emerged from the consortium responsible for the development and oversight of the protocols of the World-wide Web (WWW). They were conceived to address data integration challenges associated with internet and intranet applications. Many of these standards and technologies are capable of addressing the challenges common to health information systems. In this talk, an introductory overview of these technologies, how they address these challenges, and a brief discussion of projects where they have been used is given.
FHIR is the latest standard to be developed under the HL7 organization. Pronounced 'Fire' , FHIR stands for Fast Healthcare Interoperability Resources. I think it's the most interesting standard to have come out of HL7 since the original HL7 protocol.
Presented at the BDMS Golden Jubilee Scientific Conference 2022 "BDMS Beyond 50 years: Looking towards the centennial," Bangkok Dusit Medical Services Public Company Limited (BDMS), Bangkok, Thailand on October 19, 2022
Presented at The Thai Medical Informatics Association Annual Conference and The National Conference on Medical Informatics (TMI-NCMedInfo) 2021, Bangkok, Thailand on November 26, 2021
Presented at the Master of Science Program in Medical Epidemiology and the Doctor of Philosophy Program in Clinical Epidemiology, Department of Clinical Epidemiology and Biostatistics, Faculty of Medicine Ramathibodi Hospital, Mahidol University, Bangkok, Thailand on November 25, 2021
Presented at the Master of Science and Doctor of Philosophy Programs in Data Science for Healthcare and Clinical Informatics, Department of Clinical Epidemiology and Biostatistics, Faculty of Medicine Ramathibodi Hospital, Mahidol University, Bangkok, Thailand on November 15, 2021
Consumer Health Informatics, Mobile Health, and Social Media for Health: Part...Nawanan Theera-Ampornpunt
Presented at the Master of Science and Doctor of Philosophy Programs in Data Science for Healthcare and Clinical Informatics, Department of Clinical Epidemiology and Biostatistics, Faculty of Medicine Ramathibodi Hospital, Mahidol University, Bangkok, Thailand on November 10, 2021
micro teaching on communication m.sc nursing.pdfAnurag Sharma
Microteaching is a unique model of practice teaching. It is a viable instrument for the. desired change in the teaching behavior or the behavior potential which, in specified types of real. classroom situations, tends to facilitate the achievement of specified types of objectives.
Recomendações da OMS sobre cuidados maternos e neonatais para uma experiência pós-natal positiva.
Em consonância com os ODS – Objetivos do Desenvolvimento Sustentável e a Estratégia Global para a Saúde das Mulheres, Crianças e Adolescentes, e aplicando uma abordagem baseada nos direitos humanos, os esforços de cuidados pós-natais devem expandir-se para além da cobertura e da simples sobrevivência, de modo a incluir cuidados de qualidade.
Estas diretrizes visam melhorar a qualidade dos cuidados pós-natais essenciais e de rotina prestados às mulheres e aos recém-nascidos, com o objetivo final de melhorar a saúde e o bem-estar materno e neonatal.
Uma “experiência pós-natal positiva” é um resultado importante para todas as mulheres que dão à luz e para os seus recém-nascidos, estabelecendo as bases para a melhoria da saúde e do bem-estar a curto e longo prazo. Uma experiência pós-natal positiva é definida como aquela em que as mulheres, pessoas que gestam, os recém-nascidos, os casais, os pais, os cuidadores e as famílias recebem informação consistente, garantia e apoio de profissionais de saúde motivados; e onde um sistema de saúde flexível e com recursos reconheça as necessidades das mulheres e dos bebês e respeite o seu contexto cultural.
Estas diretrizes consolidadas apresentam algumas recomendações novas e já bem fundamentadas sobre cuidados pós-natais de rotina para mulheres e neonatos que recebem cuidados no pós-parto em unidades de saúde ou na comunidade, independentemente dos recursos disponíveis.
É fornecido um conjunto abrangente de recomendações para cuidados durante o período puerperal, com ênfase nos cuidados essenciais que todas as mulheres e recém-nascidos devem receber, e com a devida atenção à qualidade dos cuidados; isto é, a entrega e a experiência do cuidado recebido. Estas diretrizes atualizam e ampliam as recomendações da OMS de 2014 sobre cuidados pós-natais da mãe e do recém-nascido e complementam as atuais diretrizes da OMS sobre a gestão de complicações pós-natais.
O estabelecimento da amamentação e o manejo das principais intercorrências é contemplada.
Recomendamos muito.
Vamos discutir essas recomendações no nosso curso de pós-graduação em Aleitamento no Instituto Ciclos.
Esta publicação só está disponível em inglês até o momento.
Prof. Marcus Renato de Carvalho
www.agostodourado.com
- Video recording of this lecture in English language: https://youtu.be/kqbnxVAZs-0
- Video recording of this lecture in Arabic language: https://youtu.be/SINlygW1Mpc
- Link to download the book free: https://nephrotube.blogspot.com/p/nephrotube-nephrology-books.html
- Link to NephroTube website: www.NephroTube.com
- Link to NephroTube social media accounts: https://nephrotube.blogspot.com/p/join-nephrotube-on-social-media.html
Basavarajeeyam is a Sreshta Sangraha grantha (Compiled book ), written by Neelkanta kotturu Basavaraja Virachita. It contains 25 Prakaranas, First 24 Chapters related to Rogas& 25th to Rasadravyas.
263778731218 Abortion Clinic /Pills In Harare ,sisternakatoto
263778731218 Abortion Clinic /Pills In Harare ,ABORTION WOMEN’S CLINIC +27730423979 IN women clinic we believe that every woman should be able to make choices in her pregnancy. Our job is to provide compassionate care, safety,affordable and confidential services. That’s why we have won the trust from all generations of women all over the world. we use non surgical method(Abortion pills) to terminate…Dr.LISA +27730423979women Clinic is committed to providing the highest quality of obstetrical and gynecological care to women of all ages. Our dedicated staff aim to treat each patient and her health concerns with compassion and respect.Our dedicated group ABORTION WOMEN’S CLINIC +27730423979 IN women clinic we believe that every woman should be able to make choices in her pregnancy. Our job is to provide compassionate care, safety,affordable and confidential services. That’s why we have won the trust from all generations of women all over the world. we use non surgical method(Abortion pills) to terminate…Dr.LISA +27730423979women Clinic is committed to providing the highest quality of obstetrical and gynecological care to women of all ages. Our dedicated staff aim to treat each patient and her health concerns with compassion and respect.Our dedicated group of receptionists, nurses, and physicians have worked together as a teamof receptionists, nurses, and physicians have worked together as a team wwww.lisywomensclinic.co.za/
Basavarajeeyam is an important text for ayurvedic physician belonging to andhra pradehs. It is a popular compendium in various parts of our country as well as in andhra pradesh. The content of the text was presented in sanskrit and telugu language (Bilingual). One of the most famous book in ayurvedic pharmaceutics and therapeutics. This book contains 25 chapters called as prakaranas. Many rasaoushadis were explained, pioneer of dhatu druti, nadi pareeksha, mutra pareeksha etc. Belongs to the period of 15-16 century. New diseases like upadamsha, phiranga rogas are explained.
These simplified slides by Dr. Sidra Arshad present an overview of the non-respiratory functions of the respiratory tract.
Learning objectives:
1. Enlist the non-respiratory functions of the respiratory tract
2. Briefly explain how these functions are carried out
3. Discuss the significance of dead space
4. Differentiate between minute ventilation and alveolar ventilation
5. Describe the cough and sneeze reflexes
Study Resources:
1. Chapter 39, Guyton and Hall Textbook of Medical Physiology, 14th edition
2. Chapter 34, Ganong’s Review of Medical Physiology, 26th edition
3. Chapter 17, Human Physiology by Lauralee Sherwood, 9th edition
4. Non-respiratory functions of the lungs https://academic.oup.com/bjaed/article/13/3/98/278874
Local Advanced Lung Cancer: Artificial Intelligence, Synergetics, Complex Sys...Oleg Kshivets
Overall life span (LS) was 1671.7±1721.6 days and cumulative 5YS reached 62.4%, 10 years – 50.4%, 20 years – 44.6%. 94 LCP lived more than 5 years without cancer (LS=2958.6±1723.6 days), 22 – more than 10 years (LS=5571±1841.8 days). 67 LCP died because of LC (LS=471.9±344 days). AT significantly improved 5YS (68% vs. 53.7%) (P=0.028 by log-rank test). Cox modeling displayed that 5YS of LCP significantly depended on: N0-N12, T3-4, blood cell circuit, cell ratio factors (ratio between cancer cells-CC and blood cells subpopulations), LC cell dynamics, recalcification time, heparin tolerance, prothrombin index, protein, AT, procedure type (P=0.000-0.031). Neural networks, genetic algorithm selection and bootstrap simulation revealed relationships between 5YS and N0-12 (rank=1), thrombocytes/CC (rank=2), segmented neutrophils/CC (3), eosinophils/CC (4), erythrocytes/CC (5), healthy cells/CC (6), lymphocytes/CC (7), stick neutrophils/CC (8), leucocytes/CC (9), monocytes/CC (10). Correct prediction of 5YS was 100% by neural networks computing (error=0.000; area under ROC curve=1.0).
Local Advanced Lung Cancer: Artificial Intelligence, Synergetics, Complex Sys...
Exploring HL7 CDA & Its Structures
1. 1
HL7 Clinical Document
Architecture:
Overview and Applications
Nawanan Theera-Ampornpunt, M.D., Ph.D.
Department of Community Medicine
Faculty of Medicine Ramathibodi Hospital
Certified HL7 CDA Specialist
April 2, 2014
2. 2
A Bit About Myself...
2003 M.D. (Ramathibodi)
2009 M.S. in Health Informatics (U of MN)
2011 Ph.D. in Health Informatics (U of MN)
2012 Certified HL7 CDA Specialist
• Lecturer, Department of Community Medicine
• Deputy Executive Director for Informatics
(CIO/CMIO), Chakri Naruebodindra Medical Institute
Faculty of Medicine Ramathibodi Hospital
nawanan.the@mahidol.ac.th
http://groups.google.com/group/ThaiHealthIT
Research interests:
• EHRs & health IT applications in clinical settings
• Health IT adoption & eHealth development
• Health informatics education & workforce development
6. 6
Functional
Semantic
Syntactic
How Standards Support Interoperability
Technical Standards
(TCP/IP, encryption,
security)
Exchange Standards (HL7 v.2,
HL7 v.3 Messaging, HL7 CDA,
DICOM)
Vocabularies, Terminologies,
Coding Systems (ICD-10, ICD-9,
CPT, SNOMED CT, LOINC)
Information Models (HL7 v.3 RIM,
ASTM CCR, HL7 CCD)
Standard Data Sets
Functional Standards (HL7 EHR
Functional Specifications)
Some may be hybrid: e.g. HL7 v.3, HL7 CCD
Unique ID
7. 7
Message Exchange
• Goal: Specify format
for exchange of data
• Internal vs. external
messages
• Examples
HL7 v.2
HL7 v.3 Messaging
DICOM
NCPDP
Document Exchange
• Goal: Specify format
for exchange of
“documents”
• Examples
HL7 v.3 Clinical Document
Architecture (CDA)
ASTM Continuity of Care
Record (CCR)
HL7 Continuity of Care
Document (CCD)
Exchange Standards
8. 8
Messages
• Human Unreadable
• Machine Processable
Clinical Documents
• Human Readable
• (Ideally) Machine
Processable
Exchange Standards
9. 9
Hospital A Hospital B
Clinic C
Government
Lab Patient at Home
Message Exchange
Message
Message
Message
Message
Message
10. 10
Hospital A Hospital B
Clinic C
Government
Lab Patient at Home
Clinical Document Exchange
Message containing
Referral Letter
Message containing
Claims Request
Message containing
Lab Report
Message containing
Patient Visit Summary
Message containing
Communicable
Disease Report
13. 13
HL7 V3 Standards
• A family of standards based on V3
information models and development
methodology
• Components
– HL7 V3 Reference Information Model (RIM)
– HL7 V3 Messaging
– HL7 Development Framework (HDF)
15. 15
Source: “What is CDA R2? by Calvin E. Beebe
at HL7 Educational Summit in July 2012
16. 16
HL7 V3 Messaging
• V3 provides messaging standards for
– Patient administration
– Medical records
– Orders
– Laboratory
– Claims & Reimbursement
– Care provision
– Clinical genomics
– Public Health
– Etc.
17. 17
How HL7 V3 Works
• Message sent from sending application to
receiving application
• Mostly triggered by an event
• Typical scenario portrayed in a storyboard
• Message in XML with machine-processable
elements conforming to messaging
standard
• Data elements in message conform to RIM
• Not designed for human readability
18. 18
What Is HL7 CDA?
• “A document markup standard that
specifies structure & semantics of “clinical
documents” for the purpose of exchange”
[Source: HL7 CDA Release 2]
• Focuses on document exchange, not
message exchange
• A document is packaged in a message
during exchange
• Note: CDA is not designed for document
storage. Only for exchange!!
19. 19
A Clinical Document (1)
• A documentation of clinical observations
and services, with the following
characteristics:
Persistence - continues to exist in an
unaltered state, for a time period defined by
local and regulatory requirements
Stewardship - maintained by an organization
entrusted with its care
Potential for authentication - an assemblage
of information that is intended to be legally
authenticated Source: HL7 CDA R2
20. 20
A Clinical Document (2)
• A documentation of clinical observations
and services, with the following
characteristics:
Context - establishes the default context for its
contents; can exist in non-messaging contexts
Wholeness - Authentication of a clinical
document applies to the whole and does not
apply to portions of the document without full
context of the document
Human readability - human readable
Source: HL7 CDA R2
21. 21
A Clinical Document (3)
• A CDA document is a defined & complete
information object that can include
Text
Images
Sounds
Other multimedia content
Source: HL7 CDA R2
22. 22
Some Possible Use Cases of CDA
Intra-institutional
Exchange of parts of medical records (scanned or
structured electronic health records)
Lab/Imaging requests & reports
Prescriptions/order forms
Admission notes
Progress notes
Operative notes
Discharge summaries
Payment receipts
Other forms/documents (clinical or administrative)
23. 23
Some Possible Use Cases of CDA
Inter-institutional
Referral letters
Claims requests or reimbursement documents
External lab/imaging reports
Visit summary documents
Insurance eligibility & coverage documents
Identification documents
Disease reporting
Other administrative reports
24. 24
CDA Releases
• CDA Release 1 (ANSI-approved in 2000)
– First specification derived from HL7 RIM
• CDA Release 2 (2005) - Current Release
– Basic model essentially unchanged from R1
• Document has a header & a body
• Body contains nested sections
• Sections can be coded using standard vocabularies and can
contain entries
– Derived from HL7 RIM Version 2.07
Source: HL7 CDA R2
25. 25
Key Aspects of CDA
• CDA documents are encoded in XML
When alternative implementations are feasible,
new conformance requirements will be issued
• CDA documents derive their machine
processable meaning from HL7 RIM and
use HL7 V3 Data Types
• CDA specification is richly expressive &
flexible
Templates can be used to constrain generic
CDA specifications
Source: HL7 CDA R2
26. 26
Scope of CDA
• Standardization of clinical documents for
exchange
• Data format of clinical documents outside
of exchange context (such as data format
used to store clinical documents) is out-of-
scope
Source: HL7 CDA R2
27. 27
Scope of CDA
• CDA doesn’t specify creation or
management of documents and messages
related to document management
• Instead, HL7 V3 Structured Documents
WG provides specifications on standards
for document exchange within HL7 V3
messages (where CDA clinical documents
can become contents of the messages)
Source: HL7 CDA R2
28. 28
Scope of CDA
Lab Technician Physician
Lab Report
Create
document
Process &
Store
document
Transmit
document
CDA
29. 29
CDA & HL7 Messages
• Documents complement HL7 messaging
specifications
• Documents are defined and complete information
objects that can exist outside of a messaging
context
• A document can be a MIME-encoded payload
within an HL7 message
Source: “What is CDA R2? by Calvin E. Beebe
at HL7 Educational Summit in July 2012
30. 30
CDA & Message Exchange
• CDA can be payload (or content) in any kind of
message
– HL7 V2.x message
– HL7 V3 message
– EDI ANSI X12 message
– IHE Cross-Enterprise Document Sharing (XDS)
message
• And it can be passed from one kind to
another
Source: “What is CDA R2? by Calvin E. Beebe
at HL7 Educational Summit in July 2012
31. 31
CDA & Message Exchange
Clinical Document
(Payload)
HL7 V3 Message
(Message)
HL7 V2 Message
(Message)
Source: Adapted from “What is CDA R2? by Calvin E. Beebe
at HL7 Educational Summit in July 2012
32. 32
CDA As Payload
Source: From “What is CDA R2? by Calvin E. Beebe
at HL7 Educational Summit in July 2012
33. 33
MIME
• Multipurpose Internet Mail Extensions
• An Internet standard that extends the format of e-
mail to support
– Text in non-ASCII character sets
– Non-text attachments
– Message bodies with multiple parts
– Etc.
• Often used in e-mails & some HTTP data
• Encoding: e.g. base64 (converting bits into
64 ASCII characters
Source: http://en.wikipedia.org/wiki/MIME
36. 36
CDA Model
Source: From “What is CDA R2? by Calvin E. Beebe
at HL7 Educational Summit in July 2012
37. 37
A Closer Look at a CDA Document
<ClinicalDocument> ... CDA Header ...
<structuredBody> <section> <text>... Single
Narrative Block ...</text>
<observation>...</observation>
<substanceAdministration>
<supply>...</supply>
</substanceAdministration> <observation>
<externalObservation>...
</externalObservation> </observation>
</section> <section> <section>...</section>
</section> </structuredBody>
</ClinicalDocument>
Source: HL7 CDA R2
Human Readable Part
Machine Processable Parts
38. 38
Rendering CDA Documents (1)
Source: From “What is CDA R2? by Calvin E. Beebe
at HL7 Educational Summit in July 2012
39. 39
Rendering CDA Documents (2)
Source: From “What is CDA R2? by Calvin E. Beebe
at HL7 Educational Summit in July 2012
40. 40
Rendering CDA Documents (3)
• Different recipients may use different style sheets
to render the same CDA document, and thus may
display it differently (but the same content is
presented)
• This can help facilitate display of CDA documents
with specific preferences or local requirements
41. 41
Human Readability & Rendering
CDA Documents
Source: HL7 CDA R2
<ClinicalDocument> ... CDA Header ...
<structuredBody> <section> <text>... Single
Narrative Block ...</text>
<observation>...</observation>
<substanceAdministration>
<supply>...</supply>
</substanceAdministration> <observation>
<externalObservation>...
</externalObservation> </observation>
</section> <section> <section>...</section>
</section> </structuredBody>
</ClinicalDocument>
Text to be rendered
42. 42
XML Markup of CDA Documents
• CDA instances are valid against CDA Schema
• May be subject to additional validation
• No prohibition against multiple schema
languages (W3C, DTD, RELAXNG, etc.) as long
as conforming instances are compatible
Source: HL7 CDA R2
43. 43
Security, Confidentiality & Data
Integrity
• Application systems sending and receiving CDA
documents are responsible for meeting all legal
requirements for
– Document authentication
– Document confidentiality
– Document retention
• Encryption & source/recipient authentication may
be necessary but is not part of CDA specs
• Confidentiality status is available within CDA
Source: HL7 CDA R2
44. 44
CDA & Document Management
• CDA focuses on document exchange, not
storage or processing
• Clinical documents are used for various reasons
– Clinical care
– Medico-legal reasons (as evidence)
– Auditing
– Etc.
• Clinical documents may contain errors or need
data updates (e.g. preliminary lab results vs. final
results)
45. 45
CDA & Document Management
• CDA supports appending and replacement of
documents through use of Document ID, setID,
versionNumber & parent document
– Supports version control of documents
– Both old (replaced) and new versions of documents
can be stored in and retrieved from document
management systems depending on situation
– Addendum is possible through append
– Addendum itself can also be replaced with same
version control mechanism
– Document management system (not CDA) is
responsible for keeping track of most up-to-date
documents
47. 47
Achieving Interoperability
CDA is a general-purpose, broad standard
Use in each use case or context requires
implementation guides to constrain CDA
Examples
Operative Note (OP)
Consultation Notes (CON)
Care Record Summary (CRS)
Continuity of Care Document (CCD)
CDA for Public Health Case Reports (PHCRPT)
Quality Reporting Document Architecture (QRDA)
48. 48
CDA Extensibility
Locally-defined markup possible when local
semantics have no corresponding representation
in CDA specification
Additional XML elements & attributes that are not
included in CDA Schema are permitted in local
extensions
49. 49
Summary
CDA is a markup standard for document
exchange
Not message exchange
Not document storage or processing
CDA is a general-purpose standard
Use in specific context requires
Implementation Guides (and possibly
Extensions)
50. 50
Summary
CDA is XML-based and RIM-based
CDA documents can be exchanged as
encapsulated data (payload) in any message
(HL7 V2, HL7 V3, etc.)
CDA is not dependent on using HL7 V3
messages
• CDA consists of
– Header
– Body
• Section
• Entry (machine processable)
• Narrative Block (human readable)
51. 51
Next
HL7 RIM & Data Types
Navigating HL7 CDA Normative Edition
Implementation Workshop