Skip to content

Commit 2c3eb2f

Browse files
authored
Update fhir-best-practices.md
1 parent 1444d11 commit 2c3eb2f

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

articles/healthcare-apis/fhir/fhir-best-practices.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,13 @@ For data extraction, use the bulk `$export` operation as specified in the [HL7 F
7272

7373
For more information on export operations, see [Export your FHIR data](export-data.md).
7474

75+
## Storing binary data in FHIR resources
76+
* **Do** storing small payloads (up to 2MB) as base64-encoded strings within the FHIR resource.
77+
* **Consider** using external storage solutions for larger binary data. Store binary data in a blob storage and reference it in the FHIR resource using a URL to avoid inefficiencies.
78+
* **Consider** breaking up large binary files into smaller chunks (less than 2MB) and storing them as separate binary resources, which can then be linked together using a FHIR resource.
79+
* **Avoid** storing large binary data directly within the FHIR resource, as it can lead to limitations and inefficiencies in FHIR service capabilities such as import, export, and search.
80+
81+
7582
By applying these best practices you can enhance the performance and efficiency of data ingestion, bundle processing, query execution, and data extraction in Azure FHIR service.
7683

7784
[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

0 commit comments

Comments
 (0)