CH LAB-Report (R4)
1.0.0 - trial-use
This page is part of the CH LAB-Report (R4) (v1.0.0: STU 1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Certain laboratory results are available in the form of images or PDF documents. One possibility to exchange images or PDF files via HL7 FHIR, is the usage of the base64Binary data type. This data type enables embedding and transferring binary data (such as images or PDFs) in FHIR resources in Base64-encoded format.
In HL7 FHIR, the base64Binary data type is used for fields meant to hold binary data. A common example is the DocumentReference.content.attachment.data
element in the DocumentReference resource, which has the possiblity to contain documents as a base64-encoded string. When sending a file, it is first encoded in base64 and then inserted into the appropriate data element.
Example of a base64-encoded image in a DocumentReference:
{
"resourceType": "DocumentReference",
"content": [
{
"attachment": {
"contentType": "image/jpeg",
"data": "base64-encoded-data-here"
}
}
]
}
You can find another representation in the element DiagnosticReport.presentedForm
in the example 3-breath-test
Since transferring large files can impact network load and server performance, it's advisable to implement file size limitation mechanisms:
Set a file size limit: FHIR implementations can set a maximum file size limit for uploaded documents, for example, a limit of 20 MB base64Binary.
Use external links: For very large or frequently updated files, consider using an external link instead of the base64-encoded content. This can be done through the url
element of the Attachment, where only the link to the file is provided, and the actual file remains stored on a separate server.
Example:
{
"resourceType": "DocumentReference",
"content": [
{
"attachment": {
"contentType": "application/pdf",
"url": "https://example.com/path/to/document.pdf"
}
}
]
}
In summary, the base64Binary data type provides a flexible solution for transferring binary data in FHIR, and by combining size restrictions, the use of external URLs, and potential compression, the efficiency and performance of these transfers can be optimized.