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
This page describes the implementation options of the Study Retrieval task.
The overall business scenarios associated to this task is described in the Business view page
The implementation-indipendent sequence diagrams associated to this task is described in the in the Application view page
The Myhealth@EU general architecture requires that no assumptions are made on the way the service is implemented at the national level.
This implies that any solution adopted for the NCPeH to NCPeH communications has to work properly indipendently by the fact that a HL7 FHIR server, a DICOM sever, an XDS registry/repository or any other solution locally adopted.
There are multiple alternatives, not mutually exclusive, for searching, retrieving, or fetching Imaging Study Information.
For example, one option is to treat the Imaging Study Information as a document and apply the same search/fetch approach described for the Document Retrieval. See the Document Retrieval page for details.
In this case there are different ways to document the Study Information, using:
The advantage of this approach consist in the usage of a common retrieval mechanism that doesn't depend on the type of document retrieved or by its format. This approach is suitable for simple search mechanisms and requires that a DocumentReference instance is generated for each created document.
Some alternatives - described only for documentation purposes in this version of this guide - are listed below:
In this first version the Imaging Study Retrieval will be realized by searching per DocumentReference
Alternative solutions or additional capabilities can be added in the future based on the inputs collected during the first pre-operative stages.
For the implementaion details please refre to the Document Retrieval page