CH EPR mHealth (R4)
3.0.0 - DSTU3
CH EPR mHealth (R4)
3.0.0 - DSTU3
This page is part of the CH EPR mHealth (R4) (v3.0.0: DSTU3) based on FHIR (HL7® FHIR® Standard) 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
This section describes the 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 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
Find Document List example request:
GET [base]/List?patient.identifier=urn:oid:2.999|11111111 HTTP/1.1
Accept: application/fhir+json
traceparent: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-00
The response Bundle SHALL follow the CH MHD SubmissionSet Comprehensive Bundle Profile (example: MHD Find DocumentSubmissionSet (List)).
The Document Responder does not need to support the FindFolders Query from the XDS on FHIR Option.
The CapabilityStatement resource for the Document Consumer is MHD Document Consumer.
The CapabilityStatement resource for the Document Responder is MHD Document Responder.
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 [ITI-72] transaction of the IUA profile.
The traceparent header is required, as described in Trace Context header.
The Document Consumer shall be able to record a Find Document Lists Consumer Audit Event Log. Audit Example for a Find Document Lists Transaction from Consumer perspective.
The Document Responder shall be able to record a Find Document Lists Responder Audit Event Log. Audit Example for a Find Document Lists Transaction from Responder perspective.