04/10/2015. From strategies to services – eHealth as the enabler for cross-border health care.
-
Upload
anthony-day -
Category
Documents
-
view
215 -
download
2
Transcript of 04/10/2015. From strategies to services – eHealth as the enabler for cross-border health care.
19/04/23 Objectives of the ISA eHealth EIF Study
Make a recommendation of a first set of ten use cases and their associated profiles (by IHE and Continua)Make a recommendation of a first set of ten use cases and their associated profiles (by IHE and Continua)22
Define the eHealth European Interoperability Framework (EIF)Define the eHealth European Interoperability Framework (EIF)11
Provide recommendations on profiles (or their development process)Provide recommendations on profiles (or their development process)33
Jan May Sept
eHealth EIF Phase IeHealth EIF Phase I
Workshop (16th of April) Workshop
eHealth EIF Phase IIeHealth EIF Phase II
Full EIF Webinar
19/04/23 Policy Context for epSOS and EU eHealth Interoperability
2002 2004 2008 2009 2010 2011 2012 2002 2004 2008 2009 2010 2011 2012
Recommendation on cross-border interoperability of electronic health record systems
Communication on a strategic vision for European standards
Communication on Quality Criteria for Health related Websites
Communication on e-Health - making healthcare better for European citizens: An action plan for a European e-Health Area
eHealth Standardisation Mandate 403
Communication on telemedicine for the benefit of patients, healthcare systems and society
Council Conclusions on Safe and efficient healthcare through eHealth
Directive on the application of patients’ rights in cross-border healthcare
Communication on interoperability for European public services
Communication on a Digital Agenda for Europe Communication on
European Innovation Partnership on Active and Healthy Ageing
eHealth Action Plan (eHAP) 2012-2020
Article 29 Working Party
19/04/23 eHealth Governance Initiative (eHGI) and eHealth Network play an important role
eHealth Network of MSArt. 14 Directive on Patients Rights (2011)
eHealth Network of MSArt. 14 Directive on Patients Rights (2011)
Joint Action + Thematic NetworkeHealth Governance Initiative
Joint Action + Thematic NetworkeHealth Governance Initiative
epSOS project(Patient summary /
ePrescription)
epSOS project(Patient summary /
ePrescription)
Semantic Network Project
Semantic Network Project
STORK project(eIdentification within
eHealth domain)
STORK project(eIdentification within
eHealth domain)
eHealth EIF projecteHealth EIF project
CALLIOPE NetworkInteroperability
Roadmap
CALLIOPE NetworkInteroperability
Roadmap
19/04/23 eHealth EIF positioning on HITCH roadmap
Get Ready: 2012-2013 Operationalize: 2013-2014 Deploy: 2015-20XX
Can be used as input for
19/04/23 Introducing the terminology
eHealth Interoperability project
eHealth Interoperability project
An eHealth interoperability project, taking place in a EU cross border, national, regional, or local context.
Interoperability specificationInteroperability specification
Project-specific deliverable, dealing with a set of “profiles” to address a “business use case”
ProfileProfile
Combines and refines the use of a set of “base standards” to address a specific “technical use case“
Base standardsBase standards
Artefacts that are foundational to delivering open interoperability, often endorsed by standards development organisations
Business Use CaseBusiness Use Case
Description of sequences of business events that, taken together, lead to a system doing something useful
Technical Use CaseTechnical Use Case
Description of sequences of technical events that, taken together, lead to a system doing something useful
addresses
addresses
consists ofconsists of
combines and refines
delivers
e.g. epSOS
e.g. ePrescription / eDispensation
e.g. Patient identification
e.g. D3.4.2 epSOS Common Components
Specification.pdf
e.g. IHE-XCPD
e.g. HL7 V3
19/04/23 Illustrating vision with epSOS project
epSOS EU Cross-Border eHealth Interoperability ProjectepSOS EU Cross-Border eHealth Interoperability Project
International base standards and profile development
LOINCLOINC
SNOMED/CTSNOMED/CT
HL7 v2HL7 v2
HL7v3HL7v3
CDA L1 L3CDA L1 L3
eHealth European Interoperability Framework: EU Recognised profileseHealth European Interoperability Framework: EU Recognised profiles
Business Use Case “Patient Summary”
Business Use Case “Patient Summary”
Business Use Case “ePrescription / eDispensaton”
Business Use Case “ePrescription / eDispensaton”
Pdf/APdf/A
HTPP1.1HTPP1.1
UTF8UTF8
OASIS ebRIM 3.0OASIS ebRIM 3.0
OASIS ebRS 3.0OASIS ebRS 3.0
W3C MTOMW3C MTOM
W3C XOPW3C XOP
W3C SOAP 1.2W3C SOAP 1.2
WSI BP 1.1WSI BP 1.1
WSI SBP 1.1WSI SBP 1.1
RFC1305 (NTP)RFC1305 (NTP)
ETSI TS 102 231 ETSI TS 102 231
X509X509
RFC 3881RFC 3881
IHE-BPPCIHE-BPPC
IHE-XCPD IHE-XCPD
IHE-XCA IHE-XCA
IHE-XDR IHE-XDR
IHE-CT IHE-CT
IHE-ATNA IHE-ATNA
Identification Service epSOS Business Service
Dispensation Service Security and Infrastructure servicesConsent Service
Profile 1Profile 1 Profile 2Profile 2
Profile 4Profile 4
IHE-XCPD
IHE-XCPD
IHE-XCA
IHE-XCA
IHE-XDR
IHE-XDR
ExtensionsExtensions
Profile 4Profile 4IHE-
BPPC
IHE-BPPC
Profile 4Profile 4IHE-
ATNA
IHE-ATNA Profile 4Profile 4
IHE-CT
IHE-CT
ExtensionsExtensions
OASIS ebRIM 3.0OASIS ebRIM 3.0
OASIS ebRS 3.0OASIS ebRS 3.0
HL7 V3 PA DSTUHL7 V3 PA DSTU
IHE-XSPAIHE-XSPA
XACLMXACLM
HL7 V3 Datatypes HL7 V3 Datatypes
OASIS ebMS 3.0OASIS ebMS 3.0
OASIS ebRS 3.0OASIS ebRS 3.0
OASIS ebRIM 3.0OASIS ebRIM 3.0
HL7 CDA R2HL7 CDA R2NTP V3NTP V3
SNTP V4SNTP V4TLS 1.2TLS 1.2
SyslogSyslog
RFC 3881RFC 3881
WSI SBP 1.1WSI SBP 1.1
Profile 2Profile 2<To be
determined><To be
determined>
Profile 2Profile 2<To be
determined><To be
determined>
IHE-XUAIHE-XUA
IHE-XCFIHE-XCF
......
Profile 1Profile 1
IHE- (XUA)/XSPA
IHE- (XUA)/XSPA Profile 2Profile 2
IHE-XCF
IHE-XCF
OASIS ebRIM 3.0OASIS ebRIM 3.0
OASIS ebRS 3.0OASIS ebRS 3.0
Profile 1Profile 1
IHE- (XUA)/XSPA
IHE- (XUA)/XSPA
SAMLSAML
SAML (v2)SAML (v2)
XACML (v2)XACML (v2)TSL/NSLTSL/NSL
TSPTSP
CEN activitiesCEN activities
IEEE 11073IEEE 11073
……
19/04/23 Approach for first study objective
Define the eHealth European Interoperability Framework (EIF)Define the eHealth European Interoperability Framework (EIF)11
Top Down
Bottom Up
eHealth EIFeHealth EIF
(Generic) EIF(Generic) EIF
5 MS eHealth frameworks/specifications
5 MS eHealth frameworks/specifications epSOS SpecificationepSOS Specification
19/04/23 CAMSS Category Overview
Category Description
Applicability A formal specification should be usable and easy implementable in different products to be relevant for adoption by
public administrations.
This category addresses the definition of functional scope and area of application, the possible reusability in other
areas, the possible alternative specifications, the compatibility and dependency on other specifications or
technologies.
Maturity A formal specification should in itself be mature enough for adoption by public administrations.
This category addresses the development status, the quality, guidelines and stability of the formal specification.
Openness A formal specification should be sufficiently open and available to be relevant for adoption by public administrations.
This category addresses the openness of the standardisation organisation and decision-making process, and the
openness of the documentation and accessibility of the formal specification.
Intellectual
property rights
A formal specification should be licensed on (F)RAND terms or even on a royalty-free basis in a way that allows
implementation in different products.
This category addresses the availability of the documentation on the IPR and the licences for the implementation of
the formal specification.
Market support A formal specification should have sufficient market acceptance and support in order to be adopted by public
administrations.
This category addresses the proven and operational implementations of the formal specification, the market share
and demand for the products, and the support from users and communities.
Potential A formal specification should have sufficient and positive future consequences, evolution and impact for being
adopted by public administrations.
This category addresses the consequences and impact of using or adopting the formal specification, the advantages
and risks, the maintenance and possible future developments.
19/04/23
Basic Cross Sector Services Proposal
eDelivery
eSafe
Company Dossier
Citizen IDCi
tizen
ID
Com
pany
ID
eSignature
Privacy
TransportInfrastructure
Company Dossier
Citizen ID
Citi
zen
ID
Co
mp
any
ID
Privacy
TransportInfrastructure
eDoc
ContainerseID le
gal
entities
Visible Digita
l
SignaturesSyndication,
eDirecto
ries
19/04/23
• As of March 12, 2012, CZ, FR is in operational mode• ES, AT, IT live on April 13th.• DK, GR live before end May.• SE, SK are done testing Legal and Organisational steps remain• Another 5 Countries are testing epSOS Profiles in Bern
Connectathon end May
epSOS Current status and facts concerning pilot operations
19/04/23
Pilots approved by the PSB
Country B Austria Czech France Italy Spain DenmarkAustria x x x x xCzech x x x x xFrance x x x x xItaly x x x x xSpain x x x x x
Country A epSOS Patient Summmary
Country A Country B Denmark ItalyDenmark xGreece x x
epSOS e-prescription
19/04/23
• Migrate Current Solution as it is based on a mix of Open Source and Closed Source Components
– The closed source based on Standards will now be migrated to Open Source– An epSOS Open Source and Vendor Community is being built on www.joinup.eu
• Consolidate and scale up piloted epSOS services• Extend and refine functionalities of the two core services• Assess the use of the epSOS patient summary service in the context
of the European emergency (112) service• Patients Access to information• Comparatively assess the interoperability approaches of epSOS
services with those in other regions of the world
epSOS Next Steps
19/04/23
base from Mikael Erlandsson
Oh so you are also implementing eHealth?
DK, CZ, FR, ES, GR, AT, IT
SE, DE, SL
19/04/23 Cooperation is Key
AT, BE, CZ, CH, DK, DE, EE, ES, FI, FR, GR, HU, IT, MT, NL, NO, PL, PT, SE, SK, SL,TR, UK
19.04.23 project short name & title of presentation (change with menu "bottom line")
20
Thank you for your attention!