PDMP & Health IT Integration Use Case & Functional Requirements
19
PDMP & Health IT Integration Use Case & Functional Requirements February 25, 2014 1
description
PDMP & Health IT Integration Use Case & Functional Requirements . February 25, 2014. 1. PDMP & HIT Integration Initiative Proposed Use Case & Functional Requirements Development Timeline. Agenda. 2/21 All Hands Recap. During our last All Hands Call we reviewed: Use Case Scenarios - PowerPoint PPT Presentation
Transcript of PDMP & Health IT Integration Use Case & Functional Requirements
PDMP & Health IT Integration Use Case & Functional Requirements
February 25, 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, and Context Diagram
2 1/14 Review: In/Out of Scope, Context Diagram, Assumptions , ScenarioIntroduce: User Stories
Review: User Stories, In/Out of Scope, Assumptions, and Context Diagram
3 1/21 Review: In/Out of Scope, Context Diagram, Assumptions , ScenarioIntroduce: User Stories
Review: User Stories, In/Out of Scope, Assumptions, and 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, and User Stories
5 2/4 Review: Context Diagram and User StoriesIntroduce: Pre/Post Conditions, Actor and Roles
Review: Pre/Post Conditions, Actors and Roles, and User Stories
6 2/11 Review: Pre/Post Conditions, Actors and Roles, and User Stories Review: Pre/Post Conditions, Actors and Roles, and User Stories
7 2/21 Review: User Stories, Post Conditions, Actors and Roles, Activity Diagram and Base Flow Review: Activity Diagram and Base Flow
8 2/25 Review: Activity Diagrams, Base Flows, Functional Requirements and Sequence Diagrams Review: Functional Requirements and Sequence Diagrams
9 3/4 Review: Data Requirements and Risks & IssuesBegin End-to-End Review End-to-End Review by community
10 3/11 End-to-End Comments Review & disposition End-to-End Review ends
11 3/18 Finalize End-to-End Review Comments & Begin Consensus Begin casting consensus vote
12 3/25 Consensus Vote* Conclude consensus voting
Agenda
3
Topic Time Allotted
General Announcements 5 minutes2/21 All Hands Recap 5 minutesFinish reviewing Actors & Roles 15 minutesDiscuss Activity Diagrams, Base Flows, Functional Requirements and Sequence Diagrams
60 minutes
Next Steps/Questions 5 minutes
During our last All Hands Call we reviewed: 1. Use Case Scenarios 2. User Stories3. Post-Conditions4. Actors & Roles
2/21 All Hands Recap
4
Use Case ScenariosWhile it is understood that there are various workflows that can take place when a Healthcare Professional queries a PDMP (see full context diagram), for the purposes of this use case, we will be focusing on the transactions originating from the HIT to the next end point, which would be the PDMP, a Hub, or HIE/Pharmacy Intermediary
• Scenario #1 – HIT to In-State PDMP
• Scenario #2 – HIT to Hub
• Scenario #3 – HIT to HIE/Pharmacy Intermediary
EHR or Pharmacy
System
EHR or Pharmacy
SystemHub
EHR or Pharmacy
System
HIE/Pharmacy
Intermediary
5
Scenario #1 – HIT to In-State PDMP• User Story 1.1 – Legally authorized provider queries PDMP before writing a
prescription for a PDMP reported controlled substance for a patient
• User Story 1.2 – Pharmacist queries PDMP prior to dispensing a PDMP reported controlled substance to a patient
6
1. Query is sent to State PDMP to obtain patient history of controlled substances dispensed
2. PDMP sends query response
1. Query is sent to State PDMP to obtain patient history of controlled substances dispensed
2. PDMP sends query response
Scenario #2 – HIT to Hub• User Story 2.1 – Legally authorized provider queries PDMP through a hub before
writing a prescription for a PDMP reported controlled substance for a patient
• User Story 2.2 – Pharmacist queries PDMP through a Hub prior to dispensing a PDMP reported controlled substance to a patient
7
1. Query is sent to a Hub to obtain patient history of controlled substances dispensed
2. Hub sends query response
Hub
1. Query is sent to a Hub to obtain patient history of controlled substances dispensed
2. Hub sends query response
Hub
Scenario #3 – HIT to HIE/Pharmacy Intermediary• User Story 3.1 – Legally authorized provider queries PDMP through an HIE before
writing a prescription for a PDMP reported controlled substance for a patient
• User Story 3.2 – Pharmacist queries PDMP through a Pharmacy Intermediary prior to dispensing a PDMP reported controlled substance to a patient
8
1. Query is sent to an HIE to obtain patient history of controlled substances dispensed
2. HIE sends query response HIE
1. Query is sent to a Pharmacy Intermediary to obtain patient history of controlled substances dispensed
2. Pharmacy Intermediary sends query response
Pharmacy Intermediary
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 placeo The Health IT system application can provide
necessary/required authorization, authentication or privacy information to the PDMP
o The Health IT system can apply PDMP authorization requirements to restrict access to PDMP data to authorized users
2. If an intermediary, such as a Hub, is used it 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 which is recognized and accepted by the Hub/Health IT system
5. Health IT System and PDMP have a common understanding of the shared vocabulary that are required to initiate the queries and provide the query results
6. In the event a request is parsed out to other states and the other states respond back, the Health IT system, Hub (if applicable) and PDMP systems will have knowledge about the order of succession to provide the response
7. Health IT System or Hub is able to determine which state PDMP(s) should receive the query
9
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
Agenda
10
Topic Time Allotted
General Announcements 5 minutes2/21 All Hands Recap 5 minutesFinish reviewing Actors & Roles 15 minutesDiscuss Activity Diagrams, Base Flows, Functional Requirements and Sequence Diagrams
60 minutes
Next Steps/Questions 5 minutes
Note- Below sections will be reviewed within the separate Use Case word document: Discuss and review the following sections:
1. Actors & Roles2. Activity Diagrams and Base Flows3. Functional Requirements4. Sequence Diagrams
Section Review
11
Click the icon to open the
Word DocumentSections for Review
Agenda
12
Topic Time Allotted
General Announcements 5 minutes2/21 All Hands Recap 5 minutesFinish reviewing Actors & Roles 15 minutesDiscuss Activity Diagrams, Base Flows, Functional Requirements and Sequence Diagrams
60 minutes
Next Steps/Questions 5 minutes
•1.0 Preface and Introduction•2.0 Initiative Overview
– 2.1 Initiative Challenge Statement**•3.0 Use Case Scope
– 3.1 Background**– 3.2 In Scope– 3.2 Out of Scope– 3.3 Communities of Interest
(Stakeholders)** •4.0 Value Statement**•5.0 Use Case Assumptions•6.0 Pre-Conditions•7.0 Post Conditions•8.0 Actors and Roles•9.0 Use Case Diagram
Use Case OutlineTailored for each Initiative
•10.0 Scenario: Workflow– 10.1 User Story 1, 2, x, …– 10.2 Activity Diagram
o 10.2.1 Base Flowo 10.2.2 Alternate Flow (if needed)
– 10.3 Functional Requirementso 10.3.1 Information Interchange Requirementso 10.3.2 System Requirements
– 10.4 Sequence Diagram
•11.0 Dataset Requirements•12.0 Risks, Issues and Obstacles•Appendices
– Privacy and Security Considerations– Related Use Cases– Previous Work Efforts– References
** Leverage content from Charter
13
Review of Key Use Case SectionsActivity Diagram
• An Activity Diagram is a special form of a state transition diagram in which all or most of the states are activity states or action states
• The Activity Diagram illustrates the Use Case flows graphically, and represents the flow of events and information between the actors
– It also displays the main events/actions that are required for the data exchange and the role of each system in supporting the change
14
Review of Key Use Case SectionsFunctional Requirements• Functional Requirements identify the capabilities a system in a role must have in
order to enable interoperable exchange of the healthcare data of interest– They provide a detailed breakdown of the requirements in terms of the intended
functional behaviors of the application
• The Functional Requirements include:– Information Interchange Requirements– System Requirements
• The Information Interchange Requirements define the system’s name and role. They also specify the actions associated with the actual transport of content from the sending system to the receiving system
• System Requirements include the requirements internal to the system necessary to participate successfully in the transaction. System requirements may also detail a required workflow that is essential to the Use Case
15
• A Sequence Diagram is primarily used to show the interactions between objects in the sequential order that they occur
– This representation can make it easy to communicate how the exchange works by displaying how the different components interact
– The primary use of the diagram is in the transition from requirements expressed as use cases to the next and more formal level of refinement
• Note: Horizontal lines are used to identify the specific activity between the systems
Review of Key Use Case SectionsSequence Diagram
16
Agenda
17
Topic Time Allotted
General Announcements 5 minutes2/21 All Hands Recap 5 minutesFinish reviewing Actors & Roles 15 minutesDiscuss Activity Diagrams, Base Flows, Functional Requirements and Sequence Diagrams
60 minutes
Next Steps/Questions 5 minutes
Next Steps• Review: Functional Requirements and Sequence Diagrams
• Next Meeting is March 4, 2014 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
18
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]
19
