The FHIR Binary Storage configuration category includes the following configurable options:
Binary Access Operations Enabled
Automatically inflate binaries.
Binary inflation maximum size (bytes)
Blob service S3 access key
Blob service Azure account name
Blob service Azure client / application ID
Blob service Azure access key / client secret (app password) / Account-level SAS token
Blob service Azure tenant ID
Blob service bucket / container name.
Endpoint URL for S3-compatible service
Blob Service Region
Blob service secret key
Filesystem Mode: Base Directory
Binary Storage Mode
Maximum Size (bytes)
Minimum Size (bytes)
|
|
Binary Access Operations Enabled |
|
|
|
| BOOLEAN | |
| This setting enables the binary access read/write operations. See Binary Access Operations for more information. | |
|
|
true
|
|
|
|
|
Automatically inflate binaries. |
|
|
|
| BOOLEAN | |
| If set to true, binaries stored in external binary storage will be fetched and populated into the resource body automatically upon resource access. If set to false, resources will show a binary ID with which you can manually fetch the binary. | |
|
|
true
|
|
|
|
|
Binary inflation maximum size (bytes) |
|
|
|
| POSITIVE_INTEGER | |
| At most this many bytes will be fetched from external binary storage per request. If your request contains more binary data than this, anything over this threshold will be returned as a binary ID for later fetching. | |
|
|
10485760
|
|
|
|
|
Blob service S3 access key |
|
|
|
| STRING | |
| This setting allows you to set a manual access key. This is optional for AWS, as it uses its own credential chain. This setting is required if you are using MinIO. | |
|
|
| (no default) | |
|
|
|
Blob service Azure account name |
|
|
|
| STRING | |
| This setting allows you to set a manual account name for Azure. This setting is required if you are using Azure blob storage. | |
|
|
| (no default) | |
|
|
|
Blob service Azure client / application ID |
|
|
|
| STRING | |
| This setting allows to set the identifier that is associated with an application. This is optional and only needed when using Azure Active Directory Token. | |
|
|
| (no default) | |
|
|
|
Blob service Azure access key / client secret (app password) / Account-level SAS token |
|
|
|
| PASSWORD | |
| This setting allows to set a manual Azure access key, client secret or shared Access Signatures (SAS) token. This is a multipurpose property and the value is depended on the types of authentication - access keys, Azure active directory or account-level SAS token. This setting is required if you are using Azure blob storage. | |
|
|
| (no default) | |
|
|
|
Blob service Azure tenant ID |
|
|
|
| STRING | |
| This setting allows to set the unique identifier of the Azure Active Directory instance. This is optional and only needed when using Azure Active Directory Token. | |
|
|
| (no default) | |
|
|
|
Blob service bucket / container name. |
|
|
|
| STRING | |
| This setting allows you to control which bucket / container objects are stored in on the blob service provider. | |
|
|
smilecdr-binary-storage
|
|
|
|
|
Endpoint URL for S3-compatible service |
|
|
|
| STRING | |
| Overrides the endpoint for an S3-compatible service. This is optional for AWS, but required if you are using MinIO. | |
|
|
| (no default) | |
|
|
|
Blob Service Region |
|
|
|
| STRING | |
| This setting allows you to control which region S3/Minio buckets/objects are stored in. | |
|
|
us-west-2
|
|
|
|
|
Blob service secret key |
|
|
|
| PASSWORD | |
| This setting allows to set a manual S3 secret key. This is optional for AWS, as it uses its own credential chain. This setting is required if you are using MinIO. | |
|
|
| (no default) | |
|
|
|
Filesystem Mode: Base Directory |
|
|
|
| LOCAL_FILEDIR | |
When operating in FILESYSTEM binary storage mode, this setting provides the base path in which to store large binary objects.
|
|
|
|
| (no default) | |
|
|
|
Binary Storage Mode |
|
|
|
| ENUM | |
| Values |
|
| This setting sets a storage mechanism for large binary objects. See Externalized Binary Storage for more information. | |
|
|
DATABASE
|
|
|
|
|
Maximum Size (bytes) |
|
|
|
| POSITIVE_INTEGER | |
| This setting provides the maximum size of a binary object to be stored in binary storage. Binaries larger than this cutoff will be rejected and may not be stored. | |
|
|
104857600
|
|
|
|
|
Minimum Size (bytes) |
|
|
|
| NON_NEGATIVE_INTEGER | |
| This setting provides the minimum size of a binary object before it is stored in binary storage. Any binaries smaller than this size will still be stored, but may be stored inline within resource bodies as base 64 encoded content. | |
|
|
10000
|
|
|