CH EPR mHealth (R4)
0.1.1 - Draft Standard for Trial Use

This page is part of the CH EPR mHealth (R4) (v0.1.1: DSTU 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

Find Document Manifest [ITI-66]

There are no additional requirements for the Swiss EPR of the Find Document Manifests [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 Find Document Manifests [ITI-66] transaction is used to find DocumentManifest 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-2a: The result of the query is a Bundle containing DocumentManifest Resources that match the query parameters.

Actor Roles

Actor: Document Consumer
Role: Requests a list of DocumentManifest Resources, matching the supplied set of criteria, from the Document Responder.
Actor: Document Responder
Role: Returns DocumentManifest Resources that match the search criteria provided by the Document Consumer.

Referenced Standards

Mobile access to Health Documents (MHD) With XDS on FHIR Rev. 3.1 – 2019-03-06

This MHD Profile is based on Release 4 of the emerging HL7® FHIR® standard.


Trigger Events

When the Document Consumer needs to discover DocumentManifest Resources matching various metadata parameters it issues a Find Document Manifests message.

Message Example

GET [base]/DocumentManifest?patient.identifier=urn:oid:2.999|11111111 HTTP/1.1
Accept: application/fhir+json

See DocumentManifest example as response (and the corresponding profile) to the Find Document Manifest request.

Security Consideration

TLS SHALL be used. This national extension enforces authentication and authorization of access to the Patient Identity Manager using IUA profile with basic access token. Consequently the Finde Document Manifest [ITI-66] request must authorize using the Incorporate Authorization Token [ITI- 72] transaction of the IUA profile.