“Service Framework” workgroup

Slides:



Advertisements
Similar presentations
National HIT Agenda and HIE John W. Loonsk, M.D. Director of Interoperability and Standards Office of the National Coordinator Department of Health.
Advertisements

September, 2005What IHE Delivers 1 Joe Auriemma Siemens Medical Solutions, Health Services Senior Director, Integration Engineering Siemens Medical Solutions.
Interoperability Standards for Information Sharing and Safeguarding PM-ISE Slide 1 | Unclassified | Notional | DRAFT.
EHR stakeholder workshop – 11th October EHR integration for clinical research: toward new interaction models ? Isabelle de Zegher.
Test Automation Success: Choosing the Right People & Process
European Interoperability Architecture e-SENS Workshop : Cartography Tool in practise 7-8 January 2015.
Applying the SOA RA Utah Public Safety ESB Project Utah Department of Technology Services April 10, 2008 Prepared by Robert Woolley.
Overview of Nursing Informatics
Clinical Research Filtered Queries (CRFQ) from pilot to a service framework Introduction to break out sessions Isabelle de Zegher – Johan van der Lei 11.
AHCCCS/ASU Clinical Data Project March 17 th, 2009 Arizona Health Care Cost Containment Health System Medicaid Transformation Grant Program.
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Initial slides for Layered Service Architecture
EHR Integration – Project Charter slide 1 Goals  Support specification of the already started service specification within HL7 RCRIM –going to ballot.
Public Health Tiger Team we will start the meeting 3 min after the hour DRAFT Project Charter May 6, 2014.
Database Design - Lecture 1
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
TDT4252/DT8802 Exam 2013 Guidelines to answers
OneView Benefits Sales collaboration across network A “one-stop” utility portal Ease of use, scalability & accessibility Useful reports and metrics Improved.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
December 15, 2011 Use of Semantic Adapter in caCIS Architecture.
- 1 - Roadmap to Re-aligning the Customer Master with Oracle's TCA Northern California OAUG March 7, 2005.
Profiling Metadata Specifications David Massart, EUN Budapest, Hungary – Nov. 2, 2009.
POAD Distributed System Case Study: A Medical Informatics System Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe December 6, 2010.
Integrating Security Design Into The Software Development Process For E-Commerce Systems By: M.T. Chan, L.F. Kwok (City University of Hong Kong)
ASG - Towards the Adaptive Semantic Services Enterprise Harald Meyer WWW Service Composition with Semantic Web Services
Public Health Data Standards Consortium
Chapter 6 – Data Handling and EPR. Electronic Health Record Systems: Government Initiatives and Public/Private Partnerships EHR is systematic collection.
Networking and Health Information Exchange Unit 6b EHR Functional Model Standards.
Progress SOA Reference Model Explained Mike Ormerod Applied Architect 9/8/2008.
Cross-enterprise Document Workflow (XDW) IT Infrastructure Technical Committee Editors: Luca Zalunardo, Arianna Cocchiglia, Arsenal.IT.
Public Health Tiger Team we will start the meeting 3 min after the hour DRAFT Project Charter April 15, 2014.
1 Designing Effective Programs: –Introduction to Program Design Steps –Organizational Strategic Planning –Approaches and Models –Evaluation, scheduling,
Lecture 7: Requirements Engineering
This material was developed by Oregon Health & Science University, funded by the Department of Health and Human Services, Office of the National Coordinator.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe January 18, 2011.
Systems Analysis and Design in a Changing World, Fourth Edition
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
State Key Laboratory of Resources and Environmental Information System China Integration of Grid Service and Web Processing Service Gao Ang State Key Laboratory.
Semantic Web: The Future Starts Today “Industrial Ontologies” Group InBCT Project, Agora Center, University of Jyväskylä, 29 April 2003.
Introduction to Semantic Web Service Architecture ► The vision of the Semantic Web ► Ontologies as the basic building block ► Semantic Web Service Architecture.
Enterprise Architecture HOW COMPANIES ARE EXPLOITING INFORMATION TO THROUGH IT.
AESuniversity NPI Reporting.  Session Overview  Terms and Definitions  Where It Fits Within MIS  Setup Process  User Process  Questions & Answers.
Kemal Baykal Rasim Ismayilov
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Providing web services to mobile users: The architecture design of an m-service portal Minder Chen - Dongsong Zhang - Lina Zhou Presented by: Juan M. Cubillos.
Discussion - HITSC / HITPC Joint Meeting Transport & Security Standards Workgroup October 22, 2014.
12-CRS-0106 REVISED 8 FEB 2013 APO (Align, Plan and Organise)
CS223: Software Engineering Lecture 14: Architectural Patterns.
Copyright 2007, Information Builders. Slide 1 iWay Web Services and WebFOCUS Consumption Michael Florkowski Information Builders.
Office of the National Coordinator for Health Information Technology ONC Update for HITSP Board U.S. Department of Health and Human Services John W. Loonsk,
March 2008 – DRAFT 1 Electronic Health Record (EHR) Task Force Financial Analysis Isabelle de Zegher and Greg Stadler.
By Jeremy Burdette & Daniel Gottlieb. It is an architecture It is not a technology May not fit all businesses “Service” doesn’t mean Web Service It is.
1 © 2007 Chapter 3 Strategic Planning for the EHR Migration Path.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
Process 4 Hours.
Sabri Kızanlık Ural Emekçi
Advance Software Engineering
UNIT II.
Electronic Health Information Systems
EHR System Function and Information Model (EHR-S FIM based on EHR-S FM R2.0) CPS.9.4 Standard Report Generation aka S in EHR-S FM R1.1
ARCH-1: Application Architecture made Simple
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) AS.4.1 Manage Registry Communication aka S.1.1 in EHR-S FM R1.1
Electronic health records Deploying knowledge at the Point of Care
ITAS Cash Management Integration to an ERP
Self-Managed Systems: an Architectural Challenge
ONC Update for HITSP Board
Health Information Exchange for Eligible Clinicians 2019
Presentation transcript:

“Service Framework” workgroup

Problem Statement Seamless integration between clinical research requires 2 pillars “Data”: Computer semantic interoperability, based on unambiguous semantic on data shared across the HC continuum “Functions”: Standards services supporting harmonization of interactions across a very heterogeneous community of stakeholders (hospitals, GPs, nursing homes, pharmacists, companies, authorities) Today most effort focus on standardization of data; we need as well to address standardization of services through a “service framework”

Problem Statement What do we mean by services ? Definition of Services Something – based on a use case - provided by one organization to another one – and that the consumer is ‘ready to pay for”; the consumer does not see the underlying operations supporting a service Services support seamless information flow across (heterogeneous & disperse) organizations; they are available through “Yellow pages” They assume computation semantic interoperability across organizations (data are not the same in local system but when exchange they can be mapped to a common semantic) There are different level of services “low” level supporting data access, security integration services “high level” supporting business services (decision support, CRFQ, data mining, ….) and building on top of “low” level, re-usable services Services must be testable and certified !

Problem Statement What do we mean by services ? Ops1 Ops2 Ops3 Ops4 Standards Semantic signifiers) Governance Audit Functional Profile (use case – see example from CRFQ)

Problem Statement What do we mean by services Problem Statement What do we mean by services ? Use case: patient monitoring condition Use case: check how many patient – in January 2000 - met a specific set of condition (diabetic, above 50 years, within a certain time frame….) in the accessible DBs Functional Profile = “count of qualified patients” Issues: no possibility to identify double count, need to have total population Operations: Check authorization Patient selection Patient count Service = a set of operations exposed via an interface answering needs for a specific functional profile CRFQ – match patient criteria to EHR Need additional services – security, consent, anonymization, etc. ….

Problem Statement – what do we want to achieve “Service framework”=> taxonomy of standard services Services will support business specific use cases at the interface between clinical care and clinical research (like patient safety monitoring, trial set up, trial execution, …see complete list) Services will be organized in a taxonomy of integrable, re-usable components in a stepped approach Starting with some piloting of which ones would fit with each other Understanding maturity of organization (organization need be ready for using/working with services => evolution to more complex service will be related to maturity of organization to be able to use services and data => Services specification must have narrative description performance indicators, linkage to organization information model and know downstream consumers (in context of overall interaction)

Problem Statement – what do we want to achieve

Benefit – why do we believe this would bring value Manage complexity of business problems we want to solve by decomposing it into sub-components (i.e. patient safety monitoring decomposed in many different services) Cost savings Flexibility/agility/adaptability of the solution Re-usability of functionalities “low” level services across different “high” level services services across organizations Complexity of interactions more scaleable & manageable stepped approach – required adaptation for each organization at the beginning) Set up clear “contract’ with each organization (e.g. access, …) => no need to redo each time

Key Milestones 2008 / 2009 Piloting CRFQ – and other services

BACKUP

Going from some examples ALERT IT How to specify queries across the different DBs Possibility to use CRFQ – to have a more “architecture” oriented approach

OGSA-DAI project On-going Project from IBM and Manchester University , included in DebugIT Complete environment – GRID storage and GRID queries Many type of data stored + layer to manage firewall and de-identification to expose various set of standardized services User queries can be propagated and you get data back (field data mapping, quality…) Semantic mapping is relatively weak but nice in propagating queries Tools to be configured to be adapted to each EHR => underlying building block needed for service like CRFQ

List Qualified Patients Interface OGS-DAI and CRFQ Serv3 P1 Pt data P2 P4 P3 OGS-DAI List Qualified Patients Interface P1 Pt data P2 P4 P3 C R F Q Qualified patients CRFQ client (trial sponsor, CRO, Pharma) P1 Pt data P2 P4 P3 OGS-DAI Protocol I/E criteria/ Safety criteria Serv2 OGS-DAI

Definition of Services from Wikipedia A “Service” has a description or specification. This description consists of: 1. An explicit and detailed narrative definition supported by a low (but not detailed [not implementation specific]) level process model. The narrative definition is in some cases augmented by machine-readable semantic information about the service which facilitates service mediation and consistency checking of an Enterprise Architecture. 2. A set of performance indicators that address measures/performance parameters such as availability (when should members of the organization be able to perform the function), duration (how long should it take to perform the function), rate (how often will the function be performed over a period of time), etc. 3. A linkage to the organization’s information model showing what information the “Service” owns (creates, reads, updates, and deletes) and which information it references and is owned by other “Services”. 4. A listing of known downstream consumers (other “Services” that depend upon its function or information) and the documentation of their requirements.