Skip to content
Skip this journey

Layer 15 of 21 · Action and continuity

TwinBirth Creation of the patient's digital twin.

Every Twin starts somewhere. TwinBirth is intended to establish the baseline Twin from the data available at the start of the journey — Day 0 in the six-month journey — and to record what information is missing.

Why it's needed

What is the starting information set and how is the initial Twin established?

A clear statement of what the Twin was built from and what it lacks.

What it draws on

5 of 8 evidence domains.

Molecular & genomicClinical contextImaging integrationTreatment exposurePatient factorsThe testing-pathway result plus the clinical, imaging and treatment information supplied at baseline.

What it produces

A baseline structured view, with the inputs used and missing information identified where supported.

Describe the baseline integration and documented configuration of a Twin from the available case data.

Why it's essential

Layer 15 of 21.

Creates the reference point that every later update, comparison and decision record builds on.

1 · What it does

What TwinBirth does

Every Twin starts somewhere. TwinBirth is intended to establish the baseline Twin from the data available at the start of the journey — Day 0 in the six-month journey — and to record what information is missing.

2 · Scientific question

The question it addresses

What is the starting information set and how is the initial Twin established?

Intended function

Describe the baseline integration and documented configuration of a Twin from the available case data.

3 · Data inputs and required context

What it draws on

  • 01 Molecular & genomic
  • 03 Clinical context
  • 04 Imaging integration
  • 06 Treatment exposure
  • 07 Patient factors

The testing-pathway result plus the clinical, imaging and treatment information supplied at baseline.

4 · Scientific basis

The science behind it

Scientific basis

This is a data-integration and configuration step rather than an analysis. A baseline representation is only as complete as the inputs available at that moment.

5 · Output and evidence sources

What it produces

Main output

A baseline structured view, with the inputs used and missing information identified where supported.

Output type

  • Twin workflow function. Part of how the Twin is created, reviewed or updated, rather than an analytical result.

6 · Why it\u2019s essential

How it powers the Twin

Creates the reference point that every later update, comparison and decision record builds on.

Capability

Connect

Relate molecular, imaging, immune and patient information where available.

7 · Why it\u2019s needed

What it changes — for doctors, patients and researchers

Clinicians

A clear statement of what the Twin was built from and what it lacks.

Doctor & Clinical Team

Patients & caregivers

The Twin is a structured model of the available information, not a copy of the person.

Patient & Caregiver

Researchers

A documented baseline for longitudinal comparison.

Industry & Research

8 · Dependencies and limitations

Limitations

    9 · Review and uncertainty

    How the output is handled

    Output status

    An AI-assisted analytical output presented as structured findings for clinician review. It becomes part of a report only after the treating oncologist has reviewed and signed it.

    How uncertainty is communicated

    The baseline lists the inputs used and the inputs that were unavailable.

    10 · Claim boundary

    What this layer does not establish

    It does not create a complete digital copy of the patient or the cancer.

    The treating oncologist owns every decision. Every Twin report is reviewed and signed by the treating oncologist, then taken to KPCIRC's Molecular Tumour Board.

    KPCIRC sign-off process

    Continue the journey

    Longitudinal monitoring

    Every change goes in.

    →