SOP: Onboarding new dCDR Device
Summary
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
Procedure
Before Beginning
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
When the dCDR interface opens with the initial configuration screen enter the onboarding information:
Device name following the established naming conventions
Use mysantedb.example.com as the realm
Modify the client secret information to match the modified client secret sent to you (should be in the operational documentation)
Ensure Use TLS is selected
Join the domain
Follow the onboarding procedure documented in SanteDB dCDR Instances
When prompted to select an optimization strategy select the slowest network speed (highest compression rate - 2g/Dial Up)
Allow the initial synchronization to complete (there should be a notification that initial synchronization is complete)
After Completion
Update the facility and most responsible person (if applicable) in the administrative panel (see: Managing Devices)
Update the device information including Operating System, Manufacturer, Model (if required) in the administrative panel
Provide the device to the primary user and close the ticket
Summary Information
Current Status: Example Reviewed By: SanteSuite Team
Revision History
Justin Fyfe (SanteSuite)
2022-03-15
Initial Version
Last updated