Use cases
Built inside real practices.
These are anonymised snapshots of how Halo fits into teams that already have habits, drives, and pressure. Same goal everywhere: less friction between clinical work and the systems around it.
Rhythm clinic, high documentation load
Cape Town AF centre
The situation
The centre runs a busy atrial fibrillation service. Notes and follow up documents piled up between procedures and clinics, and staff were retyping the same details across systems.
What Halo did
Halo connected a secure WhatsApp based capture path to their documentation templates. Clinicians brief the work in natural language on the move; the system drafts the right document type for review before it is filed.
What changed
Documentation turnaround tightened without adding another desktop app. Admin time dropped on the busiest lists, and the medicolegal trail stays consistent because nothing is copied blindly.
- Voice first capture that matches how the team already messages
- Structured drafts that reduce retyping between systems
- Faster turnaround on letters and summaries on busy days
Renal outpatient letters, Google Workspace
Trevor, nephrologist
The situation
Trevor was producing strong letters but losing minutes to saving, naming, and filing. The same letter often needed to exist in more than one place before the week ended.
What Halo did
Halo generates each letter on his practice letterhead, then routes the PDF into the patient folder structure he already uses in Google Drive. The workflow follows his existing mental model: one patient, one folder, one source of truth beside the EHR.
What changed
Filing stopped being a separate job at the end of the day. Staff spend less time hunting for the right Drive path, and Trevor trusts that what he signed off is what the folder shows.
- Letterhead and layout applied automatically on every document
- Google Drive folders stay aligned with the live patient list
- Fits the way Trevor already works, without replacing his EHR
Theatre lists, SharePoint, investigations
Mo, surgeon
The situation
Mo needed operative documentation and outpatient letters in one place with imaging and labs, not spread across inboxes and shared links.
What Halo did
Halo prepares Mo's documents from structured templates, then places them into the correct SharePoint patient workspace. Lab and radiology results that arrive electronically are pulled into the same location so rounds and follow up start from a single view.
What changed
The patient file became easier to read before clinic and before theatre. Less time chasing attachments, fewer gaps when the team hands over.
- Documents generated to template, then filed to the right patient space
- Labs and radiology routed into the same SharePoint record
- One coherent file for theatre, clinic, and admin handoffs
Specialist practice, referrals and correspondence
Elmin
The situation
Elmin's practice was growing fast enough that intake became noisy. Referrals arrived from several channels, and filing notes into the right patient record was slowing everyone down.
What Halo did
Halo routes Elmin's clinical notes into the correct patient record by default, and runs a referral handling layer that classifies and queues what arrived overnight. Incoming PDFs and letters are matched to patients before they hit the shared inbox.
What changed
The front desk spends less time asking which patient a document belongs to. Clinical staff open the chart and see correspondence already in place. Intake and documentation feel like one system instead of two jobs.
- Notes and correspondence filed to the right patient automatically
- Referrals fielded and prioritised without losing traceability
- Incoming documents attached before the clinic day starts
Talk to Halo
Each practice is different.
Find out what will suit yours today. Book a short call and we will map where custom software actually helps.
Book a free strategy call