Enable Data Blend
To enable Data Blend, the following configurations must be completed:
Create the script that will be referenced in the MDM module configuration (classpath:mdm/mdm-rules.json). This script defines how patient records should be linked across sources.
{
"version": "1",
"mdmTypes": [
"Patient"
],
"eidSystems": {
"Patient": "http://example.org/eid-system-patient"
}
}
classpath:mdm/mdm-rules.jsonRegister the interceptor that will be referenced in the Persistence module configuration (com.smilecdr.custom.auto.mdm.export.CustomAutoMdmExportInterceptor). This interceptor is required for Data Blend functionality. It automatically injects the mdm=true parameter into data export requests, ensuring related patient records are included.
Note: The Smile Support Team or Technical Account Manager should be contacted to obtain the JAR file class.
Once obtained, place the JAR file in the smilecdr/customerlib folder on the Smile CDR server.
For more details, see the official Smile CDR documentation: Registering an Interceptor.
Note: This persistence configuration is for the repository where data from source systems are stored.
On the FHIR Storage (R4 RDBMS) module (add it if it does not already exist, or update the existing module), configure the following properties:
Yes.Yes.Yes.com.smilecdr.custom.auto.mdm.export.CustomAutoMdmExportInterceptorENABLED.On the Subscription Matcher module (add it if it does not already exist), configure the following properties:
classpath:mdm/mdm-rules.jsonMATCH_ONLYYou are about to leave the Smile Digital Health documentation and navigate to the Open Source HAPI-FHIR Documentation.