Four Blocks. The foundation for harmonised, trusted, actionable data.
Every healthcare system speaks its own dialect of data and has gaps in workflow. Our components connect workflow and data into one unified experience working with the system as it is, not what it “should be”, to make existing solutions more valuable.
We call the components Blocks. Together they are a semantic execution capability that turns a fragmented set of point solutions into one harmonised, trusted and actionable system.
- UX Block. The interaction with patients, admins and clinicians like forms, graphs, image viewers, AI output and worklists. It fills gaps in a patient, admin and clinician workflow, wherever a step is missing.
- Mapping Block. Translates clinical data between formats into open data standards. Mapping time drops from days to seconds. We can map both the syntactic and the semantic component of the data so the data is transferable and meaningful.
- Data Block. The underlying pieces of data that create a patient’s record. These Blocks are immutable, allowing clinicians, patients and admins to trace the origin of data and update evolving or incorrect information. This data is structured and coded at the most granular level meaning there is no data lost across systems.
- Orchestration Block. An AI-assisted, no-code rules engine that coordinates workflow actions and data actions across disconnected clinical systems. It connects UX Blocks and other applications into one unbroken patient journey.
One stack.
Four layers.
Where our Blocks fit in the healthcare infrastructure, and what each layer is responsible for.
Application layer. What staff and patients see and do. UX Blocks provide the screens, forms and worklists. Every entry is structured as it’s recorded.
Agentic layer. An additional layer, built once data is structured. Agents can securely look up and act on a patient’s record across systems.
Semantic interoperability layer. Where clinical data is translated and held. Mapping Blocks resolve differences in format. Data Blocks carry the shared unit of clinical meaning.
Data layer. A shared, open clinical data repository, owned by the organisation. It holds the single canonical record that every layer reads from and writes back to.
layer
interoperability
layer
layer
layer
How our Blocks enable digital and AI transformation
From fragmented systems….
Every application and dataset in a typical healthcare estate is in its own silo. Data, logic and interface are bundled together, none of it shared with the next system. Every new system adds cost rather than reducing it. Integrations don’t scale, they compound. Contracts become harder to unwind, and vendor lock-in deepens with each addition. Modern tools, including AI, need consistent and accessible data. Locked in silos, even capable tools can’t work to full effect.
…. to one AI-ready foundation.
The fix is a shared open data standards layer, owned by the organisation, that every application builds on rather than replaces. Our Blocks connect this layer to existing systems. Nothing needs ripping out. UX Blocks can create use cases that write directly into the data layer. Organisations can build their own applications, or use any other application that works off open data standards.
Transformation works best when delivered one use case at a time. Each use case should justify itself financially, on its own. Each one also adds a further capability to the same shared foundation. Once data is structured, an agent layer can be built on top, safely and with full traceability.