HL7 CDA (Clinical Document Architecture) in Structured Diagnostic Reporting



Similar documents
The Continuity of Care Document. Changing the Landscape of Healthcare Information Exchange

HL7 Clinical Genomics and Structured Documents Work Groups

HL7 and DICOM based integration of radiology departments with healthcare enterprise information systems

HL7 Clinical Document Architecture: Overview and Applications

HL7 & HL7 CDA: The Implementation of Thailand s Healthcare Messaging Exchange Standards Nawanan Theera-Ampornpunt, M.D., Ph.D.

DICOM Structured Reporting Overview

Model-Driven Health Tools (MDHT) CDA Tools Overview.

EHR Standards and Semantic Interoperability

Presenter. Deborah Kohn, MPH, RHIA, CHE, CPHIMS Principal Dak Systems Consulting San Mateo, CA

Implementing Consolidated-Clinical Document Architecture (C-CDA) for Meaningful Use Stage 2. ONC Implementation and Testing Division April 5, 2013

IHE Australia Workshops July Prepared by: Heather Grain Chair: Standards Australia IT14 Health Informatics and Ehealth Education

AN HL7/CDA FRAMEWORK FOR THE DESIGN AND DEPLOYMENT OF TELEMEDICINE SERVICES

HL7 and Meaningful Use

Clinical Interoperability to Improve Quality and the Point-of-Care of EHR

HL7 Clinical Document Architecture (CDA)

Trends in Healthcare Information Standardization

MDHT Capabilities & Success Story

Success of DICOM standard

IHE Patient Care Coordination (PCC) Technical Framework Supplement. Referral/Order Linking (ROL) Trial Implementation

Using Archetypes with HL7 Messages and Clinical Documents. Heath Frankel HL7 Working Group Meeting 14 January 2011

Cancer Reporting Errata and Clarification Document for Electronic Health Record (EHR) Technology Certification December 2012

Clinical Document Exchange Integration Guide - Outbound

NATIONAL EHEALTH ARCHITECTURE - FROM STRATEGY TO PRACTICE. Ministry of Social Affairs and Health, Finland

HL7 Clinical Document Architecture, Release 2.0

IHE IT Infrastructure Cross Enterprise Document Sharing XDS Integration Profile

Relationship of HL7 EHR System Draft Standard to X12N

SINTERO SERVER. Simplifying interoperability for distributed collaborative health care

CDA for Common Document Types: Objectives, Status, and Relationship to Computer-assisted Coding

JiveX Enterprise PACS Solutions. JiveX HL7 Gateway Conformance Statement - HL7. Version: As of

HL7 Conformance Statement

Stage 2 Eligible Professional Meaningful Use Core Measures Measure 15 of 17 Last Updated: August, 2015

Reporting Workflow: IHE Solutions for Structured Reporting CDA and Beyond

MFI 4 Extended Registry SC32/WG2

Electronic Submission of Medical Documentation (esmd) CDA Digital Signatures. January 8, 2013

HIE Ready 2.0 SPECIFICATIONS MATRIX. Product Name: Version Number: Preferred Message and Trigger

Consolidated Clinical Data Architecture

IHE Eye Care Technical Framework Supplement. Unified Eye Care Workflow Refractive Measurements (U-EYECARE Refractive) Draft for Public Comment

EHR Interoperability Framework Overview

IHE Pharmacy Technical Framework Supplement. Pharmacy Medication List (PML) Trial Implementation

RSNA 2015 RCA22 A Practical Introduction to Structured Reporting Tools and Resources. DICOM Structured Reports (SR)

ISO/HL EHR System Functional Model Standard

HIE Services & Pricing

HIE Services & Pricing

MHS EMR Program. EMR HIE Integration Toolkit

EHR Standards Landscape

TechNote. Enterprise EMR Integration. 1 Overview. 2 DR Systems Integration with Referring Physician EMR Systems

The use of ehealth standards in Norway

Community Behavioral Health. PW 0214 Executive Summary

Sharing images and documents between Enterprise VNAs Using IEP and XDS standards. Dave Harvey MRCP FRCR Medical Connections Ltd

Designing ETL Tools to Feed a Data Warehouse Based on Electronic Healthcare Record Infrastructure

Goals. Accelerating adoption & exchange of EHRs project. Evaluation Indicators EMR adoption (Hospitals) 20% (100 hospitals)

CDX Conformance Profile EMR System Conformance CDA Level 1

Adoption of HL7 Standards in Taiwan

HIMSS Interoperability Showcase 2011

MDM and SOA Timo Itälä T

From HITSP to HL7 EHR System Function and Information Model (EHR-S FIM) Release 3.0 Interoperability Specifications a Ten Year Journey

EHR STRATEGY FINLAND. Kari Harno Helsinki University Central Hospital

What s next for openehr. Sam Heard Thomas Beale

Greek ehealth Strategy under public consultation

South Carolina Health Information Exchange (SCHIEx)

Interoperability and Integrating the Healthcare Enterprise

ADVANCED MEDICAL SYSTEMS PTE LTD Singapore Malaysia India Australia JiveX Medical Archive All medical information in one location

There has to be more: iconnect Blends XDS and Image Exchange. A Merge White Paper

Implementation of a Population Health and Quality Reporting System for FQHCs

10,59 00,00 10,59 7,47 6,42 Many Topics 5,34 6,83

The Importance of IHE Cardiology Profiles. Herman Oosterwijk

New York ehealth Collaborative. Health Information Exchange and Interoperability April 2012

Benefits of Image-Enabling the EHR

A Framework for Testing Distributed Healthcare Applications

HL7 V2 Implementation Guide Authoring Tool Proposal

IHE s Contribution to Telecardiology. Nick Gawrit, heartbase Antje Schroeder, Siemens Healthcare Paul Dow, ACC Charles Parisot, GE

Setting the World on FHIR

Transcription:

RSNA Forum on Structured Reporting HL7 CDA (Clinical Document Architecture) in Structured Diagnostic Reporting Fred M. Behlen, Ph.D. American College of Radiology Co-Chair, DICOM Working Group 20 & HL7 Imaging Integration SIG Former Co-Chair, HL7 Structured Document TC Co-Editor, HL7 CDA Release 2 Co-Editor, HL7 CDA Diagnostic Imaging Report Implementation Guide President, LAITEK Inc., Homewood, IL

Goals of this talk Promote use of standards for SR results Reporting results are needed in many environments and at future times Standards facilitate communication across proprietary boundaries and through time Not to teach the CDA standards, but let you know what s there, what it s for, when to use it, how to get it. 2

Role of CDA CDA is for exchange Not an authoring template. Original design of CDA always envisioned that applications would use some internal document template and then transform to CDA for exchange CDA is for representing medical data in permanent records. CDA is a key part of HL7 V3 V3 messaging uptake mostly in government projects CDA is finding much wider use 3

CDA Use Cases Diagnostic and therapeutic procedure reports Encounter / discharge summaries Patient history & physical Referrals / prescriptions Uniform format for all clinical documents Fairly strict for header Flexible for body content 4

Sending & Storing CDA HL7 V.2 MDM messages ORU messages DICOM Storage on DICOM media 1.2.840.10008.5.1.4.1.1.104.2 (Encapsulated CDA Storage SOP Class) IHE XDS 5

Key Aspects of the CDA CDA documents are encoded in XML CDA documents derive their meaning from the HL7 Reference Information Model (RIM ) and use HL7 V3 data types A CDA document consists of a header and a body Header is consistent across all clinical documents - identifies and classifies the document, provides information on patient, provider, encounter, and authentication Body contains narrative text / multimedia content (level 1), optionally augmented by coded equivalents (levels 2 & 3) 6

CDA Release 2 Information Model Header Start Here Body Participants ID/ Type Context Sections/ Headings Clinical Statements/ Coded Entries Extl Refs 7

CDA Structured Body Arrows are Act Relationships Has component, Derived from, etc. Entries are coded clinical statements Structured Body Observation, Procedure, Substance administration, etc. Section Text Section Text Section Text Section Text Section Text Section Text Entry Coded statement Entry Coded statement Entry Coded statement 8

Hard Pill to Swallow CDA requires human-readable Narrative Block, all that is needed to reproduce the legally attested clinical content CDA allows optional machine-readable coded Entries, which drive automated processes Narrative may be flagged as derived (act relationship code = DRIV) from Entries Textual rendering of coded entries content, and contains no clinical content not derived from the entries WHY: General method for coding clinical statements is a hard, unsolved problem Very difficult to project rendering capability into all current and future viewing environments If you re creating a CDA report with coded content, you should know how to render it, so do it now and store it along with the coded content. Attestation applies only to the narrative content, but that does not mean that the coded content is allowed to be wrong. 9

Narrative and Coded Entry Example 10

CDA Implementation Guides Balloted as HL7 Informative Documents Describe what amount to templates for CDA Documents. Specify constraints on CDA content Some provide Schematron tools for validation of instances Each Implementation Guide has a Template ID attribute that is included in the root element of the conforming document Continuity of Care Document IG developed in cooperation with ASTM Diagnostic Imaging Report IG developed in cooperation with DICOM, together with SR CDA transformation in (pending) Supplement 135. 11

Summary CDA is a useful format for communicating structured diagnostic reports to clinical user and EHR settings CDA Diagnostic Report Implementation Guide provides direction for encoding of header components Pending DICOM Supplement 135 provides guidance for transformation of DICOM SR into CDA CDA Standards are available at http://www.hl7.org, but, yeah, HL7 will want you to join and/or pay. 12