OZO FHIR implementation guide
0.1.0 - ci-build
OZO FHIR implementation guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
The dropbox funcationality allows a client of the OZO FHIR API to attach a file as a URL as an attachment without having to include the file as binary to the resource. Attachments can bet added to CommunicationRequest resources and Communication resources in the payload.contentAttachment.url field.
The procedure to add an attachment to a resource is as follows:
CommunicationRequest or Communication resource with the URL in the payload.contentAttachment.url field.The endpoint is protected by the NUTS access_token mechanism, the client needs to include the access_token in the Authorization header and DPoP header if the token type is DPoP. For details please refer to the Access the API.
The file and attributes are posted to the dropbox endpoint of the OZO API, with tha file as a form attachment.
careteam_id, the logical id of the CareTeam resource, this parameter is part of the URL.fhir_attachment[file], the file to upload as a multipart data.fhir_attachment[resource_id], resource id of the resource to attach the file to.access_tokem, the access token from the NUTS node.dpop_token, the DPoP token from the NUTS node.curl -X POST -H "Authorization: DPoP <access_token>" -H "DPoP: <dpop_token>" -F "fhir_attachment[resource_id]=CommunicationRequest/3123" -F "fhir_attachment[file]=@01519_1t.webp" https://connect.zorgverband.nl/fhir/clients/9632/attachments
The response will contain a 302 redirect, the Location header will contain the URL of the file.