SanteDB's dCDR software support self-service registration of dCDR instances provided the user self-enrolling the device has proper permissions (Create Device). The self-service procedure will vary depending on:
The dCDR plugins and customizations performed (i.e. the MEMPI RegApp is different than TImR App self-service enrolment)
The strategy for the dCDR instance (online or synchronized)
The subscription architecture of the dCDR instances (identifier, catchment, etc.)
Use Procedure When
A new device is being setup with an app that is built on the dCDR technology (Android application, Web Access Gateway, Disconnected Gateway, etc.)
The device has not previously been setup or configured on the iCDR interface
Procedure
Before Beginning
Connected to the Internet
Ensure the device is protected from threats
Ensure the device has the latest operating system installed
Ensure the device has its local firewall enabled and configured
Ensure the device has antivirus software and anti-malware software installed
Ensure device name selected complies with the device naming conventions in the operational architecture documentation developed.
Ensure that a most responsible person and/or facility has been documented for the device
Install the appropriate dCDR software on the device
Ensure the user of the device has received proper instructions on care and use of the device:
Reviewed and completed the Privacy Policy
Reviewed and completed the Acceptable Use Policy
Reviewed and completed the Data Sharing Process Documents
Procedures / Tasks
1.
When the dCDR interface opens with the initial configuration screen enter the onboarding information:
1.
Device name following the established naming conventions
2.
Use mysantedb.example.com as the realm
3.
Modify the client secret information to match the modified client secret sent to you (should be in the operational documentation)