Data Migration - Database Files

Customers migrating from an EHR platform leveraging a local database (SQL, MySQL, PostgreSQL, MDB) can have data imported into DrChrono.

To successfully migrate compatible entries (data points), we require the following:

1. An export of the database: This should be a database backup file ( such as`.BAK` for Microsoft SQL databases) or other compatible file which allows our engineers to restore and query the database for compatible data points.
2. Database Documentation: Database documentation may include a dictionary or other reference material advising our engineers on the location of specified data points within the database. In lieu of documentation, the vendor may provide detailed instructions with regards to accessing these fields. If database documentation or instructions from the vendor are not available, the migration request will be rejected.
3. Documents, Files & Other Media:
   1. For some vendors, data such as "Clinical Encounter Notes" and "Scans" are saved directly to the database. If this is the case with your vendor's system, documentation must be provided to detail the location (table(s)) within the database where these files reside, and steps on how to link the files back to their patient-owners.
   2. Other vendors store hard-files separately, such as in a single `Documents` folder provided alongside a database backup. In this case, there is often a database table where the file references are stored. This must be provided in the database documentation, or instructions provided by the vendor.
   3. Compatible file types (pdf, tiff, jpeg, png, html, docx) located within the data will be indexed and imported into appropriate patient records. Incompatible file types will be returned to the vendor as a single compressed folder.

As we're not able to cover all possible scenarios here, please contact us via support ticket if you have any questions related to migrating external databases into DrChrono.

(Note: Database files from eClinicalWorks are not accepted)