Transcript here - epSOS

25/04/2020
25/04/2020
From strategies to services
– eHealth as the enabler for cross-border
health care
25/04/2020
25/04/2020
Objectives of the ISA eHealth EIF Study
eHealth EIF Phase I
Jan
eHealth EIF Phase II
May
Workshop (16th of April)
Sept
Workshop
1
Define the eHealth European Interoperability Framework (EIF)
2
Make a recommendation of a first set of ten use cases and their
associated profiles (by IHE and Continua)
3
Provide recommendations on profiles (or their development
process)
Full EIF Webinar
25/04/2020
Policy Context for epSOS and EU eHealth
Interoperability
Recommendation on crossborder interoperability of
electronic health record
systems
Communication on
Quality Criteria for
Health related Websites
2002
2004
Communication on e-Health making healthcare better for
European citizens: An action
plan for a European e-Health
Area
Communication on
interoperability for
European public
services
Directive on the
application of patients’
rights in cross-border
healthcare
Council Conclusions on
Safe and efficient
healthcare through
eHealth
2008
2009
Communication on
telemedicine for the
benefit of patients,
healthcare systems
and society
Article 29
Working
Party
2010
2011
Communication on
a Digital Agenda for
Europe
eHealth
Standardisation
Mandate 403
eHealth
Action
Plan
(eHAP)
2012-2020
2012
Communication on
European Innovation
Partnership on Active
and Healthy Ageing
Communication on a
strategic vision for
European standards
eHealth Governance Initiative (eHGI) and
eHealth Network play an important role
25/04/2020
D
e
c
i
s
i
o
n
M
a
k
i
n
g
P
r
o
d
u
c
t
i
o
n
epSOS project
(Patient summary /
ePrescription)
eHealth Network of MS
Art. 14 Directive on Patients Rights (2011)
Joint Action + Thematic Network
eHealth Governance Initiative
Semantic Network
Project
eHealth EIF project
STORK project
(eIdentification within
eHealth domain)
CALLIOPE Network
Interoperability
Roadmap
25/04/2020
eHealth EIF positioning on HITCH roadmap
Operationalize: 2013-2014
Get Ready: 2012-2013
Can be used as
input for
Deploy: 2015-20XX
25/04/2020
Introducing the terminology
e.g. D3.4.2 epSOS Common
Components
Specification.pdf
e.g. epSOS
eHealth Interoperability
project
An eHealth interoperability
project, taking place in a EU
cross border, national,
regional, or local context.
delivers
Interoperability
specification
addresses
Project-specific deliverable,
dealing with a set of “profiles”
to address a “business use
case”
consists
of
e.g. Patient
consists of
Combines and refines the use
of a set of “base standards” to
address a specific “technical
use case“
combines and refines
e.g. HL7 V3
Base standards
Artefacts that are foundational
to delivering open
interoperability, often
endorsed by standards
development organisations
Business Use Case
Description of sequences of
business events that, taken
together, lead to a system
doing something useful
e.g. IHE-XCPD
Profile
e.g. ePrescription /
eDispensation
identification
addresses
Technical Use Case
Description of sequences of
technical events that, taken
together, lead to a system
doing something useful
25/04/2020
Illustrating vision with epSOS project
International base standards and
profile development
eHealth European Interoperability Framework: EU Recognised profiles
<To be
Profile 2
determined>
Business Use Case
“ePrescription / eDispensaton”
LOINC
SNOMED/CT
HL7 v2
HL7v3
CDA L1 L3
Pdf/A
IHE-BPPC
IHE-XCPD
IHE-XCA
HTPP1.1
IHE-CT
UTF8
IHE-XDR
OASIS ebRIM 3.0
IHE-ATNA
epSOS EU Cross-Border eHealth Interoperability Project
Identification Service
IHEProfile 1
XCPD
IHE-XSPA
W3C MTOM
IHE-XUA
HL7 V3 PA DSTU
IHE-XCF
HL7 V3 Datatypes
W3C SOAP 1.2
WSI BP 1.1
Dispensation Service
RFC1305 (NTP)
TSP
ETSI TS 102 231
CEN activities
SAML
IEEE 11073
X509
…
XACLM
TSL/NSL
Extensions
IHE(XUA)/
Profile 1
XSPA
IHEProfile 2
XCF
IHEProfile 2
XCA
OASIS ebRIM 3.0
OASIS ebRS 3.0
OASIS ebRIM 3.0
OASIS ebRS 3.0
...
WSI SBP 1.1
RFC 3881
epSOS Business Service
Extensions
OASIS ebRS 3.0
W3C XOP
<To be
Profile 2
determined>
Business Use Case
“Patient Summary”
IHEProfile 4
XDR
OASIS ebMS 3.0
OASIS ebRS 3.0
OASIS ebRIM 3.0
Consent Service
IHEProfile 4
BPPC
HL7 CDA R2
Security and Infrastructure services
IHEProfile 4
ATNA
TLS 1.2
Syslog
RFC 3881
WSI SBP 1.1
IHE(XUA)/
Profile 1
XSPA
IHEProfile 4
CT
NTP V3
SNTP V4
SAML (v2)
XACML (v2)
25/04/2020
1
Approach for first study objective
Define the eHealth European Interoperability Framework (EIF)
Top Down
(Generic) EIF
eHealth EIF
Bottom Up
5 MS eHealth
frameworks/specifications
epSOS Specification
25/04/2020
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
A formal specification should be licensed on (F)RAND terms or even on a royalty-free basis in a way that allows
property rights
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.
25/04/2020
Basic Cross Sector Services Proposal
Transport
Infrastructure
Citizen ID
Company ID
Company
Dossier
Citizen ID
Transport
Infrastructure
Citizen ID
Company ID
Company
Dossier
Citizen ID
Privacy
Privacy
25/04/2020
epSOS Current status and facts concerning pilot operations
•
•
•
•
•
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
25/04/2020
Pilots approved by the PSB
Country B
Austria
Czech
France
Italy
Spain
Austria
x
x
x
x
Country A epSOS Patient Summmary
Czech
France
Italy
Spain
Denmark
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
epSOS e-prescription
Country B
Denmark
Greece
Country A
Denmark Italy
x
x
x
25/04/2020
Pilot sites – some examples
epSOS Point of Care
Database
25/04/2020
Sustainability epSOS Countries
25/04/2020
epSOS Next Steps
• 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
25/04/2020
Dialog med kommunen/andra vård-grannar
Gemensam uppslutning kring mål
Oh so you are
also implementing
eHealth?
DK, CZ, FR, ES, GR, AT, IT
SE, DE, SL
base from Mikael Erlandsson
25/04/2020
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
25.04.2020
project short name & title of presentation (change with menu "bottom
line")
Thank you for your attention!
[email protected]
20