01 / 03
HL7 routing the bed manager actually trusts.
Inside an NHS environment, we delivered patient flow integration over HL7 v2 — messages routed, retried, never lost, with the trail visible to the people on the ward.
01 / Sector
Government & public sector
Software for the public sector — built and supported inside NHS environments, with clinical safety and information governance designed in.
02 / What we know
What we know about government & public sector
Most of the team's public-sector work has been inside NHS environments — patient flow, bed management, HL7 messaging, integration between clinical systems. We understand the constraints: clinical safety, information governance and legacy systems that cannot simply be ripped out.
Public-sector software has stakes that don't apply elsewhere. A bed-management screen is in front of someone making a clinical decision at the end of a long shift. A failed HL7 message is a patient whose admission isn't on the right ward. We design with those stakes in mind, and we test against them.
Most of the work is integration. Modern FHIR APIs in front of older HL7 v2 estates, Mirth Connect routing between systems that were never meant to talk, SOAP endpoints maintained because the system on the other end still needs them. We've kept legacy applications alive while moving the workflow forward — without disrupting live use.
03 / Technologies
Technologies we work with.
HL7 v2 · FHIR · Mirth Connect · SOAP · SQL Server · VB.NET · React · IIS · clinical safety standards · information governance
04 / What we've built
What we've built in this sector.
Anonymised, because we have to be. The kind of system, for the kind of business, and what it had to do.
-
-
02 / 03
A clinical legacy application, modernised in place.
For a hospital running an older VB.NET system, we moved the front end onto a modern stack one workflow at a time — clinical users kept working while the underlying code was carried forward.
-
03 / 03
A FHIR layer over a long-standing HL7 estate.
For a clinical integration team, we put a FHIR API in front of an existing HL7 v2 stack — modern downstream consumers without unsettling the upstream systems that already worked.
05 / Questions
Common questions, answered plainly.
- 01 Do you work with NHS environments?
- Yes — the team has built and supported patient flow and bed management software in NHS hospital settings.
- 02 What integration standards do you work with?
- HL7 v2, FHIR, SOAP and REST. We've used Mirth Connect for clinical message routing.
- 03 Can you modernise an existing legacy clinical system?
- Yes. We've moved old VB.NET and classic ASP clinical applications onto modern stacks without disrupting live use.
- 04 How do you handle clinical safety and information governance?
- We treat clinical safety and information governance as design constraints from day one — not sign-off steps at the end. The work is done against the relevant safety standards from the first sprint.
- 05 Do you work outside NHS settings?
- The team's deepest public-sector experience is inside NHS environments. We work with other public-sector bodies on the same basis — workflow software where the workflow has stakes, with audit and governance designed in.
- 06 Are you UK-based?
- Yes, we operate from Scotland.