commvita™Connected care platform
Book a walkthrough
Platform › Whole person record
Whole person record

One longitudinal record, across every setting a person is known to.

Resolved rather than merged, coded against a terminology the jurisdiction binds, and honest about where the record is complete and where it is not.

The record

One record, every setting

A person is not a patient of one organisation. The record follows the person across primary care, community services, hospital, mental health, social care, dentistry, pharmacy and specialist care.

The whole person recordOne person at the centre, with eight care settings around them, each contributing to and reading the same record rather than holding a copy.One personresolved, not mergedPrimary careCommunitySecondary careMental healthSocial careDentistryPharmacySpecialist careEach setting contributes to and reads the same record. None of them owns it.

Identity is resolved across organisations rather than merged into one owner, so nobody’s record is re-keyed when an organisation changes.

  • Primary care
  • Community services
  • Secondary care
  • Mental health
  • Social care
  • Dentistry
  • Pharmacy
  • Specialist care
Clinical content

What the record holds

  • Assessments
  • Care plans
  • Referrals
  • Outcomes and PROMs
  • Diagnostics and results
  • Medications
  • Allergies and intolerances
  • Imaging
  • Pathology
  • Immunisations
  • Safeguarding flags
  • Communication needs

Every value is coded against a terminology the jurisdiction binds, not one we chose. A code means the same thing everywhere, so code content is held once; which classification a country mandates, for which purpose and from which date is a per-jurisdiction binding.

Genomics

Genomics and precision medicine, with the gap stated

The genomic surfaces are real and they read well. The registers behind three of them are not yet persisted, and that matters more here than almost anywhere else on the platform.

Clinical and genomic record architectureThe clinical record is built and persisted; the genomic surfaces exist but three of their registers are in-process lists, and there is no FHIR endpoint or national exchange.The clinical record — built and in useEncounters, medications, allergies, diagnostics, imaging, careplans and assessments, persisted and audited, with ajurisdiction-resolved terminology binding.The genomic record — surfaces built, spine notReferral, consent, pedigree and panel surfaces exist and readwell. The registers behind three of them are in-process lists: arecord created through the interface does not survive a restart.What is NOT built, stated plainlyThere is no genomics FHIR endpoint, no exchange with a national genomic service, and nothing is written to an openEHR clinical data repository.A genomic finding identifies a family, not only a patient. That is why this page states the gap rather than the ambition.Two records, two different levels of readiness.

The clinical record is built and persisted. Three genomic registers are in-process lists.

CapabilityPosition
Genomic referral, panel selection and trackingPartial Surface built; register not persisted
Consent, including cascade to relativesPartial Surface built; register not persisted
Three-generation pedigreePartial Rendered from stored fields
Pharmacogenomics panel and diplotype displayLive
ACMG/AMP five-tier variant classification displayLive
Role-gated access with default deny and audited refusalsLive
Genomic tab on the person’s recordLive
FHIR Genomics endpointNot built
Exchange with a genomic laboratory hub or national serviceNot built
Patient-facing genomic results in the portalDesigned
Storage in an openEHR clinical data repositoryNot built
Live Live — built, persisted and reachable todayPartial Partial — built with a stated limitPending licence Pending licence — built, awaiting a publisher licenceDesigned Designed — specified, not builtNot built Not built

Why this is stated so plainly

A genomic finding identifies a family, not only a person. A disclosure reaches blood relatives who never consented to anything, which makes it the one domain where an overstated capability is least acceptable.

Three of the registers are held in process memory: a record a clinician creates through the interface is lost when the service restarts and is invisible to the other replica. It needs a persistence migration before any live use, and no amount of interface polish substitutes for that.