MyHealth@Eu NCPeH API
0.0.1 - ci-build
150
MyHealth@Eu NCPeH API - Local Development build (v0.0.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
The application domain describes what are the logical (software) components involved in the MyHealth@EU business services and how they interact, collaborate or are coordinated.
The business processes associated with these services can be generalized through a set of common (meta) business processes, as described in the MyHealth@EU common business processes.
In this version of the guide, sequence diagrams are used to illustrate how these common business processes are realized independently of their technical implementation.
The sequence diagrams documented in this guide identify a set of common participants:
In these diagrams, the following aspects are not explicitly highlighted:
For each identified business process the following table describes the current implementation status and where to find the associated sequence diagram.
Business Processes | Impl. Status | Sequence Diagram View | |
---|---|---|---|
🆔 | Patient Identification | Pre-production | Patient Identification |
📥 | Document Retrieval | Pre-production | Document Retrieval |
📤 | Document Provision | Under definition | Document Provision |
📊 | Study Retrieval | Under definition | Study Retrieval |
🖼️ | Image Retrieval | Under definition | Image Retrieval |
The Patient Identification is a task used by almost all the use cases.
It is realized by searching patients by identifier and/or identification traits.
Figure 1 - Find Identity by Traits
Note: Implementation details are provided in the Patient Search page . |
The Document Retrieval may be realized by:
Figure 2 - Document Retrieval
Note: Implementation details are provided in the Document Retrieval page . |
The Document Provision is realized by sending a document to the receiving country (typically the country of Affiliation)
Figure 3 - Document Provision
Note: Implementation details are provided in the Document Provision page . |
The Imaging Study Retrieval may be realized by searching and retrieving - or fetching - the study manifest.
Figure 4 - Imaging Study Retrieval
Note: Implementation details are provided in the Study Retrieval page . |
Indipendently on the way imaging study, series or instance identifiers have been collected - for example from the Imaging Study Manifest, diagnostic reports or other documents - those identifiers, or a selection of them, are used to fetch the evidences having those instance identifiers or belonging to the selected study or series.
Figure 5 - Image Retrieval
Note: Implementation details are provided in the Images Retrieval page . |