Feature Configuration
Core Services (Recommended)
Diagnostic Logging
The diagnostic logging feature allows for logging to files, the console, or even via the trace writer in Mono. These settings provide access to the Diagnostics Configuration subsystem.
Data Privacy Controls
The privacy control services actively apply privacy policy protections on outbound messages, and ensure that inbound messages meet the minimum policy level for updating/creating records. For example, this service ensures that masked data, or sensitive data which may be inaccurate (given the submitter's policy set) cannot be recorded, and that any data is masked/hidden from the underlying repository.
The SDB_DATA_POLICY_FORBID
setting restricts the use of the indicated property in the RIM from users. For example, to restrict collection, querying, or disclosing of the religion property, and to only allow collection, querying and disclosing of vip status to users with policy 2.25.349398
Audit Repository
The audit repository feature enables the local audit repository on SanteSuite, meaning that audits are stored in the specified audit database.
ADO Data Storage
The ADO data storage service should be enabled if you plan on using the PostgresSQL or another supported database to store data.
You can swap the SanteDB core storage technology to another technology, in this case do not use the ADO data storage feature.
ADO Freetext Search
The ADO freetext search service enables the full-text indexing feature on the docker container, and is available on SanteDB iCDR versions 2.1.155 and above.
The ADO free-text search service refreshes the free-text index in real time as records are added to the SanteDB iCDR. If your deployment has no need of freetext search at the iCDR level (i.e. you are using the dCDR only for user interfaces) then you can disable this feature to improve performance.
In-Memory Caching
The in-memory caching feature instructs the iCDR container to use a local RAM-based cache (non-shared) for data operations.
REDIS Caching
The REDIS caching feature instructs the iCDR container to use a shared REDIS cache for data operations.
Core Security Services
The core security services should always be enabled, unless you're running a heavily customized version of the iCDR software which supplies its own security services.
OpenID Connect IDP
The OpenID Connect IDP service enables the OpenID Identity Provider services.
Core Health Data Service Interface
The core HDSI interface should always be enabled if you plan on using any of the SanteDB dCDR services. If you are just using the iCDR for other interfaces, you can disable this interface.
Core Administrative Management Interface
The core AMI interface should always be enabled if you plan on using any of the SanteDB dCDR services or services like the admin console which require API access. If you are just using the iCDR for other interfaces, and have no need to create users, policies, or other assets.
Core Business Intelligence Interfaces
The core BI services allow third party solutions to query and execute reports on the SanteDB server, as well as FHIR MeasureReport resources.
Setting SDB_BIS_MAX_RESULTS
will impact server performance. The default size of BI report result sets is 10,000. For reports which require more than 10,000 results, it is recommended that the developer pass the _count
parameter to the rendering API.
Optional Services
HL7 Fast Health Interoperability Resources (FHIR)
SanteDB's FHIR resources are enabled using the FHIR feature. The FHIR feature controls the exposed resources (to minimize surface area), location and options for FHIR.
SDB_FHIR_EXTENSION
is used to enable IFhirExtensionHandler
implementations, these are responsible for querying or transforming data from the Data & Information Architecture to FHIR. Extensions which are stored as extensions within the data architecture are always exposed in the FHIR objects. See: Extension Handlers
HL7 Version 2.x
The HL7 Version 2.x interface allows the iCDR docker container to expose HL7 LLP or SLLP traffic to trading partners.
Publish / Subscribe Functions
The pubsub feature enables the structured message notification system. This allows third party systems to setup standing queries which SanteDB will "notify" them of whenever new data becomes available.
Record Matching Plugin
The record matching plugin registers the SanteDB Matcher plugin in the container. This service is used by other services to match and/or merge data.
The matching modes supported are:
SIMPLE: Simple matching only performs block operations against the database, and performs no scoring. This mode is useful when your duplication detection is light. Records are given a score of 0.0 (not match) or 1.0 (match)
WEIGHTED: Weighted matching uses the SanteDB Matching plugin to perform scoring.
When composing your own image from SanteMPI you can copy match configurations to the ./match directory:
Master Data Management & Record Linking
The MDM feature sets up the MDM resource persistence strategy and subscribes one or more resources to one or more match configurations.
When enabling the MDM service, you must also enable the MATCHING service.
The supported resources for MDM management are:
Resource | Description |
Person | Places any entity of type Person or its subclasses (Provider / Patient) under MDM storage management. |
Patient | Places any entity of type Patient into MDM storage management. This is useful for Master Patient Index or Client Registry scenarios. |
Provider | Places any entity of type Provider into MDM storage management. This is useful for centralized Provider Registries. |
Material | Places any entity of Material or ManufacturedMaterial into MDM storage management. This includes kinds and instances of materials. Useful for centralized product registries. |
ManufacturedMaterial | Places only ManufacturedMaterials into MDM storage management. |
Place | Places the Place resource into MDM storage management. This is useful for centralized Geographic or Facility Registries |
Organization | Organizations (such as companies, government agencies, etc.) in MDM control. |
E-Mail Configuration
This section documents a SanteDB 3.0 feature.
The e-mail configuration allows you to configure the SMTP settings for SanteDB to send e-mails. This option is used for MFA codes, administrative alerts, etc.
Signing Configuration
This section documents a SanteDB 3.0 feature.
The signing configuration allows administrators of the Docker server to change how the server software signs tokens.
SanteMPI Features
You can enable specific SanteMPI features by enabling the IHE_*
interfaces on the santedb-mpi
container.
IHE PIX for Mobile
To enable the $ihe-pix
operation in the container:
IHE PDQ for Mobile
To enable the PDQm behaviors on the /Patient
resource:
IHE PMIR Feature
To enable the urn:ihe:iti:pmir:2019:patient-feed
operation:
IHE PIX for HL7v2
To enable the specialized behaviors on ADT messages for IHE PIX for HL7v2
IHE PDQ for HL7v2
To enable specialized behaviors on QBP messages for IHE PDQ for HL7v2
Last updated