PDMP & HITI Solution Planning Workgroup Session June 12, 2014.

Slides:



Advertisements
Similar presentations
Longitudinal Coordination of Care LTPAC SWG Monday August 19, 2013.
Advertisements

Statewide Collaboration Process Protocol and Services Work Group HEAL 5 Kick Off Mtg May 12, 2008 DRAFT.
Prescription Drug Monitoring Program (PDMP) & Health IT Integration Initiative 10 December 2014 Standards and Interoperability Framework Jinhee Lee, PharmD.
PDMP & HITI IG Development Workgroup Session August 14, 2014.
Overview of Longitudinal Coordination of Care (LCC) Presentation to HIT Steering Committee May 24, 2012.
Basic guidelines for the creation of a DW Create corporate sponsors and plan thoroughly Determine a scalable architectural framework for the DW Identify.
The HITCH project: Cooperation between EuroRec and IHE Pascal Coorevits EuroRec 2010 Annual Conference June 18 th 2010.
S&I Data Provenance Initiative Presentation to the HITSC on Data Provenance September 10, 2014.
Understanding and Leveraging MU2 Optional Transports Paul M. Tuten, PhD Senior Consultant, ONC Leader, Implementation Geographies Workgroup, Direct Project.
PDMP & Health IT Integration Use Case & Functional Requirements February 4,
PDMP & Health IT Integration Standards and Harmonization July 8 th, 2014.
Initial slides for Layered Service Architecture
PDMP & Health IT Integration Standards and Harmonization June 3 rd, 2014.
PDMP & Health IT Integration Standards and Harmonization June 17 th, 2014.
PDMP & Health IT Integration All-Hands Meeting May 13 th, 2014.
Electronic Submission of Medical Documentation (esMD) Electronic Determination of Coverage (eDoC) Home Health User Story February 4, 2015.
PDMP & Health IT Integration Use Case & Functional Requirements
PDMP & HITI Solution Planning/IG Workgroup Session July 3, 2014.
State Alliance for e-Health Conference Meeting January 26, 2007.
PDMP & Health IT Integration Standards and Harmonization June 24 th, 2014.
HIT Standards Committee Standards Summer Camp, ePrescribing of Discharge Meds Power Team (DMPT) Update and Recommendations Jamie Ferguson, Kaiser Permanente.
PDMP & Health IT Integration Use Case & Functional Requirements January 28,
Finalized Solution Plan July 1 st, Solution Planning Work Group Approach 1. Overlay standards currently in general use per transaction - focus on.
State HIE Program Chris Muir Program Manager for Western/Mid-western States.
HIT Policy Committee NHIN Workgroup Recommendations Phase 2 David Lansky, Chair Pacific Business Group on Health Danny Weitzner, Co-Chair Department of.
PDMP & HITI Solution Planning Workgroup Session I May 15 th, 2014.
Hurdles and Solutions for the Interoperable EHR John W, Loonsk, MD FACMI Chief Medical Officer CGI.
PDMP & Health IT Integration Standards and Harmonization April 29 th, 2014.
PDMP & Health IT Integration Standards and Harmonization May 27 th, 2014.
PDMP & HITI IG Development Workgroup Session August 21, 2014.
PDMP & Health IT Integration All-Hands Meeting May 27 th, 2014.
Public Health Reporting Initiative Stage 3 Sprint: Implementation Guide Development 1.
Data Provenance Community Meeting November 6, 2014.
PDMP & Health IT Integration Use Case & Functional Requirements February 25,
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
S&I PUBLIC HEALTH REPORTING INITIATIVE: DEVELOPING OF A TEAMING APPROACH S&I Public Health Reporting Initiative Nikolay Lipskiy, MD, DrPH, Co-Lead September,
Data Segmentation for Privacy November 16 th, 2011.
PDMP & Health IT Integration All-Hands Meeting July 1 st, 2014.
HIT Standards Committee Overview and Progress Report March 17, 2010.
PDMP & Health IT Integration All-Hands Meeting June 24 th, 2014.
Epic Pilot – Use Case 1 EHR PDMP HUB PDMP EHR Epic EHR Epic NCPDP 10.6 PDMP Hub OneHealthPort HIE PDMP Hub OneHealthPort HIE PMIX PDMP WA State Department.
Mariann Yeager, NHIN Policy and Governance Lead (Contractor) Office of the National Coordinator for Health IT David Riley, CONNECT Lead (Contractor) Federal.
S&I Public Health Education Series: Data Provenance July 9th, 2014 Johnathan Coleman Initiative Coordinator – Data Provenance ONC/OCPO/OST (CTR)
PDMP & Health IT Integration Standards and Harmonization July 1 st, 2014.
PDMP & HITI Solution Planning Workgroup Session June 5, 2014.
Electronic Submission of Medical Documentation (esMD) Electronic Determination of Coverage PMD User Story & Harmonization August 7, 2013.
PDMP & HITI Solution Planning Workgroup Session
Data Interchange Standards in Healthcare Rev'd Sunday A. Folayan General Data Engineering Services, Ibadan, Nigeria
Pharmacists’ Patient Care Process
PDMP & Health IT Integration All-Hands Meeting July 15 th, 2014.
July 27, 2007 HITSP Project Medications Management Use Case Presentation to CCHIT Steve Wagner and Scott Robertson.
Final Current Standards Landscape Analysis June 3 rd, 2014.
PDMP & HITI Gap Mitigation Analysis Summary May 6 th, 2014.
S&I Framework Prescription Drug Monitoring Program & Health IT Integration Initiative Use Case & Functional Requirements January 14,
PDMP & Health IT Integration Standards and Harmonization July 22, 2014.
Longitudinal Coordination of Care LCP SWG Thursday, May 23, 2013.
PDMP & HITI Solution Planning Workgroup Session May 22, 2014.
360Exchange (360X) Project 12/06/12. Reminders / announcements 360X Update CEHRT 2014 / MU2 Transition of Care Requirements 1 Agenda.
PDMP & HITI Solution Planning Workgroup Session June 26, 2014.
1 Vermont Health Information Technology Plan Workgroup January 10, 2007 VERMONT INFORMATION TECHNOLOGY LEADERS.
PDMP & Health IT Integration Standards and Harmonization May 20 th, 2014.
PDMP & HITI Solution Planning Workgroup Session June 19, 2014.
1 CDC Health Information Exchange (HIE) Accelerating State-wide Public Health Situational Awareness in New York Through Health Information Exchanges August.
SCTT Vendor Information Session Health Design Authority, OCIO.
1 The information contained in this presentation is based on proposed and working documents. Health Information Exchange Interoperability Minnesota Department.
PDMP & Health IT Integration Standards and Harmonization June 10 th, 2014.
DataNet Collaboration
Unit 5 Systems Integration and Interoperability
Health Information Exchange Interoperability
Presentation transcript:

PDMP & HITI Solution Planning Workgroup Session June 12, 2014

Agenda 1.Solution Planning Approach 2.Questions to be Answered 3.Relevant Workflows 4.Evaluation of Proposed Solutions

Solution Planning Work Group Approach 1. Overlay standards currently in general use per transaction - focus on transactions for integrated solutions 3. For each alternate workflow, propose solutions for harmonizing standards in order to pull PDMP information into EHR or Pharm. IT Systems synchronously 2. Document pros and cons for each proposed solution and prioritize in terms of technical feasibility Develop Technical Architecture  Can EHRs and Pharmacy ITs handle proposed Standards? Report findings to Community

- 4 - Controlled Substance History Report, Integration Architecture Drivers TO: Easy, timely, consistent access to reliable PDMP data FROM: Pervasive challenges to access data within clinical workflows As-Is Architecture  Segmented conceptual framework for data exchange  Varying solution practices  Varying state requirements and source ownership (e.g., authorization, authentication protocols)  Flexible interstate data sharing and intermediaries facilitating open data exchange for authorized users  Constraints on cost for Δ in source data architecture  Constraints on ease of implementation of foreign standards in established functional models/frameworks To-Be Design Principles  Congruent data / message formats across integration sites  Compatible with established PMIX-NIEM architecture  Ability to support various front-end capabilities  Ability to integrate within existing technical systems and evolve to support regulatory/technology changes Health Information Exchanges Data harmonization and structuring of a data integration layer Interstate Data sharing Hubs Continuous improvement of real time reporting Vision Architecture Drivers Controlled Substance History Information Needs

- 5 - Integrated PDMP Data Exchange Architecture Solution Plan - Multi -Level Standards State PDMPs EHREMR User Interface (Presentation) Health IT / Clinical Databases Data Harmonization Source Systems Recommendation/Notes Pharmacy IT Out of scope - however… User access modes important to consider in standards selection. Modules within ambulatory and enterprise in- patient EHRs vary. Where would the interface be most effective? Define a comprehensive query-response strategy aligned to both EHRs and Pharmacy IT systems compatible with state PDMP architecture/regulations and intermediary capabilities/infrastructure. Defined standards architecture based on source data framework: PMIX-NIEM. Metadata transformations, routing PDMP Med History Architecture Pharm. Int / HIEs Establish standard data models and an approach for data harmonization; achieve standard and consistent data in this layer for query-response while addressing the source system layer in parallel. Translations are essential for compatible standards to interoperate. Hubs Translation / Transformation ePrescribing CDS PMS Functions Med History/ Reconciliation Internal Med Orders HIE/PDMPs (Nebraska) Other Medication History Sources (eg. PBMs) Data Extraction / Transformation HL7 SCRIPT SCRIPT ASAP PMIX PMIX

Questions to be answered: How do we define intermediaries and their relationships to Health IT systems? o Can we collapse all types of intermediaries into one entity? (i.e. pharmacy, switch, HIE, etc.) or do they require to be differentiated o Pharmacies may have need for intermediaries – concerns regarding cost to leverage intermediaries or network services o Future state use of intermediaries or networks to provide controlled substance history reports Can Pharmacy IT systems and EHR systems be collapsed or need to be differentiated? o Differences in pharmacy and clinician workflows / data systems and expectations in PDMP data transmitted? Differences in care settings - Ambulatory vs. Acute; In-hospital pharmacies vs. retail pharmacies. Are different standards needed for different EHR systems or different pharmacy settings? Are there certain workflows that are unfavorable?

Relevant Workflows Current Landscape Proposed Solution Set EHR  In-State PDMP Pharmacy  In-State PDMP EHR  Intermediary  In-State PDMP Pharmacy  Intermediary  In-State PDMP EHR  Hub  PDMP  (s) Pharmacy  Hub  PDMP(s) EHR  Intermediary  Hub  PDMP(s) Pharmacy  Intermediary  Hub  PDMP(s) EHR  In-State PDMP  Hub  PDMP(s) Pharmacy  In-State PDMP  Hub  PDMP(s) EHR  In-State PDMP Pharmacy  In-State PDMP EHR  Intermediary* Pharmacy  Intermediary EHR  Hub Pharmacy  Hub 1.Aligns to in-scope Use Case scenarios 2.Approach may require translation mapping between ASAP, NCPDP SCRIPT Medication History, and H L7 V2 Messaging to PMIX Architecture 3.Implementation Guide will have to include data element modifications/additions to fully support PDMP & HITI Use Case requirements *Intermediary - An entity (service, or set of services) that routes the transaction to a receiving entity. May perform value added services such as translating data from one format to another Legend Proposed Potential Remove

Evaluate Proposed Solutions Solution Plan:

Next Steps Review: Transaction and solution evaluations Next All Hands meeting is Tuesday, 6/17 from 12:00 pm to 1:00 pm ET o Data Elements Analysis Next Solution Plan Workgroup Session is Thursday, 6/19 from 12:00 pm to 1:00 pm ET o Continue Workflow – Standards Evaluations o Evaluate prioritization of proposed solutions o Goal: Finalization of solution set Reminder: All PDMP & HIT Integration Announcements, Meeting Schedules, Agendas, Minutes, Reference Materials, Harmonization materials, Use Case, Project Charter and general information will be posted on the PDMP Wiki page – mepage mepage