Teleconsult

Starting a teleconsult

ZorgDomein Integrator facilitates the process of teleconsultation in which a requester consults an external healthcare supplier or professional without referring the patient. When doing a teleconsult or advisory consult (meekijkconsult), the requester logs in to ZorgDomein directly from his/her own information system using SSO. After logging in, he/she will select a teleconsultation product that is published by a specific healthcare supplier. This healthcare product determines the choice for the healthcare supplier. Once the healthcare supplier has been selected, the requester will compose and send a teleconsult request form to the healthcare supplier. This document contains the request for advice and provides relevant medical data about the condition of the patient. 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 requester. The requester may also add attachments to the request form. These attachments should be fetched from the information system of the requester. After submitting the request form, ZorgDomein will deliver the request form at the information system of the healthcare supplier. A copy of the request form will be sent back to the information system of the requester for archiving purposes.

Answering a teleconsult

The teleconsult request form will be delivered in the information system of the selected healthcare supplier, where it will be listed on a work list or inbox. An authorized specialist can answer the incomming request from his/her information system by logging in to ZorgDomein using SSO. After logging in, he/she will be directed to the answer form that can be used to compose an answer to the request. Some parts of content of this answer may automatically be composed based on the medical patient data from the information system of the specialist. The specialis may also add attachments to the request form. These attachments should be fetched from the information system of the specialist. After submitting the answer form, ZorgDomein will deliver the answer document to the information system of the requester. A copy of the answer document will be sent back to the information system of the specialist.

Sequence diagram

The sequence diagram below provides a schematic overview of all interactions between the involved actors when performing a teleconsult.

Referrer

ZorgDomein

Provider

Send request for teleconsult

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 teleconsult 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 teleconsult 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 teleconsult 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 teleconsult 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 teleconsult request form

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

Send attachments

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

Send copy of teleconsult request form

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

Send answer

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 context details. See SSO to ZorgDomein for more details.

Serve application context details

The FHIR server is expected to provide the requested Task resource. This Task resource must contain the ZD-number of the teleconsult request for which an answer will be sent in Task.basedOn.identifier.

Compose and send answer

Request medical patient datarepeatable

Request medical patient data

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

Serve medical patient data

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

Add attachmentsrepeatable

Query list of attachments

When the sender of the answer wants to add one or more attachments to the answer, 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 answer

After an answer has been submitted by the sender of the answer, ZorgDomein will send the answer to the receiving system as a FHIR Document. See Receive documents for more details.

Send attachments

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

Send copy of answer

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

Teleconsult

Starting a teleconsult

Answering a teleconsult

Sequence diagram

Questions or comments?

Thank you!