Migrate your Essential MD Software Suite data

Patient demographics are the primary record type in this platform. We migrate patient records with standard fields (name, DOB, contact info) and preserve any custom patient-level properties. We flag patient ID remapping whenever the destination system assigns new IDs to avoid breaking downstream encounter and billing linkages.

Appointment records carry provider, patient, date/time, and status. We preserve the full appointment history including cancelled and no-show statuses. Recurring appointment series are exported as individual records to maintain date-level fidelity in the destination system.

Clinical encounter notes and associated diagnosis codes are migrated as discrete records linked to the patient and provider. We preserve ICD and CPT codes as-is and flag any code-set version differences between source and destination systems before write-back.

Billing records are tightly coupled to encounters and appointments. We export all charge entries, payments, and adjustments. A key migration risk is breaking the linkage between a billing record and its originating encounter—our sequencing ensures this linkage is restored via a patient-encounter-billing ID map before records are committed.

Submitted and adjudicated claims are exported with payer, status, and payment details. Claims in 'pending' or 'in-process' states are flagged as requiring post-migration status monitoring, since the destination clearinghouse may re-map claim IDs that affect reconciliation workflows.

Provider records including NPI, credentials, and taxonomy are migrated. We preserve provider-to-appointment and provider-to-encounter assignments as foreign key references. When the destination system uses different provider ID formats, we create a provider mapping table to maintain referral and rendering provider relationships.

Document attachments associated with patients, encounters, or billing records are exported as binary blobs or links depending on the export format. We chunk large document sets and preserve document metadata including original upload date and associated record linkage. Any format conversion required for destination compatibility is flagged before migration.

Custom fields defined by the practice at the patient, encounter, or billing level are exported as key-value pairs. We preserve field names and data types and map them to equivalent custom fields in the destination system where supported. Unmapped custom fields are exported as notes or fallback properties to prevent data loss.

Insurance payer lists including carrier name, plan type, and address are migrated. We deduplicate by payer ID and flag payer name variations (e.g., 'BCBS' vs 'Blue Cross Blue Shield') that may cause mapping failures in the destination if the destination maintains a normalized payer list.

Template definitions and structured form schemas used for clinical note authoring are not exported as they are considered application configuration rather than patient data. We document the template schema separately so it can be manually recreated in the destination system.