This page is part of the CH EPR FHIR (R4) (v4.0.0-ballot: DSTU 4 Ballot 1) 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

Find Document References [ITI-67]

This section describes the additional requirements for the Swiss EPR of the Find Document References [ITI-67] transaction defined in the MHD Profile published in the IHE ITI Trial Implementation “Mobile Access to Health Documents”.

Scope

The Find Document References transaction is used to find DocumentReference Resources that satisfy a set of parameters. It is equivalent to the FindDocuments and FindDocumentsByReferenceId queries from the Registry Stored Query [ITI-18] transaction. The result of the query is a FHIR Bundle containing DocumentReference Resources that match the query parameters.

Actor Roles

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

Referenced Standards

1. Mobile access to Health Documents (MHD), Rev. 4.2.1 – Trial-Implementation, August 2, 2023
2. This MHD Profile is based on Release 4 of the HL7® FHIR® standard.

Messages

Find Document References Request Message

The Document Consumer SHALL include the search parameter patient.identifier with the oid of the EPR-SPID.

Find Document Reference example request:

GET [base]/DocumentReference?patient.identifier=urn:oid:2.16.756.5.30.1.127.3.10.3|761337610411353650&status=current HTTP/1.1
Accept: application/fhir+json
traceparent: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-00

Find Document References Response Message

The response Bundle SHALL follow the CH MHD Find Document References Comprehensive Response message Profile (example: MHD Find DocumentReferences).

CapabilityStatement Resource

The CapabilityStatement resource for the Document Consumer is MHD Document Consumer.

The CapabilityStatement resource for the Document Responder is MHD Document Responder.

Security Consideration

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 References [ITI-67] request must authorize using the [ITI-72] transaction of the IUA profile.

For the traceparent header handling refer to Trace Context header.

Security Audit Considerations

Document Consumer Audit

The Document Consumer shall record a Find Document References Consumer Audit Event Log. Audit Example for a Find Document References transaction from consumer perspective.

Document Responder Audit

The Document Responder shall record a Find Document References Responder Audit Event Log. Audit Example for a Find Document Lists Transaction from responder perspective.