CH EPR mHealth (R4)
0.1.3 - CI build
CH EPR mHealth (R4)
0.1.3 - CI build
CH EPR mHealth (R4), published by eHealth Suisse. This is not an authorized publication; it is the continuous build for version 0.1.3). This version is based on the current content of https://github.com/ehealthsuisse/ch-epr-mhealth/ and changes regularly. See the Directory of published versions
There are no additional requirements for the Swiss EPR extension for the 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”.
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: 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.
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.
When the Document Consumer needs to discover DocumentReference Resources matching various metadata parameters, it issues a Find Document References message.
Find Document Reference request:
GET [base]/DocumentReference?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 Reference request.
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 Find Document References [ITI-67] request must authorize using the Incorporate Authorization Token [ITI-72] transaction of the IUA profile.