ToC Use Case Components Lightning Overview
11
ToC Use Case Components Lightning Overview Presented to LCC WG December 1, 2011 1
description
ToC Use Case Components Lightning Overview. Presented to LCC WG December 1, 2011. Purpose of the Use Case. The Use Case describes: The operational context for the data exchange The stakeholders with an interest in the Use Case - PowerPoint PPT Presentation
Transcript of ToC Use Case Components Lightning Overview
ToC Use Case Components Lightning Overview
Presented to LCC WGDecember 1, 2011
1
Purpose of the Use Case
2
The Use Case describes: • The operational context for the data exchange• The stakeholders with an interest in the Use Case• The information flows that must be supported by the data exchange• The types of data required in the data exchange
Use Case Outline
3
Use Case Development Process
4
Review of Key Use Case SectionsDefining the Actors• This section of the Use Case outlines the business actors that are participants in the
information exchange requirements for each scenario. A business actor is a person or organization that directly participates in a scenario. Thus, as a person or organization, the actor can (and should) be a stakeholder.
• The business actor must use a system to perform the functions and to participate in the information interchange. The system or system actor has roles (send, receive, publish, subscribe or in some cases display) and actions which involve exchanging content. Please see the table below for an example of these designations.
• NOTE: A Business Actor may be a Stakeholder and also can have more than one role.
5
Actor System Role
PCP EHR System Sender
Specialist EHR System Receiver
Patient PHR System Receiver
Transitions of Care – Use Case Diagram
6http://wiki.siframework.org/file/view/SIFramework_ToC_UC_v%201.1.docx
Transitions of Care – Context Diagram
7
Actors & Roles
Context Diagram
Actor System RoleProvider (Person) Electronic Health Record (EHR) System Sender/Receiver or Source/Destination HISP Health Information Service Provider The “wire” across which the health information
is sent from the sender to the receiverPatient Personal Health Record (PHR) System Sender/Receiver or Source/DestinationProvider Organization Electronic Health Record (EHR) System Sender/Receiver or Source/Destination Caregivers Personal Health Record (PHR) System Sender/Receiver or Source/Destination
Transition Of CareProvider_1
Send Clinical Summary, Consultation Request Summary Discharge Summary
and/or Discharge Instruction
Patient Receives Clinical Summary, Consultation Request
Summary, Discharge Summary and/or Discharge
Instructions
Provider_2
Receive Clinical Summary, Consultation
Request Summary Discharge Summary and/
or Discharge InstructionsSend Clinical Summary and Consult
Summary
Receive Clinical Summary and Consultation Summary
Updates Provider EHRs (Out of Scope)
http://wiki.siframework.org/file/view/SIFramework_ToC_UC_v%201.1.docx
Transitions of Care – Summary of Scenarios and User Stories
8
Scenario User Story/Stories Setting
Scenario One: The Exchange of Clinical Summaries from Provider to Provider
The Exchange of Information to Support the Transfer of Patient Information from One Provider to Another
• Hospital or Emergency Department from where patient is discharged (sends discharge summary to PCP or Care Team)• Patient's PCP or Care Team (receives discharge summary from Hospital or ED clinical system)
Closed Loop Referral • PCP's office (sends consultation request clinical summary to specialist)• Specialist's office (receives referral request clinical summary from PCP; send consultation summary to PCP)
Complex Series of Care Transactions • Emergency Department• Hospital• Rehabilitation Facility
Scenario Two: The Exchange of Clinical Summaries between Provider to Patient in Support of Transitions of Care
The Exchange of Discharge Instructions and Discharge Summary between a Provider and Patient to Support the Transfer of a Patient from One Care Setting to Another
• Hospital or ED from where patient is discharged (sends discharge instructions to patient).• Patient
The Exchange of Clinical Summaries between Provider and Patients to Support the Closed-loop Transfer of a Patient from One Care Setting to Another Consultation Referral.
• PCP’s Office• Specialists Office• Patient
ToC Sequence Diagram
9
Review of Key Use Case SectionsFunctional Requirements
10
Functional Requirements for Information Interchange
Scenario 1
Initiating System
Information Interchange Requirement Name
Receiving/Responding System
Hospital/ED EHR System
Send (A.XFER.1) Discharge Summary Receives (A.XFER.2) PCP EHR System
PCP EHR System
Send (A.XFER.1) Consultation Request Clinical Summary
Receives (A.XFER.2) Specialist EHR System
Specialist EHR System
Send (A.XFER.1) Consultation Summary Receives (A.XFER.2) PCP EHR System
Scenario 2Initiating System
Information Interchange Requirement Name
Receiving/Responding System
Electronic Health Record System
Send (A.XFER.1) Discharge Summary Receives (A.XFER.2) Personal Health Record System
Electronic Health Record System
Send (A.XFER.1 Discharge Instructions Receives (A.XFER.2) Personal Health Record System
Electronic Health Record System
Send (A.XFER.1) Consultation Request Clinical Summary
Receives (A.XFER.2) Personal Health Record System
Electronic Health Record System
Send (A.XFER.1) Clinical Summary Receives (A.XFER.2) Personal Health Record System
[1] This identifier comes from ONC-SI-UC Simplification spreadsheet. See references.[1] This identifier comes from ONC-SI-UC Simplification spreadsheet. See references.
Review of Key Use Case SectionsData Sets
11
[1] This identifier comes from ONC-SI-UC Simplification spreadsheet. See references.
Ref. Section Content Additional NotesT.CC.1 Personal
InformationName, DOB, Next of Kin, Address, Phone Number, Gender, Marital Status, Religion, Race, Ethnicity
T.CC.5 Allergies and Other Adverse Reactions
Allergy Type; and Date Substance intolerance Associated Adverse Events
List of allergies which might include allergy to what (e.g., medication. food, environment). Sensitivity. Past and those that have arisen
T.CC.6 Problem List Current Diseases & Conditions monitored for the patient and status
List of problems/complaints (what was diagnosis, complaint and/or descriptor of problem/complaints, symptoms).
How do these problems/complaints impact interventions, orders or instructions.
[1] This identifier comes from ONC-SI-UC Simplification spreadsheet. See references.
