Features

Five modules. Individually functional.

Each module has been demonstrated to a customer at least once. Not the same customer, and not the same month, but at least once. What follows is the current state of each, described accurately, which is a first for this page.

Appointments

Status: v2 (superseded by v2-final)

The appointment book is the most complete module in the platform, which is why three teams have rewritten it. All three versions are still deployed. The router decides between them based on a rule nobody has been able to reconstruct.

Drag and drop with ease

Drag any appointment anywhere in the book. It returns to its original slot within thirty seconds, or on refresh, whichever comes first. Staff have adapted by writing the change down first.

Blocked on conflict-resolver (owner unknown)

Flexible appointment types

Mark an appointment urgent, waitlisted or recurring. One of these three has been built. The other two render as a checkbox that does nothing, which testing has confirmed is very fast.

Which one is built varies by tenant

Real-time updates everywhere

Because we're cloud-based, every change appears instantly on your colleague's screen and, in time, on yours — once the sync daemon and the conflict resolver reach an agreement about which of you was right.

Double bookings now arrive in real time

Multi-site scheduling

Manage several locations from one book. Locations are stored as free text, so Hamilton, hamilton and HAMILTON are three sites with separate availability.

Deduplication is a Q4 item

Billing

Status: two gateways, one of them deprecated and load-bearing

Billing was the first module scoped and the last one started. It now calls both the new claim gateway and the legacy one, in that order, and reconciles the answers overnight using a shell script.

Integrated ACC claiming

Claims are lodged through our claiming service, which calls our legacy claiming service, which emails a person. End-to-end turnaround is unchanged from paper, but the email is encrypted.

Person is on leave until March

Colour-coded claim and invoice status

Nine status colours covering four possible states. The legend lives in a PDF on the previous support site, which redirects to this page. Two of the colours are the same amber.

Amber means amber

Email client accounts

Reduce printing by emailing invoices, receipts and statements straight to clients — from a no-reply address, to whichever email address was in the record at time of migration.

Migration was in 2021

End-of-day reconciliation

Reconcile takings against appointments each evening. Where the two disagree, the platform reports both figures and lets your practice manager decide, which we consider a feature of the human-in-the-loop design.

Human is the loop

Clinical

Status: blocked on template-compiler

The clinical module is architecturally the most ambitious, in that it depends on eleven services, four of which have no owner. Clinical notes themselves are stored twice, in two shapes, to keep options open.

Dynamic clinical screen

The patient tree gives you access to every clinical action without leaving today's notes — except the six actions you use daily, which open in a new tab, in the old system.

Old system is decommissioned

Online clinical forms

Send questionnaires ahead of the appointment. Scores return to Ummni-adjacent storage and can be retrieved by raising a support ticket quoting the form's internal UUID.

UUID is not displayed anywhere

Examination templates

General, body, dermatome, myotome and reflex templates all extend the general examination template. The general examination template is scheduled for a later release.

Circular dependency: accepted

Structured notes on completion

Completed examinations generate structured notes automatically. The structure is agreed. The schema is agreed. The two are different agreements.

Reconciliation planned

Management

Status: separate product, separate login, shared brand

Everything a practice needs to run itself, sold as one platform and delivered as four. Single sign-on across them was descoped to protect the release date, which then moved anyway.

Integrated online bookings

Patients book themselves in through our online booking product: a separate subscription, a separate login, separate patient records, and a separate idea of what a week is.

Integration is planned

Patient communications

Personalised SMS and email with automatic reminders and full reply capability. Replies are delivered to a shared queue that no team has claimed ownership of since the reorganisation.

Queue depth: 214,000

Electronic new patient form

Patients prefill their personal and ACC45 details before arriving. Reception retypes them, because the form service and the patient service disagree about what a name is. Double handling is now triple handling, but online.

Net paper saved: some

Staff and roster management

Assign practitioners to rooms, rooms to sites, and sites to entities. The entity model was designed for a large hospital group that did not proceed, and remains mandatory for sole practitioners.

Minimum three entities per practice

Reporting

Status: rewritten as a micro-frontend, twice

Reporting was re-scoped in 2023 to reduce complexity, by moving it into its own frontend framework, its own build pipeline, and its own release train, which departs separately.

Interactive dashboards

Report on what's important to your practice. Click any graph to drill through into a detailed, high-fidelity loading spinner.

The spinner is our fastest component

Natural language reporting

Generate reports by asking a question in plain English. Receive appointment volumes for a clinic in Ballarat. Ask again and receive the same clinic, as a pie chart.

The Ballarat clinic is fictional

Restricted report access

Choose which reports each user can open and limit content to what's relevant to their role. At present everything is restricted, which is the most secure configuration we have ever shipped.

Working as designed

Scheduled exports

Schedule any report to arrive by email each Monday. Reports are generated at 3am against the cube, which refreshes at 4am.

Consistently one week behind

See how these five modules fit together.

They fit together across forty-seven services, three authentication systems and two event buses, neither of which is authoritative.

View the architecture