A practice that runs itself.
Practice management built for the reality of African medical practice, not a Western EMR ported to a new timezone. Scheduling, notes, billing and medical aid claims run as one loop. The doctor confirms. The system executes.
- Model
- Doctor confirms
- Built for
- Practices of one to five
- First market
- South Africa
- Principle
- The doctor confirms
In most African practices, the doctor is also the admin.
Loop assumes this from the start. One person wearing every hat is the default case, not the edge case — because in practices of one to five doctors, that is who is doing the work.
- 01
The clinician
Diagnoses, treats, refers — the work only a doctor can do.
- 02
The admin
Schedules patients, manages the diary, chases no-shows.
- 03
The billing clerk
Generates invoices, submits medical aid claims, reconciles payments.
- 04
The front desk
Answers WhatsApp messages, sends reminders, follows up results.
Loop’s whole purpose is to take the other three hats off. The doctor keeps the one that matters.
The doctor confirms. The system executes.
Six capabilities, none of them built. Everything below describes what Loop is being designed to do.
- 01
Scheduling
Designed to book, fill, and rearrange the diary, and to handle reminders and no-show recovery without being asked.
- 02
Clinical documentation
Designed to draft a structured note from the consultation in the background, for the doctor to review and sign off.
- 03
Billing & medical aid claims
Designed to generate the invoice, code the claim, submit it, and track it until the money lands.
- 04
Patient communication
Designed to answer routine queries, send follow-ups and results in the patient’s language, and escalate what matters to a person.
- 05
Compliance
Designed to keep POPIA consents and practice documentation current, and to tell the practice what its HPCSA obligations need next.
- 06 · The boundary
The clinical judgement stays human
Loop never diagnoses, never prescribes, never decides. It prepares — the doctor confirms.
Not a Western EMR ported to a new timezone.
| The reality | How the design answers it |
|---|---|
| Mixed cash & medical aid | Most African practices bill both, so the design treats one billing flow that covers cash patients and medical aid claims as the starting point rather than an add-on. No scheme integrations are built yet. |
| Multilingual patients | Reminders, instructions, and follow-ups should go out in the language the patient actually speaks. We are starting with isiZulu, isiXhosa, Afrikaans, and English. |
| Intermittent connectivity | Offline-first, not offline-tolerant. The consulting room should keep working when the connection drops, and sync when it returns. |
| Practices of one to five | No IT department, no practice manager required. Loop is sized for the solo specialist and the small group — not the hospital group. |
Today’s registrars, tomorrow’s practices.
The registrar learning on Lorraine Learn today is the specialist running their practice on Loop in three to five years. Loop follows the same philosophy: the system carries the load — at every stage of a career.
- Shaped by interviews with practising doctors and practice managers in South Africa
- Reviewed with the registrars already studying on Lorraine Learn
- Clinical judgement always stays with the doctor
Shaped by the practices already running it.
Loop is shaped by interviews with practising doctors and practice managers in South Africa, and it is on its way to Uganda. Leave your email and we will write when the beta opens in your market.
- 01Onboarding walked through with the team, not a help centre
- 02A direct line into what we build next
- 03Founding-practice pricing, held for as long as you stay
Waitlist
Loop is coming to Uganda
Loop is in beta with founding practices in South Africa. Leave your email and we will write when it opens in your market.