pdmp & health it integration use case & functional requirements february 4, 2014 1
TRANSCRIPT
PDMP & Health IT Integration Use Case & Functional Requirements
February 4, 2014
1
PDMP & HIT Integration InitiativeProposed 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
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: Context Diagram and User StoriesIntroduce: Pre/Post Conditions, Actor and Roles
Review: Pre/Post Conditions, Actors and Roles, User Stories
6 2/11Review Pre/Post Conditions, Actors and Roles, User StoriesIntroduce: Activity Diagram , Base Flow, 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. Context Diagram2. User Stories3. Pre-Conditions4. Post-Conditions5. Actors and Roles
Section Review
3
Click the icon to open the
Word DocumentSections for Review
HIE/Pharmacy
Intermediary
In-State PDMP
Out of State PDMP
Hub
EHR or Pharmacy
System
Transactions Scope
From Via To
1 EHR/Pharmacy - In-State PDMP
2 EHR/Pharmacy HIE In-State PDMP
3 EHR/Pharmacy Hub In-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. Intermediary Hub In-State PDMP
1
2
3
4
2
3 6
5
PDMP/HITI User Stories with Alternate WorkflowsHIT 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 HubHIT 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
77
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
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
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
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
PDMP & HIT Integration – Pre/Post Conditions
Pre-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 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-Conditions1. 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
PDMP & HIT Integration – Actors and RolesTo be reviewed in Word Document
10
Actor System RoleHealth Care Professional
Health IT System Send query Receive query response
PDMP PDMP System Receive query Send query response
Hub Hub ? ?
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
11
Contact Information
• For questions, please feel free to contact your support leads:– Initiative Coordinators:
• Johnathan Coleman [email protected]• Sherry Green [email protected]
– ONC Leads:• Mera Choi [email protected]• Jennifer Frazier [email protected]• Helen Caton-Peters [email protected]
– SAMHSA Leads• Jinhee Lee [email protected]• Kate Tipping [email protected]
– Support Team:• Project Management:
– Jamie Parker [email protected]– Ali Khan [email protected] (Support)
• Use Case Development: – Ahsin Azim [email protected] – Presha Patel [email protected]
• Vocabulary and Terminology Subject Matter Expert: – Mark Roche [email protected]
12