Insights · 20 articles · 5 topics

How this softwareactually gets built.

Notes from the people building hospital platforms, clinical AI and the integrations between them. Written for the engineers, clinicians and security teams who have to live with the result.

No thought-leadership theatre. What we decided, why, and what we would do differently.

FeaturedInteroperabilityOne record, twelve systems: what a patient journey really touchesA single visit passes through registration, the ward, the lab, pharmacy, billing and discharge each often its own system. We walk through where the continuous record breaks today, and the design decisions in Zypocare One that keep it whole from access to follow-up.Zyposoft Engineering21 Jul 20265 min readRead article

Reading

Latest articles.

Newest first. Filter by what you work on.

InteroperabilityThe identity problem nobody budgets forMatching a person to their record is the hardest problem in health integration and is almost always estimated as a checkbox. Duplicates, merges, near-matches, and why the auto-match threshold is a clinical decision rather than a technical one.10 Jul 20263 min read InteroperabilityHL7 and FHIR in practice: connecting the systems you are keepingNobody replaces everything at once. A field guide to the message types, mapping traps and versioning realities of wiring a new platform into the EMR, LIS and PACS a hospital already runs without a rip-and-replace.7 Jul 20263 min read InteroperabilityYour integration layer is a product, not a projectInterfaces get funded as one-off builds and then run for a decade with no owner. What changes when the integration layer is treated as something with a roadmap, a support model and a person whose name is on it.5 Jun 20263 min read

Stay in the loop

Get new writing when it lands.

Occasional, technical, and never a newsletter for the sake of one. We will only write when we have something worth your time.

Email us to subscribeNew writing, now and then Talk to us