CH EPR mHealth (R4)
3.0.0-ballot - ballot
This page is part of the CH EPR mHealth (R4) (v3.0.0-ballot: Draft Ballot 1) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
There are no additional requirements for the Swiss EPR of the Find Document Lists [ITI-66] transaction defined in the MHD Profile published in the IHE ITI Trial Implementation “Mobile Access to Health Documents”. The SubmissionSet.Author.AuthorRole mapping to DocumentManifest has to be supported. The Document Responder does not need to support the FindFolders Query from the XDS on FHIR Option.
The Find Document Lists [ITI-66] transaction is used to find List Resources that satisfy a set of parameters. It is equivalent to the FindSubmissionSets query in the Registry Stored Query ITI-18 transaction, as documented in ITI TF-2: 3.18.4.1.2.3.7.2. The result of the query is a Bundle containing List Resources that match the query parameters.
Actor: Document Consumer
Role: Requests List Resources, matching the supplied set of criteria, from the Document Responder
Actor: Document Responder
Role: Returns List Resources that match the search criteria provided by the Document Consumer
Mobile access to Health Documents (MHD), Rev. 4.0.2 – Trial-Implementation, November 8, 2021
This MHD Profile is based on Release 4 of the HL7® FHIR® standard.
When the Document Consumer needs to discover List Resources matching various metadata parameters it issues a Find Document Lists message.
Find Document List request:
GET [base]/List?patient.identifier=urn:oid:2.999|11111111 HTTP/1.1
Accept: application/fhir+json
See Bundle example (and the corresponding profile) as response to the Find Document Manifest request.
TLS SHALL be used. This national extension enforces authentication and authorization of access to the Document Responder using the IUA profile with extended access token. Consequently the Find Document Lists [ITI-66] request must authorize using the Incorporate Access Token [ITI- 72] transaction of the IUA profile.