Patient Summary sharing on a cross-border scale (epSOS)
Related Use Case
Patient summary sharing on a cross-border scale
Scenario context
More information about this Use Case, including the full description of the requirements and different versions of it, can be found in the epSOS deliverable “D3.2.2 Final definition of functional service requirements – Patient Summary”.
Actors/Roles
- Identity Checker
- Authorisation Checker
- HCP EHR System
- HCPO (Health Care Provider Organization)
- National Contact Point
- Semantic Services
- Transaction Logger
Transactions
- Patient identification (by Identity Checker)
- HCP identification (Identity Checker)
- Patient consent checking (Authorisation Checker)
- Understandable (structured and translated) Patient Summary
- All transactions should be logged
Technical process flow
- Patient visits a HCP in Country B (not country of origin)
- HCP has to be authenticated and authorised for this patient by his local system
- Patient has to be authenticated
- Patient consent has to be validated
- PS (Patient Summary) requested at NCP country A
- PS translated by semantic services
- PS sent to NCP country B
- Patient summary has to be retrieved
Associated profiles, standards, and HL7 FHIR Implementation guides
- Policy: —
- Care process: XDS-SD, XCF (planned) (Ref: D3.A.1. EED 2)
- Infrastructure: XDR, ATNA, CT
- Infrastructure, cross-community: XCPD, XCA
- Security: XUA (++), BPPC
Possible issues
- By the end of epSOS (June 2014) no legal framework exists for exchanging PS.
- The coding system is not complete which may cause missing information