October 2, 2008 | 2:00 – 3:30 pm (Eastern)

1. Quality • October 2, 2008 | 2:00 – 3:30 pm (Eastern) • Presenters HITSP Population Perspective Technical Committee • Floyd Eisenberg, MD, MPH, Senior Key Expert, Siemens Healthcare and co-chair of the Population Perspective TC • Lori Fourquet, e-HealthSign, LLC

2. Learning Objectives During this 90-minute webinar, participants will explore the population perspective of health information sharing for quality, gaining a basic knowledge of: quality measure specification data element types and value sets defining and selecting a sub-population of patients (measure denominator) defining and identifying expected interventions (measure numerator) terminology issues in identifying inclusion and exclusion criteria a webinar series on U.S. healthcare interoperability (continued)

3. Learning Objectives (continued) expectations for information transfer from EHRs to quality reporting organizations HITSP specifications for quality information sharing the relationship of the quality use case and interoperability specification to other efforts for public health and for data repurposing a webinar series on U.S. healthcare interoperability

4. Quality Quality Measure Specification Clinical Data for Analysis Inclusion Criteria Exclusion Criteria Quality Reporting Security and privacy requirements for Quality HITSP Interoperability Specification for Quality (HITSP IS 06) Units of Exchange Health Information Summary Documents Health Information Messages Conformance Subsets Questions and Answers Agenda a webinar series on U.S. healthcare interoperability

5. Introduction: Steve’s Story . . . part six Patient is a 26-year-old male coping with the long-term effects of a brain tumor that was removed during his childhood Patient is assisting with home care for his grandfather, a recent widower and diabetic who has become despondent and non-compliant with self-care requirements The family is becoming concerned about the quality of care Steve’s grandfather is receiving A search for new providers and a successful diabetes program is being conducted by the family Fact-based, not anecdotal, information is needed, e.g., Critical care information such as the reputation of the care providers and the hospitals where they primarily practice, experience with certain procedures, etc. Personal convenience information such as hours of operation, availability, etc.

6. HITSP is a volunteer-driven, consensus-based organization that is funded through a contract from the Department of Health and Human Services. The Panel brings together public and private-sector experts from across the healthcare community to harmonize and recommend the technical standards that are necessary to assure the interoperability of electronic health records. Overview

7. The HITSP Standards Harmonization Framework Identify a pool of standards for an AHIC (American Health Information Community) Use Case Identify gaps and overlaps in the standards for this specific Use Case Make recommendations for resolution of gaps and overlaps Select standards using HITSP-approved Readiness Criteria Develop Interoperability Specifications (IS) that use the selected standard(s) for the specific context Test the IS Deliverables and Mode of Operation

8. Each HITSP Interoperability Specification defines a set of “constructs” that: specify how to integrate and constrain selected standards to meet the business needs of a Use Case; and define a Roadmap to use emerging standards and to harmonize overlapping standards when resolved. In essence, a HITSP IS represents a suite of documents that integrate and constrain existing standards to satisfy a Use Case Deliverables and Mode of Operation

9. HITSP construct types, in decreasing breadth of scope, include: Interoperability SpecificationsIntegration of all constructs used to meet the business needs of a Use Case Transaction PackagesLogical grouping of transactions TransactionsLogical grouping of actions that use components and/or composite standards to realize the actions ComponentsLogical grouping of base standards that work together, such as messaging and terminology Deliverables and Mode of Operation

10. IS Status = State in the acceptance process ReleasedPanel approved for submission to HHS AcceptedSecretary of HHS has accepted for a period of testing RecognizedSecretary of HHS has recognized the IS for immediate implementation Revisions and updates may mean that multiple versions of some Interoperability Specifications exist with differing status levels Deliverables and Mode of Operation

11. Current Interoperability Specifications (IS)

12. IS 06 Quality This Interoperability Specification defines specific standards that capture the integration of data to support quality measurement feedback and reporting into electronic health records (EHRs), use of quality measures to support clinical decision making, and public reporting of healthcare quality through the exchange of data between healthcare organizations and providers and public health via an electronic network. Version: 1.0 Recognized Version 1.0.1 Panel Review Healthcare Provider Quality Reporting Organizations IS 06 VIA AN ELECTRONIC NETWORK

13. Hospital-based quality measures Automate data capture and reporting of Hospital Quality Alliance (HQA) measures through EHRs in support of provider workflows Communicate HQA measure data to external agencies Clinician-level data Automate data capture and reporting of Ambulatory Quality Alliance (AQA) measures through EHRs in support of provider workflows Communicate AQA quality measure data to external entities for aggregation and reporting IS 06 QualityOverall Objectives

14. IS 06 QualityOverall Objectives(continued) • Feedback to Clinicians • enable real-time or near-real-time feedback regarding specific quality indicators which are relevant for a particular patient • enable provision of tailored performance information to clinicians on quality measures for specific patient groups (continued)

15. IS 06 QualityOverall Objectives(continued) • Public Reporting • Aggregate data across multiple sources (claims data, medication data, laboratory data, etc.) • Support quality measurement, promote accountability among providers, and aid consumers in making informed choices • Communicate quality measurement data quickly and clearly in a manner that makes it useful to a wide variety of decision makers (patients, healthcare providers, payers, health plans, and regulators who are involved with this process)

16. Patient Clinicians Healthcare Delivery Organizations Laboratory Organizations Public Health Agencies Resource Suppliers Insurance Companies Consumers IS 06 QualityStakeholders

17. IS 06 QualityRequirements • Quality Measure Specification • Structured and codified • Denominator and Numerator Inclusions – Value Sets • Denominator and Numerator Exclusions – Value Sets • Data Capture / Aggregation • Data Reporting to External Agencies

18. IS 06 QualityRequirements (continued) Integrating the Healthcare Enterprise (IHE) Quality, Research & Public Health Domain, Performance Measurement Value Set White Paper, August 2008

19. Hospital-based care IS 06 QualityPerspectives Clinician / Ambulatory-based care

20. Healthcare Information Technology Expert Panel (HITEP) Convened by the National Quality Forum (NQF) Identified 84 Institute of Medicine (IOM) High Priority Measures Common data types Reduce logic to common data types Analyze frequency 88 Data Elements (9 additional subtypes added by HITEP) Facility / clinician demographics Patient demographics Clinical data IS 06 Quality Data Elements / Types

21. IS 06 QualityHITEP High Priority Items Diabetes Acute Myocardial Infarction (AMI) Coronary Artery Disease Heart Failure Asthma, Cancer Screening Stroke Pregnancy, Tobacco Dependency Care Coordination, Depression, End of life, Immunizations Medication Management, Surgical Medication Management, Non-surgical

22. Physical findings and observations Vital signs Physical exam Medication allergies (hypersensitivity reactions) True or anticipated side effects must be distinguished from medication allergies IS 06 QualityData Elements / Types / Examples • Lab information (including all data elements and selected standards identified for lab results from HITSP) • Result (value) e.g. lipid measurement for diabetes • Lab order (e.g. Hemoglobin A1C) • Symptom information • assessment, EKG for chest pain vs. EKG performed for non-traumatic chest pain in ED

23. Family history Patient past history Social history IS 06 QualityData Elements / Types / Examples • Diagnoses • Principal Diagnosis – for retrospective measures • Admitting/presumptive for concurrent • Chronic conditions (e.g. use of appropriate medications for asthma) • Acute conditions (e.g. appropriate treatment for children with URI) • Problem list (interdisciplinary)

24. IS 06 Quality Main Business Actors Document-Based Transmission Hospital Clinician/Ambulatory Provider Quality Measurement Organization Message-Based Transmission Other Communities

25. MDO MDO Quality Measure QMD’s MDO NQF Quality Report QRD Patient Data CDA’s IS 06 Quality Architecture #1: EHR does the work Acronym Legend MDO – Measure Development Organization NQF – National Quality Forum QMD – Quality Measure Document CDA – Clinical Document Architecture QRD – Quality Report Document measure endorsement, maintenance, syndication, and live broadcast EHR QMD imported QRD exported EHR creates CDA’s internally, uses imported QMD’s to calculate quality scores and export QRD

26. MDO MDO Quality Measure QMD’s MDO NQF Quality Report QRD Patient Data CDA’s IS 06 Quality Architecture #2:Quality Improvement Organization (QIO) Acronym Legend MDO – Measure Development Organization NQF – National Quality Forum QMD – Quality Measure Document CDA – Clinical Document Architecture QRD – Quality Report Document measure endorsement, maintenance, syndication, and live broadcast QMD’s imported QIO EHR CDA’s exported CDA’s imported QRD exported QIO uses imported QMD’s and CDA’s to calculate quality scores and exports QRD CDA calculated internally QRD exported

27. MDO MDO Quality Measure QMD’s MDO NQF Quality Report QRD EHR EHR EHR EHR EHR Patient Data CDA’s IS 06 Quality Architecture #3: QIO does the work (Aggregator helps) QMD’s imported Uses imported QMD’s and CDA’s to calculate quality scores and exports QRD QIO measure endorsement, maintenance, syndication, and live broadcast CDA’s imported QRD exported CDA’s imported, aggregated, and exported EHR Aggregator CDA’s exported Acronym Legend MDO – Measure Development Organization NQF – National Quality Forum QMD – Quality Measure Document CDA – Clinical Document Architecture QRD – Quality Report Document EHR CDA calculated internally

28. IS 06 Quality Sharing Clinical and Operational Information Query for Existing Data TP 21 Patient Level Quality Data Message Patient Level Quality Data Document C 34 C 38 Patient Demographics Query T 23

29. IS 06 Quality Privacy and Security Secured Communication Channel Entity Identity Assertion T 17 C 19 Manage Consent Directives Collect & Communicate Security Audit Trail TP 30 T 15 Consistent Time Nonrepudiation of Origin T 16 C 26 Access Control TP 20

30. IS 06 Quality Infrastructure Manage Sharing of Documents Anonymize T 13 C 25 Pseudonymize Notification of Document Availability T 24 T 29 Patient ID Cross-Referencing Retrieve Form for Data Capture TP 22 TP 50 Re-used constructs from Biosurveillance

31. IS 06 Quality Future Direction Measurement Criteria Document Measurement Criteria Message TBD TBD Current Activities: Collaborative for Performance Measure Integration with EHR Systems National Committee for Quality Assurance (NCQA) American Medical Association (AMA) Electronic Health Records Association (EHRA, formerly EHRVA) http://www.ama-assn.org/ama/pub/category/18352.html New Constructs Required

32. IS 06 Quality Future Direction(continued) Quality Measurement Message Quality Measurement Document TBD TBD Current Activities: Quality Reporting Document Architecture (QRDA) September 2008 Ballot – HL7, Vancouver, BC New Constructs Required

33. IS 06 Quality Future Direction(continued) Validation, Data Quality Checking Derived Information TBD TBD Case Review Message Case Review Document TBD TBD New Constructs Required

34. Re-UseApplying an existing construct to more than one IS Re-PurposeUpdating a construct to meet the needs of a new Use Case Can extend or constrain when reusing or re-purposing Specifications contain a common superset Superset can be extended as new requirements are encountered Superset can be constrained with use-specific constraints Units of Information Exchange HITSP IS Constructs - Re-Use and Re-Purpose Constructs (single purposeor reusable) Type 1: Base or Composite Standards

35. Effective interoperability –NEED TO UPDATE SLIDE Independent conforming implementations will interoperate Semantic Interoperability with core clinical content IS 06 Quality Strengths Will be ready on MON – 9/29 by Floyd (continued)

36. Practical interoperability – NEED TO UPDATE SLIDE Flexible interoperability Secured and Private interoperability IS 06 Quality Strengths(continued) Will be ready on MON – 9/29 by Floyd

37. Steve’s story . . . the future Patients can make informed decisions about the ongoing care of themselves and their family members consumers have access to quality and safety reports about individual providers and care facilities Data is collected automatically during routine care and reused for performance measurement Outcome data is available for determining best care protocols, enables standards-based and evidence-based care Reports are standard and comparable enabling true benchmarking and continuous improvement Transparency is the rule Decision support is part of the workflow, with useful safety alerts 

38. Healthcare in an interoperable world . . . The Future is Now HIT data exchange is becoming transparent so that the quality of care delivered by providers and hospitals can be known no matter where the patient is located Consumers are empowered to get the right information at the right time find appropriate, quality and safe care for themselves and their families assume that repeatable information will be safe and secure while also being accessible by those who need it – before, during and after a visit to a care provider Care providers are empowered to provide safe, effective and evidence-based care with information integrated within a clinical care workflow

39. Use or specify HITSP Interoperability Specifications in your HIT efforts and in your Requests for Proposals (RFPs) Ask for CCHIT certification Leverage Health Information Exchanges to promote HITSP specifications to make connections easier in the future Ask . . . Is there a HITSP standard we could be using? Get involved in HITSP . . . Help shape the standards How YOU can become involved

40. How YOU can become involved Learn more about specific HITSP activities in these webinars available for replay:         

41. Webinar Series II Coming soon Stay Tuned – same time Thursdays — 2:00-3:30 pm EDT Send your Webinar ideas to hitsp@ansi.org

42. Join HITSP in developing a safe and secure health information network forthe United States. Visit www.hitsp.orgor contact . . . Michelle Deane, ANSI mmaasdeane@ansi.org Re: HITSP, its Board and Coordinating Committees Jessica Kant, HIMSS Theresa Wisdom, HIMSS jkant@himss.orgtwisdom@himss.org Re: HITSP Technical Committees

43. A Successful Collaboration Interweaving many different standards to address business needs A successful collaboration between HITSP and several HITSP member organizations developing base standards and implementation guides/profiles

44. Sponsor Strategic Partners www.HITSP.org

45. Quality Questions and Answers