INTEROPERABILITY & STANDARDS IN EHEALTH KATRIEN VAN GUCHT PUBLIC

Transcription

1 INTEROPERABILITY & STANDARDS IN EHEALTH KATRIEN VAN GUCHT PUBLIC

2 2 EHEALTH IN BELGIUM

3 DATA SHARING IN BELGIE WHAT IS ALREADY THERE Hospital Data Document repository from hospital to clinician hub & metahub system Transmural Data Health information exchange in primary, hospital and social care health vaults Linked and interoperable Standards Informed consent Therapeutic relation

4 A CRITICAL EVALUATION THERE ARE STILL ISSUES TO TACKLE Operational on technical level Supported by politics & sector 1x connection to ehealthplatform Transmural care Care pathways Lack of business model for adopton in end-user software Inadequate workflow IT landscape Belgium

5 HEALTH TECHNOLOGY ADOPTION HURDLES CHALLENGES FOR MASSIVE USE INTEROPERABILITY USER EXPERIENCE PATIENT SAFETY EVIDENCE- BASED PRACTICE BUSINESS MODEL (REIMBURSEMENT) PATIENT PRIVACY & SECURITY 25/10/2016 5

6 WHAT ABOUT THE CITIZEN? MARKET POTENTIAL Online questionnaire* on HEALTH APPS AND WEARABLES * Online questionnaire, completely filled in by Flemish people >18 years old. Mostly early adopters. Not representative for the entire Flemish population.

7 7 INTEROPERABILITY & STANDARDS

8 INTEROPERABILITY Wet- en regelgeving Compatibele wetgeving Standaarden en Profielen, Certificering Security, Privacy, Governance Beleid Zorgprocessen Informatie Applicaties Infrastructuur Samenwerkingsovereenkomsten Afstemming van zorgprocessen Datasets, coderingen Uitwisselingsformaat, zorgapplicaties Communicatie, netwerk, servers Processes Organisations IT-systems!! Interoperability is not a system, it is quality!! Smooth health information exchange Semantics structure communication profiles - infrastructure Technical: XML, SAML, SOAP

9 STANDARDS IT-standaards Webservices, XML, Encryption, certificates, Medical standards Meaning -> Semantic interoperability Clinical terminology, coding E.g. Snowmed, ICPC2, ICF, KATZ Message structure Syntax E.g. HL7, KMEHR, DICOM Communication process Dialogue interoperability profile Based on use cases E.g. IHE

10 WHY IHE IN BELGIUM Options for procurement Avoid development and maintanance of one shot implementations Proven functionality International scope Cost saving connectathon Measurement and documentation of maturity profiles Access international players in Belgium Scaling of Belgian players abroad

11 OPPORTUNITIES FOR IHE BELGIUM ACTUAL Hub/MetaHub: 3 technically different solutions FUTURE IHE/XDS profile for all with limited specific elements + 1 for Vitalink International vendors only need to adapt to specific Belgian elements BE vendors need to develop only 1 solution + have easier access to international market

12 PITFALLS & CHALLENGES OF IHE Does not CREATE standards Suggests interoperability profiles based upon use cases Selects existing standards (e.g. HL7, Snomed ) Belgian standard KMEHR Time lapse of 18 months: use case until new profile Need for conformity testing (by IHE?) Organisation of connectathons to test functionality (global vs. local) Certification?

13 POLICY PLANS ACTIEPLAN EGEZONDHEID/PLAN D ACTION ESANTE AP/PA 13: Standards and Policy on Terminology Project Lead: ehealth Platform (standards) FOD (Terminology) 10 uses cases for use of SNOMED-CT Evolution and migration of Kmehr to HL7v3 and CDA Technical interoperability: publication of laboratory results in HL7 in Kmehr envelope in hub/metahub & ehealthbox. 13

14 @ IMEC (FORMER IMINDS) INTEROPERABILITY AND TEST SERVICES MISSION GOAL Create knowledge on interoperability and economy of scale Use case driven interoperability testing on and between applications Validation of integration and interoperability within the ehealth infrastructure Plug-in events and chain testing for stakeholders 14

15 AN ILLUSTRATION 15

16 PUBLIC