Masters Media · the platform

Ovivo · six products and the commons

Six products, one loop. And a commons above it.

The goal all seven exist to serve is a citizen-held health record. Ovivo Record is the data origin the whole platform is built around. The others exist to make that record clinically useful, evidence-grounded and continuously improving, rather than a static file the patient owns but nobody can act on.

Where this actually stands

One of the seven is going to market. Masie is Stage 1. Everything after it is the roadmap, sequenced and specified but not built. This page describes the shape of the thing, not a catalogue of what you can buy today.

The shape

Six to one.

Six products form one self-closing loop. Each layer feeds the next, and the last feeds the first. Apps on Prescription sits above the loop as the ecosystem layer, and the Federated Health Commons sits above all of it as the protocol layer.

07 Federated Health Commons the protocol layer, open source, above everything
05 Apps on Prescription the ecosystem layer, above the loop
Record Masie Guidelines Protocol outcomes Trials

Trials routes its results back into Masie, and the loop closes. Evidence improves care, care generates evidence.

The build order runs opposite to the data flow, on purpose. The products that touch no patient data are built first, so the heaviest obligations, identifiable records, medical device regulation and trials ethics, are taken on last and in walled-off layers. Record is the mission's data origin and it is still not first.

The seven

Product by product.

Listed in build order, which is not the order the data moves in.

01

Masie

Stage 1 · going to market

Universities · research hospitals · guideline bodies

Continuous evidence synthesis, the living intelligence layer. A governed team of AI agents reads, debates and integrity-checks the biomedical literature, keeping living documents current in real time. It includes Signal for change-aware alerts, Network for attributed peer commentary, and Living Studies, where researchers host a study that stays open to appraisal.

  • Runs on open-access literature and consented, de-identified datasets. No patient data.
  • Every paper is scored across ten pillars by the Epistemic Integrity Framework before it can be debated.
  • Promotion to trusted evidence requires a two-thirds council vote, logged to an immutable SHA-256 audited trail.
  • Corpus of 32M+ papers, extracted and de-duplicated.
02

Ovivo Guidelines

Stage 2 · next

Guideline councils and committees

Living clinical guidelines, licensed to the bodies that write them. When the underlying evidence moves, Ovivo drafts the proposed update for the committee to ratify rather than pushing a change unilaterally.

  • A reconciliation layer continuously flags each guideline as concordant, discordant, or in a gap against current evidence.
  • Still no patient data, but because it drafts clinical recommendations it carries clinical decision support exposure.
03

Ovivo Protocol

Stage 3 · later, regulated

Clinicians

Personalised, living treatment plans generated at the point of care from the intersection of one patient's record, current evidence and current guidelines, recomputed automatically whenever any of the three changes.

  • This is n=1 medicine. Where today's protocols are built from population averages, Protocol is built for the specific person in front of the clinician.
  • Regulated as Software as a Medical Device, preceded by clinical validation and clinician sign-off.
  • Sequenced deliberately after the evidence engine has already earned trust.
04

Ovivo Record

Stage 4 · later, isolated

Patients

The self-sovereign electronic health record. A patient-owned lifetime record, birth to death, held by the citizen rather than any institution. It is the data origin that makes the whole loop possible, and the product every other layer exists to serve.

  • Because it holds identifiable patient data it is fully walled off from the other products, with separate deployment, separate region and its own certifications.
  • Built on FHIR R4 with a patient-held consent ledger.
  • Contributes only tokenised, consent-gated signal into Masie. The mapping lives inside Record's own key management, unreachable from any other product.
  • Partners for existing patient-data rails rather than rebuilding them, adding sovereign governance and longitudinal intelligence on top.
05

Ovivo AOP

Stage 5 · later, ecosystem

Digital-therapeutics developers · payers

Apps on Prescription, the ecosystem layer sitting on top of Record and Protocol. Certified digital therapeutics integrate once for consent, real-world evidence collection and regulatory reporting, instead of building bespoke integrations market by market.

  • Sits above the loop rather than inside it.
  • Certification is the gate. An app does not reach patients because it integrated, it reaches them because it was certified.
06

Ovivo Trials

Stage 6 · later, ethics-gated

Research institutions

The evidence-generation layer that closes the loop. Embedded pragmatic trials, n-of-1 crossover studies and adaptive platform trials run across the consented network, turning it from an observational data lake into a randomised-evidence generator, with results routed back into Masie.

  • Gated deliberately. No Trials code ships until an independent international ethics advisory board and a data safety monitoring board are constituted, and first-jurisdiction ethics approval is secured.
  • Governed to Helsinki, CIOMS and ICH-GCP standards, with federated local approval per country. Global by standards, federated by law.
07

Federated Health Commons

Long horizon · open source

Governments · standards bodies · the wider health-technology ecosystem

A protocol layer for health data, sitting above the whole loop rather than inside its build sequence. Open source by design, because a protocol that other platforms and governments are asked to adopt has to be publicly inspectable, not a proprietary specification owned by one company.

  • A protocol-first alternative to building one platform and federating later. Platforms sit on top of the commons as citizen-facing applications, interoperable by default, competing on experience and trust rather than data lock-in.
  • Governed by a proposed Constitutional Commons model. A founding charter of non-negotiable principles, a rotating multi-stakeholder council for operational governance, and certification-based enforcement.
  • Governments as members rather than owners.
  • If it is pursued, the Commons, not any single product, becomes the centrepiece.
How it is governed

Two axes, and one rule.

Regulation here runs on two independent axes, not one. Conflating them is the usual mistake, and it is why the sequence looks the way it does.

Privacy

Turns on whether identifiable patient data is involved at all. Only Record carries this, which is why it is deployed separately, certified separately, and walled off from everything else.

Device

Turns on whether the software drives a clinical decision, regardless of patient data. Guidelines carries this exposure on zero patient data. Protocol is squarely software as a medical device.

Ovivo proposes, humans decide

Evidence can be promoted automatically. Guideline changes are ratified by committees, and treatment decisions are made by clinicians. Nothing in the loop closes without a person in it. It informs the decision; it never makes it.

Next

Questions about any layer of this?

We are talking to universities, research hospitals, guideline bodies, clinicians and investors. Tell us which layer you came for.