Migrate your Quanum Practice Management data

Patient demographics and core clinical data can be extracted via the Access database export or the CCDA export. The CCDA aligns with USCDI and 21st Century CURES Act requirements, covering Problems, Medications, Allergies, and Demographics. Custom patient fields stored outside the standard schema land in the Access DB and require field-level mapping work.

Encounter-level clinical documentation is included in the full Access database export. The CCDA export provides a point-in-time clinical summary rather than a full encounter history, so comprehensive encounter migration requires the Access database path.

Scheduling data lives in the Practice Management module and is extractable via the Access database. Appointment histories, recurring patterns, and provider assignments must be mapped to the target system's scheduling schema.

Billing records and insurance claim data are part of the Practice Management export. Claims histories, statuses, and payer-specific adjustments stored in the Access database require transformation to the target billing module's schema.

Treatment plan documentation is captured in the EHR module. If the source practice used EHR functionality, these records are in the Access database and can be mapped to the destination system's plan object.

Lab results flowing from Quanum Lab Services Manager are tied to the Quest Diagnostics ecosystem. Lab Services Manager itself is not discontinued, so results history may be accessible separately. We coordinate import of historical lab data alongside the PM/EHR export to avoid duplication.

Uploaded documents referenced in the EHR module are accessible in read-only mode. The export scope includes attached documents; we map file references to the target system's document management approach.

QRDA I files preserve clinical quality measure data for practices that attested to Quality Payment Program (QPP). We preserve these files as-is for re-ingestion into the destination EHR, noting that mapping into target-system quality reporting modules may require specialty-specific configuration.

Specialty-specific custom fields are stored in the Access database alongside standard fields. We flag every custom field during the profiling phase and build explicit mapping rules before loading into the target system.

Billing reconciliation reports are accessible in the read-only EHR. These cover payment posting, denial tracking, and AR aging—critical for RCM continuity. We extract these reports as structured data where available or as reference documents.