e-SENS eHealth Use Cases

eHealth Use Cases (Overview)

eConfirmation• How is a health care provider in MS B able to get an insurance confirmation

for a patient who is insured with a Health Insurance Organization in a member state of the EU/EES.

ePrescription/eDispensation• Adaption of epSOS use-case (inclusion of trust and security building blocks)

Patient Summary• Adaption of epSOS use-case (inclusion of trust and security building blocks)

e-SENS2

Relevant Trust and Security BBs

The main focus is on the creation of building blocks that are usable in different domains (not only eHealthcare)

eID• Identification/authentication using national eIDs (including mobile eID)

eSignature• Creating signed documents or seals using national eIDs (including mobile

eID) or other signature means (server side signatures)

3

Integration of BBs in eHealth UCs

Main objectives• Strengthen the role of the patient• Simplify workflows

Patient Access Portal• [DONE] Authentication of the patient using his/her eID

HCP Access Country B• Identification/Authentication of the patient using his/her eID to replace the

input of identifiers by the HCP • eID identifiers (attributes) are used to fill the XCPD-Request• in discussion: the patient‘s SAML identity assertion might be embedded into the

TRC Assertion• eSignature using the patient‘s eID

• in discussion: using the eID to sign the TRC assertion (eSeal)• In discussion: using the eID to sign a CDA based consent document (eSignature) in

country B that can be registered and evaluated in country A (e.g. render a signed CDA consent document into an XACML policy)

e-SENS4

Challenges

Technical / Infrastructural Challenges• Attributes included within the STORK identity asserton must be usable

within epSOS UCs• Mapping from STORK identifiers onto epSOS identifiers (epSOS infrastructure

Country A – additional attribute source)• Embedding of epSOS usable identifiers within a STORK assertion (additional

attribute source)• Different eID-Types must be usable at HCP B‘s site

• Problems with different card drivers and middleware components (an highly integrated component must be provided – cooperation with FutureID?!)

Legal Challanges• Usage of eIDs and associated attributes in different domains (might be an

issue in some memberstates)

e-SENS5