Standalone report

Sending a report

ZorgDomein Intagrator supports the use case where a practitioner wants to inform another practitioner about the condition of a patient by sending a report. It is possible to send a report back to referrer in response to a received referral, see the Referral use case for more details. It is also possible to send a “standalone” report, i.e. a report that is not based on a referral or other transaction type.

To send a standalone report, the sender logs in to ZorgDomein directly from his/her own information system using SSO. After logging in, he/she will be directed to the reporting flow. In this flow the sender can select the recipient for the report. After the recipient has been selected, the sender is directed to the reporting form that can be used to compose the report. The content of this report is automatically composed as much as possible based on the medical patient data from the information system of the sender. The sender may also add attachments to the report form. These attachments should be fetched from the information system of the sender. After submitting the report form, ZorgDomein will deliver the report document to the information system of the selected recipient. A copy of the report will be sent back to the information system of the sender for archiving purposes.

Sequence diagram

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

Sender

ZorgDomein

Recipient

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 direct the user to the relevant reporting flow and 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 report

Request medical patient datarepeatable

Request medical patient data

Based on the template of the selected report type, 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. See Send documents for a list of supported FHIR resources and corresponding fields in the report.

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

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

Send attachments

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

Send copy of report

A copy of the report that was sent to the recipient will also be sent to the system of the sender. This report 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.

Standalone report

Sending a report

Sequence diagram

Questions or comments?

Thank you!