Task Analysis and Interoperable Application Services for Service Event Management

Similar documents
"We have an expensive plethora of uncoordinated, unlinked, economically segregated, operationally limited micro

Hannu Virkanen, Juha Mykkänen, Jiechen Jiang University of Kuopio, HIS R&D Unit. Dr. Juha Mykkänen, FinnWell China seminar Tekes, 16 December 2008

Call for Presentations

GLOBAL HEALTH INFORMATICS STANDARDS FOR NATIONAL HEALTH INFORMATION

EMR Adoption Model. Handbook

HEALTH INFORMATICS STANDARD: AN EXAMPLE OF APPLICATION. Corso di Informatica Medica

Slide 1. Slide 2. Slide 3. Objectives. Who Needs Interoperability? Component 9 Networking and Health Information Exchange

FHIR, Interoperability, and the World of Enablement

Integration of the NIMIS Project with the HSE-National Client Index Service

Solution Sheet. Communications for Member Engagement

HITSP Construct HL7 Standard

SOA in the pan-canadian EHR

HL7 and Service-oriented Architecture (SOA) Ambassador Briefing

Integrating Standards to Achieve Semantic Interoperability. Dr Ken Lunn Director of Data Standards

Healthcare Service-Oriented Architecture Workshop: Regional Health Information Organization (RHIO) Simulation

A Merge White Paper. Closed Loop Referral Management: A Cost-Effective Strategy for Meaningful Interoperability

Enterprise Process Integration

Organization Meeting & Overview

Constructing Rural Health Information Systems for Critical Access Hospitals:

Visions of new responsibilities and opportunities for terminologists and terminology centres

VIRTUAL USER GROUP MEETING PLATFORM OVERVIEW

Improving HL7 Integration for Healthcare Providers

There Has to Be More:

Our focus: Your bottom line.

Functional and Control Integration of an ICU, LIS and PACS Information System *1

Clinical Messaging in Mendocino and Lake County

From Interaction to Integration to Transformation: Healthcare s Journey & Information s Role

Digital Health and the Challenge of Interoperability

IBM BPM on zenterprise

Working with Health IT Systems is available under a Creative Commons Attribution-NonCommercial- ShareAlike 3.0 Unported license.

Empowering ACO Success with Integrated Analytics

The Impact of Interoperability / HIE to a Health System s Strategic Roadmap: Lessons from the OpenHIE Project

IT6801 / Service Layers/ A.Kowshika SERVICE LAYERS

CLINICAL PORTAL Hospital Services. Presented by Stephen Parsons

Context. Accessibility. Relevance.

Services Directory (ServD) Response to OMG RFP Healthcare Community Services Provider Directory

IHE-FRANCE Today and future IHE Austrian Day

WEDI 2015 Health Information Exchange Value and ROI Survey

openehr & clinical modelling

EHR Data Analytics Descriptive: Predictive: Prescriptive: Data mining: Personalized medicine: Electronic Health Record (EHR):

Healthcare in the 21st Century: Why Interoperability is Important

Think Locally, Connect Nationally

Service-Oriented Architecture A View From the Field. Paul C. Brown, Ph.D. Principal Software Architect

Benefits of Cloud Computing In EHR implementation

2014 Kent State University Catalog - Fall 2014 Course Descriptions Page 940

Towards a Model-Driven and Role- Configurable Methodology Suite for Enterprise and Service- Oriented Interoperability

Integrated EHR and Practice Management solutions for your GI practice and ASC. Gastroenterology Solutions

National Program of Cancer Registries Advancing E-cancer Reporting and Registry Operations (NPCR-AERRO)

CDA vs Archetypes: Use Cases March Tomaž Gornik, Co-founder and CEO

Synapse RIS SOLUTIONS

EMC Information Infrastructure Solutions for Healthcare Providers. Delivering information to the point of care

Service-Oriented Architecture: Enabling Data Sharing Between Immunization Information Systems and Clinical Care

What good would having all your images on a single platform do? Agfa HealthCare. Enterprise Imaging

Biobanking in the Public Health Context. Liisa-Maria Voipio-Pulkki Girector General, CMO

Relations between ICT Architectures and Organizational Complexity and Risk

SERVICE ORIENTED ARCHITECTURE SOA INTRODUCTION

SOA Enabled Workflow Modernization

RSNA Image Share Validation Testing

Process Automation An (Executive) Overview. Enzo Greco WW Strategist IBM, Armonk, NY

Workflow Manager Whitepaper: WORKFLOW GAPS IN ENTERPRISE IMAGING By: Val Kapitula RT(R), PMP, CIIP

Information Paper. MAKING USE OF SNOMED CT: KEY QUESTIONS and STATUS as of SEPTEMBER 2013

Reimagine: Healthcare

Extending UML Activity Diagrams for Workflow Modelling with Clinical Documents in Regional Health Information Systems

4.13 Case Study #19: Portuguese National Broker


Telemedicine, data management, patient benefit - ehealth architectures controlled by patients for treatment and biomedical research

IBM Global Technology Services. Weaving the solution Dharanibalan Gurunathan 1 st August, Mumbai

What s New in HL7. W. Ed Hammond, PhD Director, Duke Center for Health Informatics FACMI, FAIMBE, FHL7, FIMIA Secretary, HL7; Chair-Emeritus, HL7

Introduction DICOM and imaging Replacing film with PACS What is wrong with the scenario? Going beyond DICOM IHE impact: workflow problems

Theoretical Considerations Regarding the Implementation of SOA Architecture in a Company for Electric Power Distribution and Supply

Immunization Information System Interoperability

Driving Down Network Cost Through Enhanced Interoperability

SOA Maturity Assessment using OSIMM

Architecture-Driven Modernization (ADM) Task Force: Overview, Scenarios & Roadmap. OMG Architecture-Driven Modernization Task Force

Pre- Decisional Working- Document; Not for Official Use EHR-S FM Release-3 Summer Prototype Plan 7/13. R2 Ballot Reconciled

Transformational Data-Driven Solutions for Healthcare

Technology and Integrated Care in Ireland

Venn Health Partners. Venn Health Partners, 906 Oak Tree Ave, Suite R, South Plainfield New Jersey, 07080,

IBM Enterprise Service Bus for Healthcare

Successful healthcare analytics begin with the right data blueprint

Eastern Massachusetts Healthcare Initiative

Business Continuity Standard

The New World of Unified Image Management

Enhancing Clinical Decision-Making with Corolar Clinical Data Repository (CDR)

Sharing current and archived patient data in the EMC Federation Enterprise Hybrid Cloud

1. INTRODUCTION BACKGROUND ENTERPRISE SOA BENEFITS AND TECHNOLOGIES AN ENTERPRISE SOA FRAMEWORK...6

Actian DataConnect 11

The Evolution of the Referral Process

MedicAlert. Using Service Oriented Architecture David Harrington, VP/CTO. 27 October 2005

<Insert Picture Here> Enterprise (-wide) SOA?! Thoughts beyond technology and XML

Health Information Standards in BC. W.L. Clifford, OBC, MD, FCFP September 25 th, 2017

POWERFUL INTUITIVE RESPONSIVE

The Value of Business Process Management (BPM)

Agenda. Objectives of territory-wide sharing of electronic health records (ehr) Overview of CIMS - 2. Overview of CIMS - 1

SHARED HEALTH RECORD(SHR)

Organizational Track Definitions, Assumptions and Issues

Nuacare HMS. PMS. LIMS. CMS. RIS

It s time for an enterprise-wide approach to medical imaging

AN I NTE RS YS TE M S DE C I S I O N GUIDE. Addressing the Healthcare Connectivity Challenge: Selecting a Health Service Bus

HL7 C-CDA Consolidated Clinical Document Architecture

Transcription:

Task Analysis and Interoperable Application Services for Service Event Management Juha MYKKÄNEN a, Hannu VIRKANEN a, Pirkko KORTEKANGAS b, Saara SAVOLAINEN a, Timo ITÄLÄ c a University of Eastern Finland, School of Computing, Healthcare Information Systems Research and Development, Kuopio, Finland b Medbit Oy, Turku, Finland b c Aalto University School of Science and Technology, SoberIT, Espoo, Finland juha.mykkanen@uef.fi MIE 2011 Oslo 1

Outline Background The national health IT infrastructure development in Finland The SOLEA project Materials and methods Results: the analysis model Discussion and conclusions 2

Speaker background Juha Mykkänen, PhD, research director University of Eastern Finland, Health Information Systems R&D Board member in Finnish Social and Health Informatics Association, IMIA representative of Finland, HL7 Finland chair (co-chair common services SIG), HL7 SOA Ambassador Projects developing and applying SOA and integration approaches, national-level and citizen-centred ehealth and wellbeing projects SOLEA: Agile Enterprise Architecture using SOA and BPM 2008-2011 Mind and Body programme, SalWe SHOK, 2010-1013 OmaHyvinvointi (MyWellbeing): personal wellness management 2008-2010 SerAPI: SOA and integration of healthcare applications 2004-2007 PlugIT: healthcare application integration 2001-2004 ekat / guidelines for national ebooking of health services 2008 Healthcare services specification project (HSSP) / HL7 and OMG, 2005- Integrating the Healthcare Enterprise - IHE.fi 2008- National project for social services IT - Tikesos 2006-2011 China/Finland ehealth partnership + other projects in Shanghai 2004-2008 Various HL7 Finland and web services standards specifications Juha Mykkänen, MIE 2011 31.83.201

Background: national health IT initiatives in Finland National-level centralized services for eprescription and earchive National-level information sharing through earchive service and local / regional systems which connect to it Structured patient information, agreed-upon document specifications, messaging and security solutions eprescription spreading nationally (currently more than 100 k eprescriptions made) earchive and sharing of patient documents in testing phase Many different specifications from various projects guiding the implementation work of national information sharing Difficulties in providing uniform and comprehensive composition rules for patient information from various systems and sources and from disparate local workflows Irmeli Luukkonen, MIE 2011 30.84.201

Context: SOLEA project national R&D project focusing on the use of service-oriented enterprise architecture to support the management and interoperability of complex information systems in healthcare and other industries one of many working packages: refinements required to support service events in relation to the national EPR specifications was selected as one of the main working items of the project in late 2009 Juha Mykkänen, MIE 2011 31.85.201

Service event concept Encounters are used for organizing and structuring healthcare acts which pertain to patient's health history and guidelines related to multistep clinical processes Collecting and sharing service encounter data is the foundation of an electronic health record Challenge: multiple sources, different syntaxes and semantics In Finnish national solutions, service events are used to group documentation entries of one visit or episode: "organizing or performing one healthcare service a central concept in patient consent management, reporting and billing, as well as in achieving clarity and integrity of EPR use for professionals

Goals, materials and methods Challenge: requirements and specifications stating the concepts and functionality related to the management of EPR information in clinical and administrative activities were inconsistent and dispersed Goals: clarification of definitions and interpretations of service events coherent specification of lifecycle of service events and communication of this lifecycle in various information systems related to the care process refinements to the interoperability specifications between various applications or services related rules and information and concept models reusable services to support the management of care process documentation and consent management basis for open interface specifications Materials: existing national specifications, eight expert workshops Methods of this paper: task analysis and identification of SOA application services based on this analysis (constructive conceptual development)

Tasks of service event management 1 Service event management tasks Provid er Patient EHR Archi ve Make a referral P P P Receive and process a referral P P a Insert a patient in the queue P P a Schedule an encounter based on a referral P a P a Schedule an encounter without a referral P a P a Cancel a scheduled encounter P a P a Unanticipated registration and admission P P a Define information needs P a a a Define justification of information transfer across organizations P a P a Pr = provider Pa = patient EHR = local EHR application EAr = national EPR archive service P = always participating, a = potential participant for improved automation or efficiency 8

Tasks of service event management 2 Service event management tasks Provid er Patient EHR Archi ve Document query P P P Document retrieval P P P Assess and use information in care P a Make a new information entry P P P Make an information delivery consent or denial a P a P Transfer patient to another ward / unit P P a Discharge patient / conclude a visit P P P Make a study or consultation request P P a Receive and fulfill a study or consultation request P P a Pr = provider Pa = patient EHR = local EHR application EAr = national EPR archive service P = always participating, a = potential participant for improved automation or efficiency 9

After identification of tasks... Based on the above business-level tasks, 22 lower level information processing functions were identified Each function was analyzed for specifying the logical architecture and implementation guidance identification of application roles and services which handle all necessary tasks and functions for each function: location in systems and application services specification of inputs, outputs, participants (as SOA / system roles), exceptions, automation potential, interoperability needs 10

Application roles and services SOA service / application role Centralized EPR archive Document composition service Document transmission service Entry composition service Event information repository Document retrieval service Other outputs: user storyboards and example scenarios, conceptual and ontological analysis models specifications of shared information models architectural diagrams for migration phases 11 SOA service / application role Information query service Content producer Content consumer Controller of the patient administrative process Integration infrastructure for service events Context manager

Location of application roles and services SOA service / application role Centralized EPR archive L R C D Document composition service * I I Document transmission service * I * Entry composition service * I * Event information repository * * I Document retrieval service I * I I I Implementation scope: N = national service R = regional or local shared service C = included in local core EHR or patient administration applications D = included in departmental / specialized systems I = will be implemented on this level at least in one of the involved organizations or projects * = is potentially implemented on this level depending on local requirements Other outputs: user storyboards and example scenarios, conceptual and ontological analysis models specifications of shared information models architectural diagrams for migration phases 12 SOA service / application role L R C D Information query service I * I * Content producer I I Content consumer * I * Controller of the patient administrative process Integration infrastructure for service events * I Context manager I * I

Use and evaluation of results results have been quickly taken up by various other national projects HL7 interface specification project for service event integration specification project for the architecture of lab and imaging integration harmonization project of national specifications resulting specifications of the service event work of SOLEA were evaluated using a survey for the participants of the work and users of the results in the related projects 8 respondents in evaluation questions results summaries such as location of application roles and services and detailed task specifications were seen very useful for system integrations and implementations task analysis and documentation method validation continues: requirements and services for identity and access management + consent and care relationship management for social services

Clear and flexible orchestration of care processes and documentation! Tusen takk / Kiitos additional information juha.mykkanen@uef.fi 14