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.
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.
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.
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.
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.
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.
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.