Benelux ehealth interoperability s ummit
This presentation is the property of its rightful owner.
Sponsored Links
1 / 40

Benelux Ehealth Interoperability - S ummit PowerPoint PPT Presentation


  • 80 Views
  • Uploaded on
  • Presentation posted in: General

Benelux Ehealth Interoperability - S ummit. Luc Nicolas Health Telematics , Informatics and Communication Unit Public Federal Service Public Health. eHealth certification in Belgium. Ehealth Roadmap Hub- metahub : system to system communication

Download Presentation

Benelux Ehealth Interoperability - S ummit

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Benelux ehealth interoperability s ummit

Benelux EhealthInteroperability - Summit

Luc NicolasHealth Telematics, Informaticsand Communication UnitPublic Federal Service Public Health


Ehealth certification in belgium

eHealthcertification in Belgium

EhealthRoadmap

Hub-metahub: system to system communication

Currentsituation in ambulatory care

Approach forinstitutions

Someroadsfortomorrow


Ehealth roadmap 2014 2018

Dorianservices e-santé

>EhealthRoadmap (2014-2018)

Dorian

<Hospitalisation> <Implant>

<Laboratoire> <Imaging>

<Sumehr> <Therapeuticscheme> <MyCarenet> <Register>

<RHM>

Gregory

  • <GP> <Specialist> <Imaging> <Prescriptions> <Chapter4> <Pharmacist> <MyCarenet> <DMG> <Laboratory> <Statushandicaped> <workincapacity>

Emily

<Homecare> <MRS> <Belrai> <Clinicalpath> <Hospitalisation> <Dentist> <Sumehr> <multidisciplinary collaboration> <Paliative care> < Home Hospitalisation>

Mona

Hillary

<Auto monitoring> <Teleconsultation> <Telemonitoring> <Sumehr> <Personalhealth record> <Electronic Prescription> <eFact> <eBirth>

<Psychiatry> <Méthadone> <CPAS> <Ambulance> <Emergency> <Laboratory> <Imaging> <Sumehr> <DMG>

<Wachtpost>


Sharing data via the hubs metahub system

Sharing data via thehubs & metahub system


Benelux ehealth interoperability s ummit

5

5

25/6/2010


27 standardized web services

27 Standardized web services


Basic services and authentic sources

Basic services and authentic sources

Health Portal

VAS

VAS

VAS

VAS

8

Patients, healthcare providers

and institutions

Care provider software

VAS

VAS

VAS

Healthcare institution software

VAS

RIZIV-INAMI site

eHealth platformPortal

MyCareNet

VAS

VAS

VAS

VAS

VAS

VAS

VAS

VAS

VAS

VAS

VAS

VAS

Users

Basic services

eHealth platform

Network

ADS

ADS

ADS

ADS

ADS

ADS

Suppliers


Testing and certification

Testing and certification

Mini « connecthatons »:

First targetedat Hubs and Metahub (Ehealth)

Openedlater to othersystems

Certification of individualHospitals by Hubs.

Certification of ambulatory care systems by Prorec/Ehealth


Hospital ehr minimum data set per discipline mapped with technical and se mantic standards

Hospital EHR: Minimum data set per discipline mapped with technical and semantic standards


Ambulatory care systems

> Ambulatory care systems

Global: Legal certificationTelematicsCommission

Ehealth PlatformSectorialLabel working-groupsUsers working-groupsProducers working-groupsFinancial incentives


Legal context

> Legal context

Chapitre 3 - Missions de la plate-forme eHealth

Article 5

La plate-forme eHealthest chargée des missions suivantes en vue de l'exécution de son objectif:

développer une vision et une stratégie pour une prestation de services et un échange d'informations électroniques dans les soins de santé efficaces, effectifs et dûment sécurisés, tout en respectant la protection de la vie privée et en concertation étroite avec les divers acteurs publics et privés des soins de santé;

déterminer des normes, des standards et des spécifications TIC fonctionnels et techniques ainsi qu'une architecture de base utiles pour la mise en oeuvre des TIC à l'appui de cette vision et de cette stratégie;

vérifier si les logiciels de gestion des dossiers électroniques de patients répondent aux normes, standards et spécifications TIC fonctionnels et techniques, et enregistrer ces logiciels;


Content

> Content

Block 1 : CriteriaBlock 2 : Kmehr

-Technical (incl. security)-Patientdata management-Keyaddedvalue services (data exchange)

-Usability

-Customer Services criteria (incl.dataportability)


Kmehr

>> Kmehr

Kind Messages for Electronic Healthcare RecordsBelgian Implementation Standard> Conceptual model> Transaction types> XML implementation> Coding systems


Sumehr

>> Sumehr

Summarized Electronic Health Record> Kmehr transaction> Multipurpose content> Homologation criteria> European target


Process

Process

  • Voluntary

  • Organizedevery 2 years

  • Scenariandtestingby PROREC (call for tender)

  • (Partially)fundedbyindustry

  • Link with financial incentive for users (800 €/year)

  • Partialconsolidation of the market ongoing


Approach for institutions action 2 roadmap referentials hospital ehr

APPROACH FOR INSTITUTIONSACTION 2 ROADMAPREFERENTIALS HOSPITAL EHR

  • 1. Fonctionnalities: May 2014

  • 2. Content (exchange + registers): Ongoing

  • 3. Structure (recommandation): October 2014


Functionalities

FUNCTIONALITIES

PART 1


Exemple

Exemple:


Content ongoing

CONTENT: Ongoing

2 inputs:

-> Partial normalisation linked to data exchange

Dischargeletter

Labo

Specialities reports

Key (observable) data

-> Registers(action 18)


Action 18 inventaire et consolidation des registres

Action 18: Inventaire et consolidation des registres

End 2014: Detailedinventory of all existingregisters and databases

“Cetinventairedétaillera au minimum la description précise des champs de donnéescollectées, leurstatut (facultatifou non), leurformat, les codifications (propriétairesou non) utilisées, le type d’utilisateur et d’institutionsconcernésainsiquetouteautre Information contextuelle indispensable.”

2014: referential per profession/context

Governancecriteria for new registers


131 registres and counting

131 registres (and counting..)


Results inventory

Results Inventory

  • N = 131

  • 62 completed web based questionnaires

  • 30 incomplete web based questionnaires (in progress)

  • 53 completed sets of parameters and list of values

  • 34 sets of parameters in progress

  • 5 registers in development

  • 5 registers refused participation

  • Info will be available in meta data portal (October 2014)


Intermediate results mapping with rhm mzg

Intermediate results mapping with RHM/MZG

> 700 matches between MZG and parameters of Registers


Part 3 structure to come

Part 3 : Structure (To come)

  • Le modèleestbasésurunefaçonorientée “problème” de documenter les

  • Il demande aux systèmes d’être baséssur le principe de “période de soins”.

  • Il impliquequetous les contacts avec tous les prestataires en rapport avec unemaladiesoientreliés ensemble.

  • Unefoisimplémentéil rend possible de regroupertoutes les interventions et d’évaluer les résultatsatteints pour un problèmespécifique – sans considération de qui a fourni le service..


Process1

Process

  • - Voluntary

  • - Bottom-up approach for referentials

  • - Governance: Federating public institutions

  • - Exchange (Hubs-metahub) de facto compulsory

  • - Use of auto-certification ? (security)

  • - Progressive Meaningful use policy (From 2014 on)


Benelux ehealth interoperability s ummit

8. Standard complex patients

ananmese set

15. Harmonisation and

administrative simplification

18 Inventoryr and consolidation of registers

9. Fundinglinked to effective meaningful use

13. Terminology

5: hub-méta-hub

6.  DPI minimal in eachsector

16. Tracabilityof medicaldevices

2. Developpementof an

Hospital EHR

11. Definecomplementary default aceesrules

3.Data on deliveredmedicines and medicationscheme


Objective

Objective

Hospital Patient summary

Snomed based CMV

rhm

ICD-10-CM

To Be

Snomed

Health DATA.be

Passer d’une vision de travail en « silo » des besoins vers une vision intégrée et inter-opérationnelle


1 serveur terminologique

1. serveur terminologique

Workflow de validation

Interfacesde consultation

  • Load/Extract

  • Requêtes

  • Mapping

  • Feed back

Sources et classifications

Utilisateurs

Interfacesde Gestion

ProcessBE cliniques

SVA

diagn.

Terminologie de référence

  • Mises à jour

  • Gestion des versions

  • Couplage, mapping

  • Gestion des règles

  • Validation

procéd.

Software

labo

SNOMED

ProcessBE administratifs

  • Webservice / webap.

INAMI.

ICD10

Registres

Documentation

...

ProcessBE administratifsou médicaux

- Dossier médical,

- Remboursement,

- Registre du cancer, ...

  • Glossaires

  • Documentation et références

  • Portail


2 terminology center

2. Terminology center


3 reference terminology snomed be

3. Reference terminology (snomed.be)


4 user interfaces

4. User Interfaces :

  • Context sensitive pick list

  • Syntactic and semantic search

  • Rule Based Code convertor


Priority use cases

Priority Use cases


Some roads for tomorrow

> Some roads for tomorrow

LegislationFrom common rulestolaw?

Standards:

Progressiveinternationalalignment of Technical standards

Certification:

More emphasis on meaningfuluse?


Thanks

Thanks

[email protected]/telematics/label


  • Login