ToC Use Case Components Lightning Overview Presented to LCC WG December 1, 2011 1.

Slides:

Advertisements

Similar presentations

XDM / XDR Point-to-Point Transmission of Documents

Advertisements

Consolidation Communicable Diseases User Stories: Meeting Agenda 1.News from other domains 2.Recap of a previous meeting 3.Consolidation of three more.

Consolidated User Story 1: Chronic Diseases (cancer, occupational health) Chronic Diseases, Outpatient Flow Patient, Provider/Physician, Laboratory, PH.

Longitudinal Coordination of Care (LCC) Pilots Template Insert the Name of Your Pilot / Organization Here MM/DD/YYYY.

Functional Requirements and Health IT Standards Considerations for STAGE 3 Meaningful Use for Long-Term and Post-Acute Care (LTPAC) Update to the HITPC.

CRYSTAL CLINIC ORTHOPAEDIC CENTER

A Plan for a Sustainable Community Behavioral Health Information Network Western States Health-e Connection Summit & Trade Show September 10, 2013.

How To Get To The Winners Circle with Your Patient Portal; Our Challenges To Get To The Finish Line. Julie Patterson, Baptist Health Carey Ronan, MHA,

Summary of Care Configuring RPMS-EHR for Meaningful Use Resource Patient Management System.

Meeting Stage 1 Meaningful Use Criterion Carlos A. Leyva, Esq. Digital Business Law Group, P.A.

Companion Guide to HL7 Consolidated CDA for Meaningful Use Stage 2

Overview of Longitudinal Coordination of Care (LCC) Presentation to HIT Steering Committee May 24, 2012.

Learning objectives:- 1. Introduction. 2. Define health record. 3. Explain types of health record. 4. Mention purposes of health record. 5. List general.

Proposed Meaningful Use Criteria for Stage 2 and 3 John D. Halamka.

Electronic Submission of Medical Documentation (esMD) eDoC eClinical Templates on FHIR using Structured Data Capture Use Case May 6, 2015.

Care Coordination and Information Exchange Integration of Health Information Exchange with Primary Care Provider Work Flow.

LCC Use Case 2.0 Paragraph As the number of Health Concerns increases, the health care of that individual becomes more complex. Often this complexity is.

Meaningful Use Personal Pace Education Module: Transitions of Care.

Standardized Discharge Summary Template Project Mary Shanahan, Senior Manager Dr John Edmonds, Clinical Director Medical Informatics.

Data Provenance –Use Case (Discovery) Ahsin Azim– Use Case Lead Presha Patel – Use Case Lead 1.

New Opportunity for Network Value: Using Health IT to Improve Transitions of Care 600 East Superior Street, Suite 404 I Duluth, MN I Ph

Decision Support for Quality Improvement

WHY is EHDI a part of the HIT conversation A first encounter between providers and public health As an encounter, communication becomes essential Communication.

S&I Framework Prescription Drug Monitoring Program & Health IT Integration Initiative Use Case & Functional Requirements Kickoff Meeting January 7, 2014.

Cardiac Episode with PCP referral to Cardiologist with Remote Monitoring & Follow-up Care Care Theme: Transitions of Care Use Case 9 Interoperability Showcase.

Overview of Interoperability Standards Advisory Steve Posnack Director of Office of Standards and Technology, ONC 1.

PDMP & Health IT Integration Use Case & Functional Requirements

S&I Public Health * We will start the meeting 3 min after the hour October 7 th, 2014.

Interoperability Showcase In collaboration with IHE Use Case 3 Care Theme: Leveraging National Healthcare Registries in Care Delivery Biosurveillance Monitoring.

Structured Data Capture (SDC) All Hands Meeting February 28, 2013.

HITPC – Meaningful Use Workgroup Care Coordination – Subgroup 3 Stage 3 Planning July 27, 2012.

Public Health Reporting Initiative Stage 3 Sprint: Implementation Guide Development Phone: x

Query Health Vendor Advisory Meeting 12/15/2011. Agenda Provide Overview of Query Health Seek Guidance and Feedback on Integration Approaches.

STEP Safe Transitions for Every Patient A CURRICULUM FOR PRIMARY CARE TRANSITIONS IN PRIMARY CARE.

Longitudinal Coordination of Care WG LCC All Hands Meeting

Collaborating with FADONA to Improve Care Coordination FHA Readmission Collaborative June 4, 2010.

Longitudinal Coordination of Care. Agenda Confirm Community Work Streams Use Case and Policy Whitepaper Approach Recommendation for Use Case scoping.

Meaningful Use Workgroup Report on Care Coordination Hearing David W. Bates, MD, MSc.

Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.

Referral Request and Referral Report Connie Sixta, PhD.

Data Provenance –Use Case (Discovery) Ahsin Azim– Use Case Lead Presha Patel – Use Case Lead 1.

Data Segmentation for Privacy November 16 th, 2011.

HIT Policy Committee Care Coordination Tiger Team Summary Tim Ferris Partners Healthcare October 28, 2010.

Longitudinal Coordination of Care (LCC) Workgroup (WG) LCC All Hands Meeting April 4,

MiPCT Embedded Case management Barriers to developing an embedded Case Management program.

Longitudinal Coordination of Care Use Case Scoping Discussion 3/22/2011.

Us Case 5 Care Coordination Following ICU/Hospital Encounter Care Theme: Transitions of Care Use Case 14 Interoperability Showcase In collaboration with.

The Patient Choice Project Use Case Development Introduction.

HITPC – Information Exchange Workgroup Care Coordination Discussions Stage 3 Planning July 26, 2012.

EU-US eHealth/Health IT Cooperation Initiative Interoperability of EHR Work Group August 21,

Source IT System ( LIS) Consumer IT System (Certified * Ambulatory EHR) Pre-Condition: The Source has received an Order from the Consumer (either Manually.

The Patient Choice Project Use Case Working Session February 5 th, 2016.

Longitudinal Coordination of Care LCP SWG Thursday, May 23, 2013.

David W. Bates, MD, MSc Chief Quality Officer, Brigham and Women’s Hospital Member, HIT Policy Committee President-elect, ISQua Medinfo, 2013.

Longitudinal Coordination of Care Use Case Scoping Discussion 3/19/2011.

Longitudinal Coordination of Care LCP SWG Thursday, July 11, 2013.

Data Provenance Community Meeting June 12 th, 2014.

2014 Edition Test Scenarios Development Overview Presenter: Scott Purnell-Saunders, ONC November 12, 2013 DRAFT.

Documentation in Practice Dept. of Clinical Pharmacy.

Interoperability Measurement for the MACRA Section 106(b) ONC Briefing for HIT Policy and Standards Committee April 19, 2016.

Relevant and Pertinent Short Survey Results (all responses) Final Analysis February 19, 2016 Robert Dieterle Holly Miller, MD Russel Leftwich, MD.

Referral Request and Referral Report

FROM PRIMARY CARE PHYSICIAN TO BEHAVIORAL HEALTH SPECIALIST

Clinical Data Exchange – Report Card

Nutrition in HL7 Standards

Nutrition in HL7 Standards

MEDICATION RECONCILIATION

, editor October 8, 2011 DRAFT-D

REFERRAL AND WOUND ASSESSMENT SUMMARY OF CARE DOCUMENT

Presentation transcript:

ToC Use Case Components Lightning Overview Presented to LCC WG December 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 Sections Defining 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 ActorSystemRole PCPEHR SystemSender SpecialistEHR SystemReceiver PatientPHR SystemReceiver

Transitions of Care – Use Case Diagram 6

Transitions of Care – Context Diagram 7 Actors & Roles Context Diagram ActorSystemRole Provider (Person)Electronic Health Record (EHR) SystemSender/Receiver or Source/Destination HISPHealth Information Service ProviderThe “wire” across which the health information is sent from the sender to the receiver PatientPersonal Health Record (PHR) SystemSender/Receiver or Source/Destination Provider OrganizationElectronic Health Record (EHR) SystemSender/Receiver or Source/Destination CaregiversPersonal Health Record (PHR) SystemSender/Receiver or Source/Destination

Transitions of Care – Summary of Scenarios and User Stories 8 ScenarioUser Story/StoriesSetting 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 Sections Functional 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 Send (A.XFER.1)Consultation Request Clinical Summary Receives (A.XFER.2)Specialist EHR System Send (A.XFER.1)Consultation SummaryReceives (A.XFER.2)PCP EHR System Scenario 2 Initiating 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.1Discharge InstructionsReceives (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 SummaryReceives (A.XFER.2)Personal Health Record System [1] [1] This identifier comes from ONC-SI-UC Simplification spreadsheet. See references. [1] [1] This identifier comes from ONC-SI-UC Simplification spreadsheet. See references.

Review of Key Use Case Sections Data Sets 11 [1] [1] This identifier comes from ONC-SI-UC Simplification spreadsheet. See references. Ref.SectionContentAdditional Notes T.CC.1Personal Information Name, DOB, Next of Kin, Address, Phone Number, Gender, Marital Status, Religion, Race, Ethnicity T.CC.5Allergies 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.6Problem ListCurrent 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] [1] This identifier comes from ONC-SI-UC Simplification spreadsheet. See references.