The odontogram builds the case.

The TrazaLab odontogram keeps a structured clinical identity for each site. The tooth, its surfaces, findings, treatments, evidence, priority, and status can stay related inside the same case. When a tooth opens, the workspace keeps numbering and arch context, but shows only the decisions that belong to that anatomy and the selected branch. The chart stops being an isolated illustration and becomes the visible entry into a traceable record.

Yes. Odontogram identity can be configured as adult, pediatric, or mixed dentition. This is not shrinking the same drawing: each identity keeps the sequence and morphology expected for its teeth. Mixed dentition can show primary and permanent teeth together without losing site identity. Numbering can appear as FDI or Universal according to the working configuration, while the internal record keeps the relationship between the selected tooth and the rest of the case.

Both modes use the same structured chart, but they answer different questions. Clinical mode records what the team observes or documents: condition, surface, evidence, priority, and intended action. Treatment mode defines what is requested or planned for that site and opens the specific data of the chosen branch. Changing mode does not duplicate the tooth or break its history; it keeps identity and shows the information needed for the next human decision.

TrazaLab opens a focused workspace for that tooth. Anatomy and available surfaces adapt to the tooth type: an anterior can show vestibular, distal, incisal, mesial, and lingual; a posterior includes its occlusal surface. The system keeps the tooth number, arch, and active mode, and presents the next open requirement for that branch. A crown can request characterization; an implant-supported restoration can request the emergence profile. The person completes a concrete decision without losing the full map.

The locally verified structure includes branches such as restoration, crown, veneer, inlay, onlay, implant, implant crown, extraction, guide site, pontic, and bridge abutment. Each branch can require different data; that is why the focused interface does not present a universal form. The aim is that the dental site leads the team to the information that belongs to the selected work. Final availability of each branch depends on configuration and the activation approved for the production environment.

A selected surface can keep its relationship with the finding or treatment, attached evidence, and the case version in which it was recorded. Photographs, notes, and files do not need to live as orphaned references: they can return to the site that gives them meaning. When the case changes, history lets a person understand what information was present, who performed the action, and which version was reviewed. This structure supports coordination; it does not validate a clinical interpretation by itself and does not replace professional judgment.

The architecture contemplates a focused periodontal view that relates measurement sites to the same tooth and can prepare work lists and summaries. The visualization on this page uses six editorial positions around a molar to explain the interaction principle; it does not represent data from a real patient. Values, diagnoses, and clinical decisions remain the professional’s responsibility. Availability of specific panels and fields depends on local configuration and the product activation process.

No. They are editorial visualizations created to make anatomy and the software sequence visible at commercial-page quality. The states, controls, surfaces, requirements, and relationships around the images explain locally verified behaviors; photorealistic 3D anatomy must not be read as a capture of a 3D interface already shipped. Production availability is confirmed during workflow review; this page does not present the locally verified experience as universally activated.