Healthcare Information Technology Standards Panel

1. Healthcare Information Technology Standards Panel Consumer Empowerment – Registration and Medication History June 22, 2007

2. Consumer Empowerment Registration and Medication History • Scope • Deploy to targeted populations a pre-populated, consumer-directed and secure electronic registration summary. Deploy a widely available pre-populated medication history linked to the registration summary • Addresses core consumer empowerment enabling “connected PHRs” • Now recognized to be also applicable to EHR-to-EHR information exchange for interoperable patient charts with meds, allergies, problems, registration info. • A successful collaboration between HITSP and several HITSP member organizations developing base standards and implementation guides/profiles: ASTM, CAQH, CDC, FMT, HL7, IHE, NCPDP, X12, SNOMED

3. Consumer Empowerment Registration and Medication History

4. IS03 Consumer Empowerment Registration and Medication History • Developed in support of Harmonized Use Case for Consumer Empowerment (Registration and Medication History), March 19, 2006 • Consumer creates account to host registration summary & medication history • Consumer visits Healthcare Provider and provides registration summary information • Authorized Healthcare Provider reviews medication history • Key Requirements/Functionality Enabled by the IS • Querying other organizations for data and matching to the consumer • Accessing, viewing, and sharing registration summaries and medication histories • Note: Security and privacy in the process of being addressed.

5. IS03 Consumer Empowerment Registration and Medication HistorySet of Constructs

6. IS03 Set of Constructs (cont’d)

7. Defines the methodology and metadata requirements for the registration, storage and retrieval of documents across repositories within an affinity domain Calls out a subset of transactions defined in the IHE XDS Cross Document Sharing Specification, Dec 2006 ITI 14 Register Document Set ITI 15 Provide and Register Document Set ITI 18 Registry Stored Query ITI 17 Retrieve Document Key Concepts: Sharing of source attested documents, document content neutral, document registry, document repositories distributed or centralized. pkg TP 13 «transaction package» Manage Sharing of Documents + docId = TP13 constrains «composite standard» IHE XDS + Provide & Register Document Set: ITI-15 + Registry Stored Query: ITI-18 + Register Document Set: ITI-14 + Retrieve Document: ITI-17 implements «base standard» ISO 15000 ebRS Transaction Package TP-13 – Manage Sharing of Documents

8. Transaction Package TP-13 Manage Sharing of Documents • Four Technical Actors, 4 Transactions: • A Document Source that publishes a document to a repository (architecture neutral: local, shared or central) • A Document Repository that stores the document and forwards high-level meta-data to Document Registry • A Document Registry that tracks meta-data about documents • A Document Consumer that queries the Document Registry, selects document of potential interest and retrieves one or more from the referenced Document Repositories.

9. Defines the methodology for identifying and cross-referencing different patient attributes for the same patient. Underlying source material is from the IHE IT Infrastructure (ITI) Technical Framework (TF), Volume 2 (ITI TF-2), specifically: ITI-8: Patient Identity Feed [§3.8.1] ITI-9: Pix Query [§3.9.1] used by any system capable of performing real-time HL7 query and response and/or unsolicited patient demographic feed transactions. Key Concepts Patient Identity Demographics, HL7 Query/Response pkg TP22 «transaction package» Patient ID Cross-Referencing + docId = TP22 constrains «composite standard» IHE PIX - PIX Query: ITI-9 Patient Id Feed: ITI-8 constrains «base standard» HL7 V2.5 Message TP22 – Patient Identity Cross-Referencing

10. Transaction Package TP22: Patient ID Cross-Referencing • Three Technical Actors and Two Transactions • The Patient Identity Source which creates, updates or merges Identities and communicates them with the Patient Id Cross-Reference Manager • The Patient Id Cross-Reference Manager that manages those identities and links them across identification domains (Process and Algorithm are not specified by HITSP as they are an application function within the Technical Actor). • The Patient Id Cross-Reference Consumer which queries to link on Id in one identification domain to Ids in one or more other identification domains.

11. Defines the methodology for obtaining a patient identity (or list of patient identities) that match a provided set of patient demographics From the IHE IT Infrastructure (ITI) Technical Framework (TF), Volume 2 (ITI TF-2), specifically: ITI-21: Patient Demographics Query [§3.21.1]used by any system capable of performing real-time HL7 query and response and/or unsolicited patient demographic feed transactions Key Concepts Patient Identity Demographics, HL7 Query/Response T23 – Patient Demographics Query

12. Patient Demographics Supplier Patient Demographics ­ Query [ITI - 21] Patient Demographics Consumer TransactionT23 Patient Demographics Query • Two Technical Actors, One Transaction • The Patient Demographic Supplier which manages the demographics traits of persons. • The Patient Demographics Consumer which issues a Patient Demographics Query to the Patient Demographics Supplier with some person traits, and receives in response one or more matching persons with those respective traits.

13. Describes the document content that summarizes a consumer’s registration and medication data information for the purpose of information exchange with a Personal Health Record (PHR) Uses document content description for the required data elements provided in: HL7 Implementation Guide: CDA Release 2 – Continuity of Care Document (CCD), Release 1.0, April 01, 2007 with additional clarifications and specifications as appropriate Key Concepts HL7 Clinical Document Architecture Release2, HL7 V3 Reference Information Model (RIM), Continuity of Care Medical Summary, Implementation Guide, Object Identifier (OID) C32 – Registration and Medication History Document Content «component» Registration and Med History Document Content + docId = C32 constrains maps to constrains constrains «composite stand... «base stand... CAQH CORE LOINC «composite standard» IHE IT Infrastructure maps to «composite standard» Federal Medication Terminologies constrains «base standard» NCPDP SCRIPT constrains «base stand... X12N 270/271 references «base stand... ASTM/HL7 CCD maps to «base standard» constrains NDC RxNorm SPL «base stand... «base standard» HL7 CDA R2 ASTM E2369

14. IS03 Use of C32 Registration and Medication History Document Content • Specific content modules each with multiple data elements include: • Personal Information -- Languages Spoken • Support -- Healthcare Provider • Insurance Provider -- Allergies and Drug Sensitivity • Condition -- Medications – Prescription and Non-Prescription • Pregnancy -- Advance Directives • Comments -- Information Source • The Reg/Med document, as a whole, contains a designated author that is the consumer and/or their designated agent, such as the parent of a minor child

15. Use of Component C32 : Medications –Prescription and Non-Prescription Module Key Specifications that extend CCD for medications: • Route of Administration: Value drawn from FDA route of administration • Dose: Unit attribute, if present, coded using Unified Code for Units of Measures (UCUM). • Site: a value descending from the SNOMED CT Anatomical Structure (91723000) hierarchy. • Product Form: from dosage form - FDA dosage form – source NCI Thesaurus. • Product name or brand name coded using RxNorm, or NDC. When only the class of the drug is known, it shall be coded using NDF-RT. FDA Unique Ingredient Identifier codes (UNII) codes may be used when there are no suitable codes in the other vocabularies to identify the medication. • Indication coded using the VA/KP Problem List Subset of SNOMED CT (terms descending from clinical finding (404684003) concept.

16. Use of Component C32 : Allergies and Drug Sensitivities Module Key Specifications that extend CCD for allergies and drug sensitivities: • Adverse Event Type: see below. Support tiered level of specifics. • Severity: see below • Product causing the adverse event coded to UNII for Food and substance allergies, or RxNorm when to medications, or NDF-RT when to classes of medications. • Reaction coded using the VA/KP Problem List Subset of SNOMED CT (terms descending from clinical finding (404684003) concept.

17. PIX Consumer j i PIX Query X12 270/271 Core X12 270/271 Core Provide & Register (Reg./Med. Doc) Document Repository/ Registry k l PIX Consumer NCPDP SCRIPT 8.1 Document Source m PIX Query n Document Source o PIX Consumer p Provide & Register PIX Mgr r q PIX Query t s Provide & Register v u Document Source PIX Query PIX Consumer PIX Mgr w x Query Documents y Z Retrieve Docs (Reg/Med Doc) Document Consumer A B Document Repository/ Registry Retrieve Docs (Reg/Med Doc) D C PHR Service Provider EHR System Consumer RHIO Health Plan / Intermediaries PBM / Pharmacies Logon to PHR a b PIX Query PIX Consumer PIX Mgr c d Query Documents e f Retrieve Docs (Reg/Med Doc) Document Consumer g Document Repository/ Registry Retrieve Docs (Reg/Med Doc) h g h INTEROPERABILITY SEQUENCE DIAGRAM CE – Scenario #2 – Customer Visits Health Care Provider and Provides Registration Summary Information

18. Document Repository/ Registry PIX Consumer j i PIX Query X12 270/271 Core X12 270/271 Core Provide & Register (Reg./Med. Doc) k l PIX Consumer NCPDP SCRIPT 8.1 Document Source m PIX Query n Document Source o PIX Consumer p Provide & Register PIX Mgr r q PIX Query t s Provide & Register v u Document Source PBM / Pharmacies EHR System Health Plan / Intermediaries RHIO • Populating the RHIO with a Consumers Registration and Medication Information • Uses PIX Query (TP13) to Correctly Identify the Consumer [i-j, m-n, q-t] • Physicians Provide & Register a Registration and Medication Document (C32) with Information Available in EHR System (self-generated or received from other sources) [k-l] • Health Plans & PBMs/Pharmacies Provide & Register C32 Document Directly to RHIO [ o-p, s-v] or via the EHR-System (using X12 or NCPDP transactions)

19. Consumer EHR Sys, or payer, or health plan PHR Service Provider RHIO Document Repository/ Registry Select PHR Consumer Consent PIX Consumer PIX Identity Feed & Query Document Source Provide & Register (Reg./Med. Doc) View Reg/Med Modify Reg/Med EHR PIX Query PIX Mgr PIX Consumer Query Documents Retrieve Docs (Reg/Med Doc) Document Consumer Retrieve Docs (Reg/Med Doc) INTEROPERABILITY SEQUENCE DIAGRAM View and Integrate Registration Data into EHR CE – Implementation/Architecture Variant A – No RHIO is present – RHIO functions are assumed by PHR Service provider

20. Consumer EHR Sys, or payer, or health plan PHR Service Provider RHIO Document Repository/ Registry Select PHR Consumer Consent PIX Consumer PIX Identity Feed & Query Document Source Provide & Register (Reg./Med. Doc) View Reg/Med Modify Reg/Med EHR PIX Query PIX Mgr PIX Consumer Query Documents Retrieve Docs (Reg/Med Doc) Document Consumer Retrieve Docs (Reg/Med Doc) View and Integrate Registration Data into EHR EHR to EHR communication – Care Delivery Level Information

21. Strength of IS-03: synergy between its four constructs • Effective interoperability: • Independent conforming implementations will interoperate (all dimensions of interoperability covered, including sharing/selective access, transport and identity mgt). • Semantic Interoperability with core clinical content:med, allergies, problems/conditions, and real-world clipboard information. • Designed to empower equally the consumers and their providers (PHR-PHR, PHR-EHR, EHR-EHR) with the same level of robustness. • Practical interoperability: • Standards that already have “implementation feasibility” validated (IHE Connectathon, HIMSS Interoperability Demonstration) with a significant number of implementations (prototype and commercial). • Flexible interoperability: • Designed to allow “receivers of information” to operate at various level of richness: • display (browser+any CDA style sheet) • Import the “entire document” • Import discrete coded data • Secured and Private interoperability: • 6 Security Constructs in development by HITSP (October 2007) to support IS-03.