July 20, 2007 Healthcare Information Technology Standards Panel Principles for Proper Use of HITSP Interoperability Specifications And Proposal for Proper.

Slides:



Advertisements
Similar presentations
Integrating the Healthcare Enterprise IHE Overview Keith W. Boone Interoperability Architect, GE Healthcare Co-chair, IHE Patient Care Coordination PC.
Advertisements

Cross Community (XC) Profiles Karen Witting. Outline Vision – as described in 2006 IHE White Paper on Cross Community Exchange Existing – what has been.
Catherine Hoang Ioana Singureanu Greg Staudenmaier Detailed Clinical Models for Medical Device Domain Analysis Model 1.
0 Chicago, IL March 6 th, 2007 Use Case Requirements, Design and Standards Selection HITSP Use Case Requirements, Design and Standards Selection Date:
1 Operating Rules Status NCVHS Subcommittee on Standards December 3, 2010 Updated on enhancements to Operating Rules for Eligibility and Claim Status.
HITSP – enabling healthcare interoperability 1 enabling healthcare interoperability 1 Standards Harmonization HITSP’s efforts to address HIT-related provisions.
Health Information Technology Standards Panel Ed Mikoski 19MAR09 TIA Healthcare ICT Section Teleconference.
This presentation prepared for Now is the time to initiate the one change that will have the most leverage across your business systems Patient Identity.
ISO/IEC MFI-4 Extended Registry Masaharu Obayashi SC32/WG
The HITCH project: Cooperation between EuroRec and IHE Pascal Coorevits EuroRec 2010 Annual Conference June 18 th 2010.
HITSP – enabling healthcare interoperability 1 enabling healthcare interoperability 1 Standards Harmonization HITSP’s efforts to address HIT-related provisions.
S&I Data Provenance Initiative Presentation to the HITSC on Data Provenance September 10, 2014.
S&I Framework Doug Fridsma, MD, PhD Director, Office of Standards and Interoperability, ONC Fall 2011 Face-to-Face.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
Organizing IHE Integration Profiles related to the Electronic Health Record Input to the IHE ITI Tech Committee November 2002 Charles Parisot, GE Medical.
Development Principles PHIN advances the use of standard vocabularies by working with Standards Development Organizations to ensure that public health.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
Healthcare Information Technology Standards Panel Population Health – Biosurveillance June 29, 2007.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Overview of IHE IT Infrastructure Patient Synchronized Applications.
HL7 HL7  Health Level Seven (HL7) is a non-profit organization involved in the development of international healthcare.
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.
Profiling Metadata Specifications David Massart, EUN Budapest, Hungary – Nov. 2, 2009.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe December 6, 2010.
National Institute of Standards and Technology Technology Administration U.S. Department of Commerce 1 Patient Care Devices Domain Test Effort Integrating.
Public Health Vocabulary Services (a) Gautam Kesarinath – CDC NCPHI Associate Director of Technology, (b) Nikolay Lipskiy – CDC SDO & Interoperability.
0 enabling healthcare interoperability Webinar Series Sponsored by the HITSP Education, Communications and Outreach Committee Webinar 5 July 24, 2008 |
Public Health Data Standards Consortium
Networking and Health Information Exchange Unit 6b EHR Functional Model Standards.
The United States Health Information Knowledgebase: Federal/State Initiatives An AHRQ Research Project J. Michael Fitzmaurice, PhD, AHRQ Robin Barnes,
1 HITSP – enabling healthcare interoperability Current Framework and Fundamental Concepts  For those unfamiliar with the HITSP Harmonization Framework.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Overview of IHE IT Infrastructure Patient Synchronized Applications.
DICOM and ISO/TC215 Hidenori Shinoda Charles Parisot.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise HIMSS Demonstration XDS Document Content Specifications Keith W.
0 Connectathon 2009 Registration Bob Yencha Webinar | August 28, 2008 enabling healthcare interoperability.
Geneva, Switzerland, April 2012 Introduction to session 7 - “Advancing e-health standards: Roles and responsibilities of stakeholders” ​ Marco Carugi.
0 enabling healthcare interoperability Webinar Series Sponsored by the HITSP Education, Communications and Outreach Committee Building Blocks for Healthcare.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe January 18, 2011.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
1 Healthcare Information Technology Standards Panel Care Delivery - IS01 Electronic Health Record (EHR) Laboratory Results Reporting July 6, 2007.
1 Standards Harmonization Readiness Criteria TIER 1 March 2, 2006 HITSP Standards Harmonization Criteria Committee.
Consumer Empowerment Registration and Medication History
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Electronic Submission of Medical Documentation (esMD)
Healthcare Information Standards Panel 2007,2008, and Beyond John D. Halamka MD Chair, HITSP.
July 27, 2007 HITSP Project Medications Management Use Case Presentation to CCHIT Steve Wagner and Scott Robertson.
PDMP & HITI Gap Mitigation Analysis Summary May 6 th, 2014.
Proposed S&I Public Health Reporting Initiative 1 Challenge -There is a lack of harmonized activities to enable electronic data exchange between clinical.
Electronic Health Record (EHR) and Vital Record (VR) Systems Information Exchange National Center for Health Statistics Classifications and Public Health.
September, 2005What IHE Delivers 1 Patient Index and Demographic Implementation Strategies IHE Vendors Workshop 2006 IHE IT Infrastructure Education Rick.
Public Health Reporting Initiative July 25, 2012.
Integrating the Healthcare Enterprise The IHE Process: Developing Standards-based Solutions Kevin O’Donnell Co-chair, IHE Radiology Planning Committee.
PIX/PDQ – Today and Tomorrow Vassil Peytchev Epic.
Cross Community Access Profile Karen Witting IBM Co-chair ITI technical committee.
Integrating the Healthcare Enterprise Retrieve Information for Display (RID) Integration Profile Ellie Avraham Kodak Health Imaging IHE IT Infrastructure.
Dynamic/Deferred Document Sharing (D3S) Profile for 2010 presented to the IT Infrastructure Technical Committee Karen Witting February 1, 2010.
Interoperability Measurement for the MACRA Section 106(b) ONC Briefing for HIT Policy and Standards Committee April 19, 2016.
Certification Commission for Healthcare Information Technology Validation of Laika Usage Scenarios Dennis Wilson – Certification Technology Director, CCHIT.
Patient Demographics Query (PDQ) Didi Davis Director, Eclipsys Corporation Co-Chair, IT Infrastructure Planning Committee.
1 The information contained in this presentation is based on proposed and working documents. Health Information Exchange Interoperability Minnesota Department.
eHealth Standards and Profiles in Action for Europe and Beyond
Healthcare Information Technology Standards Panel
HITSP Project Medications Management Use Case Presentation to CCHIT
IHE Radiology Webinar IHE-Japan National Extensions July 25th, 2016
Current Framework and Fundamental Concepts
Patient Identifier Cross-Referencing for MPI (PIX)
Public Health Laboratory Data (PH-Lab) Exchange Project: Overview
Health Information Exchange Interoperability
Object Oriented Analysis and Design
Standards Harmonization Readiness Criteria
, editor October 8, 2011 DRAFT-D
Presentation transcript:

July 20, 2007 Healthcare Information Technology Standards Panel Principles for Proper Use of HITSP Interoperability Specifications And Proposal for Proper Use of IS-03 CE Registration and Medication History

1 Topics  Objective  HITSP Constructs  Well-defined ways to Use HITSP Construct  Proposal for use of HITSP IS-03 CE Registration and Medication History

2 HITSP Construct Proper Use Objective of this Proposed Definition of Principles for Proper Use of HITSP Constructs  To clarify principles for appropriate, consistent use of HITSP Interoperability Specifications and other HITSP construct specifications by intended users.  Intended users include, for example: –HITSP Committees (e.g., in new work efforts) –CCHIT –Health Information Exchanges –Healthcare stakeholders (e.g., during IT systems procurements) –Healthcare IT Vendors –Healthcare Information policy makers

3 HITSP Construct Proper Use Component (Composite) Transaction (Composite) Transaction Pkg. (Composite) For Internal Reuse HITSP Framework Use Case or Modification Request Interoperability Specification Transaction Package (1..m transactions or composite standards) Transaction (1..n components or composite standards) Component (1..c base or composite standards) Base Standard #1 Base Standard #4 Base Standard #2 Base Standard #3 Base Standard #5 Base Standard #... Base Standard #n SDOs For External Use Interoperability Specification Component (Composite) Transaction (Composite) Transaction Pkg. (Composite) For Internal Reuse

4 HITSP Construct Proper Use General Perspective on types of Proper Use  Use of a HITSP Interoperability Specification and Associated Constructs. –HITSP Technical Committees defines ways users can appropriately use an IS and associated constructs  Longer term questions that will require definition of well- defined processes –Managing "internal consistency" across HITSP constructs below construct level – e.g., consistent vocabulary value set, same micro data structure for describing an allergy, use of OIDs in certain fields –External reuse/repurposing of a HITSP Construct that is not an Interoperability Specification

5 HITSP Construct Proper Use Different Types Of External Use of an I.S. and Associated Constructs  Actor Scoping  Subsetting  HITSP Optionality

6 HITSP Construct Proper Use Different Types Of External Use of an I.S. and Associated Constructs - Actor Scoping  For entire Interoperability Specification (IS), meet requirements for selected subset of Business and supporting Technical Actors.  Implement set of transactions and information components involving a specific sub-set of Actor(s) in IS. –E.g., for EHR-lab, implement information exchange for the laboratory information system Business Actor

7 HITSP Construct Proper Use Different Types Of External Use of an I.S. and Associated Constructs - Subset  A subset is partial implementation of an Interoperability Specification –Must include at least two actors and a transaction. –May involve all or some of the IS defined Actors. –May be defined based on a subset of scenarios, information content, or semantic richness in the Interoperability Specification  Appropriate subsets are identified by HITSP Technical Committees to notify users what is allowed for a specific IS or construct. –Note: subsets will be documented in a later release for V2.0 of EHR-Lab, Consumer Empowerment, and Biosurveillance Interoperability Specifications (IS-01, 02 and 03).

8 HITSP Construct Proper Use Different ways to subset  Scenario/workflow –Implement a subset of available scenarios for the I.S. –e.g., EHR-Lab use case has two sub-workflows: lab results to ordering providers and sharing historical lab results  Information content –Implement a portion of the information content of an I.S. –e.g., implement IS 03 Consumer Empowerment with only registration information and no medication information  Semantic richness –Add a well-defined alternative to a less constrained field –e.g., use of an optional coding system in addition to textual concepts

9 HITSP Construct Proper Use HITSP Optionality  External entity may elect to exercise optionality identified by a HITSP IS or construct.  HITSP identifies optionality to support a domain choice (e.g., policy) rather than an individual implementation.  Optionality may be for a field in a message (e.g. laboratory phone number in a returned lab result that is optional in C-36).

10 Topics  Objective  HITSP Constructs  Well-defined ways to Use HITSP Construct  Proposal for use of HITSP IS-03 CE Registration and Medication History

11 HITSP Construct Proper Use Proposal for Actor Scoping and Subsets Definition for the Normal Usage of HITSP IS-03  This proposal is under development by the HITSP CE Technical Committee.  Goals are to allow implementations of subsets of HITSP IS-03, while ensuring smooth evolution towards the implementation of the complete use case.  Address real world needs, without introducing fragmentation which would be counter to the goal of interoperability.  Further input is welcome, especially from CCHIT.

12 HITSP Construct Proper Use First selection: Actor Scoping  A specific IT system selects one or more business actor(s)  Selects among the optional corresponding technical actors (those required shall be implemented).

13 HITSP Construct Proper Use Example: Actor Scoping for an EHR Business Actor  An EHR shall support the following Technical Actors: –Document Source –Document Consumer  An EHR shall support either: –A Patient Identity Source and a Patient ID Cross-Referencing Consumer –A Patient Demographics Consumer –Both of the above  An EHR may support the following Technical Actor: –Document Repository Conditional: Shall support: (1) Patient Identity Source + PIX Consumer, or (2) Patient Demographics Consumer, or (3) Both

14 HITSP Construct Proper Use Second selection: One or more subsets  Subsets are focused on the content of the registration and medication history document.  All rely on the same document sharing transactions (TP-13) and patient identification (TP-22 or T-23).  A specific IT system for the Technical Actor it supports shall select one or more subsets among:

15 HITSP Construct Proper Use Proposed Subset Definitions for Document Source

16 HITSP Construct Proper Use Actor Scoping and Subsets Definition for the Normal Usage of HITSP IS-03  This proposal is under development by the HITSP CE Technical Committee.  Goal is to include in next revision of the IS-03 and to ensure that subset definition meets market need and CCHIT certification roadmap.  Cooperation with CCHIT is welcome in the next few weeks to define and approve.