Implementing GI Quality Measures: Where does the HL7 Clinical Document Architecture fit? June 09, Bob Dolin, MD



Similar documents
Digital Imaging and Communications in Medicine (DICOM) Part 20: Transformation of DICOM to and from HL7 Standards

The ASTM/HL7 Continuity of Care Document. HIMSS 2008 Liora Alschuler

Implementation Guide for Study Design Structured. Document. FDA Guidance for Human Clinical Trials

The HL7 Clinical Document Architecture. HIMSS 2008 Liora Alschuler

HL7 Clinical Document Architecture: Overview and Applications

IHE Pharmacy Technical Framework Supplement. Pharmacy Dispense (DIS) Trial Implementation

DICOM Correction Proposal

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

CMS Implementation Guide for Quality Reporting Document Architecture Category I and Category III

Implementation Guide for CDA Release 2.0 Progress Note (U.S. Realm) Draft Standard for Trial Use Levels 1, 2, and 3 First Ballot September 2010

HL7 Clinical Document Architecture, Release 2.0

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

NIST GCR Templated CDA: Key Concept for Interoperability

DRAFT CMS Implementation Guide for Quality Reporting Document Architecture Category I and Category III

HL7 and SOA Based Distributed Electronic Patient Record Architecture Using Open EMR

Outline. Vision for Delivering Quality Care Do the Right Thing. Lessons from Quality

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

SMART C CDA Collaborative Perspective & Debriefing

Reconciliation of Clinical Content and Care Providers (RECON) Draft for Public Comment

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

MDHT Capabilities & Success Story

Shelly Spiro, Executive Director, Pharmacy HIT Collaborative reports no relevant financial relationships.

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

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

HL7 & Meaningful Use. Charles Jaffe, MD, PhD CEO Health Level Seven International. HIMSS 11 Orlando February 23, 2011

Asthma Intervention. An Independent Licensee of the Blue Cross and Blue Shield Association.

HL7 Clinical Genomics and Structured Documents Work Groups

OECD Workshop on Pharmacogenetics

CDA and CCD for Patient Summaries

The HL7 Electronic Health Record Technical Committee is focused on standards applicable to EHR Systems and EHR Records.

Quality, Research and Public Health (QRPH) Technical Framework Supplement. Physician Reporting to a Public Health Repository Cancer Registry (PRPH-Ca)

Quality Reporting Under Meaningful Use Stage 2. Crystal Kallem, Director of Business Analysis & Policy Lantana Consulting Group

How To Use A Pharmacy To Help Your Health Care System

An Overview of Asthma - Diagnosis and Treatment

PTE Pediatric Asthma Metrics Reporting Updated January 2015

Pre-Operative Services Teaching Rounds 2 Jan 2011

Subject ID: Subject Initials Date completed Interviewer. Person answering questions. 1 yes 2 no

HL7v3, the vocabulary. Marc de Graauw

Ontology Content Patterns - A Quick Overview

How To Improve Data Collection

May 7, Re: RIN 0991-AB82. Dear Secretary Sebelius:

Healthcare Information Technology Standards Panel

Classifying Asthma Severity and Initiating Treatment in Children 0 4 Years of Age

What You Should Know About ASTHMA

Managing Asthma Long Term

Current Problems of CITI Lab

Pathway for Diagnosing COPD

THE STIMULUS AND STANDARDS. John D. Halamka MD

HL7 Personal Health Record System Functional Model and Standard & Industry Update

EHR Standards Landscape

HL7 CDA (Clinical Document Architecture) in Structured Diagnostic Reporting

Information for Behavioral Health Providers in Primary Care. Asthma

Healthcare Data: Secondary Use through Interoperability

Health IT Enabled Quality Measurement and Improvement: The HL7 Clinical Quality Information Workgroup

Advanced Aspects of Hospital Information Systems

EHR Exchange and TMT

IHE Pharmacy Technical Framework Supplement. Medication Treatment Plan (MTP) Trial Implementation

Beacon User Stories Version 1.0

PULMONARY FUNCTION TESTS A Workshop on Simple Spirometry & Flow Volume Loops

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

Clinical Research Pediatric Pulmonary Division

Recommendation for Complete Electronic Health Records and Patient Privacy Protection in the Stimulus Bill. January 15, 2009

The patient s response to therapy within the first hour in the Emergency Room is one of the most reliable ways to predict need for hospitalization.

ISO/HL EHR System Functional Model Standard

Strategies for Improving Patient Outcomes in Pediatric Asthma Through Education. Pediatric Asthma. Epidemiology. Epidemiology

Online Public Health Level Seven

Meaningful Use - HL7 Version 2

Meaningful Use Stage 2 Update: Deploying SNOMED CT to provide decision support in the EHR

How To Analyze Data From A Patient Record

Logistics. Registration for free continuing education (CE) hours or certificate of attendance through TRAIN at:

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

Your Go-to COPD Guide

Board Presentation: Overview of Current Activity

Severe asthma Definition, epidemiology and risk factors. Mina Gaga Athens Chest Hospital

Implementation Guide for CDA Release 2 Genetic Testing Report (GTR)

ehr Sharable Data Vicky Fung Senior Health Informatician ehr Information Standards Office

Achieving Quality and Value in Chronic Care Management

Asthma in Infancy, Childhood and Adolescence. Presented by Frederick Lloyd, MD Palo Alto Medical Foundation Palo Alto, California

Towards Semantic Interoperability in Healthcare: Ontology Mapping from SNOMED-CT to HL7 version 3

Testimony for National Committee on Vital and Health Statistics Subcommittee on Standards February 24, 2009

August 22, 2013 MU Office Hours Chris Lamer, PharmD, MHS, BCPS, CDE. Thursday, August 22, 13

NQF health information technology glossary. a guide to HIT jargon

equality (slide showing logos) Lantana Consulting Group

The Annual Direct Care of Asthma

Department of Surgery

Chronic Obstructive Pulmonary Disease (COPD) Admission Order Set

Il lavoro di armonizzazione. e HL7

CDX Conformance Profile EMR System Conformance CDA Level 1

Quiz 5 Heart Failure scores (n=163)

Asthma Triggers. What are they and what can be done about them?

Respiratory Concerns in Children with Down Syndrome

HL7 and Meaningful Use

Family History Information Exchange Services Using HL7 Clinical Genomics Standard Specifications

GCE AS/A level 1661/01A APPLIED SCIENCE UNIT 1. Pre-release Article for Examination in January 2010 JD*(A A)

Preventive Care Recommendations THE BASIC FACTS

Achieving Clinical Statement Interoperability using R-MIM and Archetype-based Semantic Transformations

American Osteopathic College of Occupational and Preventive Medicine 2012 Mid-Year Educational Conference St. Petersburg, Florida

Tests. Pulmonary Functions

14 million. 4th largest U.S. Who is HCSC 9/7/2015. Cultivating EDI into E-Solutions HEALTH DENTAL LIFE DISABILITY CONNECTIVITY PHARMACY HEALTH IT

Including changes in health status since last exam. Known occupational exposures.

Transcription:

Semantically Yours, LLC. All rights reserved. Implementing GI Quality Measures: Where does the HL7 Clinical Document Architecture fit? June 09, 2009 Bob Dolin, MD BobDolin@gmail.com 1

About me Bob Dolin, MD, FACP, FACMI (BobDolin@gmail.com) HL7 Chair-elect, HL7 Board of Directors Co-chair, HL7 Structured Documents WG Co-editor, HL7 Clinical Document Architecture Co-editor, Using SNOMED CT in HL7 Version 3 US HITSP Co-chair, HITSP Foundations Committee SNOMED Prior member, SNOMED International Editorial Board Member, IHTSDO Content Committee Responsible for Kaiser Permanente s enterprise-wide SNOMED CT deployment. Semantically Yours, LLC Healthcare interoperability standards consultant 2

Outline Evolving US quality reporting framework HL7 Clinical Document Architecture Clinical scenario HL7 Quality Reporting Document Architecture 3

US Interoperability Standards development HHS federal recognition ONC oversight AHIC/NeHC - prioritization HITSP align use cases with standards CCHIT - certification NHIN implementation IHE end to end profiling SDO standards development HL7 clinical messages and documents IHTSDO clinical terminology NCPDP - medications X12 - financial HITSP HHS ONC CCHIT AHIC NHIN NCPDP HL7 X12 IHE IHTSDO 4

US Interoperability Standards development HHS ONC HIT Policy Committee HIT Standards Committee NIST NHIN NCPDP HL7 IHTSDO X12 IHE 5

Quality framework and where CDA fits feedback ONC/HITSP Quality Use Case NCQA, AMA, APQ... Measure definition The Collaborative, RAND emeasure specification Measure Development emeasure Specification NQF HITEP Quality Data Set HIMSS IHE: Multi-party choreography using HL7 messages, services CDA (QRDA) CDA (QRDA) CDA (QRDA) Aggregators, Requestors

What is the CDA? The CDA is a document markup standard for the structure and semantics of an exchanged "clinical document". A clinical document is a documentation of observations and other services with the following characteristics: Persistence Stewardship Potential for authentication Context Wholeness Human readability A CDA document is a defined and complete information object that can exist outside of a message, and can include text, images, sounds, and other multimedia content. 7

CDA Business Case CDA hits the sweet spot CDA encompasses all of clinical documents. A single standard for the entire EHR is too broad. Multiple standards and/or messages for each EHR function may be difficult to implement. CDA is just right. Implementation experience - CDA has been an ANSI standard since 2000, and has been balloted through HL7's consensus process. CDA is widely implemented. Gentle on-ramp to information exchange - CDA is straight-forward to implement, and provides a mechanism for incremental semantic interoperability. Improved patient care - CDA provides a mechanism for inserting best practices and evidence-based medicine directly into the process of care (via the same template mechanism used to build CCD), thereby making it easier to do the right thing. Lower costs CDA s top down strategy let s you implement once, and reuse many times for new scenarios. 8

Key Aspects of the CDA CDA documents are encoded in Extensible Markup Language (XML). CDA is derived from HL7's central Reference Information Model (RIM), thereby enabling data reusability - with lab or pharmacy messages, with claims attachments, clinical trials, etc. The CDA specification is richly expressive and flexible. Templates, conformance profiles, and implementation guides can be used to constrain the generic CDA specification. (More on this when we talk about CCD ) 9

Major Components of a CDA Document <ClinicalDocument>... <structuredbody> <section> <text>...</text> <observation>...</observation> <substanceadministration> <supply>...</supply> </substanceadministration> <observation> <externalobservation>... </externalobservation> </observation> </section> <section> <section>...</section> </section> </structuredbody> </ClinicalDocument> External References Narrative Block E N T R I E S S E C T I O N S Header B O D Y D O C U M E N T 10

CDA Model CDA R2 object model, showing a portion of the header and its connection to the document body. 0..1 representedorganization Organization classcode*: <= ORG determinercode*: <= INSTANCE id: SET<II> [0..*] name: SET<ON> [0..*] telecom: SET<TEL> [0..*] addr: SET<AD> [0..*] standardindustryclasscode: CE CWE [0..1] <= OrganizationIndustryClass ClinicalDocument classcode*: <= DOCCLIN moodcode*: <= EVN id*: II [1..1] code: CE CWE [1..1] <= DocumentType title: ST [0..1] effectivetime: TS [1..1] confidentialitycode: CE CWE [1..1] <= x_basicconfidentialitykind languagecode: CS CNE [0..1] <= HumanLanguage 0..* parentdocument relateddocument typecode*: <= x_actrelationshipdocument ParentDocument classcode*: <= DOCCLIN moodcode*: <= EVN id*: SET<II> [1..*] code: CD CWE [0..1] <= DocumentType text: ED [0..1] setid: II [0..1] versionnumber: INT [0..1] AssignedEntity classcode*: <= ASSIGNED id: SET<II> [1..*] code: CE CWE [0..1] <= RoleCode addr: SET<AD> [0..*] telecom: SET<TEL> [0..*] 0..1 assignedperson Person classcode*: <= PSN determinercode*: <= INSTANCE name: SET<PN> [0..*] 1..* assignedentity author typecode*: <= AUT functioncode: CE CWE [0..1] <= ParticipationFunction contextcontrolcode*: CS CNE [1..1] <= "OP" time*: TS [1..1] 0..1 assignedentity legalauthenticator typecode*: <= LA contextcontrolcode*: CS CNE [1..1] <= "OP" time*: TS [1..1] signaturecode*: CS CNE [1..1] <= ParticipationSignature 1..1 bodychoice component typecode*: <= COMP contextconductionind*: BL [1..1] "true" bodychoice NonXMLBody classcode*: <= DOCBODY moodcode*: <= EVN text: ED [1..1] confidentialitycode: CE CWE [0..1] <= x_basicconfidentialitykind languagecode: CS CNE [0..1] <= HumanLanguage StructuredBody classcode*: <= DOCBODY moodcode*: <= EVN confidentialitycode: CE CWE [0..1] <= x_basicconfidentialitykind languagecode: CS CNE [0..1] <= HumanLanguage component typecode*: <= COMP contextconductionind*: BL [1..1] "true" 1..* section 1..* assignedauthor author Section classcode*: <= DOCSECT moodcode*: <= EVN id: II [0..1] code: CE CWE [0..1] <= DocumentSectionType title: ST [0..1] text*: ED [0..1] confidentialitycode: CE CWE [0..1] <= x_basicconfidentialitykind languagecode: CS CNE [0..1] <= HumanLanguage 11

CDA Model CDA R2 object model, showing the connection from a document section to nested CDA entries. Organization classcode*: <= ORG determinercode*: <= INSTANCE id: SET<II> [0..*] name: SET<ON> [0..*] telecom: SET<TEL> [0..*] addr: SET<AD> [0..*] standardindustryclasscode: CE CWE [0..1] <= OrganizationIndustryClass DrugOrOtherMaterial LabeledDrug classcode*: <= MMAT determinercode*: <= KIND code: CE CWE [0..1] <= DrugEntity name: EN [0..1] Material classcode*: <= MMAT determinercode*: <= KIND code: CE CWE [0..1] <= MaterialEntityClassType name: EN [0..1] lotnumbertext: ST [0..1] Section classcode*: <= DOCSECT moodcode*: <= EVN id: II [0..1] code: CE CWE [0..1] <= DocumentSectionType title: ST [0..1] text*: ED [0..1] confidentialitycode: CE CWE [0..1] <= x_basicconfidentialitykind languagecode: CS CNE [0..1] <= HumanLanguage 0..1 manufacturerorganization component typecode*: <= COMP contextconductionind*: BL [1..1] "true" 0..* section entryrelationship ManufacturedProduct classcode*: <= MANU id: SET<II> [0..*] 1..1 manufactureddrugorothermaterial typecode*: <= x_actrelationshipentryrelationship contextconductionind*: BL [1..1] "true" 0..1 subject entry typecode*: <= x_actrelationshipentry contextconductionind*: BL [1..1] "true" 0..* clinicalstatement 1..1 manufacturedproduct consumable typecode*: <= CSM 0..1 manufacturedproduct * product typecode*: <= PRD 0..* clinicalstatement clinicalstatement Observation classcode*: <= OBS moodcode*: <= x_actmooddocumentobservation id: SET<II> [0..*] code*: CD CWE [1..1] <= ObservationType negationind: BL [0..1] statuscode: CS CNE [0..1] <= ActStatus effectivetime: IVL<TS> [0..1] value: ANY [0..1] targetsitecode: SET<CD> CWE [0..*] SubstanceAdministration classcode*: <= SBADM moodcode*: <= x_documentsubstancemood id: SET<II> [0..*] code: CD CWE [0..1] <= SubstanceAdministrationActCode statuscode: CS CNE [0..1] <= ActStatus effectivetime: GTS [0..1] repeatnumber: IVL<INT> [0..1] routecode: CE CWE [0..1] <= RouteOfAdministration dosequantity: IVL<PQ> [0..1] Supply classcode*: <= SPLY moodcode*: <= x_documentsubstancemood id: SET<II> [0..*] code: CD CWE [0..1] <= ActCode statuscode: CS CNE [0..1] <= ActStatus effectivetime: GTS [0..1] quantity: PQ [0..1] Procedure classcode*: <= PROC moodcode*: <= x_documentproceduremood id: SET<II> [0..*] code: CD CWE [0..1] statuscode: CS CNE [0..1] <= ActStatus effectivetime: IVL<TS> [0..1] prioritycode: CE CWE [0..1] <= ActPriority methodcode: SET<CE> CWE [0..*] approachsitecode: SET<CD> CWE [0..*] targetsitecode: SET<CD> CWE [0..*] 0..* observationrange referencerange typecode*: <= REFV 0..* criterion precondition typecode*: <= PRCN ObservationRange classcode*: <= OBS moodcode*: <= EVN.CRT code: CD CWE [0..1] <= ActCode text: ED [0..1] value: ANY [0..1] interpretationcode: CE CNE [0..1] <= ObservationInterpretation Criterion classcode*: <= OBS moodcode*: <= EVN.CRT code: CD CWE [0..1] <= ActCode text: ED [0..1] value: ANY [0..1] 12

Temperature is 36.9 C. CDA Body Entries <section> <code code="8716-3" codesystem="2.16.840.1.113883.6.1" codesystemname="loinc"/> <title>vital Signs</title> <text>temperature is 36.9 C</text> <entry> <observation classcode="obs" moodcode="evn"> <code code="386725007" codesystem="2.16.840.1.113883.6.96" codesystemname="snomed CT" displayname="body temperature"/> <statuscode code="completed"/> <effectivetime value="200004071430"/> <value xsi:type="pq" value="36.9" unit="cel"/> </observation> </entry> </section> Required narrative block Optional entries 13

CDA Body Entries Father had fatal heart attack in 1970. <section> <code code="10157-2" codesystem="2.16.840.1.113883.6.1" codesystemname="loinc"/> <title>family history</title> <text>father had fatal heart attack in 1970.</text> <entry> <observation classcode="obs" moodcode="evn"> <code code="assertion" codesystem="2.16.840.1.113883.5.4"/> <value xsi:type= CD code="22298006" codesystem="2.16.840.1.113883.6.96" codesystemname="snomed CT" displayname="mi"/> <effectivetime value="1970"/> <subject> <relatedsubject classcode="prs"> <code code="fth" codesystem= 2.16.840.1.113883.5.111 /> </relatedsubject> </subject> <entryrelationship typecode="caus"> <observation classcode="obs" moodcode="evn"> <code code="assertion" codesystem="2.16.840.1.113883.5.4"/> <value xsi:type= CD code="399347008" codesystem="2.16.840.1.113883.6.96" displayname="death"/> <effectivetime value="1970"/> </observation> </entryrelationship> </observation> </entry> 14

CDA Body Entries Suture removal from left forearm performed. <section> <code code="29554-3" codesystem="2.16.840.1.113883.6.1" codesystemname="loinc"/> <title>in-office Procedures</title> <text>suture removal from left forearm performed.</text> <entry> <procedure classcode="proc" moodcode="evn"> <code code="30549001" codesystem="2.16.840.1.113883.6.96" codesystemname="snomed CT" displayname="suture removal"> <qualifier> <name code="363704007" codesystem="2.16.840.1.113883.6.96" displayname="procedure site"/> <value code="66480008" codesystem="2.16.840.1.113883.6.96" displayname="left forearm"/> </qualifier> </code> <effectivetime value="200004071430"/> </procedure> </entry> </section> 15

CDA Body Entries Captopril 25mg PO every 12 hours <section> <code code="10160-0" codesystem="2.16.840.1.113883.6.1" codesystemname="loinc"/> <title>medications</title> <text>captopril 25mg PO every 12 hours.</text> <entry> <substanceadministration classcode="sbadm" moodcode="evn"> <effectivetime xsi:type="pivl_ts"> <period value="12" unit="h"/> </effectivetime> <routecode code="po" codesystem="2.16.840.1.113883.5.112" codesystemname="routeofadministration"/> <dosequantity value="1"/> <consumable> <manufacturedproduct> <manufacturedlabeleddrug> <code code="317172" codesystem="2.16.840.1.113883.6.88" codesystemname="rxnorm" displayname="captopril 25mg oral tablet"/> </manufacturedlabeleddrug> </manufacturedproduct> </consumable> </substanceadministration> </entry> </section> 16

The A in CDA CDA R2 consists of a single CDA XML Schema, and the architecture arises from the ability to apply one or more templates which serve to constrain the richness and flexibility of CDA. Professional society recommendations, national clinical practice guidelines, standardized data sets can be expressed as CDA templates. This presentation will describe the CDA template process, and will show how the ASTM Continuity of Care Record (CCR) data set is used as a template to constrain CDA specifically for summary documents, resulting in the HL7/ASTM Continuity of Care Document (CCD) specification. 17

The A in CDA There are many kinds of templates that might be created. Among them, two are particularly relevant for clinical documents: (1) those that constrain the document sections based on the type of document (section-level templates); (2) those that constrain the entries within document sections (entry-level templates). CDA Schema CDA Schema :: Progress Note section-level template applied. CDA Schema :: Progress Note section-level and Vital Signs entrylevel template applied. CDA Schema :: Endocrinology Progress Note section-level and Vital Signs entry-level template applied. CDA Schema :: Progress Note section-level and ICU Vital Signs entry-level template applied. CDA Schema :: Cardiology Progress Note section-level template applied CDA Schema :: Cardiology Progress Note section-level and Cardiac Exam entry-level template applied. CDA Schema :: Endocrinology Progress Note section-level template applied. CDA Schema :: Endocrinology Progress Note section-level and Vital18 Signs entry-level template applied.

CDA Templates a clinical scenario Evidence-based medicine often manifests through the creation of Clinical Practice Guidelines. Clinical Practice Guidelines are most useful when integrated into the process of care. Integration options include: Templates Alerts Clinical Practice Guidelines can be transformed into CDA templates, to guide the collection of key data elements. 19

A typical day in the office History Henry Levin, the 7th is a 67 year old male referred for further asthma management. Onset of asthma in his teens. He was hospitalized twice last year, and already twice this year. He has not been able to be weaned off steroids for the past several months. Past Medical History Asthma Hypertension Medications Theodur 200mg BID Proventil inhaler 2puffs QID PRN Prednisone 20mg qd HCTZ 25mg qd Allergies Penicillin - Hives Aspirin - Wheezing Social History Smoking :: 1 PPD between the ages of 20 and 55, and then he quit. cont... 20

A typical day in the office Physical Exam Vital Signs :: BP 196/100; Wt 185lb; Resp 16 and unlabored; T 98.6F; HR 86 and regular. Lungs :: Clear with no wheeze. Good air flow. Cardiac :: RRR with no murmur, no S3, no S4. Labs PFTs 02/03/1999: FEV1 1.2; FVC 1.9; FEV1/FVC = 0.63. CBC 02/03/1999: Hgb 15.1; WBC 7.2; PLT 279k; MCV 88. ABG 02/03/1999: (room air) po2 78; pco2 48; ph 7.38. CXR 02/03/1999: Hyperinflated. Normal cardiac silhouette, clear lungs. PFTs today: FEV1 1.4; FVC 2.0; FEV1/FVC = 0.70. Peak Flow today: 260 l/m. Assessment Asthma, with prior smoking history. Difficulty weaning off steroids. Will try gradual taper. Hypertension, poorly controlled. Add lopressor. Plan Complete PFTs with lung volumes. Chem-7 Provide educational material on inhaler usage and peak flow self-monitoring. Decrease prednisone to 20qOD alternating with 18qOD. Lopressor 25mg BID. RTC 1 week.

A typical day in the office Lab Order Form CBC with Differential Count Chem-7 Liver Enzymes Calcium Magnesium Urinalysis Theophylline level X Cardiopulmonary Order Form Test: Complete Pulmonary Function Study with Lung Volumes Arterial Blood Gas Treadmill Stress Test, Routing Echocardiogram Other (Specify) :: X Indications: Baseline evaluation Specific Questions:

A typical day in the office Health Summary Form Screening DATE DATE DATE DATE DATE DATE Colonoscopy Breast Exam Mammogram Pap Smear PSA Immunizations DATE DATE DATE DATE DATE DATE Pneumovax Influenza Education DATE DATE DATE DATE DATE DATE Cholesterol Smoking Seat Belts 23

Am I following the NHLBI guidelines? Which environmental and occupational triggers did I ask about? I forgot to ask about triggers. Have I provided proper patient education? Information to answer this question is in the narrative portion of my note. Is my assessment of asthma severity consistent with the NHLBI guidelines? NHLBI asthma severity is based on several factors, the worst of which determines diagnosis.

NHLBI Asthma Template The NHLBI Asthma Guidelines can be expressed as a CDA template. A CDA document that is authored with the NHLBI Asthma Template will conform to the CDA standard AND will conform to the additional constraints in the template. 25

NHLBI Asthma Template History Frequency of wheezing: Daily and continual. Daily but not continual. Episodes per week :: Labs Peak Flow :: l/m. Assessment Asthma, Intermittent. Asthma, Mild Persistent. Asthma, Moderate Persistent. Asthma, Severe Persistent. Plan Pneumococcal Vaccine Complete PFTs with lung volumes. Provide education on peak flow self-monitoring. Environmental and Occupational screening questionnaire. Teach inhaler/spacer/holding chamber technique. Discuss environmental control measures to avoid exposure to known allergens and irritants. Teach self-monitoring.

NHLBI Asthma Template Plan Pneumococcal Vaccine Complete X PFTs with lung volumes. Provide X education on peak flow self-monitoring. Environmental and <section> Occupational screening questionnaire. Teach inhaler/spacer/holding <templateid chamber root="2.16.840.1.113883.3.27.354 /> technique. Discuss environmental <title>plan</title> control measures to avoid exposure to known allergens and irritants. Teach self-monitoring. <text>complete PFTs with lung volumes; Provide education on peak flow self-monitoring;...</text> <entry> <observation classcode="obs" moodcode="int"> <code code="23426006" codesystem= &SNOMEDCT;" displayname="pulmonary function test"/> </observation> </entry> <entry> <act classcode="act" moodcode="int"> <code code="223468009" codesystem= &SNOMEDCT;" displayname="teaching of skills"> <qualifier> <name code="363702006" displayname="has focus"/> <value code="29893006" displayname="peak flow rate measurement"/> </qualifier> </code>

NHLBI Asthma Template NHLBI Guideline defines the Template. HL7 RIM defines the fields. Standard terminologies define the field values. And it s all packaged together in a standardized way within the CDA.

NHLBI Asthma Template atop CDA NHLBI Guideline defines the Template. HL7 RIM defines the fields. Standard terminologies define the field values. <section> <templateid root="2.16.840.1.113883.3.27.354"/> <title>plan</title> <text>complete PFTs with lung volumes; Provide education on peak flow self-monitoring;...</text> <entry> <observation classcode="obs" moodcode="int"> <code code="23426006" codesystem= &SNOMEDCT;" displayname="pulmonary function test"/> </observation> </entry> <entry> <act classcode="act" moodcode="int"> <code code="223468009" codesystem= &SNOMEDCT;" displayname="teaching of skills"> <qualifier> <name code="363702006" displayname="has focus"/> <value code="29893006" displayname="peak flow rate measurement"/> </qualifier> </code> And it s all packaged into CDA.

NHLBI Asthma Template atop CDA NHLBI Guideline defines the Template. HL7 RIM defines the fields. Standard terminologies define the field values. And it s all packaged into CDA. <section> <templateid root="2.16.840.1.113883.3.27.354"/> <title>plan</title> <text>complete PFTs with lung volumes; Provide education on peak flow self-monitoring;...</text> <entry> <observation classcode="obs" moodcode="int"> <code code="23426006" codesystem= &SNOMEDCT;" displayname="pulmonary function test"/> </observation> </entry> <entry> <act classcode="act" moodcode="int"> <code code="223468009" codesystem= &SNOMEDCT;" displayname="teaching of skills"> <qualifier> <name code="363702006" displayname="has focus"/> <value code="29893006" displayname="peak flow rate measurement"/> </qualifier> </code>

NHLBI Asthma Template atop CDA Which environmental and occupational triggers did I ask about? Have I provided proper patient education? Plan Pneumococcal <section> Vaccine X Complete PFTs <templateid with lung volumes. root="2.16.840.1.113883.3.27.354"/> X Provide education <title>plan</title> on peak flow self-monitoring. Environmental and <text>complete Occupational screening PFTs questionnaire. with lung volumes; Provide education Teach inhaler/spacer/holding on peak chamber flow self-monitoring; technique....</text> Discuss environmental <entry> control measures to avoid exposure to known allergens and irritants. Teach self-monitoring. <observation classcode="obs" moodcode="int"> <code code="23426006" codesystem= &SNOMEDCT;" displayname="pulmonary function test"/> </observation> </entry> <entry> <act classcode="act" moodcode="int"> <code code="223468009" codesystem= &SNOMEDCT;" displayname="teaching of skills"> <qualifier> <name code="363702006" displayname="has focus"/> <value code="29893006" displayname="peak flow rate measurement"/>

Is my assessment of asthma severity c/w NHLBI? Severe Persistent NHLBI Asthma Template atop CDA Symptoms (cough, wheeze, shortness of breath, chest tightness) Continual symptoms Daily limited physical activity Maintenance oral corticosteroids More than 1 steroid burst the past month History Frequency of wheezing: Daily X and continual. Daily but not continual. Labs Peak Flow :: 260 l/m. Nighttime Symptoms Frequent (at least 4 nights per week) Lung Function FEV 1 or PEF 60% predicted PEF variability >30% (AM/PM) Assessment Asthma, Intermittent. Asthma, Mild Persistent. Asthma, X Moderate Persistent. Asthma, Severe Persistent. 32

Quality Reporting Document Architecture Project Goal To standardize the framework of quality reports and to define the way quality measurement data should be structured to create interoperability between reporting and receiving systems.

Types of QRDA Reports Category 1: Single Patient Reports DSTU ballot http://www.hl7.org/dstucomments/index.cfm Category 2: Patient List Reports Informative ballot, for comments Category 3: Calculated Reports Informative ballot, for comments 34

Layout of a QRDA Cat I Report 35

Sample QRDA Category 1 Report Contains raw patient data No assertion about the status of quality compliance When pooled and analyzed, each report contributes to quality compliance

Vermont-Oxford Neonatal Admission Temperature

CHCA BMI Index Percentile Measure

Sample QRDA Category 2 Report Proposed as a multipatient level report Includes flags for each patient indicating whether the patient qualifies for the numerator, denominator, exclusion

Sample QRDA Category 3 Report Aggregate quality report Calculated summary data for one or more measures on a population

HL7 web site: http://www.hl7.org/ For more information HL7 Structured Documents listserver (public but must register to post): http://www.hl7.org/special/committees/lists.cfm CDA: strucdoc@lists.hl7.org Dolin RH, Alschuler L, Boyer S, Beebe C, Behlen FM, Biron PV, Shabo A. HL7 Clinical Document Architecture, Release 2. J Am Med Inform Assoc. 2006;13:30 39. (http://www.jamia.org/cgi/reprint/13/1/30) CDA R2 Quality Reporting Document Architecture, Draft Standard for Trial Use http://www.hl7.org/dstucomments/index.cfm 41