1. PDMP & Health IT Integration Use Case & Functional Requirements February 4, 2014 1

2. PDMP & HIT Integration Initiative Proposed Use Case & Functional Requirements Development Timeline Week Target Date (2014) All Hands WG Meeting Tasks Review & Comments from Community via Wiki page due following Monday @ 12 noon 11/7 Use Case Kick-Off & UC Process Overview Introduce: In/Out of Scope, Context Diagram and Scenario Concert Series Presentation: ASAP Review: In/Out of Scope, Assumptions, Context Diagram 21/14 Review: In/Out of Scope, Context Diagram, Assumptions, Scenario Introduce: User Stories Review: User Stories, In/Out of Scope, Assumptions, Context Diagram 31/21 Review: In/Out of Scope, Context Diagram, Assumptions, Scenario Introduce: User Stories Review: User Stories, In/Out of Scope, Assumptions, Context Diagram 41/28 Review: Context Diagram and User Stories Introduce: Pre/Post Conditions, Actor and Roles Concert Series Presentation: OneHealthPort & WADOH Review: Pre/Post Conditions, Actors and Roles, User Stories 52/4 Review: Context Diagram and User Stories Introduce: Pre/Post Conditions, Actor and Roles Review: Pre/Post Conditions, Actors and Roles, User Stories 62/11 Review Pre/Post Conditions, Actors and Roles, User Stories Introduce: Activity Diagram, Base Flow, Functional Requirements and Sequence Diagram Review: Functional Requirements, Sequence Diagram, Activity Diagram and Base Flow 72/21 Review Functional Requirements and Sequence Diagram Introduce: Data Requirements and Issues and Risks Review: Data Requirements and Issues and Risks 2/25HIMSS Meeting 83/4 Review: Data Requirements and Risks & Issues Begin End-to-End Review End-to-End Review by community 93/11End-to-End Comments Review & dispositionEnd-to-End Review ends 103/18Finalize End-to-End Review Comments & Begin ConsensusBegin casting consensus vote 113/25Consensus Vote*Conclude consensus voting

3. Note- Below sections will be reviewed within the separate Use Case word document: 1.Discuss and review the following sections: 1.Context Diagram 2.User Stories 3.Pre-Conditions 4.Post-Conditions 5.Actors and Roles Section Review 3 Click the icon to open the Word Document

4. HIE/ Pharmacy Intermediary In-State PDMP Out of State PDMP Hub EHR or Pharmacy System Transactions Scope FromViaTo 1  EHR/Pharmacy -In-State PDMP 2  EHR/PharmacyHIEIn-State PDMP 3  EHR/PharmacyHubIn-State PDMP 4  In-state PDMP-Out of State PDMP 5 ? HIE/Ph. Intermediary-Out-of-State PDMP 6  Hub-Out-of-State PDMP 7 ? HIE/Ph. IntermediaryHubIn-State PDMP 1 2 3 3 4 2 3 3 6 5 PDMP/HITI User Stories with Alternate Workflows HIT to In-State PDMP: 1: HIT to In-state PDMP 2: HIT to In-state PDMP via HIE 3: HIT to in-state PDMP via Hub HIT to Out-of-State PDMP: 1+4: HIT to out-of-state PDMP via In-state PDMP 2+4: HIT to out-of-state PDMP via HIE & In-state PDMP 2+5: HIT to out-of-state PDMP via HIE 3+4: HIT to out-of-state PDMP via Hub & In-State PDMP 3+6: HIT to out-of-state PDMP via Hub 7: HIE to In-State PDMP via Hub 7 7 7 7

5. Generic Scenario & Context Diagram Pre-Step: Healthcare Professional authenticates to 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 authenticates to 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 5

6. 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 authenticates to 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 6 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

7. 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 authenticates to 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 7 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

8. 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 8 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

9. PDMP & HIT Integration – Pre/Post Conditions Pre-Conditions 1.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 place 1.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 9 Post-Conditions 1.Health IT System has sent a query 2.PDMP system has received the query 3.PDMP system has sent a response to the Health IT system 4.Health IT system has successfully received the query results from the PDMP system 5.Health IT system can display/present query response

10. PDMP & HIT Integration – Actors and Roles To be reviewed in Word Document 10 ActorSystemRole Health Care Professional Health IT System  Send query  Receive query response PDMPPDMP System  Receive query  Send query response Hub ????

11. Next Steps Review: Pre/Post Conditions, Actors and Roles, and User Stories Next Meeting is Tuesday, February 11 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 http://wiki.siframework.org/PDMP+%26+Health+IT+Integration +Homepage 11

12. Contact Information For questions, please feel free to contact your support leads: – Initiative Coordinators: Johnathan Coleman jc@securityrs.comjc@securityrs.com Sherry Green sgreen@namsdl.orgsgreen@namsdl.org – ONC Leads: Mera Choi mera.choi@hhs.govmera.choi@hhs.gov Jennifer Frazier Jennifer.Frazier@hhs.govJennifer.Frazier@hhs.gov Helen Caton-Peters Helen.Caton-Peters@hhs.govHelen.Caton-Peters@hhs.gov – SAMHSA Leads Jinhee Lee Jinhee.Lee@samhsa.hhs.govJinhee.Lee@samhsa.hhs.gov Kate Tipping Kate.Tipping@samhsa.hhs.govKate.Tipping@samhsa.hhs.gov – Support Team: Project Management: – Jamie Parker jamie.parker@esacinc.comjamie.parker@esacinc.com – Ali Khan Ali.Khan@esacinc.com (Support)Ali.Khan@esacinc.com Use Case Development: – Ahsin Azim Ahsin.Azim@accenturefederal.comAhsin.Azim@accenturefederal.com – Presha Patel presha.patel@accenture.compresha.patel@accenture.com Vocabulary and Terminology Subject Matter Expert: – Mark Roche mrochemd@gmail.commrochemd@gmail.com 12