A Metabolic Syndrome Health Check EHR based on openehr



Similar documents
A MODEL OF OPENEHR-BASED ELECTRONIC MEDICAL RECORD IN INDONESIA

A MODEL OF OPENEHR BASED ELECTRONIC MEDICAL RECORD IN INDONESIA

Archetype-Based Knowledge Management for Semantic Interoperability of Electronic Health Records

HL7 CDA, Clinical Modelling and openehr

Electronic Health Records: An introduction to openehr and archetypes

Integration Information Model

Electronic Health Record (EHR) for use and

Trends in Healthcare Information Standardization

Using Archetypes with HL7 Messages and Clinical Documents. Heath Frankel HL7 Working Group Meeting 14 January 2011

Introduction to openehr Archetypes & Templates. Dr Ian McNicoll Dr Heather Leslie

EHR Archetypes in practice: getting feedback from clinicians and the role of EuroRec

Towards a Repository for Managing Archetypes for Electronic Health Records

Advanced Aspects of Hospital Information Systems

Clinical Knowledge Manager. Product Description 2012 MAKING HEALTH COMPUTE

Open Source Modular Units for Electronic Patient Records. Hari Kusnanto Faculty of Medicine, Gadjah Mada University

The next generation EHR

EHR Definition, Scope & Context. Sam Heard for Peter Schloeffel ISO/TC 215 WG1 Aarhus, Denmark 3 Oct 2003

Techniques for ensuring interoperability in an Electronic health Record

EHR Standards Landscape

What s next for openehr. Sam Heard Thomas Beale

Health Informatics Standardisation - educational, informative and normative

Standardised and Flexible Health Data Management with an Archetype Driven EHR System (EHRflex)

Service Oriented Architecture and Design Strategies

Data modelling methods in clinical trials: Experiences from the CTMND project (ctmnd.org)

Il lavoro di armonizzazione. e HL7

Speaker Second Plenary Session ELECTRONIC HEALTH RECORDS FOR INFORMED HEALTH CARE IN ASIA- PACIFIC: LEARNING FROM EACH OTHER.

Object-relational EH databases

Ontology-based Archetype Interoperability and Management

Clinical Decision Support Strategies

CHAPTER 6. Discussion and Conclusion. patient health information, such as diagnosis, medicine orders, managing patient

Building the National EHR Strategy

International HL7 Interoperability Conference - IHIC 2010

openehr The Reference Model Thomas Beale Sam Heard

gehr Project: Nation-wide EHR Implementation in JAPAN

IBM Software. IBM Initiate: Delivering Accurate Patient and Provider Identification for Canadian Electronic Health Records

Reusing openehr Archetypes for the Expression of Cerebral Palsy Electronic Medical Records

Patient-Centric Secure-and-Privacy-Preserving Service-Oriented Architecture for Health Information Integration and Exchange

Health Information Exchange. Scalable and Affordable

EHR Systems: an Introduction

Improving EHR Semantic Interoperability Future Vision and Challenges

Standardization of the Australian Medical Data Exchange Model. Michael Legg PhD

An Introduction to Laboratory Management Solution (LMS)

EHR Standards and Semantic Interoperability

ehealth, HIS, etc ehealth All information about health HMIS mhealth HIS Statistical IS Credited: Karl Brown, Rockefeller Foundation

Applying Standards in Cross-sector Communication for an Integrated Health Environment

EHR Data Reuse through openehr Archetypes

DIPS Arena New Archetype-based EHR. Sigurd From, DIPS ASA

The use of ehealth standards in Norway

Health & Medical Billing System (RSystems)

The Six A s. for Population Health Management. Suzanne Cogan, VP North American Sales, Orion Health


Electronic Health Record (EHR) Standards Survey

Electronic Health Record. Standards, Coding Systems, Frameworks, and Infrastructures

European Quality Labelling, Certification, Electronic Health Record systems (EHRs) gf v1

HL7 EHR System Functional Model: A Major Development Towards Consensus on Electronic Health Record System Functionality

ehealth Interoperability State of the Art in Serbia

E-HEALTH PLATFORMS AND ARCHITECTURES

Version: January 2008 ASTM E-31: EHR and Informatics Standards Education For Health Professional Disciplines. Background

CLOUD-BASED DEVELOPMENT OF SMART AND CONNECTED DATA IN HEALTHCARE APPLICATION

Creating a national electronic health record: The Canada Health Infoway experience

Author: Una Ismaili Main supervisor: MD, PhD, Rong Chen, Department of LIME, Karolinska and

ISO :2008 Здравна информатика -- ЕЗД комуникация -- Част 1: Референтен модел

Health Information Technology Professional (HIT Pro ) Examinations

An overview of Health Informatics Standards

2009 Progress in Comprehensive Care for Rare Blood Disorders Conference

Standards and Interoperability: The DNA of the EHR

Health Informatics Standardization: Relevance and Indian Initiatives

How To Understand The Difference Between Terminology And Ontology

What do clinical data standards mean for clinicians? Dr Nick Booth GP and Informatician, Warden, Northumberland, UK

HIT Workflow & Redesign Specialist: Curriculum Overview

HL7 AROUND THE WORLD

HL7 and SOA Based Distributed Electronic Patient Record Architecture Using Open EMR

E-Health in The Netherlands

Transcription:

Seagaia Meeting 2009, Okinawa A Metabolic Syndrome Health Check EHR based on openehr 2009/05/15 早 稲 田 大 学 国 際 情 報 通 信 研 究 科 Waseda University, GITS Kano Lab Hsu WanYen (Nora) 徐 婉 晏 1

Research Background EHR* is a promising technology to improve quality, efficiency, and reduce the cost of care. However, adoption rate of EHR* is low due to the lack of accepted standard for EHR. Current problems in healthcare industry are: 1. Lack of standard; 2. Lack of interoperability: difficult to share information and to exchange patient data between hospitals ; 3. Lack of flexibility: because of the lack of clear layer separation between clinical domain expertise and technical domain expertise. It is difficult to change or add new features. 2 *(EHR) Electrical Health Record

Research Objective Study the existing open source initiative EHR architecture, called openehr 1 which claims to offer open access to: 1. documents 2. software source (including schemas, interfaces) 3. executable software 4. and knowledge products, such as terminologies Use openehr architecture to build an EHR for metabolic syndrome check 2 to examine: 1. Interoperability 2. Flexibility 3. Future standard possibility Review the relationship between openehr and other standards including ISO 3, CEN 4 and HL7 5 3 1. openehr : www.openehr.org 2. (Metabolic Syndrome check ) 特 定 健 康 診 査 3. (ISO) International Organization for Standardization 4. (CEN) Committee European Normalization 5. (HL7) Health Level Seven

Metabolic Syndrome EHR Prototype In April 2008, MHLW 1 of Japan started the metabolic syndrome check 2 for age betweens 40 to 74 years old in Japan. To achieve the research objective, a prototype was created for Metabolic Syndrome test result, for example, height, weight, abdominal circumference, lipid test, liver function test and Body Mass Index (BMI). Currently, Metabolic Syndrome EHR Prototype is implemented on a PC within a secure intranet-based network environment, thus allowing metabolic syndrome test result to be shared locally. 4 1. (MHLW) Ministry of Health, Labour and Welfare 2. (Metabolic Syndrome check ) 特 定 健 康 診 査

Metabolic Syndrome EHR Prototype Medical history Laboratory test 5

Use Ocean EhrView to view test result(1) Login with Username Password 6 Source: Ocean Informatics

Use Ocean EhrView to view test result(2) Show test result by input date 7 Source: Ocean Informatics

8 Evaluation(1) Using the metabolic syndrome EHR prototype, the following features were confirmed regarding the openehr architecture: 1. Separation of clinical domain and technical domain: I, a software engineer, could develop, in two months, the metabolic syndrome EHR prototype using archetypes, developed by medical experts and a tool (template designer) provided in the openehr software repository. 2. Flexibility to change In creating the above prototype, I could easily add, and sometimes, delete archetypes in the EHR template. Archetypes would be able to expand to accommodate new findings of the medical discipline. Medical experts can change or create new archetypes using the software tool, Archetype Editor. 3. Interoperability 4. Openness I could not confirm the interoperability by myself, but I am following closely the developments of interoperability discussions currently taking place among experts of openehr, HL7 and CEN to confirm this. I found that some openehr software tools and repository are completely open, while some others require a license. Having obtained an academic license, Kano Lab students including myself are able to access openehr software tools and repository from our lab in GITS.

Evaluation(2) User Evaluation: Results of survey questionnaire from 62 people mostly my friends and acquaintance in Japan with average age of 28. 1. They replied that the EHR prototype is easy to use, and, therefore, they are willing to use it. 2. Respondents are either using the prototype EHR on their own PC, or were shown demonstration on my computer. They expressed the hope that they would like to use it, but they expressed preference to use it over the internet. 3. User s feedback shows they are ready to use EHR and the only concern is security. The openehr software does not provide security measures. The responsibility lies in each software implementer. 9

10 Evaluation(3) Interview with an expert; a practicing nurse, a healthcare consultant and a doctor course student at a medical university. 1. She was impressed with the flexibility in the openehr architecture provided by the separation of medical domain specialists from software engineers. 2. She was also impressed by the openness and potential interoperability of openehr architecture. 3. She said that there were already several proprietary implementations of metabolic syndrome test results. They were not interoperable and this would create a big problem in the future.

Conclusion openehr provides an open environment to users: 1. Everyone can have accessibility to openehr specification. 2. openehr reference model can be used as a structure to build any EHR application. 3. Flexibility to accommodate changes are confirmed. 4. It offers a non-medical background user an opportunity to provide an EHR for various diseases in the world. Future improvements are required for an openehr approach in the following: 1. Web-based design with full security measures. 2. To implement Japanese language version. 11

THE END THANK YOU VERY MUCH 12

REFERENCE: openehr <http://www.openehr.org/home.html> Ocean Informatics,Australia <http://oceaninformatics.biz> Japan Medical Association <http://ww.med.or.jp> 特 定 健 診 特 定 保 健 指 導 <http://www.med.or.jp/chiiki/kenshin/index.html> Health Level Seven (HL7)< http://www.hl7.org> Comité Européen de Normalisation (CEN) <http://www.cenorm.be> Metabolic syndrome check : Japan Ministry of Health, Labour and Welfare <http://www.mhlw.go.jp/bunya/shakaihosho/iryouseido01/info02a.html> T. Beale, S. Heard, 2007, openehr : Architecture Overview <http://www.openehr.org/releases/1.0.1/architecture/overview.pdf> Ocean Informatics clinical tools : Archetypes Editor software <https://wiki.oceaninformatics.com/confluence/display/ttl/archetype+editor+releases> Ocean Informatics clinical tools : Template Designer software <https://wiki.oceaninformatics.com/confluence/display/ttl/template+designer> 13