FHIR Bulk Operations
The FHIR Bulk Operations configuration category includes the following configurable options:
Enable Bulk Export batch job reuse
FHIR Bulk Export Enabled
Maximum Bulk Export file capacity
Bulk Export file retention (hours)
Normalize Terminology on Bulk Export
Restrict Download to Initiating User
FHIR Bulk Import Enabled
|
|
Enable Bulk Export batch job reuse |
|
|
|
| BOOLEAN | |
| If this is enabled, the bulk export operation will check whether a batch job already exists with identical parameters, and if so, will reuse that batch job. If disabled, the bulk export operation will always create a new batch job. Defaults to enabled. | |
|
|
true
|
|
|
|
|
FHIR Bulk Export Enabled |
|
|
|
| BOOLEAN | |
| If enabled, this server will support the FHIR Bulk Export protocol. See FHIR Bulk Export for more information. | |
|
|
false
|
|
|
|
|
Maximum Bulk Export file capacity |
|
|
|
| INTEGER | |
| If set, provides the maximum number of resources that will be stored in each binary file created by a bulk export. If set to 1000, then up to 1000 resources will be included per NDJSON file in the output. The complete contents of individual files are held in memory while they are being created, so large values may require additional RAM to be available. | |
|
|
1000
|
|
|
|
|
Bulk Export file retention (hours) |
|
|
|
| INTEGER | |
| Files related to a bulk export job will be purged after this many hours from the point at which the job started. If set to 0 or less, the files will never be removed. | |
|
|
24
|
|
|
|
|
Normalize Terminology on Bulk Export |
|
|
|
| BOOLEAN | |
| If enabled, Smile CDR will attempt to normalize codes in generated bulk export files. | |
|
|
false
|
|
|
|
|
Restrict Download to Initiating User |
|
|
|
| BOOLEAN | |
| If enabled, generated Bulk Export Binary files will only be readable by the specific user who initiated the export. See Accessing Bulk Export Files for more information. | |
|
|
true
|
|
|
|
|
FHIR Bulk Import Enabled |
|
|
|
| BOOLEAN | |
| If enabled, this server will support the FHIR Bulk Import protocol. See FHIR Bulk Import for more information. | |
|
|
false
|
|
|