commvita
Connected care platform
How the platform is wired

Module Linkage & Product-Theme Map

Every module in commvita sits in a product theme, and every theme binds to the same two spines — one person and record spine and one interoperability layer. That is the whole design: data arrives once, lands in one open record, and every surface above reads the same truth. Nothing below is a separate product with its own database.

Live vs demonstrated: Live — real, API-backed platform logic, wired end-to-end today Demonstrated — representative control surface with seeded data or illustrative mock-up
commvita — Module Linkage & Product-Theme MapA representative system map of modules grouped by product theme, with the documented cross-cutting architectural spines. Modules shown are exemplars of each theme.01PEOPLE-FACING— how a person, carer or clinician reaches the servicePatient PortalPortal · nudges · feedback · NHS AppReferrals & Accesse-RS · triage · waiting list · RTTAmbulance & Pre-HospitalCrew app · JRCALC · handoverFront Door & AssistMyDay · Concierge · Ask commvita02CARE DELIVERY— where care is actually recorded, across every settingClinical CoreConsults · meds · CDSSRemote & CommunityVirtual ward · RPMMental Health & SocialMH · IAPT · social careAllied HealthPhysio · OT · SLTCondition ProgrammesDiabetes · stroke · MSK03THE SPINE— one open record and one way in. Everything above and below binds herePERSON & RECORD SPINEEMPI Hub · Whole Person Record · Care Journey · Neighbourhood Health RecordopenEHR archetypes · FHIR R4 · SNOMED CT · dm+d — your data, in an open standardINTEROPERABILITY & EPR LAYERPulseGrid · HL7 Engine · EPR Hub · GP Connect · NRL · FHIR BulkThe only place integration work is needed — at the edge, not between themes04RUN THE ORGANISATION— operations, assurance and money, computed from the same recordFlow & OperationsFlow · OPEL · beds · dischargeGovernance, Safety & RiskIncidents · PSIRF · IG · AIBoard & AssuranceBoard · BAF · EPRR · HIMSSWorkforce & L&DRostering · staffing · LearnAnalytics & PopulationCohorts · PROMs · inequalitiesUS Care ManagementCCM · RAF · STAR · payerFinance & CommissioningTariff · ICB · Care Act05SHARED SERVICES— one of each, used by every theme above. Config-driven, not rebuiltPlatform & AIAI Hub · commvita Sign · flagsCommunications CRMCRM · telephony · SMS · NotifyJurisdiction & ConfigProfiles · packs · RBAC · policyWhat the lines meanPerson binding — every care surface reads and writes one record — no orphaned copiesPerson entry — portal, referral and front-door contact lands on the same recordFlow orchestration — ambulance → flow → bed → discharge; OPEL → on-call → EPRRGolden thread — event → theme → systemic issue → risk → board objectiveCohort to action — population analysis becomes recall, prescribing or a care planShared services — one AI hub, one e-signature, one CRM, one jurisdiction profileBackbone = person and record spine + interoperability layer. Non-SaMD. 613 modules built, 570 live — boxes above name exemplars, not the full inventory.
01 · READ IT DOWNWARDS

Surfaces on top, spines in the middle

Orange and teal rows are where people work. The navy band is the backbone they all bind to. Everything below the backbone consumes that same record rather than keeping its own copy.

02 · FOLLOW A COLOUR

Six linkages, six meanings

Each line in the legend is a real architectural route — person binding, interoperability feed, flow orchestration, the incident-to-board golden thread, cohort-to-action, and the shared-services rail.

03 · WHY IT MATTERS

No integration layer to buy

Because the themes share a record rather than exchanging files, the integration work that normally falls to your people is not needed between them — only at the edge, where other systems connect.

© 2026 Commvita Digital Health Solutions Ltd. All rights reserved.