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.
The document provides an introduction to FHIR (Fast Healthcare Interoperability Resources). It outlines some of the limitations of previous HL7 standards like V3 being too complex and documents (CDA) not being sufficient. It notes the need for a transition path from V2 and something to address new markets. FHIR is presented as a new approach that is focused on implementers and uses resources as the basic building block. Each resource has its own model and unique ID. The goal is to make implementation easier compared to previous standards.
This document summarizes a presentation on FHIR terminology given by Lloyd McKenzie at the FHIR Developer Days on November 25, 2014. The presentation covered how coded data is shared in FHIR using bindings and value sets, the process for creating and using value sets, and the future of FHIR terminology. The objectives of the tutorial were to explain how coded data is shared in FHIR, understand bindings and profiling vocabulary, learn the process for creating and using value sets, and discuss the future of FHIR terminology.
The document provides an overview of HL7 version 2.x messaging conformance and message profiles. It discusses the background and concepts of HL7 messaging, including why HL7 standards were developed and how message profiles can help reveal assumptions, reduce ambiguity, highlight conflicts, and consolidate viewpoints when specifying message structures. The document also outlines the key components of message profiles, including their static and dynamic definitions, and provides examples of how profiles constrain HL7 message structures.
The document discusses the need for profiles and validation in FHIR. It notes that healthcare data can vary significantly between countries, disciplines, clinicians and IT systems. Profiles are needed to define constraints and rules for how resources should be used in particular contexts. The goal of FHIR is to create a common platform that can support interoperability even where global interoperability is not possible. The conformance resources, including profiles, value sets, and conformance statements, provide guidance on how to use the FHIR framework in a standardized way.
This document provides an introduction and progress report on FHIR (Fast Healthcare Interoperability Resources). Key points:
- FHIR is a new, implementer-friendly standard for healthcare interoperability that has generated significant interest internationally.
- The core infrastructure is in draft form and several clinical domains are actively working on defining FHIR resources.
- FHIR can be used for RESTful exchanges, documents, messages, services, and integrating with XDS standards.
- The goal is to have more resources balloted in 2013 and release a draft standard for trial use in 2014.
This document provides an overview of how LOINC (Logical Observation Identifiers Names and Codes) codes can be used with FHIR (Fast Healthcare Interoperability Resources). It discusses how LOINC codes are represented and used in various FHIR resources like Observation, Questionnaire, DiagnosticReport, etc. It also describes how FHIR terminology services can be used to retrieve information about LOINC codes and structures like parts, answer lists, and properties to build value sets. The document demonstrates how LOINC enhances interoperability when clinical data is coded with LOINC and accessible via FHIR.
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.
The document provides an introduction to FHIR (Fast Healthcare Interoperability Resources). It outlines some of the limitations of previous HL7 standards like V3 being too complex and documents (CDA) not being sufficient. It notes the need for a transition path from V2 and something to address new markets. FHIR is presented as a new approach that is focused on implementers and uses resources as the basic building block. Each resource has its own model and unique ID. The goal is to make implementation easier compared to previous standards.
This document summarizes a presentation on FHIR terminology given by Lloyd McKenzie at the FHIR Developer Days on November 25, 2014. The presentation covered how coded data is shared in FHIR using bindings and value sets, the process for creating and using value sets, and the future of FHIR terminology. The objectives of the tutorial were to explain how coded data is shared in FHIR, understand bindings and profiling vocabulary, learn the process for creating and using value sets, and discuss the future of FHIR terminology.
The document provides an overview of HL7 version 2.x messaging conformance and message profiles. It discusses the background and concepts of HL7 messaging, including why HL7 standards were developed and how message profiles can help reveal assumptions, reduce ambiguity, highlight conflicts, and consolidate viewpoints when specifying message structures. The document also outlines the key components of message profiles, including their static and dynamic definitions, and provides examples of how profiles constrain HL7 message structures.
The document discusses the need for profiles and validation in FHIR. It notes that healthcare data can vary significantly between countries, disciplines, clinicians and IT systems. Profiles are needed to define constraints and rules for how resources should be used in particular contexts. The goal of FHIR is to create a common platform that can support interoperability even where global interoperability is not possible. The conformance resources, including profiles, value sets, and conformance statements, provide guidance on how to use the FHIR framework in a standardized way.
This document provides an introduction and progress report on FHIR (Fast Healthcare Interoperability Resources). Key points:
- FHIR is a new, implementer-friendly standard for healthcare interoperability that has generated significant interest internationally.
- The core infrastructure is in draft form and several clinical domains are actively working on defining FHIR resources.
- FHIR can be used for RESTful exchanges, documents, messages, services, and integrating with XDS standards.
- The goal is to have more resources balloted in 2013 and release a draft standard for trial use in 2014.
This document provides an overview of how LOINC (Logical Observation Identifiers Names and Codes) codes can be used with FHIR (Fast Healthcare Interoperability Resources). It discusses how LOINC codes are represented and used in various FHIR resources like Observation, Questionnaire, DiagnosticReport, etc. It also describes how FHIR terminology services can be used to retrieve information about LOINC codes and structures like parts, answer lists, and properties to build value sets. The document demonstrates how LOINC enhances interoperability when clinical data is coded with LOINC and accessible via FHIR.
This document provides an agenda and overview for an HL7 FHIR training course. The morning session will include introductions to FHIR, resources, and the RESTful model. Exercises are planned to apply the concepts. The agenda also includes an introduction to the FHIR data model and more exercises before breaking for lunch. The trainer is identified as Ewout Kramer from Furore in Amsterdam, and he has experience with FHIR and healthcare software development.
Tutorial on Principles of Health Interoperability, presented at Informatics for Health Conference, Manchester 23 April 2017. Covers SNOMED CT, HL7 and FHIR and why interoperability is hard.
FHIR for Developers tutorial as given during the HL7 WGM meetings. Good introductory text for developers getting started with FHIR, HL7's new messaging standard for healthcare.
HL7 is an international standards organization that develops standards for exchanging electronic health information. It aims to allow disparate healthcare applications to exchange clinical and administrative data through interoperability standards. HL7's standards include messaging specifications that define how information is packaged and communicated between parties, as well as document and application standards. HL7 develops standards for different workflows and uses various encoding methods like XML.
The document provides an overview of HL7 Version 3, including its reference information model (RIM) which defines core classes like Entity, Role, Act, and their relationships. It describes the RIM's object-oriented methodology and backbone classes. The training objectives are to define HL7 terms and concepts, describe its modeling methodology, and introduce HL7 Version 3 at NCICB.
This document provides information about HL7's certification exam for HL7 v2 Control, including how to take the exam, certifications offered, the application process, testing policies, exam scope and structure, available study materials, and sample exam questions. The exam consists of 70 multiple choice questions covering HL7 v2 Control chapters and is designed to test understanding of HL7 v2 messaging concepts, construction and processing rules, control segments, datatypes, and conformance. Exam questions address topics such as trigger events, acknowledgment protocols, segment attributes, field rules, and sample HL7 messages.
The document discusses HL7 and FHIR. It begins by explaining that HL7 is a standards development organization that provides a framework and standards for exchanging health information to support clinical practices and health services management. It then defines what "Level Seven" refers to in relation to the ISO communication model. The document also provides information on various HL7 product families, including FHIR, CDA, EHR functional model, SOA, and context management architecture. It concludes by summarizing HL7 Version 2 and Version 3 messaging standards.
FHIR for Architects and Developers - New Zealand Seminar, June 2014David Hay
This document provides an overview of FHIR (Fast Healthcare Interoperability Resources) for architects and developers. It discusses FHIR architectures and paradigms including REST, documents, messages, and services. It describes when each paradigm should be used and provides examples. The document also demonstrates how to work with FHIR resources and test FHIR servers using tools.
The document provides an introduction and overview of HL7, including:
- HL7 is a protocol for exchanging healthcare data between systems that defines messages and procedures for exchanging them.
- It aims to enable interoperability between different healthcare IT systems.
- HL7 messages are composed of segments, fields, and components that provide specific types of patient, clinical, or administrative data.
- Common HL7 messages are used for admissions, discharges, patient registration, orders, results, and other clinical and administrative workflows.
Hl7 Standards, Reference Information Model & Clinical Document ArchitectureNawanan Theera-Ampornpunt
This document discusses HL7 standards and includes information about:
- HL7 version 2 (HL7 v2), which is the most commonly used HL7 standard for defining electronic messages supporting hospital operations.
- HL7 version 3, which adds semantic capability to messaging.
- The Clinical Document Architecture (CDA), which defines the structure and semantics of clinical documents.
The document discusses different data models including hierarchical, network, and relational models. The hierarchical model uses a tree structure with parent-child relationships, while the network model allows a child to have multiple parents. The relational model uses tables with rows and columns to represent relationships between data through the use of primary and foreign keys. Each model has advantages like ease of use, but also disadvantages such as complexity or inability to represent certain relationships. The relational model is currently the most widely used.
CDISC is a non-profit organization that establishes clinical research data standards to support data acquisition, exchange, and submission. It has developed several standards including CDASH, which aims to standardize data collection fields across clinical trials to streamline data analysis and reduce errors. CDASH defines a set of common safety domains and variables that can be collected consistently across studies in a standardized way. This helps analyze data more efficiently, reduces training time for sites, and decreases potential errors from inconsistent data collection.
The document discusses FHIR documents and their structure. It notes that FHIR documents are bundles that contain a Composition resource along with other resources like sections, lists, observations, etc. bound together. Documents can be used when persistence of data across multiple resources is needed or when authentication of the full content is required. The document describes how FHIR documents can be communicated by posting the bundle to various FHIR endpoints like the Mailbox, Document/Bundle, or as a transaction to create/update the individual resources. It also notes documents can be posted as a Binary resource or referenced through a DocumentReference resource.
There are three key forms of health information exchange:
1) Directed exchange allows providers to electronically send and receive secure information like lab results between providers involved in a patient's care.
2) Query-based exchange allows providers to find and request information on a patient from other providers, often used for emergency care.
3) Consumer mediated exchange allows patients to aggregate and manage their health information online and help transfer it between providers.
In this presentation, Principal Statistical Scientist Ben Vaughn explains how clinical trial data moves from collection in the case report form to its presentation to FDA.
This document provides information about HL7 standards and two experts, Dr. Supachai Parchariyanon and Dr. Nawanan Theera-Ampornpunt. It discusses Dr. Parchariyanon's background and interests in standards and interoperability. It then outlines the topics to be covered, including an introduction to standards and interoperability, what HL7 is, HL7 Version 2 and 3, the Reference Information Model, and Clinical Document Architecture.
This document provides an overview of HL7 standards. It discusses HL7 version 2 and version 3 messaging standards. HL7 version 2 is the most commonly used standard for healthcare information exchange, using a pipe-delimited format. HL7 version 3 adds semantic capability and uses XML formatting and the Reference Information Model. The document also discusses other HL7 standards like Clinical Document Architecture and different levels of interoperability that standards support.
This document provides an agenda and overview for an HL7 FHIR training course. The morning session will include introductions to FHIR, resources, and the RESTful model. Exercises are planned to apply the concepts. The agenda also includes an introduction to the FHIR data model and more exercises before breaking for lunch. The trainer is identified as Ewout Kramer from Furore in Amsterdam, and he has experience with FHIR and healthcare software development.
Tutorial on Principles of Health Interoperability, presented at Informatics for Health Conference, Manchester 23 April 2017. Covers SNOMED CT, HL7 and FHIR and why interoperability is hard.
FHIR for Developers tutorial as given during the HL7 WGM meetings. Good introductory text for developers getting started with FHIR, HL7's new messaging standard for healthcare.
HL7 is an international standards organization that develops standards for exchanging electronic health information. It aims to allow disparate healthcare applications to exchange clinical and administrative data through interoperability standards. HL7's standards include messaging specifications that define how information is packaged and communicated between parties, as well as document and application standards. HL7 develops standards for different workflows and uses various encoding methods like XML.
The document provides an overview of HL7 Version 3, including its reference information model (RIM) which defines core classes like Entity, Role, Act, and their relationships. It describes the RIM's object-oriented methodology and backbone classes. The training objectives are to define HL7 terms and concepts, describe its modeling methodology, and introduce HL7 Version 3 at NCICB.
This document provides information about HL7's certification exam for HL7 v2 Control, including how to take the exam, certifications offered, the application process, testing policies, exam scope and structure, available study materials, and sample exam questions. The exam consists of 70 multiple choice questions covering HL7 v2 Control chapters and is designed to test understanding of HL7 v2 messaging concepts, construction and processing rules, control segments, datatypes, and conformance. Exam questions address topics such as trigger events, acknowledgment protocols, segment attributes, field rules, and sample HL7 messages.
The document discusses HL7 and FHIR. It begins by explaining that HL7 is a standards development organization that provides a framework and standards for exchanging health information to support clinical practices and health services management. It then defines what "Level Seven" refers to in relation to the ISO communication model. The document also provides information on various HL7 product families, including FHIR, CDA, EHR functional model, SOA, and context management architecture. It concludes by summarizing HL7 Version 2 and Version 3 messaging standards.
FHIR for Architects and Developers - New Zealand Seminar, June 2014David Hay
This document provides an overview of FHIR (Fast Healthcare Interoperability Resources) for architects and developers. It discusses FHIR architectures and paradigms including REST, documents, messages, and services. It describes when each paradigm should be used and provides examples. The document also demonstrates how to work with FHIR resources and test FHIR servers using tools.
The document provides an introduction and overview of HL7, including:
- HL7 is a protocol for exchanging healthcare data between systems that defines messages and procedures for exchanging them.
- It aims to enable interoperability between different healthcare IT systems.
- HL7 messages are composed of segments, fields, and components that provide specific types of patient, clinical, or administrative data.
- Common HL7 messages are used for admissions, discharges, patient registration, orders, results, and other clinical and administrative workflows.
Hl7 Standards, Reference Information Model & Clinical Document ArchitectureNawanan Theera-Ampornpunt
This document discusses HL7 standards and includes information about:
- HL7 version 2 (HL7 v2), which is the most commonly used HL7 standard for defining electronic messages supporting hospital operations.
- HL7 version 3, which adds semantic capability to messaging.
- The Clinical Document Architecture (CDA), which defines the structure and semantics of clinical documents.
The document discusses different data models including hierarchical, network, and relational models. The hierarchical model uses a tree structure with parent-child relationships, while the network model allows a child to have multiple parents. The relational model uses tables with rows and columns to represent relationships between data through the use of primary and foreign keys. Each model has advantages like ease of use, but also disadvantages such as complexity or inability to represent certain relationships. The relational model is currently the most widely used.
CDISC is a non-profit organization that establishes clinical research data standards to support data acquisition, exchange, and submission. It has developed several standards including CDASH, which aims to standardize data collection fields across clinical trials to streamline data analysis and reduce errors. CDASH defines a set of common safety domains and variables that can be collected consistently across studies in a standardized way. This helps analyze data more efficiently, reduces training time for sites, and decreases potential errors from inconsistent data collection.
The document discusses FHIR documents and their structure. It notes that FHIR documents are bundles that contain a Composition resource along with other resources like sections, lists, observations, etc. bound together. Documents can be used when persistence of data across multiple resources is needed or when authentication of the full content is required. The document describes how FHIR documents can be communicated by posting the bundle to various FHIR endpoints like the Mailbox, Document/Bundle, or as a transaction to create/update the individual resources. It also notes documents can be posted as a Binary resource or referenced through a DocumentReference resource.
There are three key forms of health information exchange:
1) Directed exchange allows providers to electronically send and receive secure information like lab results between providers involved in a patient's care.
2) Query-based exchange allows providers to find and request information on a patient from other providers, often used for emergency care.
3) Consumer mediated exchange allows patients to aggregate and manage their health information online and help transfer it between providers.
In this presentation, Principal Statistical Scientist Ben Vaughn explains how clinical trial data moves from collection in the case report form to its presentation to FDA.
This document provides information about HL7 standards and two experts, Dr. Supachai Parchariyanon and Dr. Nawanan Theera-Ampornpunt. It discusses Dr. Parchariyanon's background and interests in standards and interoperability. It then outlines the topics to be covered, including an introduction to standards and interoperability, what HL7 is, HL7 Version 2 and 3, the Reference Information Model, and Clinical Document Architecture.
This document provides an overview of HL7 standards. It discusses HL7 version 2 and version 3 messaging standards. HL7 version 2 is the most commonly used standard for healthcare information exchange, using a pipe-delimited format. HL7 version 3 adds semantic capability and uses XML formatting and the Reference Information Model. The document also discusses other HL7 standards like Clinical Document Architecture and different levels of interoperability that standards support.
Presented at the 7th Healthcare CIO Certificate Program, Hospital Administration School, Faculty of Medicine Ramathibodi Hospital, Mahidol University on September 15, 2016
This document provides information about HL7 standards and two experts, Dr. Supachai Parchariyanon and Dr. Nawanan Theera-Ampornpunt. It discusses HL7 Version 2 and Version 3 messaging standards. Version 2 is the most commonly used standard, using segments and a pipe-delimited format. Version 3 adds semantic capability using XML messages based on a Reference Information Model. The document compares the two versions and their approaches to addressing interoperability.
The document discusses HL7 standards and provides context about HL7 version 2 and version 3. It notes that HL7 version 2 is the most commonly used standard for healthcare information exchange, using a pipe-delimited format. HL7 version 3 adds semantic capability and uses XML messaging based on a Reference Information Model. The document also profiles Thailand's HL7 certified specialists and provides examples of HL7 version 2 message segments.
This document provides an overview of HL7 standards. It discusses HL7 version 2 and version 3 messaging standards, as well as the Clinical Document Architecture (CDA). HL7 version 2 is the most widely implemented healthcare data exchange standard. Version 2 uses a pipe-delimited format while version 3 uses XML and is based on the Reference Information Model (RIM). The RIM defines common data types and allows semantic interoperability. The document also notes some challenges with implementing version 3.
This document provides an overview of HL7 standards. It begins with introducing Thailand's certified HL7 specialists and then discusses why standards are important for health information exchange. The document explains different levels of interoperability and describes various HL7 standards including HL7 v2, HL7 v3, and CDA. It highlights key differences between HL7 v2 and v3 and provides examples of HL7 message segments.
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.
HL7 & HL7 CDA: The Implementation of Thailand's Healthcare Messaging Exchange...Nawanan Theera-Ampornpunt
This document discusses the implementation of HL7 and HL7 CDA standards for healthcare messaging exchange in Thailand. It provides background on the speaker, Nawanan Theera-Ampornpunt, and outlines Thailand's vision for eHealth, current status, and the role of standards. It then describes HL7 standards including versions 2 and 3, the Reference Information Model, and Clinical Document Architecture. The document outlines Ramathibodi Hospital's experience implementing HL7 messaging and CDA documents for lab results exchange. Next steps involve encouraging broader CDA adoption.
This document provides an overview of interoperability challenges in healthcare and standards used to address those challenges, with a focus on HL7 standards and FHIR. It discusses the need for standardized data exchange to ensure clinical data is available where and when needed. It summarizes key HL7 standards like V2, CDA, C-CDA and introduces FHIR as the latest standard, combining features of previous standards. The document compares features of different standards and provides examples of FHIR resources and operations. It concludes with a demo of FHIR capabilities.
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.
The document discusses health information exchange and HL7 standards. It provides an overview of the importance of health information exchange and standards. It then describes HL7, including what HL7 is, its mission to enable interoperability and sharing of health data, the versions and products of HL7 standards, and examples of HL7 standard adoption.
HL7 is an organization that develops standards to enable interoperability in healthcare. It has progressed through several stages, starting with simple messaging and expanding to include documents, services and an enterprise architecture framework. IHE builds on standards by providing implementation guides to integrate multiple standards in real-world use cases. What's hot includes CDA documents and SAEAF, while standards adoption remains a challenge.
Ramathibodi Hospital has experience implementing HL7 standards including HL7 v2, v3, and CDA. They developed prototypes for patient registration using HL7 v3 messaging and clinical document exchange using CDA. Ramathibodi exchanged lab results with another hospital using HL7 v2 and v3 messaging and CDA documents. Ramathibodi aims to further adopt CDA and HL7 standards for use cases like referrals, claims, reports, and electronic health records.
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
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.
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.
Interfaces Demo Eclipsys Baroda India Part OneMonisha Ghuman
The document provides an overview of HL7 (Health Level Seven) standards for exchanging healthcare information and testing HL7 interface functionality in Eclipsys systems. It introduces HL7 components like message types, segments, and versions. It also explains how to set up HL7 dictionaries, define applications and processes, install interfaces, and use testing utilities like Interfaceslite and HL7Test to validate HL7 message exchange.
Interoperability Between Healthcare ApplicationsJohn Gillson
The document discusses interoperability between heterogeneous healthcare information systems. It describes standards for achieving interoperability, including HL7 versions 2 and 3 for message exchange, the Reference Information Model (RIM), Clinical Document Architecture (CDA), and Integrating the Healthcare Enterprise (IHE) profiles like Cross-Enterprise Document Sharing (XDS). It also discusses electronic health records (EHRs), master patient indexes (MPIs), virtual medical records (VMRs), and how the Professional Exchange Server (PXS) can bridge gaps between disparate healthcare systems through its various components.
Presentation on Healthcare Interoperability at AEA, delhi chapter meeting 27t...Kumar Satyam
This document summarizes an upcoming meeting of the Association of Enterprise Architects Delhi Chapter. The meeting agenda includes updates on the chapter and EA field, a presentation by Mr. Kumar Satyam from Philips on healthcare interoperability, feedback/Q&A, and future plans. The chapter aims to advance EA excellence in Delhi/NCR. The healthcare interoperability talk will discuss challenges like standards, data sharing, and regulations, and opportunities like APIs and initiatives like NDHM and IHE profiles.
Similar to Health Information Standards & Overview of HL7 Standards (April 30, 2019) (20)
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
Telemedicine provides healthcare at a distance using telecommunications technology. It has grown from focusing on increasing access to now emphasizing convenience and cost reduction. Store-and-forward and home-based telemedicine have evidence for treating chronic diseases, while office/hospital telemedicine is effective for verbal interactions in specialties like neurology and psychiatry. Current trends include expanding telemedicine to more chronic conditions and migrating services from clinical settings to homes and mobile devices. However, reimbursement remains limited and fragmented while quality of remote care compared to in-person visits requires more evidence. Proper guidelines, standards, training and balancing innovation with risk-based regulation can maximize telemedicine's benefits while minimizing harms.
This document discusses digital health transformation and the role of health information technology. It begins by exploring concepts like artificial intelligence, blockchain, cloud computing and big data. It then examines the potential for "smart" machines in healthcare while acknowledging the complexities of digitizing such a system. The document emphasizes that clinical judgment is still necessary given variations in patients. It outlines components of healthcare systems and forms of health IT both within and beyond hospitals. Finally, it discusses using health IT to support clinical decision making and reduce errors.
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
The document discusses the field of health informatics and provides definitions and examples. It defines health informatics as the application of information science to healthcare and biomedical research. It describes the relationships between health informatics and other fields like computer science, engineering, and the medical sciences. The document also discusses different areas of health informatics like clinical informatics, public health informatics, and consumer health informatics. It provides examples of common health information technologies used in healthcare settings like electronic health records, computerized physician order entry, and picture archiving systems.
This document provides an introduction to research ethics and ethics for health informaticians. It begins with definitions of ethics, morals, and norms. It then discusses the role of law, professional codes of conduct, and ethics in establishing standards of acceptable behavior. Key topics in research ethics are introduced through discussions of historic cases like the Nazi human experiments, Beecher's research ethics violations, and the Tuskegee Syphilis Study. The document outlines the Belmont Report's three ethical principles of respect for persons, beneficence, and justice. Ethical issues in health informatics like alerts fatigue from clinical decision support systems and unintended consequences of health IT are also discussed.
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
DECODING THE RISKS - ALCOHOL, TOBACCO & DRUGS.pdfDr Rachana Gujar
Introduction: Substance use education is crucial due to its prevalence and societal impact.
Alcohol Use: Immediate and long-term risks include impaired judgment, health issues, and social consequences.
Tobacco Use: Immediate effects include increased heart rate, while long-term risks encompass cancer and heart disease.
Drug Use: Risks vary depending on the drug type, including health and psychological implications.
Prevention Strategies: Education, healthy coping mechanisms, community support, and policies are vital in preventing substance use.
Harm Reduction Strategies: Safe use practices, medication-assisted treatment, and naloxone availability aim to reduce harm.
Seeking Help for Addiction: Recognizing signs, available treatments, support systems, and resources are essential for recovery.
Personal Stories: Real stories of recovery emphasize hope and resilience.
Interactive Q&A: Engage the audience and encourage discussion.
Conclusion: Recap key points and emphasize the importance of awareness, prevention, and seeking help.
Resources: Provide contact information and links for further support.
About this webinar: This talk will introduce what cancer rehabilitation is, where it fits into the cancer trajectory, and who can benefit from it. In addition, the current landscape of cancer rehabilitation in Canada will be discussed and the need for advocacy to increase access to this essential component of cancer care.
Michigan HealthTech Market Map 2024. Includes 7 categories: Policy Makers, Academic Innovation Centers, Digital Health Providers, Healthcare Providers, Payers / Insurance, Device Companies, Life Science Companies, Innovation Accelerators. Developed by the Michigan-Israel Business Accelerator
Can Allopathy and Homeopathy Be Used Together in India.pdfDharma Homoeopathy
This article explores the potential for combining allopathy and homeopathy in India, examining the benefits, challenges, and the emerging field of integrative medicine.
LGBTQ+ Adults: Unique Opportunities and Inclusive Approaches to CareVITASAuthor
This webinar helps clinicians understand the unique healthcare needs of the LGBTQ+ community, primarily in relation to end-of-life care. Topics include social and cultural background and challenges, healthcare disparities, advanced care planning, and strategies for reaching the community and improving quality of care.
Exploring the Benefits of Binaural Hearing: Why Two Hearing Aids Are Better T...Ear Solutions (ESPL)
Binaural hearing using two hearing aids instead of one offers numerous advantages, including improved sound localization, enhanced sound quality, better speech understanding in noise, reduced listening effort, and greater overall satisfaction. By leveraging the brain’s natural ability to process sound from both ears, binaural hearing aids provide a more balanced, clear, and comfortable hearing experience. If you or a loved one is considering hearing aids, consult with a hearing care professional at Ear Solutions hearing aid clinic in Mumbai to explore the benefits of binaural hearing and determine the best solution for your hearing needs. Embracing binaural hearing can lead to a richer, more engaging auditory experience and significantly improve your quality of life.
At Apollo Hospital, Lucknow, U.P., we provide specialized care for children experiencing dehydration and other symptoms. We also offer NICU & PICU Ambulance Facility Services. Consult our expert today for the best pediatric emergency care.
For More Details:
Map: https://cutt.ly/BwCeflYo
Name: Apollo Hospital
Address: Singar Nagar, LDA Colony, Lucknow, Uttar Pradesh 226012
Phone: 08429021957
Opening Hours: 24X7
MBC Support Group for Black Women – Insights in Genetic Testing.pdfbkling
Christina Spears, breast cancer genetic counselor at the Ohio State University Comprehensive Cancer Center, joined us for the MBC Support Group for Black Women to discuss the importance of genetic testing in communities of color and answer pressing questions.
Gemma Wean- Nutritional solution for Artemiasmuskaan0008
GEMMA Wean is a high end larval co-feeding and weaning diet aimed at Artemia optimisation and is fortified with a high level of proteins and phospholipids. GEMMA Wean provides the early weaned juveniles with dedicated fish nutrition and is an ideal follow on from GEMMA Micro or Artemia.
GEMMA Wean has an optimised nutritional balance and physical quality so that it flows more freely and spreads readily on the water surface. The balance of phospholipid classes to- gether with the production technology based on a low temperature extrusion process improve the physical aspect of the pellets while still retaining the high phospholipid content.
GEMMA Wean is available in 0.1mm, 0.2mm and 0.3mm. There is also a 0.5mm micro-pellet, GEMMA Wean Diamond, which covers the early nursery stage from post-weaning to pre-growing.
Healthy Eating Habits:
Understanding Nutrition Labels: Teaches how to read and interpret food labels, focusing on serving sizes, calorie intake, and nutrients to limit or include.
Tips for Healthy Eating: Offers practical advice such as incorporating a variety of foods, practicing moderation, staying hydrated, and eating mindfully.
Benefits of Regular Exercise:
Physical Benefits: Discusses how exercise aids in weight management, muscle and bone health, cardiovascular health, and flexibility.
Mental Benefits: Explains the psychological advantages, including stress reduction, improved mood, and better sleep.
Tips for Staying Active:
Encourages consistency, variety in exercises, setting realistic goals, and finding enjoyable activities to maintain motivation.
Maintaining a Balanced Lifestyle:
Integrating Nutrition and Exercise: Suggests meal planning and incorporating physical activity into daily routines.
Monitoring Progress: Recommends tracking food intake and exercise, regular health check-ups, and provides tips for achieving balance, such as getting sufficient sleep, managing stress, and staying socially active.
TEST BANK For Accounting Information Systems, 3rd Edition by Vernon Richardso...rightmanforbloodline
TEST BANK For Accounting Information Systems, 3rd Edition by Vernon Richardson, Verified Chapters 1 - 18, Complete Newest Version
TEST BANK For Accounting Information Systems, 3rd Edition by Vernon Richardson, Verified Chapters 1 - 18, Complete Newest Version
TEST BANK For Accounting Information Systems, 3rd Edition by Vernon Richardson, Verified Chapters 1 - 18, Complete Newest Version
Hypertension and it's role of physiotherapy in it.Vishal kr Thakur
This particular slides consist of- what is hypertension,what are it's causes and it's effect on body, risk factors, symptoms,complications, diagnosis and role of physiotherapy in it.
This slide is very helpful for physiotherapy students and also for other medical and healthcare students.
Here is summary of hypertension -
Hypertension, also known as high blood pressure, is a serious medical condition that occurs when blood pressure in the body's arteries is consistently too high. Blood pressure is the force of blood pushing against the walls of blood vessels as the heart pumps it. Hypertension can increase the risk of heart disease, brain disease, kidney disease, and premature death.
Hypertension and it's role of physiotherapy in it.
Health Information Standards & Overview of HL7 Standards (April 30, 2019)
1. 1
HL7 Standards
Nawanan Theera-Ampornpunt, M.D., Ph.D.
Faculty of Medicine Ramathibodi Hospital
Certified HL7 CDA Specialist
Some slides reproduced & adapted with permission from
Dr. Supachai Parchariyanon
April 30, 2019
2. 2
Nawanan Theera-Ampornpunt
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
Assistant Dean for Informatics
Faculty of Medicine Ramathibodi Hospital
nawanan.the@mahidol.ac.th
www.facebook.com/InformaticsRound
Research interests:
• EHRs & health IT applications in clinical settings
• Health IT adoption
• Health informatics education & workforce development
3. 3
Outline
• Introduction to Standards & Interoperability
• What is Health Level Seven (HL7)?
• What HL7 does?
• HL7 Version 2
• HL7 Version 3 Messaging Standard
• Reference Information Model (RIM)
• Clinical Document Architecture (CDA)
Slide reproduced/adapted from Dr. Supachai Parchariyanon
5. 5
Standards: Why?
• The Large N Problem
N = 2, Interface = 1
# Interfaces = N(N-1)/2
N = 3, Interface = 3
N = 5, Interface = 10
N = 100, Interface = 4,950
6. 6
Health Information Exchange (HIE)
Hospital A Hospital B
Clinic D
Policymakers
Patient
at Home
Hospital C
HIE Broker
9. 9
Various Kinds of Standards
• Unique Identifiers
• Standard Data Sets
• Vocabularies & Terminologies
• Exchange Standards
– Message Exchange
– Document Exchange
• Functional Standards
• Technical Standards: Data Communications,
Encryption, Security
10. 10
Functional
Semantic
Syntactic
How Standards Support Interoperability
Technical Standards
(TCP/IP, encryption,
security)
Exchange Standards (HL7 V2,
HL7 V3 Messaging, HL7 FHIR,
HL7 CDA, DICOM)
Vocabularies, Terminologies,
Coding Systems (ICD-10, ICD-9,
CPT, SNOMED CT, LOINC)
Information Models (HL7 V3 RIM,
ASTM CCR, HL7 CCD)
Standard Data Sets
Functional Standards (HL7 EHR
Functional Specifications)
Some may be hybrid: e.g. HL7 V3, HL7 CCD
Unique ID
11. 11
What is HL7?
• HL7 is an ANSI-accredited Standards
Development Organization (SDO)
operating in the healthcare arena.
• It is a non-profit organization made up of
volunteers – providers, customers,
vendors, government, etc.
Slide reproduced/adapted from Dr. Supachai Parchariyanon
12. 12
What is HL7? (Cont.)
• HL7 is an acronym for Health Level Seven
– Seven represents the highest, or “application”
level of the International Standards
Organization (ISO) communications model for
Open Systems Interconnection (OSI) networks.
Slide reproduced/adapted from Dr. Supachai Parchariyanon
14. 14
What HL7 does?
• HL7 focuses on the clinical and administrative
data domains.
• It defines data exchange standards for these
domains called messages or messaging
specifications (aka HL7 messages)
– Messages are developed by technical committees and
special interest groups in the HL7 organization.
• HL7 organization defines 2 versions of the
messaging standard:
– HL7 v2.x (syntactic only)
– HL7 v3.0 (semantic capability added)
Slide reproduced/adapted from Dr. Supachai Parchariyanon
16. 16
HL7 Standards
• HL7 V2.x
– Defines electronic messages supporting hospital
operations
• HL7 V3
• HL7 Clinical Document Architecture
(CDA) Releases 1 and 2
• HL7 Arden Syntax
– Representation of medical knowledge
• HL7 EHR & PHR Functional Specifications
• Etc.
17. 17
The Industry Standard
HL7 Version 2 (HL7 V2)
• Not “Plug and Play” - it provides 80 percent of the
interface and a framework to negotiate the remaining 20
percent on an interface-by-interface basis
• Historically built in an ad hoc way because no other
standard existed at the time
• Generally provides compatibility between 2.X versions
• Messaging-based standard built upon pipe and hat
encoding
• In the U.S., V2 is what most people think of when people
say “HL7″
Slide reproduced/adapted from Dr. Supachai Parchariyanon
18. 18
HL7 version2
• HL7 V2 is still the most commonly used HL7
standard
– Over 90% of US hospitals have implemented some
version of 2.x HL7 messages
• The HL7 V2 messaging standard is considered:
– The workhorse of data exchange in healthcare
– The most widely implemented standard for healthcare
information in the world
• HL7 V2.5 was approved as an ANSI standard in
2003
• HL7 is currently working on version 2.7
Slide reproduced/adapted from Dr. Supachai Parchariyanon
19. 19
HL7 V2 Message
• Composed of reusable segments, each
identified by a 3-letter mnemonic
• All messages must start with header segment
MSH which includes sender, receiver, date-
time, message identifier, message type, and
trigger event
• Segments used in a message are determined
by message type
Slide reproduced/adapted from Dr. Supachai Parchariyanon
20. 20
Part of Sample HL7 V2 Message
(Lab Result)
OBX|1|NM|10839-9^TROPONIN-I^LN||5|ng/ml|
0-1.3|H||H|F|19980309…
21. 21
HL7 Basic Transaction Model
send
HL7 ADT
A01 msg
receive HL7
ACK msg
ADT system
Lab system
Receive A01,
send ACK
(external) admit
event
trigger event
network
Slide reproduced/adapted from Dr. Supachai Parchariyanon
22. 22
Patient Admission Scenario,
Inform Lab System
• Trigger event is admission : A01
• Message type is: ADT
• Messages composed of:
– MSH (message header)
– PID (patient identification)
– PV1 (visit data)
Slide reproduced/adapted from Dr. Supachai Parchariyanon
23. 23
HL7 V2 Message
• Messages composed of
– Segments composed of
• Fields composed of
– Components
• Delimiters
– Field separator: |
– Component separator: ^
– Repetition separator: ~
– Escape character:
– Subcomponent: &
– Segment terminator: <cr>
Slide reproduced/adapted from Dr. Supachai Parchariyanon
24. 24
Message Header Segment - MSH
MSH|^~|&|SMS|OR2|TMR|SICU|201010191535|password|ADT^A01|MSG1632|P|2.7<cr>
Sending
Unit
Receiving
Unit Date
Time
Message
type
Trigger
ID
Sending
Place Receiving
Place
Message
Number
version
Delimiters
production
Slide reproduced/adapted from Dr. Supachai Parchariyanon
25. 25
PID Segment – 1/3
PID|Z12345^5^M11||||PATIENT^JOSEPH^M^IV|
Patient ID
Check digit
Method
Last name
First name
Middle
Initial
Suffix
Patient name
Null fields
Data field
Field delimiter
Slide reproduced/adapted from Dr. Supachai Parchariyanon
26. 26
PID Segment – 2/3
MAIDEN|19610605|M||C|1492 OCEAN STREET^
Mother’s
maiden name
Gender
Date of birth Race
Street
address
Data component Component
delimiter
Slide reproduced/adapted from Dr. Supachai Parchariyanon
27. 27
PID Segment – 3/3
DURHAM^NC^27705|DUR|(919)684-6421<cr>
City
State
Zip Code
County
Telephone
Segment terminator
Slide reproduced/adapted from Dr. Supachai Parchariyanon
31. 31
Problems with HL7 v2
• HL7 v2 cannot support all this!
– Ad Hoc design methodology
– Ambiguous – lacking definition
– Complicated, esoteric encoding rules.
– Artifacts left to retain backward compatibility
– Too much optionality
– Can’t specify conformance
– No standard vocabulary
Slide reproduced/adapted from Dr. Supachai Parchariyanon
32. 32
What’s Different About V3?
• Conceptual foundation
– A single, common reference information model to be used across
HL7
• Semantic foundation
– Explicitly defined concept domains drawn from the best
terminologies
• Abstract design methodology
– That is technology-neutral
– Able to be used with whatever is the technology de jour
• XML, UML, etc.
• Maintain a repository
– Database of the semantic content
– Ensures a single source and enable development of support
tooling
Slide reproduced/adapted from Dr. Supachai Parchariyanon
33. 33
How is V3 different than V2?
• V3 is approaching “Plug and Play”
• V2 uses pipe and hat messaging, while V3
uses the Reference Information
Model(RIM) and XML for messaging
• V3 is a brand new start – it is NOT
backward compatible with V2
Slide reproduced/adapted from Dr. Supachai Parchariyanon
34. 34
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)
35. 35
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
36. 36
V3 Messaging Standard
• Based on an object information model, called the
Reference Information Model, (RIM)
– This model is “abstract,” that is, it is defined without
regard to how it is represented in a message “on the
wire” or in a “service architecture” method or in a
“clinical document”
– In fact, each of these representations can contain the
same “instance” of information
• Consequently, can be extended incrementally
when new clinical information domains need to
be added, in a way that doesn’t require changing
what has already been created
Slide reproduced/adapted from Dr. Supachai Parchariyanon
37. 37
HL7 V3 Messaging
• V3 provides messaging standards for
– Patient administration
– Medical records
– Orders
– Laboratory
– Claims & Reimbursement
– Care provision
– Clinical genomics
– Public Health
– Etc.
39. 39
HL7 V3 Reference
Information Model
• Referral
• Transportation
• Supply
• Procedure
• Consent
• Observation
• Medication
• Administrative act
• Financial act
• Organization
• Place
• Person
• Living Subject
• Material
• Patient
• Member
• Healthcare facility
• Practitioner
• Practitioner assignment
• Specimen
• Location
Entity
0..*
1
Role
1
0..*
1
0..*
Act
Relationship
1..*
10..*
1
Participation Act
• Author
• Reviewer
• Verifier
• Subject
• Target
• Tracker
• Has component
• Is supported by
Slide reproduced/adapted from Dr. Supachai Parchariyanon
40. 40
HL7 V3 Components and Process:
RIM UML Instance Scenario
Classes are color coded:
◼ Green = Entity, Yellow = Role, Blue = Participation, Red/Pink = Act, Purple = Infrastructure, Lilac = message
controller.
John Doe Patient Subject
Entity Role Participation Act
Dr. Smith
HealthCare
Provider
Surgeon
John Doe Patient Subject
Has Pertinent
InformationAct Relationship
(Clinical Trial Act)
Protocol ECOG
1112
XYZ
Hospital
HealthCare
Facility
Location
(Procedure Act)
Prostectomy
Slide reproduced/adapted from Dr. Supachai Parchariyanon
42. 42
Source: “What is CDA R2? by Calvin E. Beebe
at HL7 Educational Summit in July 2012
43. 43
The HL7 V3 Solution
• Approaching “Plug and Play” - less of a
“framework for negotiation”
• Utilizes RIM for data model
• Utilizes XML as transport method
• HL7 V3 is not the next release of HL7 V2 -
It is a paradigm shift
Slide reproduced/adapted from Dr. Supachai Parchariyanon
44. 44
The HL7 V3 Solution (Cont.)
• HL7 V3 addresses the problems of HL7 V2
by:
– Reducing HL7 V2 optionality
– Including testable conformance rules
• HL7 V3 is based on a formal development
methodology:
– Follows an Object Oriented (OO) approach
– Uses Universal Modeling Language (UML) principles
• Most importantly, HL7 V3 supports
semantic interoperability
Slide reproduced/adapted from Dr. Supachai Parchariyanon
45. 45
Interoperability in HL7 V3
• The Four Pillars of Semantic
Interoperability in HL7 V3
– A common Reference Information Model (RIM) which
spans the entire patient care, administrative and
financial healthcare universe
– A well-defined and tool-supported process for deriving
data exchange specifications ("messages") from the
RIM
– A formal and robust Data Type Specification upon
which to ground the RIM
– A formal methodology for binding concept-based
terminologies (vocabulary) to RIM attributes
Slide reproduced/adapted from Dr. Supachai Parchariyanon
46. 46
HL7 Model Repository
• Database holding the core of HL7
semantic specifications
– RIM
– Storyboards
– Vocabulary domains
– Interaction models
– Message designs
– Message constraints
Slide reproduced/adapted from Dr. Supachai Parchariyanon
48. 48
Navigating the V3 Ballot
Publication
Slide reproduced/adapted from Dr. Supachai Parchariyanon
49. 49
Navigating the V3 Ballot
Publication
• Domains: The Functional Content of the
Publication
– Universal Realm Domains
• Administration Domains
• Health and Clinical Practice Domains
• Common Use Domains
– US Realm domains
• Medicaid Information Technology Architecture
(MITA)
– Other realm specific domains..
Slide reproduced/adapted from Dr. Supachai Parchariyanon
50. 50
Domain Publication
Structure
Each Realm contains a collection of
Domains. Domains are further divided into
Topics
• Domain
• Topic
Slide reproduced/adapted from Dr. Supachai Parchariyanon
51. 51
V3 Messaging Concerns
• Difficult to implement
• No one understands V3
• Overhead too much
– 1% of message is payload compared to V2
(delimiters) is about 90-95%
• No one understands what implementation of V3
messaging means
• Need stability, clarity, definition of V3 messaging
Slide reproduced/adapted from Dr. Supachai Parchariyanon
52. 52
The Future of HL7 Standards
• FHIR: Fast Healthcare Interoperability
Resources
– Pronounced “Fire”
• FHIR defines a set of “Resources” that
represent granular clinical concepts, which
can be managed in isolation, or
aggregated into complex documents
• Resources are based on simple XML or
JSON structures, with an http-based
RESTful protocol
http://wiki.hl7.org/index.php?title=FHIR
53. 53
HL7 Clinical Document
Architecture (CDA)
Nawanan Theera-Ampornpunt, M.D., Ph.D.
Department of Community Medicine
Faculty of Medicine Ramathibodi Hospital
Certified HL7 CDA Specialist
Some slides reproduced & adapted with permission from
Dr. Supachai Parchariyanon
54. 54
Message Exchange
• Goal: Specify format
for exchange of data
• Internal vs. external
messages
• Examples
▪ HL7 V2
▪ HL7 V3 Messaging
▪ DICOM
▪ NCPDP
Document Exchange
• Goal: Specify format
for exchange of
“documents”
• Examples
▪ HL7 V3 Clinical Document
Architecture (CDA)
▪ ASTM Continuity of Care
Record (CCR)
▪ HL7 Continuity of Care
Document (CCD)
Exchange Standards
55. 55
Messages
• Human Unreadable
• Machine Processable
Clinical Documents
• Human Readable
• (Ideally) Machine
Processable
Exchange Standards
56. 56
Hospital A Hospital B
Clinic C
Government
Lab Patient at Home
Message Exchange
Message
Message
Message
Message
Message
57. 57
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
58. 58
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!!
59. 59
What is CDA?
• CDA is based on XML
• XML is eXtensible Markup Language
• In XML, structure & format are conveyed
by markup which is embedded into the
information
Slide reproduced/adapted from Dr. Supachai Parchariyanon
61. 61
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
62. 62
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
63. 63
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
64. 64
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
65. 65
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
66. 66
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
67. 67
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
68. 68
Scope of CDA
Lab Technician Physician
Lab Report
Create
document
Process &
Store
document
Transmit
document
CDA
69. 69
Scope of document content
• Clinical content of the documents is
defined by the RIM and not by CDA.
• CDA only standardizes the structure and
semantics required to exchange
documents.
Slide reproduced/adapted from Dr. Supachai Parchariyanon
70. 70
Goals of CDA (1)
• Give priority to delivery of patient care
• Allow cost effective implementation across
as wide a spectrum of systems as possible
• Support exchange of human-readable
documents between users, including those
with different levels of technical
sophistication
• Promote longevity of all information
encoded according to this architecture
Source: HL7 CDA R2
71. 71
Goals of CDA (2)
• Enable a wide range of post-exchange
processing applications
• Be compatible with a wide range of document
creation applications
• Promote exchange that is independent of the
underlying transfer or storage mechanism
• Prepare the design reasonably quickly
• Enable policy-makers to control their own
information requirements without extension to this
specification
Source: HL7 CDA R2
72. 72
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
73. 73
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
74. 74
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
75. 75
CDA As Payload
Source: From “What is CDA R2? by Calvin E. Beebe
at HL7 Educational Summit in July 2012
76. 76
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
79. 79
Major Components of a CDA
• A CDA document is wrapped by the
<ClinicalDocument> element, and contains a
header and a body.
• The header lies between the <ClinicalDocument>
and the <StructuredBody> elements and identifies
and classifies the document and provides
information on authentication, the encounter, the
patient, and the involved providers.
Slide reproduced/adapted from Dr. Supachai Parchariyanon
85. 85
Rendering CDA Documents (1)
Source: From “What is CDA R2? by Calvin E. Beebe
at HL7 Educational Summit in July 2012
86. 86
Rendering CDA Documents (2)
Source: From “What is CDA R2? by Calvin E. Beebe
at HL7 Educational Summit in July 2012
87. 87
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
88. 88
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)
89. 89
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)
90. 90
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
91. 91
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)
92. 92
CDA 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)
93. 93
CDA 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
▪ Most likely early use cases for CDA
▪ Referrals
▪ Claims & Reimbursements
▪ Lab/imaging Reports
▪ Electronic Health Records Documents
94. 94
HL7: Take Home Message
• HL7 is not panacea and so does other standards
• People and processes matter most
• Do not aim to build HIS to comply with HL7
specification but do aim to let it be able to
communicate to another systems via HL7
• Most specifications in standards and
interoperability provide framework but not
implementation guide, at times you need experts
Slide reproduced/adapted from Dr. Supachai Parchariyanon
95. 95
Additional Information
• Health Level Seven http://www.hl7.org
• HL7 Reference Information Model
– https://www.hl7.org/library/data-model/RIM/C30202/rim.htm
• HL7 Vocabulary Domains
– http://www.hl7.org/library/data-model/RIM/C30123/vocabulary.htm
• HL7 v3 Standard
– http://www.hl7.org/v3ballot/html/welcome/environment/index.htm
• HL7 v3:
– “Driving Interoperability & Transforming Healthcare Information
Management” by Charles Mead, MD, MSc.
– http://www.healthcare-informatics.com/webinars/05_20_04.htm
• FHIR: http://www.hl7.org/implement/standards/fhir/
Slide reproduced/adapted from Dr. Supachai Parchariyanon