Admissions and flow, beds, theatre, medication rounds, rostering, monitoring, statutory reporting and revenue — running on the same patient records your clinicians already work in, not a second system bolted alongside.
Every module is enabled per organisation. A hospital opens a command centre; a single clinic never sees any of it.
Lunas · Bayline General Hospital
Watch it work
A shift in the hospital, in two minutes.
The command centre, the bed board, the drug round checked by barcode, theatre and the reports. Narrated, with captions.
Recorded from the Lunas demo, with invented patients.
Command centre
The operational picture, before anyone asks for it.
Each module writes to the same organisation-scoped records, so the command centre reads one live picture rather than reconciling eight of them.
Hospital command centre
One queue across every module, ranked by what will hurt first: a monitoring alert, a blocked bed, a late dose, a revenue exception, an unfilled shift.
Beds and patient flow
Beds. Every bed opens: its ward, its state, who is in it, and the patient’s chart from there.
Medication rounds
Medication rounds. What is due, and the checks to make before each dose, in one line at the top.
Operational brief · generated from live recordsClinicians and accountable managers verify before acting. The brief never initiates a clinical decision on its own.
Product screens from the Lunas demo, with invented patients.
Modules
Eight modules. One record. Turn on what the site actually runs.
Nothing here is a separate product. Each module reads and writes the same patients, staff and audit trail, and each is switched on per organisation and per role.
AF
Admissions & flow
Every patient journey from expected arrival through to completed discharge, with the blockers that are holding each one up.
Collections drafted, validated, approved and submitted, so the reporting obligation is a workflow rather than a spreadsheet.
Validation before approvala collection cannot be submitted until its validation has passedRC
Revenue cycle
Coding, exceptions, claim submission and payment reconciliation, joined to the clinical record the activity came from.
Exceptions surface firstthe queue leads with what is blocking payment, not what is already clean
In practice
Three of them, in the detail that matters.
The rest work the same way: a worklist, a safe transition, and a record of who did what.
Theatre keeps its own running record.
A case carries the checklist, the surgeon and anaesthetist, the planned start and its progression through the list. During the procedure, anyone in the room can write to it.
Each safety check is ticked by name, with the time it was ticked
Checklist completion gates the transition to ready, and ready gates the start
Notes are appended, never overwritten — the record grows rather than being edited
Every note and every status change is written to the append-only audit trail
Theatre · safety checklist
A dose is checked at the bedside, online or off.
The round is a worklist of what is due. Before a dose is given, the allergy and any cross-reaction are on the screen; then the wristband is scanned, then the pack.
A wrong patient is refused, and the screen names both
The pack is matched to the order by medicine, strength and form, with its batch and expiry read from it
A dose already recorded as given can’t be recorded again
The round keeps working offline; doses given offline are sent and checked again when the connection is back
Medication round · scan to give
Rostering that refuses an unsafe assignment.
Coverage is planned week by week or month by month, using the same calendar the clinic uses for appointments. Moving a shift is a first-class action, not a delete and re-create.
Assignment checks active membership, credentials, capabilities and registration
A move is re-validated against approved leave and overlapping shifts before it saves
If the new time conflicts, the move is refused and the roster is left unchanged
Coverage gaps are surfaced on the day they fall, not buried in a list
Rostering · this week
Product screens from the Lunas demo, with invented patients and staff.
Governance
Built so an auditor can follow it.
The same controls that make the clinical record defensible apply to every operational transition.
Organisation-scoped
Every record belongs to one organisation. A request from another organisation cannot read it and cannot change it — it is answered as though the record does not exist, so nothing leaks by its absence.
Role-gated per module
Each module names the roles that may write to it. A clinician, a nurse and an administrator see different actions on the same record, and the check runs on the server rather than in the interface.
Append-only audit trail
Status changes, notes, roster moves and submissions are written to a sequenced audit chain as they happen, recording the actor, the resource and what changed.
Australian-region hostingNonce-based CSPNo advertising or tracking pixelsShort-lived, role-bound sessionsConsent required before transcription
Preview workflows still require site configuration, validation and clinical-governance approval before live use.
Early access
Run Lunas inside the hospital.
Lunas Edge puts Lunas on a tower server on site, so the wards keep working when the connection doesn’t and catch up with the cloud when it’s back. Lunas Edge AI keeps consultation audio in the building.
Hospital deployments start with the modules you actually run, the roles that use them and the reporting you are accountable for. Tell us the shape of the site and we will map it. We onboard each organisation directly, with the privacy, hosting and governance controls agreed before any real record is entered.
