Data dictionary — caseFormV0 — Dentum
ODIN · data dictionary

Data dictionary — caseFormV0

Every field of a registry case: types, requiredness, values. Source — the @dentum/registry schema; the table is generated at build time.

FieldTypeRequiredValues / boundsComment
study_uuid uuid server issued by the server
consent_scopes enum[] yes model_training | external_research | commercial_use
consent_confirmed bool yes “no consent, no record”
age int yes 18–100
sex enum yes m | f
smoking enum yes no | former | current
diabetes enum yes no | type1 | type2
hygiene enum no good | fair | poor
tooth_fdi int yes 11–48 see the FDI note below
bone_type enum no 1 | 2 | 3 | 4
implant_system string yes –60 brand — strongest single predictor
implant_length_mm num no 4–20
implant_diameter_mm num no 2–8
immediate_placement bool no
augmentation bool no
surgeon_experience_years int no 0–40 top-2 importance in the prototype
prosthetics enum no single_crown | bridge | overdenture | full_arch
outcome enum no success | periimplantitis | failure
marginal_bone_loss_mm num no 0–15
outcome_date date no
failure_reason string no –200

Field names = API names (never translated). Outcome fields are empty at baseline and filled at the 6/12-month recall.

FDI

Tooth number — FDI/ISO-3950: two digits, first = quadrant (1–4), second = tooth (1–8). E.g. 36 = lower left first molar.

Outcome definitions

success — implant in function, no clinical complaints

periimplantitis — inflammation with signs of bone loss

failure — implant removed or failed to integrate

Consent scopes (dynamic consent)

model_training — model training

external_research — external research (T1/T2)

commercial_use — commercial use

Book a visit

Our AI assistant in Telegram picks a clinic and books you in a minute — 24/7.

Continue in Telegram

Instant · AI · 24/7

or
No Telegram?

We reply on Telegram or by phone during business hours (9:00–19:00).