Migrate from Zedmed to Microsoft Dynamics 365 Sales

Zedmed patient demographics (name, DOB, address, contact details) map 1:1 to Dynamics 365 Contact. Medicare number and pension/health fund card numbers store as custom fields. Unlinked patients get a default Account record in Dynamics. We also preserve the original Zedmed patient ID in a custom Source_System_ID__c field for traceability and future delta runs.

Referring doctors with provider numbers map to Dynamics 365 Account records (for organisations) or Contact records (for individual practitioners). Referring relationships to patients surface as custom lookup fields or a junction entity. If a referring practitioner also appears as a patient in Zedmed, the system creates both an Account and a Contact, linking them via a custom relationship to avoid data duplication.

Zedmed consultation records map to Dynamics 365 Task activities with Type='Appointment'. Appointment type, duration, practitioner, and attendance status stored as custom fields on the Task. Historical appointment counts preserved for reporting continuity. Each Task also records the original Zedmed appointment ID for audit trail and to support future delta synchronisation if required.

Zedmed Medicare item numbers, MBS fees, bulk-billing flags, and private fee amounts map to Dynamics 365 Opportunity records with custom billing fields or to a custom Billing_History__c table linked to Contact. Open vs closed claim status maps to Opportunity stage.

Zedmed clinical encounter notes, SmartForms, and drawing annotations cannot map to a native Dynamics 365 entity. We export them as text files or PDF attachments stored in Dynamics 365's SharePoint integration. Practitioners rebuild structured templates using Dynamics Word merge tooling.

E-prescription and pathology result links from Zedmed cannot transfer as functional records. We export the metadata (date, provider, result summary) as a Note on the Contact. Full clinical content must be accessed from the prescribing/pathology system directly. The Note includes a reference link back to the original Zedmed record for audit purposes.

Zedmed payer configurations (Medicare, DVA, TAC, WorkCover, health funds) map to custom pick-list fields on Contact and Account. Fee schedule values stored as custom currency fields or in a related custom Fee_Schedule__c table. The mapping preserves the payer priority order, enabling Dynamics workflows to route claims to the appropriate processing queue based on the payer type.

Zedmed practitioner accounts resolve by email match against Dynamics 365 users. Unmatched practitioners flagged before migration — the practice either provisions Dynamics users or assigns records to a fallback owner before data lands. All resolved owners retain the original Zedmed practitioner ID in a custom field to maintain audit trails across the platform.

Zedmed SMS reminder configuration ( ZedSMS, telehealth link schedules) has no Dynamics 365 equivalent. We preserve reminder counts and last-sent timestamps as custom fields on Contact and recreate reminder workflows using Dynamics 365 Sales automated flows. These custom fields capture the reminder frequency and channel preferences, allowing automated flows to replicate Zedmed’s recall logic within Dynamics.

Zedmed file attachments on patient records (referral letters, consent forms) re-upload to Dynamics 365 SharePoint integration attached to the Contact record. File size limits from the SharePoint backend apply. During migration, we verify file integrity via checksum and log any attachments that exceed SharePoint size limits for manual re-upload after go-live.

Zedmed health fund membership details, policy numbers, and benefit tier information require custom fields on Contact since Dynamics 365 Sales has no native health insurance entity. These custom fields store the fund name, membership ID, and tier level, enabling reporting on payer mix and reimbursement trends across the patient base.