CCD and CCR Executive Summary Jacob Reider, MD Medical Director, Allscripts.

Slides:



Advertisements
Similar presentations
Integrating the Healthcare Enterprise
Advertisements

Continuity of Care Record
DOCUMENT TYPES. Digital Documents Converting documents to an electronic format will preserve those documents, but how would such a process be organized?
Clinical Documents with HL7 CDA. HL7 CDA – Key messages CDA is the standard for electronic exchange of clinical documents; levels 1,2,3 are different.
5/3/2015. PHR is a tool for collecting, tracking and sharing important, up-to-date information about an individual’s health or the health of someone.
Healthcare Link Initiatives: Bridging Clinical Research and Healthcare May 29, 2008 Bay Area Users’ Group Landen Bain CDISC Liaison to Healthcare.
Standardized Interoperable Information and Low Cost Connections to HIE The Bridge Between LTSS and The Rest of Health Care Terrence O’Malley, MD
Companion Guide to HL7 Consolidated CDA for Meaningful Use Stage 2
Evolution of Image Sharing: A long and winding road Elliot Silver, M.Sc. Senior Standards Analyst.
Electronic Health Records
EsMD Background Phase I of esMD was implemented in September of It enabled Providers to send Medical Documentation electronically Review Contractor.
What did Continua do with CDA? Interface to EHR and PHR systems Keith Naylor December 2009.
INTRODUCTION TO WEB DATABASE PROGRAMMING
1 PDF Healthcare Overview A guide to safe access and transport of health information.
1 Charles Parisot, GE Healthcare IHE IT Infrastructure Planning Committee Co-chair IHE Update to DICOM.
Initial slides for Layered Service Architecture
Overview for IHE The MITRE Corporation. Overview hData was originally developed by The MITRE Corporation – Internal R&D – Focus on simplifying Continuity.
IHE Radiology –2007What IHE Delivers 1 Christoph Dickmann IHE Technical Committee March 2007 Cross Domain Review PCC.
Accelerating Recovery Information Technology Maturity Index Presented by: Stephen A. Wood, FHIMSS HealthCare Perspective, LLC.
Status of the CCR: Continuity of Care Record Claudia Tessier, CAE, RHIA Co-Chair, ASTM E31 Workgroup on CCR Executive Director, MoHCA Health Tech Net February.
December 15, 2011 Use of Semantic Adapter in caCIS Architecture.
 Information technology is defined as the use of computer hardware and software to manage information.  Six functions of data management: Convert.
HL7 HL7  Health Level Seven (HL7) is a non-profit organization involved in the development of international healthcare.
Patient Care Coordination Tone Southerland Greenway Medical Technologies Co-chair, IHE PCC Marcia Veenstra Senior Health Inc. Co-chair, IHE PCC Nursing.
HITSP’s Scope  The Panel’s mission is to assist in the development of a Nationwide Health Information Network (NHIN) by addressing the standards-related.
September, 2005What IHE Delivers 1 Presenters: Keith W. Boone, John Donnelly, Larry McKnight, Dan Russler IHE Patient Care Coordination.
Query Health Operations Workgroup HQMF & QRDA Query Format - Results Format February 9, :00am – 12:00am ET.
1 Health Level Seven (HL7) Report Out Population Science and Structured Documents Workgroup (SDWG) Riki Ohira September 22, 2011.
Toolkit for Planning an EHR-based Surveillance Program | HL7 Clinical Document Architecture An Introduction.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
September, 2005What IHE Delivers Content Integration Profiles Ana ESTELRICH, GIP-DMP, FRANCE Charles PARISOT, GE Grateful thanks to Charles Parisot, Keith.
Interoperability Framework Overview Health Information Technology (HIT) Standards Committee June 24, 2010 Presented by: Douglas Fridsma, MD, PhD Acting.
HIT Standards Committee Clinical Operations Workgroup Report Jamie Ferguson, Chair Kaiser Permanente John Halamka, Co-chair Harvard Medical School 20 August,
Dave Iberson-Hurst CDISC VP Technical Strategy
Clinical Document Architecture. Outline History Introduction Levels Level One Structures.
MED INF HIT Integration, Interoperability & Standards ASTM E-31 January 14, 2010 By Imran Khan.
Health Information Technology Summit Wendy Angst CapMed, Division of Bio-Imaging Technologies Inc.
Provider Data Migration and Patient Portability NwHIN Power Team August 28, /28/141.
Networking and Health Information Exchange Unit 5b Health Data Interchange Standards.
HealthBridge is one of the nation’s largest and most successful health information exchange organizations. An Overview of the IT Strategies for Transitions.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 3b National and International Standards Developing.
September, 2005Cardio - June 2007 IHE for Regional Health Information Networks Cardiology Uses.
1 Healthcare Information Technology Standards Panel Care Delivery - IS01 Electronic Health Record (EHR) Laboratory Results Reporting July 6, 2007.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Technology Issues : Getting Communities Connected Continuity of Care Record (CCR) in Connected Health Communities Get Connected Knowledge Forum June 27-29,
HIT Standards Committee Overview and Progress Report March 17, 2010.
CHAPTER 7 THE INTERNET AND INTRANETS 1/11. What is the Internet? 2/11 Large computer network ARPANET (Dept of Defense) It is international and growing.
September, 2005Cardio - June 2007 Retrieve Information for Display (RID) and Retrieve ECG for Display (ECG)
Patient Care Coordination John T. Donnelly IntePro Solutions Co-Chair, Patient Care Coordination Planning Committee.
Networking and Health Information Exchange Unit 6a EHR Functional Model Standards.
September, 2005What IHE Delivers 1 Presenters Scanned Documents.
DICOM WG10: Strategic Advisory Committee Report to DSC meeting May 7, 2002, Seoul.
Primary Goal: To support case detection and investigation for the reportable infectious diseases (conditions) using electronic information exchanges between.
Source IT System ( LIS) Consumer IT System (Certified * Ambulatory EHR) Pre-Condition: The Source has received an Order from the Consumer (either Manually.
S ecure A rchitecture F or E xchanging Health Information in Central Massachusetts Larry Garber, M.D. Peggy Preusse, R.N. June 9 th, 2005.
THE DICOM 2014 INTERNATIONAL SEMINAR August 26Chengdu, China HL7 and DICOM: Complementary Standards, Collaborating Organizations Bao Yongjian Principal.
CDA Overview HL7 CDA IHE Meeting, February 5, 2002 Slides from Liora Alschuler, alschuler.spinosa Co-chair HL7.
Integrating the Healthcare Enterprise Retrieve Information for Display (RID) Integration Profile Ellie Avraham Kodak Health Imaging IHE IT Infrastructure.
Dr. Mark Gaynor, Dr. Feliciano Yu, Bryan Duepner.
Tung Tran, Ph.D. What is the EMR? Computerized legal medical record created by healthcare organizations Enables storage and retrieval of patient information.
NAACCR CDA Pilot Project - Overview, Status, and Findings 2009 NAACCR Conference Ken Gerlach, Co-Chair, NAACCR Clinical Data Work Group; Health Scientist,
Dave Iberson-Hurst CDISC VP Technical Strategy
Networking and Health Information Exchange
Open Platforms for Innovation
Electronic Health Information Systems
Quality Measure & Interoperability Solutions
, editor October 8, 2011 DRAFT-D
Health Information Exchange for Eligible Clinicians 2019
Presentation transcript:

CCD and CCR Executive Summary Jacob Reider, MD Medical Director, Allscripts

Stadard A technical standard is an established norm or requirement. It is often represented as a formal document that establishes uniform technical criteria.

What is an SDO? A standards organization, standards body, standards development organization or SDO is any entity whose primary activities are developing, coordinating, promulgating, revising, amending, reissuing, interpreting, or otherwise maintaining standards that address the interests of a wide base of users outside the standards development organization.

SDO’s with Healthcare Standards HL7 ASTM ISO CEN (note that IHO is NOT an SDO.. IHE defines profiles that leverage existing standards)

Moving Patient Information

CCR circa 1200 BC

9 Uses of the CCR Referrals, inpatient or outpatient Transfers between institutions Discharges without a referral or transfers Enterprise specific information, e.g., home healthcare Clinical specialty information Public health purposes: routine reporting as well as disasters, terrorism, epidemics

Clinical Document Architecture “The CDA Release 2.0 provides an exchange model for clinical documents (such as discharge summaries and progress notes) …. By leveraging the use of XML, the HL7 Reference Information Model (RIM) and coded vocabularies, the CDA makes documents both machine-readable - ;so they are easily parsed and processed electronically - and human-readable - so they can be easily retrieved and used by the people who need them. CDA documents can be displayed using XML-aware Web browsers or wireless applications such as cell phones. While Release 2.0 retains the simplicity of rendering and clear definition of clinical documents formulated in Release 1.0 (2000), it provides state-of-the-art interoperability for machine-readable coded semantics. The product of 5 years of improvements, CDA R2 body is based on the HL7 Clinical Statement model, is fully RIM-compliant and capable of driving decision support and other sophisticated applications, while retaining the simple rendering of legally-authenticated narrative.” Source:

HL7 CDA HL7’s Clinical Document Architecture (CDA) is a standard for the storage or transfer of clinical documents in or between systems. – Documents: discharge summaries, progress notes, history and physical reports, prior lab results, etc. CDA defines a generic structure for delivering “any document” between systems. All messaging standards are based on the HL7 Reference Information Model (RIM) HL7 Version 3 Messaging implements the RIM and provides an XML representation

Clinical Document Architecture - Levels “… the concept of "levels" applied to CDA means the degree to which a receiver can expect to drive automated processes. A Level One CDA sets no expectations beyond the standard header metadata and human- readability for the body. A Level Two CDA means that the body is in XML and that the sections and sub-sections are coded. A Level Three CDA contains the same expectations as Levels One and Two, plus it contains some coded information within the sections.” Source: Header Metadata Body Narrative Clinical Statements Level 1 Level 2 Level 3

CCR In a nutshell Think of the CCR standard as a way to collect summary health information from one or more sources - such as diagnoses, medications, allergies, and insurance info - and organize this in a single patient-centric XML file that permits: Expression of the information as a web page, a Microsoft Word document, or an Adobe pdf document for viewing on a computer screen or printed out on paper Secure carriage and transmission of the electronic file via physical transport media, e.g. USB thumb drive, cell phone, CD ROM, or smart card Secure transmission of the electronic file via a network, e.g. LAN, T1 line, or the Internet Creation, editing, management, and reporting of the data using both proprietary electronic health records (EHRs) and (nearly) free desktop computing software, e.g. web forms, pdf forms, Firefox plug-in, and other familiar applications, as well as commercial PHRs

HL7 Continuity of Care Document HL7 to created a template to present the ASTM CCR data set in the Clinical Document Architecture Release Two (CDA R2) The HL7 CCD is likely the first “Level 3” CDA template The HL7 CCD template places a series of constraints on CDA R2

ASTM CCR and HL7 CCD ASTM CCR was designed to represent a patient summary data set aggregated from multiple sources ASTM CCR provides the capability to digitally sign individual data objects (i.e. medication) ASTM CCR does not depend on underlying representation and provides an XML representation of the data set ASTM CCR separates data from display HL7 CCD was designed to represent a patient summary document HL7 CCD provides the capability to sign the entire document HL7 CCD is derived from the Hl7 Reference Information Model; HL7 Version 3 XML; and CDA, which can be a step learning curve for developers HL7 CCD intermingles data and display by allowing inclusion of HTML in a CCD - structuring the data is completely optional CDA-based formats are explicit in specification of which element(s) are used to display information to a user whereas the CCR is ambiguous about this.

Translation? CCR  CCD? Several initiatives underway to provide translation. See discussion: Mirth some point have Open Source Channels for CCR transforms. ( )