Request for research, service or device

Starting a request

ZorgDomein Integrator facilitates requests for several different healthcare services and products such as:

Requests for diagnostic research, such as lab research, medical imaging and function research
Execution requests (NL: uitvoeringsverzoeken)
Requests for medical devices

When doing a request for research, serivce or device, the referrer logs in to ZorgDomein directly from his/her own information system using SSO. After logging in, he/she will select a healthcare product that is published by a specific healthcare supplier. This healthcare product matches the type of research, serivce or device the referrer intends to request and determines the choice for the healthcare supplier. Once the healthcare supplier has been selected, the referrer will compose and send the following documents to the healthcare supplier:

Request form: this document lists the requested services or products. Additionally this document provides relevant medical patient data for the requested serives or products. This data is automatically added to the request form as much as possible based on the medical patient data from the information system of the referrer.
Appointment message (optional): a logistic message that announces the request and contains the logistic data of the request, i.e. details of the patient, referrer, referring organization, recipient and selected healthcare request. In most cases this document is unnecessary and will therefore be omitted, because the request form already contains all relevant data.

A copy of both documents will be sent back to the information system of ther referrer for archiving purposes.

Sending a supplement

After sending the request, the referrer may sooner or later decide to send one or more supplemental documents. The referrer may optionally add one or more attachments to the supplemental letter. A copy of the supplemental document will be sent back to the information system of the referrer.

Please note that not all request types support supplements.

Cancelling a request

In some cases, the referrer may choose to cancel the request by sending a cancellation message to the selected healthcare supplier. A copy of the cancellation message will be sent back to the information system of the referrer.

Currently there are only a few healthcare suppliers support cancellation of a request for research, serivce or device. Please contact us if you want to implement this functionality in your connector.

Sequence diagram

The sequence diagram below provides a schematic overview of all interactions between the involved actors when performing a request for research, serivce or device.

Referrer

ZorgDomein

Provider

Send request

Sign on and get application context

SSO call to ZorgDomein

The SSO call to ZorgDomein consists of a HTTP GET request to the JWT login endpoint of ZorgDomein. In this request a valid SSO token (JWT) must be provided as query parameter. See SSO to ZorgDomein for more details.

Request application context details

The SSO token must contain the ID of a FHIR Task resource in the context.xis-transaction-id claim of the SSO token. ZorgDomein will request that Task resource to request additional patient context details. See SSO to ZorgDomein for more details.

Serve application context details

The FHIR server is expected to provide the requested Task, Patient and Coverage resources.

Compose and send request form

Request medical patient datarepeatable

Request medical patient data

Based on the selected healthcare product, ZorgDomein will request medical details that are relevant for the healthcare product at the sending system. This is established by a series of FHIR search requests at several FHIR endpoints. See Send documents for a list of supported FHIR resources and corresponding fields in the request form.

Serve medical patient data

The FHIR server of the sending system is expected to answer all requested FHIR resources, for as far as the requested data can be provided by the sending system. If the requested data cannot be provided by the sending system, it should respond with either an empty FHIR search set, or with HTTP 404.

Add attachmentsrepeatable

Query list of attachments

When the referrer wants to add one or more attachments to the request form, ZorgDomein will first query a list of potentially relevant attachments by sending a FHIR search query to the DocumentReference endpoint of the sending system. See Adding attachments to documents for more details.

Serve list of attachments

The FHIR server of the sending system is expected to serve a FHIR search set that represents a list of the relevant documents that may be added to the request form in ZorgDomein.

Query binary data

After the relevant documents have been selected, ZorgDomein will query the actual binary data of the documents. See Adding attachments to documents for more details.

Serve binary data

The FHIR server of the sending system is expected to serve the requested binary data.

Send request form

After a request form has been submitted by the referrer, ZorgDomein will send the request form to the receiving system as a FHIR Document of type “Aanvraagformulier”. See Receive documents for more details.

Send attachments

When the referrer has added one or more attachments to the request form, these attachments will be sent to the receiving system in a separate FHIR Document.

Send copy of request form

A copy of the request form that was sent to the recipient will also be sent to the system of the referrer. This request form is presented at the sending system as a FHIR Document of type “Aanvraagformulier”, and should be saved as outbound correspondence for the patient. See Send documents for more details.

Send supplement

Add attachmentsrepeatable

Query list of attachments

When the referrer wants to add one or more attachments to the supplement, ZorgDomein will first query a list of potentially relevant attachments by sending a FHIR search query to the DocumentReference endpoint of the sending system. See Adding attachments to documents for more details.

Serve list of attachments

The FHIR server of the sending system is expected to serve a FHIR search set that represents a list of the relevant documents that may be added to the supplement in ZorgDomein.

Query binary data

After the relevant documents have been selected, ZorgDomein will query the actual binary data of the documents. See Adding attachments to documents for more details.

Serve binary data

The FHIR server of the sending system is expected to serve the requested binary data.

Send supplement

After a supplement has been submitted by the referrer, ZorgDomein will send the supplement to the receiving system as a FHIR Document of type “Nazending”. See Receive documents for more details.

Send attachments

When the referrer has added one or more attachments to the supplement, these attachments will be sent to the receiving system in a separate FHIR Document.

Send copy of supplement

A copy of the supplement that was sent to the recipient will also be sent to the system of the referrer. This supplement is presented at the sending system as a FHIR Document of type “Nazending”, and should be saved as outbound correspondence for the patient. See Send documents for more details.

Request for research, service or device

Starting a request

Sending a supplement

Cancelling a request

Sequence diagram

Questions or comments?

Thank you!