FHIR R4 Service
Last updated
Last updated
The FHIR R4 configuration panel is used to control the configuration of the FHIR API endpoint.
Setting | Description | Examples |
---|---|---|
REST API Service Name | The name of the REST API service the FHIR interface should bind to. The default is FHIR however if you change the REST API name (in the panel section above) you should also change the name here. |
|
Landing Page | The HTML page where the FHIR service should use when a user accesses the FHIR base URL with no specific request. |
|
Resource Handlers | When configured, the allowed resources which can be used on the FHIR server. If not set, then the FHIR handler will enable all installed resources on the server. This setting allows the administrator to reduce the number of resources which can be used. | |
Operation Handlers | When configured, the allowed operations (via | |
Message Handlers | When configured, the allowed FHIR messages on the API endpoints (via | |
Extension Handlers | When configured, the extensions which are permitted to be used on the FHIR server. When disabled, the SanteDB FHIR API will enable all FHIR extensions. Note: When an extension handler is disabled, it merely disables special treatment of that extension - the extensions being received will be placed into the | |
Profile Handlers | When configured, the special profile validation services which should be used on the FHIR API. | |
Behavior Modifiers | When configured, the behavior modifiers for the FHIR service. Behavior modifiers allow the FHIR API to implement specific standards-based behaviors on the FHIR service. | |
Base Operation URL | The URL to expose to clients when a |
|
Default Format | The default format for FHIR requests. | JSON / XML |