Transitions of Care Initiative Companion Guide to Consolidated CDA for Meaningful Use

2 Problem Statement Consolidated CDA Implementation Guide not enough for implementers – Call for public collection of implementation guidance, sample clinically-valid documents and testing procedures 2014 Edition CEHRT requirements do not provide technical specifications based on the current version of Consolidated CDA Transitions of Care Initiative implementation considerations not fully addressed in Consolidated CDA standard

3 CMS & ONC Rules: “Meaningful Use” Meaningful Use Stage 2 (MU2) CMS: Medicare and Medicaid EHR Incentive Programs Stage 2 outlines incentive payments (+$$$) for early adoption outlines reimbursement penalties (-$$$) for late adoption/non-compliance Reference: CMS Medicare and Medicaid Programs; Electronic Health Record Incentive Program – Stage 2 Final Rule ONC: Standards, Implementation Specifications & Certification Criteria(SI&CC) 2014 Edition Specifies the data and standards requirements for certified electronic healthrecord (EHR) technology (CEHRT) needed to achieve “meaningful use” Reference: ONC Health Information Technology : Standards, Implementation Specifications, and Certification Criteria for Electronic Health Record Technology, 2014 Edition; Revisions tothe Permanent Certification Program for Health Information Technology (b)(1)&(2)

4 MU2 Certification Categories & Objectives Overview Export Summary when a patient transitions from provider or setting to another, a medication reconciliation should be preformed Data Portability (b)(7) Transition of Care/Referral Summary when transitioning a patient to another care setting, the EP or EH/CAH should provide a summary care record Transition of Care (b)(1)&(2) Care Coordination MU (b) Clinical Summary provide clinical summaries for patients for each office visit Clinical Summary (e)(2) Ambulatory or Inpatient Summary patients must be able to view & download their own medical info & also be able to transmit that info to a 3 rd party View/Download/Transmit (e)(1) Patient Engagement MU (e) ObjectiveDescriptionCert. Category Req. Summary Type MU2

5 MU2 Data Requirements Example: Transition of Care Objective Transition of Care/Referral Summary when transitioning a patient to another care setting, the EP or EH/CAH should provide a summary care record Transition of Care (b)(1)&(2) Care Coordination MU (b) ObjectiveDescriptionCert. Category Summary Type MU2 Patient name Sex Date of birth Race ** Ethnicity ** Preferred language Care team member(s) Allergies ** Medications ** Care plan Problems ** Laboratory test(s) ** Laboratory value(s)/result(s) ** Procedures ** Smoking status ** Vital signs Common MU2 Data Set Provider Name & Office Contact Information (Ambulatory Only) Reason for Referral (Ambulatory Only) Encounter Diagnoses ** Cognitive Status Functional Status Discharge Instructions (Inpatient Only) Immunizations ** Objective-Specific Data Requirements NOTE: Data requirements marked with a double asterisk (**) also have a defined vocabulary which must be used

6 MU2 Vocabulary Example: Smoking Status Vocabularies are used to assign a unique value to a clinical concept SNOMED-CT values acceptable for “Smoking Status” DescriptionSNOMED-CT Code Current every day smoker Current some day smoker Former smoker Never smoker Smoker, current status unknown Unknown if ever smoked Heavy tobacco smoker Light tobacco smoker By standardizing a distinct set of codes for a clinical concept, MU2’s use of vocabularies promotes the use of common definitions when sharing information across diverse clinical environments.

7 Clinical Document Architecture (CDA) & Consolidated-CDA (C-CDA) Overview Clinical Document Architecture (CDA) is the base standard for building electronic clinical documents To help simplify implementations, commonly used templates were harmonized from existing CDA implementation guides and “consolidated” into a single implementation guide – the C-CDA Implementation Guide (IG) (07/2012) Templates provide the “building blocks” for clinical documents

8 C-CDA IG as a Single Source for 9 Key Document Templates HL7 Implementation Guide for CDA® Release 2: IHE Health Story Consolidation, Release US Realm Document Templates: 9 Continuity of Care Document (CCD) Consultation Note Diagnostic Imaging Report (DIR) Discharge Summary History and Physical (H&P) Operative Note Procedure Note Progress Note Unstructured Document Section Templates: 60 Entry Templates: 82 Continuity 0f Care Document (CCD) Allergies Medications Problem List Procedures Results Advance Directives Encounters Family History Functional Status Immunizations Medical Equipment Payers Plan of Care Document Template Section Template(s) Section templates in YELLOW demonstrate CDA’s interoperability and reusability. History & Physical (H&P) Allergies Medications Problem List Procedures Results Family History Immunizations Assessments Assessment and Plan Plan of Care Social History Vital Signs History of Present Illness Chief Complaint Reason for Visit Review of Systems Physical Exam General Status

9 MU2 Requirements Achieved using C-CDA Templates are used to specify the ‘packaging’ for those clinical concepts MU2 adds data requirements, which can be layered on top of C-CDA document templates by the EP or EH/CAH to achieve MU2 compliance Sets of CDA templates are arranged to create a purpose-specific clinical document CDA standardizes the expression of clinical concepts which can be used/re-used MU2 NOTE: No single C-CDA document template contains all of the data requirements to sufficiently meet MU2 compliance – C-CDA & MU2 guidelines must be implemented together.

10 C-CDA IG Template Definitions Referenced templates are hyperlinked in the C-CDA IG for easier navigation Each template is identified by a unique ID Template data requirements are listed as “SHALL” (required), “MAY” (optional – not shown here) or “SHOULD” (recommended) statements in the C-CDA IG.

11 Problem Statement (Revisited) Consolidated CDA Implementation Guide not enough for implementers – Call for public collection of implementation guidance, sample clinically-valid documents and testing procedures 2014 Edition CEHRT requirements do not provide technical specifications based on the current version of Consolidated CDA Transitions of Care Initiative implementation considerations not fully addressed in Consolidated CDA standard

12 Solution – Companion Guide Defines explicit mappings of data requirements in MU2 objectives to Consolidated CDA structures Provides a streamlined view of the relevant Consolidated CDA IG components that apply to MU2 objectives Includes clinically-accurate examples of Consolidated CDA components necessary to meet MU2 objectives Incorporate Transitions of Care Initiative implementation considerations

13 Companion Guide Sections SectionTitleDescription 1Introduction Overview of Companion Guide development and TOC Initiative 2General C-CDA Guidance Navigating the 503-page C-CDA IG, migration strategies (MU1 to MU2), implementation considerations for MU2 3 Implementing MU Requirements All representations of Requirements in C-CDA, best practices guidance, examples 4C-CDA Document Alignment Implementing MU2 requirements using any of the current C-CDA documents 5 Initiative Recommended Approach Specific implementation to meet MU2 requirements and needs of clinicians 6Tools & Resources Additional educational materials and tools to assist implementers AppendixClinical Best PracticesImpact on clinicians, implications of Direct

Where can I find it? Latest drafts of the Companion Guide are published at the following address: – Publication contents: – Companion Guide – Requirements-mapping spreadsheet (not yet available) – XML sample files (not yet available) Examples of recommended C-CDA Sections A complete sample CCD meeting MU2 requirements Volunteer Leads: David Tao, Dr. Holly Miller & Dr. Russell Leftwich Anticipating consensus by October 15th 14