Industry
Healthcare software.
Healthcare software is judged on what it can prove after the fact. Every read of a patient record is potentially discoverable, interoperability is mandated rather than optional, and downtime has clinical consequences. That shapes architecture from the first decision onward.
What shapes the architecture
Constraints that are specific to this sector.
These are the things that would be wrong or meaningless if written about a different industry. They are design inputs, not compliance paperwork added at the end.
- 01
Audit trails are append-only
Access logging has to record who read what and when, and it cannot be editable by the application that writes it. That usually means an append-only store separate from the operational database.
- 02
Interoperability is mandated
HL7 v2 for the installed base, FHIR R4 for anything new. Both need a translation layer, because neither maps cleanly onto a domain model designed for your own product.
- 03
Consent is a data model, not a checkbox
Who may see which record, for how long, and delegated to whom — this belongs in the schema. Retrofitting it later touches every query in the system.
- 04
Degraded mode has to be designed
A clinician cannot wait for a service to recover. Read paths need to keep working when write paths are down, which is an explicit architectural choice.
Typical work in healthcare.
- Patient portals and appointment scheduling
- EHR and EMR integration layers
- Telehealth and remote consultation
- Clinical workflow and triage tooling
- Claims and billing pipelines
- Diagnostic and imaging data handling
What it has to talk to.
- HL7 v2
- FHIR R4
- DICOM
- SMART on FHIR
- ABDM / ABHA
Integration surfaces are where most sector projects actually fail. We treat each one as a boundary with its own translation layer, rather than letting an external format leak into the domain model.
Reference build
How we'd build it, decisions included.
An illustrative architecture for this sector — the problem, the approach, and the alternatives we rejected with reasons.
Other sectors
Explore the rest.
Start here
Tell us the problem.
We'll be honest about the fit.
A first conversation costs nothing and is useful even if you go elsewhere — you'll leave with an architecture opinion and a realistic sense of scope.
- Reply within 24 hours
- No sales sequence