Enterprise Architecture

Scope. commvita is a global health platform factory, not a customised health IT product. 615 modules (571 live at build B-525) span primary care, community, mental health, social care, acute and governance across 16 configured jurisdictions, on one record and one codebase. Every architectural decision is evaluated against the factory distinction: variance is modelled and versioned, never forked into local code.

Requirements Management is not a phase; it is the hub every phase touches. In commvita the requirements repository is the set of governing PRDs and binding standards held in the repository alongside the code, so a requirement, its implementation and its test are versioned together.

Why the editions matter architecturally: Governance & Assurance is deliberately separable — it consumes the same spine but stores no patient identifiable data, which is what allows it to be deployed inside one financial year while the clinical platform follows on its own assurance timetable.

The layers are stable; the occupants are not. England has replaced its commissioning tier twice in a decade — 211 clinical commissioning groups in 2013, 106 by 2021, 42 integrated care boards in 2022, 36 from April 2026 — with a stated intent to align boundaries with the new strategic authorities, and its national arm’s-length body is being wound into the department. Every one of those is a change of instances at the COMMISSIONER layer. None is a change to the layer model. That is the architectural claim this phase makes: the typed four-layer model, plus organisational structure held as effective-dated configuration rather than as schema, is what allows a reorganisation to be a data migration of hours rather than a programme of years. An enterprise architecture that has to be redrawn every time a commissioner merges is not an architecture.

Cell topology. Cells are drawn on residency and regulatory boundaries: NHS nations in one production cell, Crown Dependencies in another, CMS and ACO customers in a third, Gulf ministries in sovereign in-country cells. Data residency is a deployment property, not an application concern.

Absent from the previous edition. Phase G is where the doctrines become enforceable. Assurance runs as six automated domains, and the promotion gate is the architecture contract in executable form — a change that cannot satisfy it cannot reach a regulated deployment.

Absent from the previous edition. Phase H answers the question the factory model depends on: when a jurisdiction, tenant or regulator wants something different, what changes? The answer must never be a branch.

Jurisdiction-specific instruments — electronic signature law, background-check schemes, professional registers, care regulators and billing regimes — are not listed here. They are resolved at runtime from the Jurisdiction Profile, which is the point: a standard that varies by country is data, not documentation.