- 1: epSOS Home.
- 2: About epSOS.
- 3: Project Structure & Results.
- 3.1: Work Package 1.1.
- 3.2: Work Package 1.2.
- 3.3: Work Package 1.3.
- 3.4: Work Package 2.1.
- 3.5: Work Package 3.1.
- 3.6: Work Package 3.2 .
- 3.7: Work Package 3.3.
- 3.8: Work Package 3.4.
- 3.9: Work Package 3.5.
- 3.10: Work Package 3.6.
- 3.11: Work Package 3.7.
- 3.12: Work Package 3.8.
- 3.13: Work Packages 3.9 and 3.10.
- 3.14: Work Package 4.1.
- 3.15: Work Package 4.2.
- 3.16: Work Package 4.3.
- 3.17: Work Package 4.4.
- 3.18: Work Package 5.1.
- 3.19: Work Package 5.2.
- 3.19.1: D5.2.1 - Initial Scope.
- 3.20: Work Package 5.3 .
- 4: Use Cases.
- 5: epSOS Countries.
- 6: Large Scale Pilot.
- 7: Participants.
- 8: FAQ.
- 9: News & Events.
- 10: Press section.
- 11: Links & Collaborations.
- 12: Download Area.
- 13: Glossary.
| Title: | Initial Scope |
|---|---|
| Author: | Andreas Grode |
| Work Package: | 5.2 |
| Working Task: | 5.2.1 |
| D5.2.1: | Initial Scope |
Initial Scope
Summary
Detailing what epSOS embodies and thereby establishing a common basic vocabulary, a common set of assumptions, and a uniform understanding of the project goals, is an essential step towards reaching these goals. Deliverable 5.2.1 addresses itself to this task.
Fundamentally, epSOS’ initial scope is to investigate, build, and evaluate a service infrastructure demonstrating the interoperability and cross-boarder access to patient summaries and ePrescription services.
In a practical sense, this aim should manifest itself in several measurable outputs, such as:
- An assessment of the volume of information to be accessed by the proposed infrastructure.
- A precise analysis of legal, technical and operational constraints affecting the proposed personal health information exchange infrastructure.
- The establishment of an agreed framework for integral elements of a common service infrastructure, such as identification / authentication.
- A common vocabulary, i.e. semantic and syntactic interoperability, as well as harmonized definitions of patient summaries and electronic prescriptions.
- Piloted technical solutions as well as methodological proposals to replicate these solutions.
Achieving these outputs has to occur in consideration of a defined set of prerequisites and requirements, guaranteeing compliance with existing relevant national and European processes, patient privacy and safety, as well as their requirements and requests, while simultaneously maintaining a strict policy of non-interference and subsidiarity with regard to local health care systems of member states.
Since the selection of pilot sites will become necessary during the project, a set of basic assumptions allowing for the definition of precise selection criteria for these pilot sites is provided.
In compliance with the project’s initial goals as defined in Annex I, epSOS focuses on a set of Use Cases, which, at this point, are defined as UML sequence diagrams. Basically, epSOS will tackle two health care scenarios with two sub-variations each:
- The request of a patient summary
- By a regular visitor
- By a one-time / occasional visitor
- Filing a prescription
- Prescribed by the country of origin
- Newly prescribed by the country visited.