MyHealth@Eu NCPeH API
9.1.1-ci - ci-build
150
MyHealth@Eu NCPeH API - Local Development build (v9.1.1-ci) 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.
| Further investigations are needed, taking in consideration the results of some on-going standardizaton activities and the feedback colelcted by the early adopters.</a> |
The overall business scenarios associated to this task is described in the Business view page
The implementation-independent 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.
In this first version the Imaging Study Retrieval will be realized by searching per DocumentReference. For the implementation details please refer to the Document Retrieval page
The Imaging Study Information is treated in fact as a document, applying the same search/fetch approach described for the Document Retrieval. 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.
There are different ways to document the Study Information, using:
Details about how to have equivalent representation with these two opitons is documented in the IHE MADO profile.
There are multiple other alternatives, not mutually exclusive, for searching, retrieving, or fetching Imaging Study Information, described only for documentation purposes in this version of this guide:
The following tags are of interest to be retrieved from the DICOM KOS metadata file, when used:
| Tag | Name | Description |
|---|---|---|
| (0020,000D) | Study Instance UID | Unique identifier for the Study |
| (0020,000E) | Series Instance UID | Unique identifier of the Series |
| (0008,1155) | Instance UID | Uniquely identifies the SOP Instance |
Alternative solutions or additional capabilities can be added in the future based on the inputs collected during the first pre-operation stages.