Formal Design of Electronic Public Health Records - ICMCC

icmcc.org

Formal Design of Electronic Public Health Records - ICMCC

The International Council on Medical & Care

Compunetics Event 2006

The Hague, The Netherlands June 7th-9th 2006

Formal Design of Electronic

Public Health Records

eHCC

Diego M. Lopez

Bernd Blobel

eHealth Competence Center

University of Regensburg Medical Center

Franz-Josef-Strauss-Allee 11, D-93053 Regensburg, Germany


Contents

• Introduction (EHR, EPHR, Objective )

Formal Design of EPHR-S

– Requirements

– A component-based approach

• A EPHR-S scenario

• Conclusions

June 7th 2006

eHCC

eHealth Competence Center

Regensburg


Introduction: Scope EHR

• EHR: “a repository of information regarding the

health status of a subject of care, in computer

processable form.” [ISO/TR 20514]

• subject of care: “one or more persons

scheduled to receive, receiving, or having

received a health service”

Core EHR

Extended EHR

Health Care

Billing

Health Care

Patient

P. Administrat.

Population

Health man.

Accounting

Public Health actors make use of EHR information, but..

June 7th 2006

Clinician

eHCC

Scheduling

Hospital Administration

eHealth Competence Center

Regensburg

....

Demographics

Public Health Auth


Introduction: EHR vs EPHR

Consider the WHO definition of Public Health:

“A social and political concept aimed at the improving

health, prolonging life and improving the quality of life

among whole populations through health promotion,

disease prevention and other forms of health

intervention.”

EPHR: “a repository of information regarding the

health status of whole populations, in computer

processable form.”

Subject of Care vs Population

June 7th 2006

eHCC

eHealth Competence Center

Regensburg


Introduction: EPHR Characteristics

• Contains de-identified data

• Limited to some processes (public Health

activities): Health Promotion, Disease

Prevention, vaccination, etc.

• Can be formed as a aggregation of EHR +

• Some other sources of data.

A&D EPHR-S

June 7th 2006

eHCC

eHealth Competence Center

Regensburg


June 7th 2006

Objective and Method

Discuss the analysis and design of EPHR

according to the advanced state of

knowledge in methodologies, models,

techniques and tools.

A formal component-based architectural

methodology, based on internationally

agreed terminologies, healthcare

standards and software engineering de

facto standards.

eHCC

eHealth Competence Center

Regensburg


Formal design of EHR Systems

1. Designing EHR-S is not simple

• Participation of several stakeholders.

• knowledge about the healthcare “business”

• Interaction with other domains.

• Openness, scalability, flexibility, semantic

interoperability, portability, etc.

2. A Component-Based architecture is demanded.

Architecture: Specification of the system

components and its relationships.

June 7th 2006

eHCC

eHealth Competence Center

Regensburg


TheProposedArchitectural

Approach (I)

•The Generic Component Model

Domains

June 7th 2006

eHCC

eHealth Competence Center

Regensburg


TheproposedArchitectural

Approach (II)

Enterprise Viewpoint

Information and

Computation Viewpoint

Engineering

and Technology Viewpoint

Scope

Definition

System Use

Cases

Use Cases

Realization

Design

Classes

Static Domain

Model

Business

Use Cases

Dynamic

Domain

Model

Model of static

views

Model of

dynamic

views

Analysis

Classes

Analysis

Components

Design

Components

Implementation

Model

Test Model

Glossary

Deployment

Model

Computation-Independent Modelling Platform-Independent Modelling Platform-Specific Modelling

RUP

Workflows

BUSINESSMODELLING

REQUIREMENTS

ANALYSYS

DESIGN

IMPLEMENTATION

TEST

DEPLOYEMENT

June 7th 2006

eHCC

eHealth Competence Center

Regensburg


A scenario in Public Health

• System: Surveillance System for

measles diseases.

• Artefacts:

1. Scope Definition

2. Business Use Case

3. Dynamic Domain Model

4. Static Domain Model

5. Glossary

June 7th 2006

eHCC

eHealth Competence Center

Regensburg


1. Scope definition

Business Process: Reporting of Measles Cases

HCP

Health Ministry

Primary

Care

HCP

PHC

(Micronetwork)

Local Level

PHO

(Provincial)

Prov. Level

Nat. Level

HCP

2. Business Use Case

June 7th 2006

eHCC

eHealth Competence Center

Regensburg


3. The Dynamic Domain Model

June 7th 2006

eHCC

eHealth Competence Center

Regensburg


4. The Static Domain Model

Domain Model (D- MIM) :Public Health Reporting Domain Information Model

(PORR_DM100001)

InvestigatedEntity

InvestigatedPerson

classCode*:


5. Glossary

June 7th 2006

eHCC

eHealth Competence Center

Regensburg


Summary and Conclusions

Designing EPHR systems is complex.

• Ruled by Component-Based Architectures

• The proposed approach:

– Uses the GCM

– Abstraction by RM-ODP viewpoints.

– Unified Process.

– HL7 DM

• A component-based architecture for EPHR-S is

a step forward the integration with EHR –S.

June 7th 2006

eHCC

eHealth Competence Center

Regensburg


Acknowledgments

The authors are in debt to their colleagues

from HL7, ISO TC 215, CEN TC 251, and

OMG/CORBA for kind co-operation. We also

want to thank Vicerectoria de Investigaciones for

its partial support to this work under project

1661: “Formulación de un Programa de

Doctorado en Ingeniería, Área Telemática”

June 7th 2006

eHCC

eHealth Competence Center

Regensburg


Acknowledgments

The authors are in debt to their colleagues from HL7, ISO

TC 215, CEN TC 251, and OMG/CORBA for kind cooperation.

We also want to thank Vicerectoria de

Investigaciones for its partial support to this work under

project 1661: “Formulación de un Programa de Doctorado

en Ingeniería, Área Telemática”.

Questions?

Diego M. Lopez

Email Diego.Lopez-Gutierrez@stud.uni-regensburg.de

URL http://www.ehealth-cc.de

June 7th 2006

eHCC

eHealth Competence Center

Regensburg

More magazines by this user
Similar magazines