360x Overall Flow and Interactions Primary goals are to: Standardize the type of data exchanged and how the data is transported. Provide transparency to.

Slides:



Advertisements
Similar presentations
The Performance Appraisal Process
Advertisements

Electronic Submission of Medical Documentation (esMD) eDoC Administrative Documents Templates for HL7 Orders October 25, 2013.
SERVICE MANAGER 9.2 PROBLEM MANAGEMENT TRAINING JUNE 2011.
Joint Portal USER CONFERENCE & SYMPOSIUM 2013 MASTERING HEALTHCARE STRATEGIES AUSTINTEXAS.
Request Management Mirror-. A random three day sample of Incidents revealed that about 86% of the registered Incidents were legitimate Requests Many other.
Meaningful Use Stage I Core Objectives
Improving health and healthcare one network connection at a time... Copyright 2011, Sooner Health Access Network.
and Patient Information Reconciliation
Next Throughout this demo, if nothing happens for a couple of seconds click ‘Next’ to continue … SCI Gateway Product Demonstration Updated next.
Eugenie Coakley, Susan Grantham, Alec McKinney, Natalie Truesdell, Melina Ward May 4, 2012.
CareCentrix Direct Training.
How Do I Evaluate Workflow?
Going with the Flow All you ever wanted to know about flowcharting Jay Ford.
Changes to Medical Documentation Form and Requirements 1.
HUD-VASH Case Management System Paul Smits, MSW Associate Chief Consultant, Roger Casey, PhD Director, Grant and Per Diem Program.
S&I Framework Provider Directories Initiative esMD Work Group October 19, 2011.
TIU Management - Notes. OBJECTIVES Use naming conventions and standardization Create and Inactivate a Note Title Change or Rename a Note Title Reassign.
Companion Guide to HL7 Consolidated CDA for Meaningful Use Stage 2
What is Workflow?. Defining workflow Definitions of workflow vary. Here are a couple: –The flow of work through space and time, where work is comprised.
© 2008 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat &
CHAPTER 22 PENDING RESULTS. OBJECTIVES Process the incomplete charts using the Pending processors Process a referral using the Referral dashboard.
E-Referral enabled collaborative health care Opportunities and considerations Presented by: Sasha Bojicic Emerging Technology Group Canada Health Infoway.
Safe Transitions Of Care STOC 2011 MHA Pilot- 4Q 2010 Transition responsibility belongs to the sending clinician/organization, until the receiving practitioners.
GAC-GNSO Consultation Group On GAC Early Engagement in GNSO PDP London Progress Report 22/06/2014.
WHY is EHDI a part of the HIT conversation A first encounter between providers and public health As an encounter, communication becomes essential Communication.
Disclosure I have no relevant financial relationships with the manufacturers of any commercial products and/or provider of commercial services discussed.
Information Assurance The Coordinated Approach To Improving Enterprise Data Quality.
Radiology Participant Workshop, Oct Notification Options for Scheduled Workflow Departmental Appointment Notification Availability of PPS-Referenced.
Affordable Healthcare IT Solutions. MU RX Compliance with Meaningful Use Stage 2.
Developed for GRHCC Charles Schmitt MD 3/11/2007 Taking Care of Business Managing Consults in RPMS-EHR For Sending Consults.
Harmonizing Clinical Information Between Patient Record Systems: Distinguishing Information from Data.
November, 2012What IHE Delivers XDW (Cross-Enterprise Document Workflow) & XBeR-WD (Cross-Enterprise Basic eReferral Workflow Definition) Workflow Management.
Continuous Improvement Story Cover Page The cover page is the title page Rapid Process Improvement Story Template O Graphics are optional This CI Story.
Year 1 Semester 2 E*Value Training for Students (Training 2) WASHINGTON STATE UNIVERSITY COLLEGE OF NURSING | GRADUATE PROGRAMS (Click to advance to next.
 Read through problems  Identify problems you think your team has the capacity and interest to solve  Prioritize the problems and indicate the.
Subject to Consultation Insert Slide Title Here Insert Name and Date Here.
Mandatory Payload = MU2 Consolidated CDA. Qualifier: "leniency" (allowance for null or alternative codes) should be allowed in the following areas of structured.
Standards Analysis Summary vMR –Pros Designed for computability Compact Wire Format Aligned with HeD Efforts –Cons Limited Vendor Adoption thus far Represents.
Unified Case Management Treatment Plan Training June 2008.
Developed for GRHCC Charles Schmitt MD 3/11/2007 Taking Care of Business Scheduling/Managing Consults in RPMS-EHR For Front Desk Personnel.
Review of Infoway’s COPD* Use Case for Care Plan Business Requirements Sasha Bojicic, Canada Health Infoway Ron Parker, Canada Health Infoway
Longitudinal Coordination of Care. Agenda Confirm Community Work Streams Use Case and Policy Whitepaper Approach Recommendation for Use Case scoping.
HR Action Request The Ohio State University OAA HR Service Center.
EsMD Harmonization Mapping Analysis for X & X
Out the Door (Overview) Chapter 12. Objective  Understand the Visit Documentation screen.
GEtServices Purchasing Units & Materials Training For Suppliers Request.
Human Resources 1 G-Top Global Workflow Employee View September 2014.
HL7 SDWG Topic October 29, 2015 David Tao.  HL7 Success! C-CDA 2.1 is cited, and Care Plan is in 2015 Edition Certification Final Rule  Common Clinical.
Project management Topic 7 Controls. What is a control? Decision making activities – Planning – Monitor progress – Compare achievement with plan – Detect.
TITLE OF AUDIT Author Date of presentation. Background  Why did you do the audit? eg. high risk / high cost / frequent procedure? Concern that best practice.
© 2015 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
SIT Professional Development- Defining the Consultation Model Permission to reprint granted with appropriate acknowledgement ©2009 DPS.
Fundamentals of Workflow Analysis and Process Redesign
Interactions & Automations
Overview PRINCE Hogeschool Rotterdam. 2 Project definition  A project is a temporary organization that is created for the purpose of delivering.
Assumptions The base use case is a referral initiated by the PCP, and a response sent back by a specialist The minimal payload requirement is a CCDA structured.
Longitudinal Coordination of Care Use Case Scoping Discussion 3/19/2011.
The OASIS Feedback Process Using OASIS to Drive Improvement.
What’s New for Transition to Special Education Services? Paula E. Goff, Part C Coordinator May 23, 2013.
Innovations in Primary Care: Implementing Clinical Care Management in Primary Care Practices Judith Steinberg, MD, MPH Deputy Chief Medical Officer Jeanne.
Quality Case Practice Improvement
Hospice CTI Best Practice.
Conducting the performance appraisal
Conducting the performance appraisal
Using the Software ProtoMED Practice Management and Electronic Medical Records software enables users to … View schedules View patient information View.
MRA Member Summary, Open Conditions & Clinical Inference
How Do I Evaluate Workflow?
REFERRAL AND WOUND ASSESSMENT SUMMARY OF CARE DOCUMENT
SCOPA - Health 16 May 2018.
Comments Option to Print the Referral form as a pdf in a proper formatted way for external hospital referral.
Presentation transcript:

360x Overall Flow and Interactions Primary goals are to: Standardize the type of data exchanged and how the data is transported. Provide transparency to progress and/or gaps in care until the loop is closed Design a process with a low bar of entry for implementations Add value to clinicians and overall clinical workflows Focus is placed on the transport and data exchanged Referral transparency will be inferred by the payload content (no explicit status) to indicate various checkpoints throughout the referral lifecycle.

Referral Workflow Review Referral Initiator Referral Recipient Referral Request Data: Patient, Referral Identifier, Priority, Reason, etc. Documentation: Referral Note Referral Request Response (Accept/Decline) Data: Patient, Referral Identifier, Status Documentation: None required Referral Scheduled Notification (Optional) Data: Patient, Referral Identifier, Date/time of appointment, Location, Provider Documentation: None required Referral No Show Notification (Optional) Data: Patient, Referral Identifier, Status Documentation: None required Referral Findings (Close the Loop) Data: Patient, Referral Identifier, Status Documentation: Consult Note

Referral Request Data: Patient Identifier and demographics Referral Identifier Priority Referral Note Code (LOINC: ) Reason for Referral Should we send this as standardized structured content? How can we support clarity? If reasons are not sufficient, what else is necessary to resolve concerns? Order Information Documentation: Summary clinical data (C-CDA) Should this be required? Are all sections appropriate? How can we prevent too much data vs. too little?

Referral Request Response (Accept/Decline) Data: Patient Identifier Referral Identifier Order Status Ability to send codified reason if declined Documentation: None

Referral Scheduled Notification (Optional) Data: Patient Identifier Referral Identifier Date/time of appointment Appointment Location Assigned Provider Documentation: None.

Referral No Show Notification (Optional) Data: Patient Identifier Referral Identifier Date/time of appointment Appointment Location Assigned Provider Documentation: None.

Referral Findings (Close the Loop) Data: Patient Identifier and demographics Referral Identifier Documentation: Consult Note (C-CDA) Any other additional documentation?

Potential Exception Flows Referral Cancellation Referral Initiator would send a cancellation request Referral Recipient would reply with a cancellation confirmation Referral Patient Seen Notification Provides a checkpoint noting the desired care was provided, but the results are delayed and will be provided at a later date. Referral Interim Consultation Note In the case of chronic treatment or resolutions that require multiple visits, interim “progress” may be desired instead of one Referral Findings (Close the Loop) result.

Other Questions Can a detailed description of the current AMA implementation be provided? What are the strengths of the current approach? What are the opportunities for improvement? What is the overall workflow for a typical referral? What content is exchanged throughout the workflow? What are the transport mechanisms used to send/receive referrals? What are the metrics being captured and analyzed? What additional metrics are desired/necessary to achieve additional improvement? What are the timelines/expectations for piloting?

360x Workflow Specific Questions Is there a need to support multiple recipients? Should the C-CDA be required to initiate a referral request? If not, what supplemental documentation is necessary to reduce redundancy concerns? ???