Choosing a systemGuide
How to switch clinic management systems without losing records
Changing clinic software is less a software project than a records project. This guide covers what to migrate, what to ask of your old vendor, which obligations follow your data, and a realistic plan from first export to the end of the first month.
Key takeaways
- Secure the data first: a full export in documented formats, covering clinical notes, finances and attached documents, is the most important term in any exit.
- MOH licence conditions require electronic patient health records to be kept for the patient’s lifetime plus 6 years, so anything you do not migrate still needs a readable archive.
- Load at least one trial copy and reconcile patient counts, allergies and balances against the old system before go-live. Problems found after go-live are found by patients and staff.
- For NEHR-contributing and Healthier SG clinics, confirm the new system’s compatibility and agree how pending submissions will be completed so there is no gap.
- Most single-site clinics do better with a hard cutover on a quiet day, backed by a final delta import, than with weeks of double entry.
The short answer
To switch clinic management system without losing records, treat the move as a records project with software attached. The order that works: get a complete export from the old vendor, map it to the new system, load a trial copy, reconcile it, keep the old data readable for as long as the law requires, then cut over on a quiet day with both vendors on call.
Why clinics switch
The reasons are usually practical rather than dramatic:
- The system cannot meet a new requirement, such as NEHR contribution, Healthier SG, or a new payer.
- Pricing changes: per-module charges, or a costly upgrade just to stay supported.
- Support has thinned out, or the product is no longer actively developed.
- An on-premise server nearing end of life, with backups nobody has tested.
- A group wanting one system and one patient record across sites.
- Workarounds, such as spreadsheets for claims or a personal phone for WhatsApp, that have become the real system.
None of these is a reason to rush; rushed migrations are where records go missing. If you have not chosen a replacement yet, start with how to choose a clinic management system.
What to migrate, and what to check
List every type of data the old system holds, then decide for each: migrate as structured data, attach as a read-only document, or archive outside the new system. Structured data is what the new system can act on, such as allergy alerts and balances. Documents are for reading.
| Data | Migrate as | Check after the trial load |
|---|---|---|
| Patients (name, NRIC or ID, date of birth, contacts, next of kin) | Structured | Counts match; duplicates merged, not multiplied; ID formats valid |
| Allergies and alerts | Structured, never free text only | Each allergy shows as an alert; spot-check high-risk patients |
| Visit notes and diagnoses | Structured where coded, text where not | Visits per patient; dates and doctors intact; codes mapped |
| Prescriptions and dispensing history | Structured | Drugs mapped to the new formulary; doses and quantities kept |
| Chronic medication and follow-up dates | Structured | Repeat prescriptions and recall dates carried over |
| Inventory | Opening stock at cutover | Quantities, batches and expiry dates match a physical count |
| Balances and receivables | Opening balances, invoice history for reference | Outstanding totals per patient, company and insurer match to the cent |
| Appointments | Future bookings only | Every booking present, with the right doctor and time |
| Documents (scans, referral letters, lab reports, MCs) | Attached files | Files open, sit on the right patient, and counts match |
| Audit trail and user history | Archive export | Readable for the retention period |
Two traps recur. First, free text that looks structured: allergies typed into a notes field will not trigger alerts unless someone maps them. Second, codes: diagnosis and drug codes rarely map one-to-one, and anything unmapped should be listed for a decision, not silently dropped.
Your old vendor, your contract and your obligations
Read the exit clauses before you give notice
Your current vendor processes patient data on your behalf, which makes it a data intermediary under the PDPA; the clinic stays responsible for that data. Before serving notice, check the contract for:
- Notice period and end date, so you neither pay for two systems longer than planned nor lose access before the new one is live.
- Export scope and format: all clinical, financial and document data in a documented format with a data dictionary, not PDFs of screens.
- Export fees and turnaround, including a second, final delta export at cutover.
- Read-only access after termination, and for how long.
- Return and deletion: written confirmation that the vendor has deleted its copies, including backups, once your export is verified.
- Cooperation: whether the vendor will answer the new vendor’s questions about its data structures.
If the contract is silent, ask in writing early. PDPC’s guide on data protection clauses for agreements covers return and deletion of personal data and is a useful reference when negotiating.
Records you must keep regardless
MOH’s licence conditions require HCSA licensees to keep electronic patient health records for the patient’s lifetime plus 6 years, paper outpatient records for 6 years from the last consultation, and high-risk cases for at least 15 years. Scanned paper counts as electronic. Switching software does not reset these duties. Anything you choose not to migrate, such as very old visits or legacy attachments, needs an archive you can still open, search and print years from now, with access controlled like the live system. Our PDPA checklist for clinics covers retention and disposal.
NEHR, Singpass and the other connections
Your clinic system talks to more than your staff. Each outside connection needs a plan so it works on day one.
- NEHR. The Health Information Act, passed by Parliament on 12 January 2026, makes NEHR contribution compulsory in phases; healthinfo.gov.sg lists general practitioners from September 2027 and specialist outpatient clinics from September 2028. Healthier SG clinics must already use a compatible system and keep contributing. Ask the new vendor to show its standing under Synapxe’s SmartCMS certification, and agree how submissions pending in the old system will be completed. More in NEHR contribution for private clinics.
- Singpass and Myinfo. If patients register with Singpass today, confirm the new system supports it and what setup is needed before go-live, so the front desk is not back to typing details.
- Laboratories and imaging. Order and result interfaces are set up per provider, and results still in transit at cutover need an owner.
- Insurers and TPAs. Portal access usually belongs to the clinic, but claim templates and corporate billing rules must be rebuilt.
- Government scheme claims. Decide how claims already submitted from the old system will be tracked through to payment.
- WhatsApp and SMS. Moving the clinic number to a new messaging provider can interrupt reminders. Schedule it, and carry consent and opt-out flags across.
- Payment terminals and accounting exports, tested with a real transaction.
Parallel run or hard cutover, and a week-by-week plan
A parallel run means entering every visit in both systems for a while. It sounds safe, but in a busy clinic it doubles front-desk work, and the two systems drift apart within days. Most single-site clinics do better with a hard cutover backed by a checked trial copy and a final delta import.
| Parallel run | Hard cutover with trial copy | |
|---|---|---|
| How it works | Both systems live for days or weeks | Old system goes read-only at close; new one is live next morning |
| Staff effort | Double entry throughout | Concentrated in rehearsal and the first week |
| Main risk | Records diverge; staff drift back to the old system | Issues surface on day one |
| Suits | Complex groups or unusually messy data | Most single-site clinics with a clean trial load |
The timeline is illustrative for a single-site clinic moving from one system. Large archives, several sites or a slow export will stretch it.
| Week | Work | Done when |
|---|---|---|
| 1–2 | Contract review; request a full sample export; list data and connections | Sample export received and readable |
| 3–4 | Mapping; first trial load; users, roles, fee schedules and drug list set up | Staff can log into the trial copy |
| 5 | Reconciliation: counts, balances, allergies, doctors’ spot-checks | Discrepancies resolved or accepted in writing |
| 6 | Second trial load; connections tested; training by role | Every staff member has had a practice session |
| 7 | Rehearsal of a full clinic day; go-live checklist signed off | Go or no-go decision made |
| 8 | Final delta export and import; go-live | First day completed |
| 9–12 | Close support; first-month checks | Month-end closed in the new system |
Training
Train by role, not by feature tour: front desk on registration, queue and billing; nurses on vitals and dispensing; doctors on notes, prescribing and referrals; the manager on reports and day-end closing. Use the trial copy with your own patients’ data so staff recognise what they see, and name one person per role as the first stop for questions in week one.
Go-live day and the first month
Go-live day checklist
- The evening before: old system set to read-only after the last patient; final delta export taken and imported.
- Before opening: patient counts, today’s appointments and outstanding balances reconciled; opening stock confirmed.
- Every staff member logs in; printers, label printers, card terminals and scanners tested.
- First patients: registration, consultation, prescription, dispensing, payment and receipt run end to end, with a doctor checking the note and prescription.
- Connections: a test NEHR submission, a Singpass registration and a lab order confirmed working.
- Close: day-end closing done and cash reconciled.
- Issues logged in one shared list with an owner for each, not scattered across chat messages.
First-month checks
- Week 1: review the issue list daily with the vendor; confirm allergy alerts fire on migrated patients.
- Week 2: compare visit counts and revenue with a comparable period; unexplained drops often mean billing items were not set up.
- Week 3: confirm NEHR submissions are accepted, not just sent, and that rejections are fixed.
- Week 4: close the month; reconcile receivables and claims against the old system’s final balances; remove test logins.
- Then: confirm the archive of the old system opens, and only then ask the old vendor for written confirmation of deletion.
Frequently asked questions
How long does it take to switch clinic management system?
It depends mostly on how quickly the old vendor delivers a usable export and how clean the data is. The illustrative plan here runs about eight weeks for a single-site clinic; groups and large archives take longer. Loading data is quick; checking it is what takes time.
Will we lose our old patient records when we change systems?
Not if you plan for it. Migrate what the new system must act on as structured data, attach documents, and keep a readable archive of the rest. MOH requires electronic records to be kept for the patient’s lifetime plus 6 years, whichever system they live in.
What if our old vendor will not give us our data?
Check the contract’s termination and data-return clauses, then make a written request stating the scope and format you need. Under the PDPA the clinic stays responsible for its patients’ data and the vendor processes it on your behalf. If the contract is unhelpful, take legal advice before your notice period starts.
Do we need to tell patients we are changing systems?
The purposes for which you hold patient data usually do not change, so fresh consent is generally not needed. Update your privacy notice if the vendor, hosting location or messaging number changes, and tell patients if reminders will arrive from a different number.
Should we run the old and new systems in parallel?
Usually only briefly, if at all. Double entry is error-prone in a busy clinic. A reconciled trial copy, then a hard cutover with a final delta import, gives most of the safety with less risk of the records diverging.
Will our NEHR submissions be interrupted?
They should not be if you plan for it. Agree with both vendors how pending submissions from the old system will be completed, test a submission from the new system before go-live, and check in the first weeks that submissions are accepted.
Sources
- MOH Circular 85/2022 — Licence Conditions on the Retention Periods of Patient Health Records
- PDPC — Advisory Guidelines for the Healthcare Sector (revised 20 September 2023)
- PDPC — Guide on Data Protection Clauses for Agreements Relating to the Processing of Personal Data
- MOH — Overview of the Health Information Act (healthinfo.gov.sg)
- Synapxe — SmartCMS Programme
- Primary Care Pages — Healthier SG requirements for clinics
Primary sources checked on the date above. Schemes and requirements change — always confirm against the latest official notice.
This article is general information for clinic operators, not legal, regulatory or financial advice.