Migrate your Zedmed data

Patient records in Zedmed include demographics, contact details, Medicare/DVA numbers, and payer associations. Schema is stable across versions. We map Patient records 1:1 to the destination system, preserving all demographic fields and payer linkages.

Practitioner records store provider details, prescriber numbers, provider numbers, and provider type. Owner/User assignment maps directly. We preserve practitioner-provider number linkages which are critical for Medicare claiming continuity.

Clinical encounters capture the consultation record including reason for visit, observations, diagnoses, and treatment notes. We extract the full encounter history and preserve the temporal link back to the originating Appointment.

Appointment records include date/time, type, status, practitioner assignment, and patient linkage. Zedmed v39 supports multiple SMS reminders per appointment. We map appointment records including telehealth appointments with their SMS confirmation status.

Electronic prescriptions are stored as structured data within the clinical record. We extract prescription content, medication names, dosages, and prescriber attribution. Linked to the Practitioner and Patient records.

Pathology results flow via HealthLink integration and are attached to patient records and encounters. We extract result content, ordering practitioner, and collection date. Results management status (viewed/unviewed) is also preserved.

Free-text clinical notes are stored in structured fields. Drawing annotations on images are embedded as image blobs. We extract all text fields directly; drawing data requires image conversion during migration and may need re-annotation on the destination platform.

Referrals are generated via the batch letter writer and stored as documents. Outgoing referral content and recipient details are extracted. The referral status tracking is proprietary and requires field mapping to match destination workflow states.

SmartForms are proprietary structured forms used for patient intake and clinical data collection. The form schema and stored values require custom field mapping to match the destination platform's equivalent object structure.

Payers include Medicare, DVA, health funds, WorkCover, TAC, and Motor Vehicle third parties. Each payer has its own fee schedule and claiming rules. We extract payer configurations including P-codes used in the fee structure.

Item records use MBS codes for Medicare services with associated fee values. The payer-item-fee hierarchy is complex — P1/P2/P3 private fee levels, derived items, and add-on rules all require value-level mapping to the destination billing setup.

Invoice records are generated from the payer-item-fee intersection. Medicare/DVA Eclipse claiming and Tyro integration produce claim status records. Historical invoice and payment history requires extraction with careful attention to claim state (submitted, paid, rejected).

Clinical templates are created in WordPerfect and stored as RTF files. Templates with merge fields link to patient and practitioner data. Templates not created within Zedmed Clinical may be incompatible even in RTF format — we flag all templates for pre-migration review.

Document attachments include clinical letters, reports, and uploaded files stored in the Zedmed database. RTF documents are extracted as-is; PDFs and other formats are preserved as binary blobs. We note any encoding or format conversion required by the destination system.