Kyber Clinical AI Request access

Platform — private preview

Kyber Clinical AI by DEOX Clinical Clinical data standards, built in.

The Kyber Data Standards (KDS) define the resources, fields and codelists that clinical-trial operations run on, crosswalked to FHIR R4 and CDISC and released as versioned packs.

Request access Explore the standards
  • Crosswalked to
  • FHIR R4
  • CDISC SDTM
  • CDISC Define-XML
The Kyber emblem: a faceted crystal holding an orange DNA double helix
KDS in numbers

One vocabulary for clinical-trial operations.

Counted, not estimated. Every figure has a source.

  • 156 resources defined in KDS
  • 4,627 fields across those resources
  • 915 codelist files 358 pinned to an external terminology
815

fields mapped to ≥1 external standard, 17.6% of all 4,627 fields. We publish coverage as it stands.

  • Any external standard815 · 17.6%
  • FHIR R4751
  • CDISC SDTM132
  • CDISC Define-XML132

Bars share one scale: all 4,627 fields. Standard targets overlap, so one field can count towards more than one standard.

As of 4 October 2026. Source: KDS campaign at commit 33dc3b6. Machine-readable figures and provenance (stats.json).

What's inside KDS

Four building blocks. One governed standard.

From trackers and quality events to the data that feeds a submission.

Resources & fields

The records a clinical-trial organisation keeps, as typed resources and fields, published as a governed schema and registry.

156 · 4,627resources · fields
Resources in detail

FHIR ↔ CDISC crosswalks

Fields pinned to FHIR R4 for exchange and to CDISC SDTM and Define-XML for submission. Crosswalk files ship inside the packs.

815fields mapped (17.6%)
How the crosswalk model works

Tracker event taxonomy

SOC/PT-style coding for quality events, Class → Category → Term, on 10 shared classes. CAPAs, deviations and audit findings trend together. Adverse events stay on MedDRA.

3 levelsv0.1 draft
The taxonomy (v0.1 draft)

Versioned kds-packs

Each release is a versioned pack with a SHA-256 integrity manifest. Current packs: v0.1 and v0.1.0.

By requestpack access
Pack list
How it works

Define once. Pin to the standards. Ship as a pack.

KDS is the operational vocabulary. External standards are targets, not replacements.

  1. Define once

    A field is defined in its KDS resource and bound to a codelist where a controlled value is expected.

  2. Pin to targets

    Each mapping pins the field to a named target in FHIR R4, CDISC SDTM or Define-XML. KDS stays the source of truth.

  3. Release as a pack

    Crosswalks ship inside versioned kds-packs, checked file by file against a SHA-256 manifest.

Source of truth KDS field Defined once, in its resource
  • FHIR R4Exchange
    751fields pinned
  • CDISC SDTMSubmission
    132fields pinned
  • CDISC Define-XMLSubmission
    132fields pinned

One field can be pinned to several targets, which is why the counts overlap. The full crosswalk model.

The platform

Kyber platform — private preview

Built around KDS, so trackers, quality events and study data share one set of definitions. Open to a small number of organisations during private preview.

Private preview · request access

Arrange a walkthrough
Inside the platform

The actual platform, in private preview

Real views from the Kyber platform — safety oversight, site management and CAPA workflow — shown on an illustrative mock study. Synthetic data throughout.

Kyber platform — private preview Actual UI · mock study data
SAE safety dashboard: summary tiles and a table of adverse events with severity, relatedness and outcome
SAE safety — event grading, relatedness and outcomes in one view
Site information dashboard: activation status, principal investigators and enrolment by site
Site management — activation, investigators, enrolment
CAPA board: corrective and preventive actions across open, in progress, implemented, verified and closed columns
CAPA workflow — from open to verified closure
Roadmap

Where KDS is heading

What is in progress now. We report coverage as it stands, not as it will be.

  1. In progress

    Crosswalk coverage

    Extending external mappings across the standard. 88 resources are not yet externally mapped; they are next in line.

  2. v0.1 draft

    Tracker event taxonomy

    The v0.1 seed vocabularies, starting with CAPA, deviations, protocol deviations and audit findings, are under quality review before ratification.

  3. Ongoing

    Versioned pack releases

    New kds-packs as coverage grows, each with its own version and integrity manifest.

  4. Private preview

    Kyber platform

    Access for early partners, by request.

Early access

Request access

The Kyber platform and the KDS packs are available by request during private preview.

Early-access programme — opening soon.

Read the standards summary