Record origin and record role are different
3Shape distinguishes direct intraoral capture from digitizing a physical model with a laboratory scanner. That describes where the surface record comes from; it does not tell the designer which decision it governs. A filename such as upper-final is insufficient when a package contains several stages.
Begin with a record manifest: identifier, acquisition method, date or revision, arch, role, relationship to other records, and sender. Keep a reference record separate from the surface selected for active design. A newer file should not silently replace an approved reference.
A practical record-role map
| Role | Design question | Clarification needed |
|---|---|---|
| Preparation or working surface | Which geometry is active for this revision? | Coverage and intended restored sites |
| Opposing arch | Which opposing reference accompanies this stage? | Applicable relationship record |
| Bite or jaw relationship | How are the arches related? | Governing reference and approval |
| Pre-op or proposed setup | What form or arrangement is being referenced? | Reference versus approved target |
| Scan-body or component reference | What documented component is represented? | Identity, library and instructions |
| Removable reference | Which record and workflow stage is represented? | Stage-specific receiving requirements |
This is an editorial intake map, not a mandatory acquisition protocol. A role may require more than one record, and a file may contain several objects. Record the software object assignment as well as the filename.
Handle conflicting references explicitly
Illustrative example: a pre-op record and a proposed setup show different arrangements. Ask which feature each is intended to guide and which stage has approval. Do not blend both into an undocumented target. Store the answer with the case revision and mark dependent decisions held until clarified.
A surface scan should not be treated as interchangeable with a different imaging modality merely because both are digital. This page addresses CAD surface-record handoff; imaging indications and interpretation belong to the responsible clinical team.
Review boundary
Technical review pending — unverified locally. Unverified locally: Louie must validate terminology, actual workflow dependencies and practice-case applicability. Source review is not software or clinical validation.
Use these worksheets to make uncertainty visible. They do not authorize a clinical decision, repair, production release or unsupported software configuration. Preserve original records and record who approved each change.
Source notes
Primary documentation checked October 6, 2026. Software details describe the cited product documentation; the handoff frameworks and illustrative examples are original editorial guidance. Confirm current version and account requirements with the publisher.
Prepared by Pristine Dental Design · October 6, 2026. Guidance for professional case communication and review. Actual prescriptions, manufacturer requirements and receiving-team approvals govern design and production.