Messages built from the encounter
Diagnoses, medication coded to the national drug dictionary, allergies and immunisation are taken from the record you already wrote. Nothing is typed twice.
Integrations
The connections are the product.
A Singapore clinic system is judged on what it does with the outside world: the national record, the subsidy schemes, the laboratory, the insurer. Anyone can draw those as logos on a slide. Below is what each one actually does, including how it fails.
- NEHR128 submitted · 2 held
- Singpass / Myinfoconnected
- Innoquest14 orders · 9 results
- DA Vantage6 claims packaged
- WhatsApp41 messages
- PayNowS$3,481.20 collected
Two NEHR submissions are held. Each opens in the worklist; none is buried in an email.
National record
NEHR
The integration that decides whether a clinic system is serious.
Every submission is a tracked task
Each submission keeps what was sent and what came back. Held, failed and accepted are lists you can open, not something you guess from silence.
Rectification for what comes back rejected
Failed-message reports are imported and matched to the encounters that produced them; corrected messages are regenerated and held for review before anything is resent.
Reconciliation files
The submission and reconciliation files are produced in the required formats, with the audit trail attached.
One login into the national portal
Staff move from ClinicPlus into the national portal through Corppass without a second username and password.
A held queue, on purpose
Submissions can be held for release rather than fired automatically, which is what you want in the first month after go-live and whenever the national format changes.
Identity
Singpass and Myinfo
Registration starts from verified particulars instead of a hurried retype at the counter.
Patient details from the source
Registration pulls verified particulars instead of asking the front desk to key an NRIC correctly under pressure.
Identifier types done right
Pink IC, Blue IC, FIN, passport and foreign travel documents are distinct types per the national standard — which is what keeps the same person matched across systems.
Only what you need, with consent
The patient approves the request in Singpass, the consent is recorded, and the clinic receives only the particulars registration needs.
Falls back to manual
When Myinfo is unavailable, registration continues by hand and reconciles later. An outage upstream does not stop your clinic.
Subsidy · Coming soon
CHAS and CDMP: coming soon
CHAS and CDMP support is in development and not yet available. This is what it is being built to do.
Eligibility on the patient record
Scheme status will be part of the patient, so it drives billing rather than being remembered at the counter.
Applied at invoice time
The subsidised and patient portions will be lines on the same invoice, which keeps the receipt, the report and the claim consistent.
Chronic cycles tracked
CDMP follow-up cycles will be modelled, so the recall list follows the scheme.
Claim-ready reporting
Subsidy statements will be generated from invoice lines, so what you report is what you billed.
Diagnostics
Laboratories
Orders go out from the consultation and results come back to the doctor who asked.
A second lab is a setup job
Every laboratory connection is built on the same foundation, so adding another provider is a scoped piece of work, not a new integration project.
Innoquest Diagnostics
Live today: orders go out, results come back, and sample labels print at the point of collection.
Results land on the order
Returned results attach to the requisition and the patient, and notify the ordering doctor.
A slow lab never freezes the consultation
Incoming results wait in a queue and are retried if needed, so a slow provider never holds up the doctor.
Payers
Insurers, TPAs and corporate accounts
Claims leave in the shape each payer expects, and the money is matched back when it arrives.
Claim packaging
Diagnosis, procedure and dispensing detail assembled into the payer’s expected claim shape.
Portal automation where there is no API
Where a payer only offers a portal, submission is driven through it rather than left as a manual re-key.
Remittance matched back
Payments are reconciled against the claims they settle, and shortfalls stay visible.
Corporate statements
Sponsoring organisations receive consolidated statements generated from the visits themselves.
Communication and money
WhatsApp, payment and notifications
The channels patients and money actually move through, recorded against the visit.
WhatsApp Business Cloud API
Official API rather than an unofficial bridge — inbound to a shared inbox, outbound as approved templates, delivery tracked per recipient.
PayNow and card
Online and counter payment recorded against the invoice, with reconciliation back to the day-end totals.
Email and browser push
Email for patients and optional browser notifications for staff. Neither is required, and nothing breaks if you leave them off.
Your own integrations
A documented API with approved app access, so a clinic group can connect its own tools without waiting for us to build a one-off.
Coming from elsewhere
Migration from your current system
Your history comes with you, you check it before go-live, and there is a documented way out.
Historical import
Patients, visits, diagnoses, prescriptions, invoices and inventory imported from the incumbent system — including archives going back more than a decade.
Reconciled, then cut over
Imported records are counted and compared against the source, with gaps listed rather than glossed over.
A trial copy first
You log in and check your own data before anything becomes live.
And an exit, documented
Full export of the clinical and financial record in open formats with a data dictionary — because a system you cannot take your data out of is a system that locks you in.
Questions
Integration questions
What happens when NEHR is down?
Submissions queue and retry. The consultation, the bill and the dispensing are unaffected, and the backlog drains when the service returns.
Can you connect a laboratory you do not support yet?
Yes. Providers are implemented as adapters against a shared kernel, which is a scoped piece of work rather than a rewrite.
Do we get API access?
Yes — a typed API with OAuth 2.0 authorised apps, so your own tools can read and write with scoped permissions and a full audit trail.
Next step
See it against your own clinic day.
Thirty minutes, screen shared, using your workflow — your busiest hour, your payer mix, your claim types. We will tell you plainly if we are the wrong fit.
No slide deck. No obligation.