Trust

What your governance committee will want to know

The questions every doctor and every clinic board has asked us, with the answers as they stand in the build. Full architecture, access-control, recovery-test and audit-log documentation is available on request.

Who is accountable for what MAISSY sends?

A person, every time. Nothing with financial consequence leaves the clinic without a human pressing the button. Every clinical statement is the doctor's own, approved before it is used. Every figure traces to its source, its rule version and its human approver, so accountability is recorded, not assumed.

Does it touch the national health record?

No. Ever. MAISSY has no connection to the national record. Clinical facts come from your own practice system, under your authority, and your certified CMS stays the system of record.

Where does patient data live, and who can reach it?

In Singapore, and only by role. The environment that runs MAISSY sits in Singapore and clinic and patient data stays inside that boundary. Access is granted by role, protected by multi-factor sign-in and short-lived tokens; when someone leaves, their access is gone within 24 hours. Data is encrypted with AES-256 at rest with key rotation and TLS on every call, and no patient data is held at rest unless the task actually requires it. Traffic passes a web application firewall and an API gateway that checks every token.

How do we audit a figure on a claim six months later?

Trace it end to end. Immutable audit logs record who did what and when, so any claim, booking or payment can be followed from the note to the payer field. Every rule change is versioned, so you can show what the system was doing on any past date.

What happens to payer portal logins?

They stay yours. Portal credentials where needed are kept secure, and automation stops cleanly at every login and 2FA wall for a person to clear. Nothing is filled silently or in the background; fields are filled only when confirmed.

What if it goes down?

Back in minutes, not days. Recovery is tested rather than assumed: the last exercise restored the full platform in under 9 minutes against a 30-minute target. Because your CMS remains the system of record, the clinic keeps running on it throughout.

What do we get for our AI-governance file?

The pack ships with the product. A registry entry, a validation record and staff training, aligned to Singapore's 2026 healthcare AI guidance on human oversight. Your clinic stays the data owner.

Singapore hostingPDPACCoP 2.0 alignmentCyber Essentials certificationAES-256 at rest · TLS in transit
Who does what

MAISSY drafts. A person approves. Your CMS stays the record.

The division of labour is fixed in the architecture, not in a policy document. Singapore's 2026 healthcare AI guidance requires human oversight; MAISSY was designed that way from the first frame.

MAISSY

Does the typing and the watching

  • Checks eligibility and quotes limits at the counter.
  • Drafts the invoice from the approved note and prices it against the live contract.
  • Navigates the payer portal and fills the form, field by field, with an audit of each transformation.
  • Watches every submission and ranks what is stuck by dollar, with the fix prepared.
  • Stops cleanly at every login and 2FA wall.
Your team

Approves everything that leaves the building

  • The doctor approves every clinical statement before it is used.
  • The nurse reviews the draft and presses submit on the payer's form.
  • The practice manager works the queue and clears authentication walls.
  • How much MAISSY does on its own is set per step and per clinic, and raised only on measured evidence.
Your systems

Keep their roles

  • Your certified CMS stays the system of record. MAISSY sits above it, never in place of it.
  • No connection to the national record. Ever. Clinical facts come from your own system, under your authority.
  • Payer portals are used as you already use them, with credentials kept secure.
  • Bank and payment feeds are read for matching, not moved.

Need the documentation pack?

Architecture, access control, recovery tests and audit logs, on request.

Request documentation