Patient-facing software with compliance designed in, not bolted on
Clinics run on re-keyed intake forms, phone-tag scheduling and coordination that lives in inboxes — while consent and retention are tracked by folder convention. We build intake platforms, scheduling and compliance-aware data flows for clinic groups and health-tech founders, with consent, retention and access control in the architecture from the first milestone.
Systems we build in healthcare
Operational software around care — intake, scheduling, coordination, data. Each one answers to a metric: intake minutes, no-show rate, admin hours per clinic. A representative list, not a boundary — if the system you need isn't on it, we build that too.
Patient-intake platforms
Digital intake across multi-clinic groups — forms, consent capture and eligibility in one flow, so the front desk stops re-keying PDFs and patients stop filling the same form twice.
Scheduling & capacity
Clinicians, rooms and equipment scheduled in one system — with waitlists, reminders and rescheduling flows that cut the phone-tag and the no-shows it produces.
Compliance-aware data flows
Consent, retention and access control designed in from the first milestone — who can see what, for how long, and with what recorded justification. Not bolted on before go-live.
Clinic operations tools
Referrals, follow-ups, admin queues and approval flows — the coordination work between visits that currently lives in spreadsheets and shared inboxes.
Integrations with clinical systems
We connect to the EHR, practice-management and lab systems you already run — integrate, not replace. Nothing critical switches off until its replacement has proven itself.
Reporting & group oversight
Utilisation, throughput and intake funnels across every clinic in the group — pulled from the systems of record, not assembled by hand at month-end.
Where clinic groups lose hours — and patients
The diagnosis phase measures these in your clinics specifically. These are the patterns we find most often.
Paper and PDF intake
Front-desk staff re-keying forms patients already filled in — per visit, per clinic. Multiply by a clinic group and it's full-time headcount spent on transcription.
Phone-tag scheduling
Booking, confirming and rescheduling by phone produces no-shows and idle clinician hours — the most expensive empty slots in the building.
Consent handled ad hoc
Consent and retention tracked in filing cabinets and folder conventions. It mostly works — until someone asks you to prove it, per patient, per purpose.
Coordination in inboxes
Referrals and follow-ups living in email means patients fall through between visits — and nobody can see where.
How we work in healthcare
The same four phases as every engagement — with your counsel or DPO in the loop from the architecture onwards. You can stop after any phase and keep everything produced.
See the full process →- 1
We map how patients, data and staff actually move through your clinics — where intake stalls, where consent lives, where coordination breaks. If software isn't the answer, we say so.
- 2
Scope, milestones, cost — and the metric the system answers to: intake minutes, no-show rate, admin hours per clinic. The estimate holds; overruns are ours.
- 3
Working software from week two, with consent, retention and access control in the architecture from the first milestone — reviewed with your counsel or DPO, not retrofitted for go-live.
- 4
Monitoring, documentation and a 90-day warranty ship with the system. Then a retainer, or a clean handover to your team — including hiring help.
A clinical founder with distribution and no product — built under a hybrid equity deal
Reduced price plus equity. We built the patient-intake platform; she filled it with clinics. The company has since raised institutional funding — with SigmaJunction still on the cap table.
Read the case study →Common questions from healthcare teams
How do you handle patient data?
As the most constrained thing in the system. Access control mirrors clinical roles, every access is logged, retention rules are enforced by the system rather than by memory, and data stays inside your boundary. These are architecture decisions made in milestone one — not a hardening pass at the end.
Are you HIPAA / GDPR certified?
Honest answer: certification applies to organisations and products, and your obligations are defined by your counsel or DPO — we're engineers, not a law firm. What we do is design the flows to the requirements they set — consent, retention, access, auditability — and implement them verifiably, in writing.
Can you work with our existing EHR and clinic systems?
Yes — that's the default. We build around the EHR, practice-management and lab systems you already run, integrating through their supported surfaces. Rip-and-replace is almost never the right first move, and we'll tell you if we think it is.
I'm a clinical founder with distribution but no product. Can we work together?
That's exactly the profile behind our patient-intake case study — built under a hybrid equity deal: reduced price plus equity. If you have real traction and no product yet, read how partnership works and pitch us.
How long does a patient-facing platform take?
A focused v1 usually ships in 2–3 months across 3–4 milestones, with working software in your hands from week two. Compliance review runs alongside the build, not after it — so go-live isn't waiting on a retrofit.
Do you build diagnostic AI or medical devices?
No — we build the operational software around care: intake, scheduling, coordination, data flows. If your project is a regulated medical device or diagnostic algorithm, the diagnosis will say so plainly, and we'll point you at the regulatory path instead of building around it.
Three ways to engage us
For clinical founders with traction and no product, the partnership model is often the right door.
Running clinics on spreadsheets — or founding something better?
The diagnosis session is free, whether you run a clinic group or you're pitching a partnership.