Presentation is loading. Please wait.

Presentation is loading. Please wait.

Update to HL7 HL7 Working Group Meeting April-May 2003 Guy Mansfield, Ph.D. Health Informatics, IDX Systems A collaborative project to develop a universal.

Similar presentations


Presentation on theme: "Update to HL7 HL7 Working Group Meeting April-May 2003 Guy Mansfield, Ph.D. Health Informatics, IDX Systems A collaborative project to develop a universal."— Presentation transcript:

1 Update to HL7 HL7 Working Group Meeting April-May 2003 Guy Mansfield, Ph.D. Health Informatics, IDX Systems A collaborative project to develop a universal framework for encoding and disseminating electronic clinical guidelines A collaborative project to develop a universal framework for encoding and disseminating electronic clinical guidelines

2 Project Overview An R&D consortium to develop the technology infrastructure to enable computable clinical guidelines, that will be shareable and interoperable across multiple clinical information system platforms Scope: 3 year, $18 M, multi-site, collaborative project Partners in the project are: IDX Systems Inc. Apelon, Inc. Intermountain Healthcare (IHC) Mayo Clinic Stanford Medical Informatics (SMI) University of Nebraska Medical Center (UNMC) Funded in part by: NIST Advanced Technology Program IDX Health Informatics IHCUNMCMayoSMIApelon

3 Project Approach Level 1: Original text guideline Level 2: Structured markup Level 3: Scrubbed markup (disambiguated) Level 4: Codified markup (vocabulary standards) Level 5: Knowledge markup (structured knowledge) Level 6: Context markup (specify clinical setting) Level 7: Executable form (deployable knowledge) SAGE Jim Campbells Taxonomy of Guidelines

4 Project Approach Standards-based S harable A ctive G uideline E nvironment Ultimate goal: An infrastructure that will allow execution of standards-based clinical practice guidelines across heterogeneous CIS platforms. Focus is on the goal of active deployment of guideline knowledge within the workflow of clinical information systems. Employ (and extend where necessary), best available informatics standards and controlled terminologies. Build on an invaluable foundation of earlier research and effort. Close collaboration with leading Standard Development Organizations: HL7, SNOMED, LOINC, others.

5 SAGE Main deliverables An interoperable guideline model – A computable knowledge representation format for encoding the content and logic of executable clinical practice guidelines. A guideline workbench – A software tool for authoring, encoding, and maintaining guidelines in the format of the SAGE guideline model. A guideline deployment system – Software that decodes the content of electronic guidelines and surfaces that content via functions of the local clinical information system. Controlled resources -- Specification of a common layer of information models and terminologies to mediate guideline content. VMRCEMs Scenarios; HDF Guideline model components CIS interoperability specifications Terminologies

6 SAGE Main deliverables An interoperable guideline model – A computable knowledge representation format for encoding the content and logic of executable clinical practice guidelines. A guideline workbench – A software tool for authoring, encoding, and maintaining guidelines in the format of the SAGE guideline model. A guideline deployment system – Software that decodes the content of electronic guidelines and surfaces that content via functions of the local clinical information system. Controlled resources -- Specification of a common layer of information models and terminologies to mediate guideline content.

7 Imagine if SAGE technology were in place today... Author Encode Publish Import Install In Practice Evaluate Feedback Research, meta analysis, crafting the guideline Disambiguation, encoding, testing Guidelines.net? Guidelines-R-Us.com? Download to local care delivery organization Clinical editing, guideline set up Guidelines active in local CIS Outcomes research Consolidated feedback Guidelines would be routinely encoded in a standard, computable format, and would be widely available for downloading. Healthcare organizations would be able to import proven guidelines, and execute them via their local clinical information systems.

8 Guideline content encoded using standard terminologies and information models SAGE Guideline Execution Engine Standards- based API Local EMR concepts mapped to standard models for execution Clinical Information System ApplicationsEMR Common Layer of Terminologies and Information Models Patient Data Model (Virtual Medical Record) Care Workflow Model Medical Ontologies Health Care Organization Model SAGE Guideline Model Concepts DecisionsActionsContext Guideline Recommendation Sets DecisionsActions Metadata Route Expression Language Data queries and decision logic represented using standard expression language Binding Conceptual Overview of SAGE Architecture

9 Local Clinical Information System CIS Rule Execution System CIS Order Entry CIS Patient EMR Local CIS Resources Guideline File(s) SAGE Challenges: Guideline Deployment Concepts QueriesCIS Actions EventsEMR data SAGE Engine Guideline Execution Services Guideline goals Guideline context Guideline actions Guideline decisions

10 Imagine if...

11 Iterative Deployment Architecture Development Deployment System Requirements Use Case Prototyping Guideline scenario storyboarding Usability evaluation; use case analysis Deployment System Architecture Design Iterative Workbench Design and Development Iterative Guideline Model Specification End-to-end SAGE Integrated Testing SAGE Project Plan Overview Continuing Model Refinement (timeline approximate) Guideline Workbench Requirements Guideline Model Requirements Use Case Prototyping Controlled Resources (Phase 1) Controlled Resources (Phase 2) Aug 03Jan 04Jun 04Nov 04

12 Requirements Analysis Work Cycle 1.Select initial generic guideline 2.Define/storyboard specific scenarios 3.Model and evaluate user interactions (Mayo Usability Laboratory) 4.Document use cases 5.Perform UML Modeling

13 Selecting Exemplar Guidelines Exemplar Guideline Diabetes Management (DBM) Immunizations (IMM) Community Acquired Pneumonia (CAP) Total Joint Replacement (TJR) Clinical Domain Chronic disease monitoring and treatment. Acute exacerbation of chronic disease. Chronic disease as a comorbidity. Routine health maintenance, in both outpatient and inpatient settings. Emergency room evaluation and diagnosis. Outpatient treatment of acute disease. Inpatient and ICU treatment of acute disease. Follow-up of acute disease. Surgical guideline. Comprehensive pre-op workup, inpatient plan of care, and post-op outpatient management.

14 What is our Coverage of Universe of Guideline Content ??? DBM IMM CAP TJR DBM IMM CAP TJR Wide Coverage: Comprehensive Guideline Model Narrow Coverage: Limited Guideline Model ??? N scenarios for each guideline

15 1.Select initial generic guideline 2.Define/storyboard specific scenarios (clinical setting, roles, context) 3. Model and evaluate user interactions (Mayo Usability Laboratory) 4. Document use cases 5. Perform UML Modeling Apply HDF 101? Requirements Analysis Work Cycle

16 Making Guideline Content Specific Enough to Encode and Execute Scenario: Outpatient Visit Scenario: Pediatric Inpatient Text-based Ambiguous Text-based Specificity Added: Clinical context Care setting Care roles Care work flow Decision logic Actions defined Guideline File(s) Encoded Executable Generic Immunization Guideline

17 Specify Guideline Scenarios Completed with Clinician input. Modeled initially using PowerPoint slides

18 Model CIS User Interfaces Screens developed using VISIO/HTML Guideline recommendations integrated into a nurse care flowsheet View suggested orders Submit suggested orders Real time access to information – potentially via infobutton functionality Next Step: On to the Usability Lab

19 Usability Lab Evaluation Done using scenarios and prototypes Performed at Mayo Usability Laboratory

20 Usability Lab Evaluation Done using scenarios and prototypes Performed at Mayo Usability Laboratory

21 Use Case Documentation

22 UML Modeling Sequence diagrams

23 SAGE: Frequently Asked Questions Is the SAGE project developing guideline content ? No. While we are fully characterizing and encoding a small set of guidelines to be used in our R&D work, the main objective of the SAGE project is to enable a technology infrastructure for encoding and wide-spread dissemination of active guideline content. Is the SAGE project developing an IDX-specific solution ? No. We are using IDX Carecast as our prototyping CIS environment during the project; however, our goal is a universal infrastructure that will allow activation of guideline content in multiple HIS vendor systems. Where can I get more information on the SAGE project ? Our project web site is just coming online and will provide increasing detailed project updates in the near future.

24 Thank You ~


Download ppt "Update to HL7 HL7 Working Group Meeting April-May 2003 Guy Mansfield, Ph.D. Health Informatics, IDX Systems A collaborative project to develop a universal."

Similar presentations


Ads by Google