PDMP & Health IT IntegrationAll-Hands Meeting

January 28th, 2014

Meeting Etiquette

• Remember: If you are not speaking keep your phone on mute

• Do not put your phone on hold – if you need to take a call, hang up and dial in again when finished with your other call– Hold = Elevator Music = very frustrated speakers and

participants• This meeting, like all of our meeting is being

recorded– Another reason to keep your phone on mute when not

speaking• Feel free to use the “Chat” feature for questions,

comments or any items you would like the moderator or participants to know.

NOTE: This meeting is being recorded and will be posted on the Meeting Artifacts Wiki page after

the meeting

From S&I Framework to Participants:Hi everyone: remember to keep your phone on mute

2

Agenda

3

Topic Time Allotted General Announcements 5 minutesConcert Series Presentation• OneHealthPort & Washington State

Department of Health 30 minutes

PDMP & HITI Use Case Development•Assumptions, Context Diagram, User Stories•Introduce: Pre/Post Conditions, Actors and Roles

50 minutes

Next Steps/Questions 5 minutes

General Announcements…• Starting today we will be extending the time of our

All-Hands call 30 minutes to ensure we can get through our use case keeping with our timeline.– 12:00-1:30 pm (ET)

• We will be rescheduling our February 18th, 2014 meeting– Friday February 21st – same time 12:00-1:30 pm (ET)

• OneHealthPort (Washington State) will be presenting as part of our concert series today.

4

General Announcements continued

• To join our weekly webinars, visit the PDMP & Health IT Integration initiative Homepage for the latest meeting information: http://wiki.siframework.org/PDMP+%26+Health+IT+Integration+Homepage

5

• To subscribe to our mailing list, simply complete the PDMP & Health IT Project Signup Form: http://wiki.siframework.org/PDMP+%26+Health+IT+Integration+Join+the+Initiative

• To access current and archived meeting materials, visit the Project Meeting Artifacts section: http://wiki.siframework.org/PDMP+%26+Health+IT+Integration+Meeting+Artifacts

Note: Please check the meeting schedule weekly to get the most up-to-date meeting information

WA State Department of Health

PMP Transaction Processing through the OneHealthPort “statewide” HIE

Today’s Discussion• Brief Overview of the HIE

• Key Drivers

• Prescription Monitoring Program (PMP) Transaction

• PMP Security

• PMP Transaction Standards

• Lessons Learned

• Additional Levers

• Questions

Brief Overview of the HIE

• Washington State HITech grant dollars were used to fund a statewide health information exchange.– OneHealthPort managed the vendor selection process

and designed the HIE model based on community/constituent input

– OHP HIE is an “exchange” model – no central repository

– OHP HIE can leverage many large existing repositories (EPIC, EHRs, DOH, HCA, etc.)

– OHP HIE provides secure, trusted trading options• Hosted central web services

• Central meeting point for secure connections

• Leveraging and promoting data standards

The Initiative’s Key Drivers• To reduce Rx misuse we need to Increase Provider

Use:– SAMHSA Grant Funding Opportunity

– Operational funding for PMP program is in place

– Medicaid budget proviso requiring ER prescribers to register for PMP access (effective June 2012)

– DOH pain management rules recommend PMP use (from ESHB 2876 – all rules effective by January 2012)

– LNI guideline for opioid prescribing requires PMP use• http://www.lni.wa.gov/ClaimsIns/Files/OMD/MedTreat/FINALOpioidGuideline010713.pdf

(effective July 2013)

Prescription Monitoring Program

The WA State Department of Health (DOH) operates a repository of dispensed medications, known as the Prescription Monitoring Program (PMP) hosted by Health Information Designs, LLC (HID). • Repository represents a history of controlled substance

prescriptions dispensed from licensed pharmacies or licensed practitioners.

• Access to that data is provided via the Health Information Exchange (HIE) to:– licensed practitioners (valid current registration with the online

PMP system)

– making a secure query from a health information system connected to the HIE.

The response provided from the PMP database via the HIE is:• A real-time transaction based on the authentication

of the requestor’s license (pre-registration of the user in the online PMP system) and…

• A match of the patient record requested • The request and response utilize the NCPDP Script

standard for medication history. – OHP HIE is utilizing the NCPDP 2013.12 standard.

Prescription Monitoring Program

• Pre-requirements– Requestors of medication history from the DOH PMP

repository have registered in the Prescription Review service online at http://www.wapmp.org/practitioner/pharmacist/.

– Any organization planning to automate the queries can request to use the license of a Medical Director and must contact the Department of Health PMP program director for education and information about the implications for that practitioner before implementation.

Prescription Monitoring Program

• Secure, encrypted connectivity – Certificate exchange and authentication

– Certificate handling by the HIE hub for signing and encrypting all messages

• Specifically with HID the PMP vendor, certificate authentication rules applied for signing and encrypting all messages is in the order specified by HID as SignBeforeEncryptAndEncryptSignature

– Secure handling includes signature validation and encryption of ALL messages as well as transport over https.

– The messages are fully secured and posted to secure URLs designated by the DOH vendor, HID, and OHP-HIE.  The keys for this process are only shared between the HIE hub and the DOH vendor.

PMP Security

• Secure, encrypted connectivity – The response message is a synchronous transaction. The

message channel is open for the response which is a few second wait at most. 

– The HIE receives the response on the same thread programmatically decrypting, stripping the PMIX SOAP wrapper, re-encrypting and forwarding to the querying trading partner.

– No PHI is exposed or stored by the HIE.

– The HIE provides an audit trail of all transactions traded and can identify which trading partners are involved in the information exchange via message metadata including the routing identification of the trading partners

PMP Security

• OneHealthPort was a “stakeholder” participant in the earlier S & I workgroup evaluating PMP standards. – The recommendation from that work was that NCPDP standards

should be incorporated in PMP exchanges to facilitate adoption and minimize development efforts for EHR vendors.

• Concurrently, the WA State DOH came to OHP for assistance in moving forward their SAMHSA grant for connecting EHRs to the State PMP

• WA DOH, their vendor - HID, and OHP jointly evaluated options with the standards recommendations in mind and moved forward with a solution for interoperability

PMP Standards

PMP Standards

PMP Standards – PMIX Soap Wrapper

Lessons Learned• If you build it, “they” may not necessarily come

– Must have business reason and/or regulatory requirements to truly engage healthcare providers who have limited resources

• It’s not rocket science, but…– It takes willing, ready and able vendors, exchanges, and trading

partners

– Creative problem solving

– Development effort

– Tenacity, professionalism, and sometimes, good humor

Additional Levers• Stage 2: Meaningful Use Approval: WA DOH has obtained

approval to list the PMP as an official “other specialized registry” in compliance with stage 2 meaningful use– It will be listed as an Eligible Professionals (EP) Menu item

– We feel this will assist trading partners with finding a business reason to connect

• DOH and other state agencies are moving towards mandated participation in the state-wide health information exchange (HIE)– DOH has several health systems that will be accessed via the

HIE

Questions?

PDMP & Health IT Integration Use Case & Functional Requirements

January 28, 2014

21

Proposed Use Case & Functional Requirements Development Timeline

22

Week Target Date (2014) All Hands WG Meeting Tasks Review & Comments from Community via Wiki page

due following Monday @ 12 noon

1 1/7Use Case Kick-Off & UC Process Overview

Introduce: In/Out of Scope, Context Diagram and ScenarioConcert Series Presentation: ASAP

Review: In/Out of Scope, Assumptions, Context Diagram

2 1/14 Review: In/Out of Scope, Context Diagram, Assumptions , ScenarioIntroduce: User Stories

Review: User Stories, In/Out of Scope, Assumptions, Context Diagram

3 1/21 Review: In/Out of Scope, Context Diagram, Assumptions , ScenarioIntroduce: User Stories

Review: User Stories, In/Out of Scope, Assumptions, Context Diagram

4 1/28Review: Context Diagram and User StoriesIntroduce: Pre/Post Conditions, Actor and RolesConcert Series Presentation: OneHealthPort & WADOH

Review: Pre/Post Conditions, Actors and Roles, User Stories

5 2/4 Review: Finalize User Stories, Pre/Post conditions, Actors and RolesIntroduce: Activity Diagram and Base Flow Review: Activity Diagram and Base Flow

6 2/11 Review Activity Diagram and Base FlowIntroduce: Functional Requirements and Sequence Diagram

Review: Functional Requirements , Sequence Diagram , Activity Diagram and Base Flow

7 2/21 Review Functional Requirements and Sequence DiagramIntroduce: Data Requirements and Issues and Risks Review: Data Requirements and Issues and Risks

2/25 HIMSS Meeting

8 3/4 Review: Data Requirements and Risks & IssuesBegin End-to-End Review End-to-End Review by community

9 3/11 End-to-End Comments Review & disposition End-to-End Review ends

10 3/18 Finalize End-to-End Review Comments & Begin Consensus Begin casting consensus vote

11 3/25 Consensus Vote* Conclude consensus voting

Note- Below sections will be reviewed within the separate Use Case word document: 1. Discuss and review the following sections:

1. Assumptions2. Context Diagram 3. User Stories

2. Introduce and review the following sections:1. Pre-Conditions2. Post-Conditions3. Actors and Roles

Section Review

23

Click the icon to open the

Word DocumentSections for

Review

Use Case Assumptions

1. Health IT system is capable of querying a PDMP2. All Healthcare Professionals have appropriate legal authority based on

state regulations to request and receive information from state PDMP3. Healthcare Professionals accessing the PDMP follow state guidelines as

appropriate, including any privacy and security requirements as required by each individual state PDMP authority

4. The PDMP returns high positive matches to the Healthcare Professional1

5. The Healthcare Professional accesses information that already exists within the PDMP at the time of querying

6. Each organization has the responsibility to figure out how query response is presented and integrated

To be reviewed in Word Document

1 Question for Community: What are the responses you receive when querying a PDMP?

24

Generic Scenario & Context Diagram

Pre-Step: Healthcare Professional logs into Health IT System

1. Sends query to state PDMP

Healthcare Professional receives requested information

PDMP & HIT Integration Use Case Scope

2. PDMP sends query response

Pre-Step: Healthcare Professional logs into Health IT System

1. Sends query to state PDMP

Healthcare Professional receives requested information

PDMP & HIT Integration Use Case Scope

2. PDMP sends query response

Interstate Hub

AND/OR

To be reviewed in Word Document

25

User Story 1: A legally authorized provider queries PDMP before writing a prescription for a patient

Trigger: Patient needs medication for chronic back pain

1. Healthcare Professional logs into Health IT System 2. Sends query to state PDMP to check if patient has

been prescribed narcotics/controlled substance in past X weeks

4. Healthcare Professional makes an informed decision to prescribe medication based on information received

Use Case Scope

3. PDMP sends query response

26

• Draft User Story: A patient arrives at the physician’s office or hospital for treatment of chronic back pain. If necessary, the Healthcare Professional authenticates to the Health IT system. At the appropriate point in the workflow, the query is sent to the State PDMP to see if the patient had been prescribed a controlled substance in the past X weeks. The PDMP processes the request and identifies the appropriate response to send back to the requestor. After receiving the query response from the PDMP, the Healthcare Professional makes an informed decision of whether or not to prescribe the medication or modify the dosage based on the information received.

To be reviewed in Word Document

User Story 2: A legally authorized provider queries PDMP through a Hub before writing a prescription for a patient

Trigger: Patient needs medication for chronic back pain

1. Healthcare Professional logs into Health IT System 2. Sends query to state PDMP to check if

patient has been prescribed narcotics/controlled substance in past X weeks

4. Healthcare Professional makes an informed decision to prescribe medication based on information received

Use Case Scope

3. PDMP sends query response

27

• Draft User Story: A patient arrives at the physician’s office for treatment of chronic back pain. If necessary, the Healthcare Professional authenticates to the Health IT system. At the appropriate point in the workflow, the query is sent to a Hub through his Health IT system to see if the patient had been prescribed a controlled substance in the past X weeks. The Hub receives the query, and reroutes the query to the appropriate state PDMP(s) (Note: this transaction implies that a Memorandum of Understanding is already in place between state PDMPs). The PDMP(s) process the request and identify the appropriate response to send back to the requestor. The PDMP(s) send the query response to the Hub involved in the transaction. The Hub reroutes the query response back to the Health IT system where the query originated. After receiving the query response(s), the Healthcare Professional makes an informed decision of whether or not to prescribe the medication or modify the dosage based on the information received.

To be reviewed in Word Document

Interstate Hub

User Story 3: Pharmacist queries PDMP prior to dispensing opioids to a patient

Trigger: Patient arrives at pharmacy and drops off prescription to be filled

1. Pharmacist logs into Pharmacy Dispensing System

2. Sends query to state PDMP to check if patient has received narcotics/controlled substance in past X weeks

3. PDMP sends query response

4. Pharmacist makes an informed decision to dispense medication based on information received

Use Case Scope

28

• Draft User Story: A patient arrives at the pharmacy to have his prescription filled. The pharmacist logs into the Pharmacy Dispensing system, and she enters her credentials. After, she sends a query to the State PDMP through her Pharmacy Dispensing system to see if the patient had filled a prescription for a controlled substance in the past X weeks. The PDMP processes the request and identifies the appropriate response to send back to the requestor. After receiving the query response from the PDMP, the pharmacist makes an informed decision of whether or not to dispense the medication based on the information received.

To be reviewed in Word Document

Pre/Post ConditionsPre-Conditions1. The necessary access controls and

authorization protocols based on State and/or Federal regulations (which could include patient consent or privacy permissions) for any of the systems or users described, are in place1. The Health IT system application can

provide any necessary authorization, authentication or privacy information to the PDMP

2. An intermediary, such as a Hub, provides necessary technology infrastructure to allow PDMP data exchange from the PDMP to the Health IT system

3. Query parameters required to create the query in a standardized format by the Health IT system/Hub are recognized and accepted by the PDMP system

4. The PDMP system can provide a query response in a standardized format recognized and accepted by the Hub/Health IT system

5. The PDMP system has knowledge about the Hub and the Hub has knowledge about the Health IT system to send a query response (this is in the event a request is parsed out to other states and the other states respond back)

6. Health IT System and PDMP have a common understanding of the shared vocabulary that is used to create the queries and provide the query results

7. Health IT System is able to determine which state PDMP(s) should receive the query

To be reviewed in Word Document

29

Post-Conditions1. Health IT System has sent a query2. PDMP system has received the query3. PDMP system has sent a response to the Health

IT system4. Health IT system has successfully received the

query results from the PDMP system5. Health IT system can display/present query

response

Actors and RolesTo be reviewed in Word Document

30

Actor System RoleHealth Care Professional

Health IT System Send query Receive query response

PDMP PDMP System Receive query Send query response

Hub Hub ? ?

Looking Forward:Proposed Use Case & Functional Requirements Development Timeline

31

Week Target Date (2014) All Hands WG Meeting Tasks Review & Comments from Community via Wiki page

due following Monday @ 12 noon

1 1/7Use Case Kick-Off & UC Process Overview

Introduce: In/Out of Scope, Context Diagram and ScenarioConcert Series Presentation: ASAP

Review: In/Out of Scope, Assumptions, Context Diagram

2 1/14 Review: In/Out of Scope, Context Diagram, Assumptions , ScenarioIntroduce: User Stories

Review: User Stories, In/Out of Scope, Assumptions, Context Diagram

3 1/21 Review: In/Out of Scope, Context Diagram, Assumptions , ScenarioIntroduce: User Stories

Review: User Stories, In/Out of Scope, Assumptions, Context Diagram

4 1/28Review: Context Diagram and User StoriesIntroduce: Pre/Post Conditions, Actor and RolesConcert Series Presentation: OneHealthPort & WADOH

Review: Pre/Post Conditions, Actors and Roles, User Stories

5 2/4 Review: Finalize User Stories, Pre/Post conditions, Actors and RolesIntroduce: Activity Diagram and Base Flow Review: Activity Diagram and Base Flow

6 2/11 Review Activity Diagram and Base FlowIntroduce: Functional Requirements and Sequence Diagram

Review: Functional Requirements , Sequence Diagram , Activity Diagram and Base Flow

7 2/21 Review Functional Requirements and Sequence DiagramIntroduce: Data Requirements and Issues and Risks Review: Data Requirements and Issues and Risks

2/25 HIMSS Meeting

8 3/4 Review: Data Requirements and Risks & IssuesBegin End-to-End Review End-to-End Review by community

9 3/11 End-to-End Comments Review & disposition End-to-End Review ends

10 3/18 Finalize End-to-End Review Comments & Begin Consensus Begin casting consensus vote

11 3/25 Consensus Vote* Conclude consensus voting

Next Steps• Review: Pre/Post Conditions, Actors and Roles, and User

Stories

• Next Meeting is Tuesday, February 4 from 12:00pm - 1:30pm EST

• Reminder: All PDMP & HIT Integration Announcements, Meeting Schedules, Agendas, Minutes, Reference Materials, Use Case, Project Charter and general information will be posted on the PDMP Wiki page– http://wiki.siframework.org/PDMP+%

26+Health+IT+Integration+Homepage

32

Contact Information• For questions, please feel free to contact your support leads:

– Initiative Coordinators: • Johnathan Coleman jc@securityrs.com• Sherry Green sgreen@namsdl.org

– ONC Leads:• Mera Choi mera.choi@hhs.gov• Jennifer Frazier Jennifer.Frazier@hhs.gov• Helen Caton-Peters Helen.Caton-Peters@hhs.gov

– SAMHSA Leads• Jinhee Lee Jinhee.Lee@samhsa.hhs.gov• Kate Tipping Kate.Tipping@samhsa.hhs.gov

– Support Team:• Project Management:

– Jamie Parker jamie.parker@esacinc.com– Ali Khan Ali.Khan@esacinc.com (Support)

• Use Case Development: – Ahsin Azim Ahsin.Azim@accenturefederal.com – Presha Patel presha.patel@accenture.com

• Vocabulary and Terminology Subject Matter Expert: – Mark Roche mrochemd@gmail.com

33