Migrate Dentricity Patient Database To Cloud Storage
Summary
This guide helps you troubleshoot and resolve: Migrate Dentricity Patient Database To Cloud Storage. Follow the steps below to fix the issue.
Common Causes
Migrating patient records from an on-premise server to cloud-hosted storage requires careful planning to protect sensitive health information and maintain practice continuity. This guide assists dental and medical specialists and practice managers in migrating a patient database to cloud storage while addressing backup integrity, Australian data residency, encryption, and compliance obligations under the Privacy Act 1988 and the Australian Privacy Principles (APPs).
Vendor disclaimer: Before beginning this migration, confirm with your practice management software vendor that the application is certified for cloud-hosted database storage and that moving the database to a cloud endpoint will not void support agreements or affect clinical data integrity.
Prerequisites
- Administrator access to the practice management application and the local server
- Active cloud storage account hosted in an Australian data centre to satisfy health records data residency requirements
- A recent, verified full backup of the existing patient database stored on an external drive or secure network location
- Stable broadband connection at the practice with sufficient upload and download bandwidth for cloud database access
- Documentation of the cloud provider’s encryption-at-rest and encryption-in-transit standards
- A signed data processing agreement or business associate agreement with the cloud provider covering the handling of patient health information
Pre-Migration Backup Verification
- Perform a full backup of the existing on-premise patient database before making any configuration changes.
- Store the backup on an external drive or secure network location that is physically separate from the production server.
- Verify the backup by restoring it to a test environment or confirming the backup integrity report generated by the application.
- Document the backup date, time, location, and the name of the staff member who performed the verification.
- Retain this on-premise backup for the legally required period under Australian health records legislation. Do not delete or overwrite it until post-migration verification is complete and you have confirmed patient record integrity in the cloud environment.
Migration Steps
1. Prepare Australian-based cloud storage
- Log in to your cloud storage provider’s management console.
- Confirm the storage region is set to an Australian data centre to meet data residency obligations for patient health information.
- Create a new container or bucket with a descriptive name, such as
practice-patient-records. - Enable encryption-at-rest for the container using the provider’s recommended encryption standard.
- Enable encryption-in-transit (TLS/SSL) for all connections to the cloud endpoint.
- Record the cloud endpoint URL or UNC path provided by the service.
- Create a dedicated service account with read/write permissions to the container only.
- Review the provider’s data processing agreement and ensure it covers the storage and handling of Australian health information in accordance with the Privacy Act 1988 and APPs.
2. Configure the cloud path in the practice management application
- Open the practice management application on the local server as an administrator.
- Navigate to Settings > Database Configuration.
- Locate the Database Path or Storage Location field.
- Enter the cloud endpoint path, for example
\\cloud-storage\practice-patient-records\or the provider’s specified endpoint. - Enter the service account credentials when prompted.
- Select Test Connection to confirm the application can reach the cloud storage over an encrypted connection.
- Click Save or Apply to commit the change.
C:\PracticeCache\ to maintain performance during patient consultations.3. Map local file shares to the cloud endpoint
- On the server, open File Explorer.
- Select This PC from the navigation pane.
- Click Map network drive in the top ribbon.
- Choose an available drive letter, such as
Z:. - In the Folder field, enter the cloud endpoint path.
- Select Reconnect at sign-in if you want the mapping to persist after reboot.
- Click Finish and enter credentials if prompted.
- Confirm the mapped drive appears under This PC and is accessible.
4. Verify patient record indexing after migration
- Open the practice management application on a client workstation used by reception or clinical staff.
- Perform a search for an existing patient record by surname or patient ID.
- Open the record and confirm all clinical notes, appointment history, and billing details load correctly.
- Create a test patient record with a unique identifier.
- Search for the newly created record to confirm indexing is writing to the cloud location.
- Check the application logs under Tools > Logs for any database connection errors or failed write operations.
- Confirm that encryption-at-rest and encryption-in-transit indicators are active within the application or cloud console where available.
Post-Migration Backup Confirmation
- Run a backup of the database now hosted in the cloud storage container.
- Verify that the cloud backup completes successfully and that restore tests can access patient records.
- Document the cloud backup schedule, retention period, and recovery point objective for the practice.
- Ensure backup copies remain stored in Australian data centres to maintain compliance with health records storage requirements.
Rollback Procedure
- If migration fails or patient record indexing cannot be verified, repoint the application database path back to the original on-premise server location under Settings > Database Configuration.
- Restore the verified pre-migration backup from the external drive or secure network location to the local server.
- Restart the practice management application service to force a re-index of the restored on-premise database.
- Perform test searches and open sample patient records to confirm clinical data is accessible and intact.
- Contact your IT support provider for assistance if the rollback does not restore normal operations.
Decommissioning the On-Premise Server
- Only after successful post-migration verification and backup confirmation, power down the on-premise database server.
- Retain the on-premise backup media for the legally required retention period under Australian health records legislation.
- Securely wipe or destroy any local drives containing patient health information in accordance with your practice’s information security policy and APP 11 requirements for data security and disposal.
- Update practice documentation to reflect the new cloud storage location, backup schedule, and emergency contact for cloud support.
Troubleshooting
Application cannot connect to cloud storage
- Verify the cloud endpoint path is entered correctly, including trailing slashes if required.
- Confirm the service account has read/write permissions on the cloud container.
- Check that the practice firewall allows outbound traffic on the ports required by your cloud provider.
- Run
pingorTest-NetConnectionfrom the server to the cloud endpoint to confirm network reachability. - Verify that encryption-in-transit is enabled and not being blocked by a security appliance.
Authentication failure with cloud provider
- Confirm the service account credentials are current and not locked out.
- Check whether multi-factor authentication is required and configure an application-specific password if supported.
- Verify that the service account has not exceeded its assigned permission scope for the container.
Patient records missing or not indexing
- Ensure the database path points to the correct cloud container and not an empty subfolder.
- Confirm the migration copied all index files, not just the primary database file.
- Restart the practice management application service on the server to force a re-index of the cloud location.
- Review the application event log for file lock or permission errors.
Sync conflicts between local cache and cloud storage
- Check the application logs for conflict errors when multiple workstations access the same patient record.
- Confirm the local cache path is configured on a fast local volume and has sufficient free space.
- Schedule large report generation outside peak consultation periods to reduce sync load.
Slow performance when opening records
- Check the practice internet connection speed; cloud database access depends on consistent upload and download bandwidth.
- Confirm a local cache path is configured in the application settings.
- Avoid large report generation during peak consultation periods.
Once verification is complete, retain the on-premise backup for the legally required period under Australian health records legislation as a rollback option. If you encounter errors during the migration or indexing verification, Open a Ticket for assistance.
Still Having Issues?
💻 Open a Ticket