We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byGeoffrey Sedlock
Modified over 4 years ago
Copyright © 2001 HL7 HL7: Standards for e-Health CCOW Context Management Standard Robert Seliger CCOW Co-Chair President and CEO, Sentillion, Inc. firstname.lastname@example.org Barry Royer CCOW Co-Chair Advisory Systems Designer, Siemens Medical Solutions Barry.email@example.com
Copyright © 2001 HL7 The Challenge Multiple disparate applications: labs, meds, cardiology, scheduling, billing, etc. Users in need of easy access to data and tools: physicians, nurses, therapists, administrators, etc. Kiosk as well as personal workstations: hospitals, clinics, offices, homes, etc.
Copyright © 2001 HL7 ( ) WHAT: Couple, Coordinate, Synchronize Applications at Point-of-Use. HOW: “Easy” Standards Using Component-Based Technology. WHY: Providers: Flexibility to Choose Applications They Want. Vendors: Faster to Market with Best-of-Class Solutions. Everyone: “Out-of-the-Box” Integration. WHEN: NOW! HL7 CCOW Technical Committee
Copyright © 2001 HL7 Example: Patient Link Nancy Furlow
Copyright © 2001 HL7 Standard Subjects Ratified as of V1.3: User Patient Encounter Observation Certificate Work in progress for CCOW V1.4: Various DICOM subjects Authenticate action subject
Copyright © 2001 HL7 Other Capabilities Secure Subjects - Only applications with access privileges may set or get (e.g., User) Dependent Subjects - The value of a subject must be consistent with the value for another subject (e.g., Encounter depends on Patient) Custom Subjects - May be defined by healthcare providers and/or vendors, distinct from HL7’s standard subjects Annotation Subjects - Data that is in addition to a subject’s identity (e.g., a Certificate is an annotation for the User subject)
Copyright © 2001 HL7 Subject Hierarchy User* Patient Encounter Observation Certificate* * = secure subject = identity subject = annotation subject
Copyright © 2001 HL7 Architecture Disparate Applications Context Manager / CCOW Interfaces Copyright © 2000 Sentillion, Inc. CCOW Mapping Agent Annotation Agent CCOW
Copyright © 2001 HL7 Implementations Copyright © 2000 Sentillion, Inc. Agent Context Manager Client-Centric DB Agent Context Manager Server-Centric Web Server
Copyright © 2001 HL7 Component Architecture or CP Application #1 Implementation CM CD Context Manager Implementation Common Context Data Optional Mapping Agent Implementation MA II Tool, etc. Application #N Implementation Optional Annotation Agent Implementation CA II Tool, etc. CA Interface Legend CP context participant CM context manager CD context data II implementation interface MA mapping agent CA context agent
Copyright © 2001 HL7 ActiveX Component Mapping Interface Legend CP context participant CM context manager CD context data II implementation interface MA mapping agent CA context agent AR authorization repository SB secure binding SD secure context data CA II CP Application #N Implementation CP Application #1 Implementation CMSD Context Manager Implementation Common Context Data Optional Context Agent Implementations Optional External Authentication Repository Implementation AR SB II Tool, etc. SB CD Windows Registry
Copyright © 2001 HL7 Web Component Mapping CA II CP Application #N Implementation CP Application #1 Implementation CMSD Context Manager Implementation Common Context Data Optional Context Agent Implementations Optional External Authentication Repository Implementation AR SB II Tool, etc. SB CD Context Management Registry CMR Listener Applet Notify Applet Interface Legend CP context participant CM context manager CD context data II implementation interface MA mapping agent CA context agent AR authorization repository SB secure binding SD secure context data CMR context management registry
Copyright © 2001 HL7 Simple Context Lifecycle User Application AAAContextManagerApplication BBB I choose "Sam Smith" CM::StartContextChanges CM::JoinCommonContext(CP iface to AAA, surveyYes) CD::SetItemValues CM::EndContextChanges survey results: all applications accept CM::PublishChangesDecision("accept") CM::JoinCommonContext(CP iface to BBB, surveyNo) CP::ContextChangesAccepted CM::LeaveCommonContext "Sam Smith" CD::GetItemValues item values
Copyright © 2001 HL7 Context Change Process Application XX ( 1) User selects the patient of interest from any application on the clinical desktop Context Manager Application YY Application ZZ (5) Context manager tells the other applications that a new patient context has been proposed. The context manager surveys the applications to determine whether each can apply the new context. (8) Context manager tells each application to apply new context, or that the transaction has been cancelled. ( 6) Each application indicates whether or not it can apply the new context. (2) Application tells the context manager to start a context change transaction and sets the context data to indicate the newly selected patient. (7) If one or more of the applications cannot or prefers not to apply the new context, the user is asked to decided whether to continue, or cancel. ( 3) Context manager tells patient mapping agent that context change is occurring; mapping agent supplies the context manager with other identifiers by which the patient is known. ( 9) Each application applies the new context if instructed to do so by the context manager. Each application gets the new patient context from the context manager. Demographics Annotation Agent (Optional) ( 4) Context manager tells demographics annotation agent that context change is context manager with authentic demographics data occurring; annotation agent supplies Patient Mapping Agent (Optional)
Copyright © 2001 HL7 CCOW Standard Status 1.0 (Ratified April 1999) Component Architecture Common Links: Patient Link Secure Links: User Link Component Interfaces for: Applications Context Manager Patient Mapping Agent User Mapping Agent Authentication Repository Technology Mapping to COM User Interface for Windows 1.1 (Ratified January 2000) Inter-dependent Subjects: Encounter Link Custom Subjects and Items Conformance Statements 1.2 (Ratified May 2000) Technology Mapping to Web 1.3 (Ratified January 2001) Additional Security Capabilities Annotation Agents Observation Link Digital Certificate Annotation 1.4 (Scheduled January 2002) Action Subjects (Authenticate) DICOM Study Link Multiple User Contexts / One Device Change Event Filters 1.5 (Scheduled May 2002) Technology Mapping to SOAP Nested contexts Wireless Devices
IT Infrastructure Glen Marshall Siemens Health Solutions IHE IT Infrastructure Committee Co-chair.
HL7 CCOW Tutorial - St. Louis - September 2000
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Patient Identifier Cross-referencing for MPI (PIX) Profile Mike Henderson.
IHE Workshop – June 2006What IHE Delivers 1 Cynthia A. Levy Cedara Software IHE Technical Committee Import Reconciliation Workflow Profile.
© 2006 Canada Health Infoway Inc. 1 January 16, 2007 Dennis Giokas Chief Technology Officer Canada Health Infoway Inc. Architecture and Standards at Infoway.
IHE Canada Workshop – Sept What IHE Delivers 1 Kevin ODonnell Toshiba Medical Systems IHE Structure & Concepts.
September, 2005What IHE Delivers 1 Lloyd Hildebrand, M.D., American Academy of Ophthalmology, Medical Information Technology Committee Chair IHE Eye Care.
Copyright 2008 Keystone Health Information Exchange TM IHE Connectathon January 29,2008 Jim Younkin KeyHIE Project Director.
Aspects of DICOM for Patient Safety
1 HL7 Educational Session – eHealth Week Budapest 2011 © Health Level Seven International, Inc. All Rights Reserved. HL7 and Health Level Seven.
SAML CCOW Work Item: Task 2
DICOM Structured Reporting Workshop - March 2000 Structured Reporting and the IHE Year 2 Technical Framework Simon Wail, PhD Marconi Medical Systems.
DIGIDOC A web based tool to Manage Documents. System Overview DigiDoc is a web-based customizable, integrated solution for Business Process Management.
Copyright HEALTHone Global – July 2009 The HEALTH one EHR server.
Electronic Health Record Systems: What are They, Why have They Failed for so Long, and What Progress is Being Made Now? C. Peter Waegemann CEO, Medical.
Overview of IHE IT Infrastructure Integration Profiles IHE IT Infrastructure Technical Committee Charles Parisot, GE Medical Systems Information Technologies.
0 UMN 2011 ERP Terapan SAP BASIS General Concept Session # 3.
Bringing HIPAA to Hospital Systems HIPAA impact on hospital systems viaMD solution for HIPAA compliance W e b e n a b l i n g Pa t i e n t A d m i t t.
1 1 Secure Medical Information Exchange (MIX ™ ) System Sead Muftic SETECS Medical Technologies SETECS MIXSystem SETECS ® MIX ™
ECHO: NASA’s E os C learing HO use Integrating Access to Data Services Michael Burnett Blueprint Technologies, 7799 Leesburg.
© 2019 SlidePlayer.com Inc. All rights reserved.