Orbit / Clinical

Coming soon · In development

More time for the patient.
More context for their care.

Orbit Clinical is a planned set of tools for Australian healthcare. Patients prepare for their appointment, GPs get clearer notes and a map of the visit, and both choose what gets shared.

1 · Patient Assistant

“I’ve had a dry cough for about a week.”

Any fever or chills? Does lying flat make it worse?

Symptom summary ready
The patient approves before anything is sent
2 · Clinical Scribe Flags what hasn’t been covered yet

Three tools. One connected visit.

Orbit Clinical is being designed around a simple idea: the patient and the GP each see what matters, and neither loses control of their information.

Planned

Patient Assistant

Asks the follow-up questions a clinician would, organises the answers into a clear summary and points to emergency help when symptoms sound urgent. It doesn’t diagnose. The patient reviews the summary and decides whether to send it to their GP.

Planned · First priority

Clinical Scribe

With the patient’s consent, turns the consultation into a draft note and a mind map of the visit, including what hasn’t been covered yet. The GP checks, edits and approves everything. It can be tested against the real conversation, which is why it comes first.

Planned

Connected care

The GP chooses which reviewed notes or instructions to share back. The patient can then ask questions in everyday language and get answers drawn from that shared information, with the source shown.

Concept preview

See a visit from both sides in under 40 seconds.

A scripted walkthrough of the planned experience, from a patient preparing at home to a GP reviewing the visit. Tap a moment to jump to it.

Fictional example and scripted preview with no audio. It doesn’t record anyone, give advice or send anything, and details may change before release.

Before, during and after the appointment.

Choose a moment to see how it could work. These are scripted concept previews using fictional information. They don’t record audio, generate advice or send reports.

Planned · Clinical Scribe

The conversation becomes a draft. The GP makes it final.

With the patient’s consent, the GP would start transcription on their computer. Orbit would turn the consultation into structured notes for the GP to check, edit and approve, and lay the visit out as a mind map so nothing important is easy to overlook.

The local scribe is being designed so consultation audio, transcripts and draft notes stay on the GP’s computer. No cloud upload would be needed for that workflow. The device requirements and offline behaviour still need testing.

Sharing a reviewed summary with a patient would be a separate choice. Local transcription would not automatically send anything to Orbit or a practice inbox.

Orbit Clinical ScribeConcept preview
On this computer · Local processing planned

Consultation transcript

Patient “The headaches started three days ago. I notice them more after work.”

GP “I’ll check the consultation note before sharing a summary with you.”

Draft consultation note

Patient-reported concern
Headaches starting three days ago, more noticeable after work.
Examination and assessment
Not recorded in this excerpt. GP to complete.
Documentation
GP to review the note before sharing a summary.
Awaiting GP review

Visit mind map

Fictional example. A draft for the GP to verify.

Designed to keep people in charge.

Healthcare needs more care than most software. These are the principles Orbit Clinical is being designed around, and what the clinical testing will check.

Nothing is shared without a yes

Patients approve every report before it’s sent, and choose the recipient. GPs choose what goes back.

The GP signs off

Every note is a draft until the GP checks, edits and approves it. The GP stays responsible for the record.

Urgent symptoms go to help

The patient assistant is designed to point to emergency help, such as 000, when symptoms sound urgent.

No diagnoses

It organises information and explains. It doesn’t diagnose, prescribe or change treatment. Those stay with the clinician.

Local processing planned

The scribe is being designed to keep consultation audio, transcripts and notes on the GP’s computer. This still needs testing.

Clearly labelled sources

Patient-reported information is marked as such, and answers show where they came from.

Planned · NovaSoft model development

Australian healthcare, built into the model’s training.

We plan to fine-tune an open-weight model with carefully prepared Australian healthcare information and medically reviewed examples. The aim is a NovaSoft-trained model that understands local terminology, GP documentation and Australian care workflows.

It could support a Clinical Assistant for GPs, helping organise information and prepare documentation, alongside a Patient Assistant for appointment preparation and explanations grounded in GP-shared material.

Model selection, dataset permissions, training and clinical evaluation are still ahead. No model training run or clinical validation has been confirmed. Training would use separately approved datasets, not automatically reuse patients’ consultations.

Real progress. A clear path to clinical use.

The patient preparation work has moved beyond an idea. The connected clinical experience above is the next direction.

Built · review only

Built for review

The Orbit Clinical development workspace includes recording and audio import, transcript correction, consultation, SOAP and referral templates, and review before export. Optional cloud transcription and AI drafting require configured, reviewed processing. The separate Orbit Health review build offers patient preparation and local PDFs. Neither is clinically validated for patient care.

Planned

Coming next

Local GP transcription, a NovaSoft-trained Australian healthcare model, an opt-in practice report inbox and patient questions grounded in doctor-shared information. These are planned capabilities, with no release date announced.

Required first

Before clinical release

Independent clinical review, privacy and security checks, consent and sharing controls, and testing of transcription accuracy and local processing. The GP remains responsible for reviewing clinical documentation.

The current Health review build does not include GP transcription, report delivery to practices or doctor-connected question answering. Optional external AI in that build is separately gated; the planned local scribe is a different workflow.