.png)
Research report
AI Does Not Remove the Bottleneck
Find your real workflow constraints before buying AI tools.
Built for the clinician on a twelve-hour shift.
Clinical integration, patient platforms and data work for providers, payers and health-tech teams.
Where we help
The work we are asked to do in healthcare.
01
Integration with what already exists
FHIR R4 where it fits and HL7 v2 where it does not, because both are still in the building.
02
Clinical workflow tooling
Systems designed around what a clinician does in the ninety seconds they have.
03
Patient-facing platforms
Portals and scheduling that people complete without calling reception.
04
Data platforms and reporting
Lineage and access controls that hold up when the information governance team asks.
05
Modernising clinical legacy
Incremental replacement of systems that cannot be switched off for a weekend.
The numbers behind our healthcare work
Interoperability is a solved problem on paper and an unsolved one in every hospital. Standards work; the integration projects that stall do so on the legacy HL7 v2 feed nobody wants to touch and the department that will not change its intake form. We would rather start at that feed than at the API layer, because the API layer is rarely what is broken.
17
where our software is in use
HL7 v2, FHIR R4
what we have connected
12 min per shift
what it gave back
15
years building software people are treated through
Selected work
Engagements in healthcare, described rather than named.
A UK e-prescription startupBuilding an e-prescription platform around trust, access, and scale.Clinic management and electronic prescribing with eIDAS-compliant signatures, and a pharmacy lookup that needs no account at all.16 wksfrom kickoff to a launch-ready platformRead the case
A US healthcare practiceMaking surgery clearance easier to track.Referrals, pre-authorisations and clearances tracked in one place, with a rules engine that decides when a patient is ready.4 wksfrom kickoff to a tool the practice runs on dailyRead the case
A US remote-monitoring healthtechSupporting rehabilitation after dischargeRemote therapeutic monitoring built so the billing qualification cannot be faked, with an AI care plan no patient sees unapproved.15 mina day for a physician to review a full patient panelRead the case
A UK community pharmacy groupAnswering pharmacy calls without adding headcount.An AI phone receptionist covering twenty stores around the clock, each with its own knowledge base and its data walled off from the rest.20 storesanswered around the clock by one AI receptionistRead the caseQuestions we get asked
Have you worked with HL7 and FHIR?
Yes, and the interesting problems are usually in HL7 v2 rather than FHIR. FHIR is pleasant to build against; the feed that actually carries your admissions is often a v2 interface written years ago that nobody wants to touch. We start there, because that is where integration projects stall.
Can you integrate with our EHR?
Usually, and what governs it is the vendor's interface programme and your contract with them rather than the engineering. Epic, Cerner and the rest each have their own route, cost and timeline for third-party access. We establish that early, because it sets the shape of everything downstream.
How do you handle patient data?
As the most sensitive category, with the controls designed in from the first architecture conversation. Encryption at rest and in transit, role-based access, immutable audit logging, and vendor agreements signed before anything touches real records. Where a task can be done without identifiable data, that is the design we propose.
Are you HIPAA compliant?
We build to HIPAA technical safeguards and sign a BAA for engagements handling PHI. We will tell you plainly which certifications we hold and which we do not, because a vague answer here helps nobody through a procurement review.
Can clinicians use it on a ward?
That is the test we design against. Software written for a demo assumes an unhurried user with both hands free, which describes almost nobody on a ward. We watch the work before designing it, and the measure that matters is time given back per shift.
How long does clinical software take to ship?
Longer than the equivalent elsewhere, and the difference is approvals rather than engineering. Information governance, clinical safety review and vendor interface access each take real time. We plan for them from week one, because discovering them at the end is how these projects lose a quarter.
How we deliver it
.png)
.png)
