ReadoutThe short answer
First verify the clinic's exact installed state: model, configuration, serial number, installation and service history, licensed capabilities, software environment, quality-control status, workflow, case mix, and decision authority. Then route the account to the supported motion: first acquisition, capability upgrade, replacement, service and QA, software and integration, adjacent workflow, training and utilization, multi-location standardization—or no action.
Diagnose the gap before naming the product. The most credible rep can explain why a clinic should repair, upgrade, train, integrate, keep referring, wait—or replace.
This U.S.-focused field guide is for dental equipment sellers. It helps choose a commercial discovery path; it does not determine patient-level imaging need, diagnose equipment performance, establish regulatory compliance, or replace manufacturer, clinician, physicist, IT, financial, or legal review.
The eight CBCT opportunity paths
| Possible motion | When it may fit | What can disprove it | Best opening question |
|---|---|---|---|
| 1. First acquisition | The site lacks owned CBCT, and its appropriately selected cases or referral workflow create a verified clinical or operational gap. | Referral works well; relevant case volume is uncertain; lower-exposure imaging is sufficient; or the practice lacks implementation ownership. | “For the cases where 3D information is needed, what happens from referral through image review and patient follow-up today?” |
| 2. Capability upgrade | The current configuration cannot support a recurring, defined requirement, and an eligible FOV, modality, software, hardware, or license change may close the gap. | The capability is already present but unlicensed, unconfigured, misunderstood, or unused; service or training may solve the problem. | “Which required capability is physically absent, unlicensed, unconfigured, or simply not being used?” |
| 3. Replacement or refresh | The system cannot reliably, supportably, securely, or economically meet verified requirements after reasonable remediation alternatives are considered. | The unit performs acceptably, passes applicable testing, remains supportable, and meets the current workflow. Appearance and estimated age are not enough. | “What documented reliability, support, performance, security, or continuity problem remains after service and remediation?” |
| 4. Service, QA, or continuity | Faults, downtime, inconsistent images, calibration or positioning concerns, repeat scans, overdue tests, weak service access, or no downtime plan are visible. | Performance is stable, testing is current, service is responsive, and the practice has an acceptable continuity plan. | “Could we review the fault, repeat, service, and quality history before assuming a scanner change is needed?” |
| 5. Software, workstation, storage, or integration | The hardware is clinically adequate, but slow reconstruction, crashes, storage, backup, unsupported software, export, patient matching, or data flow impairs use. | The problem is operator workflow or training; the desired integration is not supported by the specific endpoints; or a change would break validated functions. | “Is the bottleneck image acquisition, or what happens to the image after it is captured?” |
| 6. Adjacent digital workflow | The CBCT data is adequate, but planning, IOS alignment, lab exchange, guide design, printing, post-processing, or workflow ownership causes delay or rework. | Referral or lab workflows are effective; volumes do not support change; or the team lacks validated production and clinical ownership. | “Which step between scan, plan, design, production, and delivery creates the most friction?” |
| 7. Training, protocol, or utilization | The installed system is capable, but positioning, protocol selection, interpretation confidence, onboarding, viewer use, or handoffs prevent consistent use. | Low utilization is clinically appropriate; the issue is true equipment performance; or the required capability is genuinely unavailable. | “Would a protocol and utilization review be more valuable than changing equipment?” |
| 8. Multi-location standardization | Different systems, software, service paths, protocols, data access, or training create a measurable governance or continuity problem across locations. | Local variation is justified; useful assets would be stranded; central authority or IT readiness is absent; or uniform hardware would not solve the actual problem. | “Where would standardization improve continuity or governance, and where should existing equipment remain?” |
The paths should not be collapsed into “new unit” and “replacement.” They have different buyers, budgets, proof thresholds, and next steps. One organization can also have several motions at once—for example, a software issue at one location and a first acquisition at another.
A five-minute installed-base triage
- Identify the asset. Record the manufacturer, exact model, hardware revision, serial number, installed configuration, location, and known delivery or acceptance date.
- Separate capability from activation. Confirm which FOVs, modalities, acquisition modes, software modules, and interfaces are physically present, licensed, configured, supported, and actually used.
- Locate the bottleneck. Is the problem acquisition, image performance, service response, workstation speed, storage, export, integration, interpretation, training, or a downstream workflow?
- Verify lifecycle evidence. Review service history, fault and downtime logs, applicable acceptance or quality-control results, current support status, software compatibility, repair options, and continuity risk.
- Choose the smallest supported motion. Start with the remedy that closes the verified gap. Escalate to hardware only when a reasonable non-hardware path cannot do so.
The AAPM's dental CBCT quality-control guidance describes acceptance testing, image-quality performance measures, radiation output, and routine QC. Those evaluations belong with qualified professionals; a rep can request the evidence without trying to interpret it as a physicist.
If the clinic already owns CBCT, start here
| Installed-base condition | Best first motion | Escalate toward hardware when… |
|---|---|---|
| Reliable system, current testing, available support, and a workflow that meets present requirements | No action or lifecycle monitoring | A new verified requirement or material continuity risk emerges. |
| Faults, repeats, calibration warnings, positioning drift, image complaints, or downtime | Service, QA, and repeat analysis | Qualified review establishes a persistent limitation or an uneconomic repair path. |
| Adequate scanner but slow, unstable, unsupported, or capacity-constrained software environment | Software, workstation, server, storage, and security review | The required supported stack cannot operate with the acquisition hardware, or remediation is disproportionate. |
| Images do not move cleanly to planning, radiology, lab, archive, or practice-management systems | Interface and interoperability assessment | The installed system lacks a required supported export or interface that cannot be added or validated. |
| Capable system with low confidence, inconsistent protocols, or one trained operator | Training, governance, and workflow support | The unresolved problem proves to be a real capability or reliability limit. |
| Working scanner with a fragmented implant, guide, IOS, sharing, or printing workflow | Adjacent digital workflow | The scanner data or coverage cannot support the validated end-to-end requirement. |
| Product appears old, “legacy,” phased out, or absent from the current website | Lifecycle fact verification | The manufacturer or authorized service path confirms a material parts, support, software, security, or economic issue for the exact unit. |
Replacement is a conclusion, not a prospecting label
A replacement case becomes credible when documented reliability, performance, serviceability, software support, security, interoperability, continuity, or economics show that the existing system cannot reasonably meet the clinic's verified requirements. Before using that label, compare service, calibration, QA, training, software, workstation, storage, interface, and available upgrade paths.
What does not prove replacement
Visual age, model-family launch year, a resale listing, warranty expiration, an old manual, disappearance from a product page, or a generic “legacy” label.
What strengthens the case
Exact-unit support evidence, recurring documented downtime, unacceptable results after qualified review, unavailable service or parts, an unresolvable supported-software gap, or a complete repair-versus-replace case.
Keep these dates separate: product launch, regulatory clearance, public first-seen date, delivery, installation, acceptance, warranty start, service-contract term, support termination, and usable life. One does not substitute for another.
Use an evidence ladder, not a visual guess
| Evidence level | Useful examples | What the rep may conclude |
|---|---|---|
| Strong account-specific evidence | Authorized serial/configuration lookup; invoice or acceptance record; service and fault history; current support statement; current compatibility matrix; warranty or service contract; recent qualified testing. | The installed configuration, relevant lifecycle dates, actual repair burden, covered components, supported environment, and current service path—within the scope of the record. |
| Useful product-level evidence | Current manufacturer page, technical manual, system requirements, field-upgrade documentation, formal phase-out or end-of-support bulletin. | What a named configuration or version may support and which account facts need verification. Product-family evidence may not apply to every serial number. |
| Weak hypothesis only | Clinic website, office photo, social post, archived page, launch announcement, apparent age, resale listing, or absence from a current catalog. | A reason to ask a question. These sources do not establish ownership today, installation date, configuration, condition, support, or replacement need. |
Do not confuse scanner problems with stack problems
A clinic can have a functioning scanner and a failing imaging environment. Ask about acquisition and viewing versions, operating systems, workstation resources, database growth, storage, restore testing, secure remote support, identity matching, exports, and every system that needs to receive the study.
“DICOM compatible” is not an interoperability test. The current DICOM conformance guidance states that DICOM by itself does not guarantee interoperability; conformance statements are a starting point, and the required exchange should be tested between the specific endpoints. Where ePHI is involved, HHS risk-analysis guidance calls for regulated entities to assess risks and vulnerabilities, including when new technology is introduced.
Useful diagnostic question: “Is the problem making the image, interpreting the image, moving the image, finding the image later, or using it in the next workflow?”
Fourteen questions a rep can use in the field
- What exact manufacturer, model, revision, serial number, and configuration is installed at each location?
- Which capabilities are present, licensed, configured, supported, and routinely used?
- When was this specific unit delivered, installed, accepted, and last relocated?
- Who services it, and what warranty or service coverage is active?
- Which real cases or workflows cannot be completed with the current setup?
- What faults, repeats, emergency visits, repair costs, and downtime occurred during the last 12–24 months?
- What did the latest applicable acceptance, annual, or constancy review show?
- Has the manufacturer or authorized channel confirmed current parts, service, and field-upgrade eligibility for this serial number?
- Which acquisition, viewing, planning, and practice-management versions run on which operating systems?
- When was the last successful backup restore test?
- Where are files manually exported, renamed, copied, uploaded, or re-entered?
- Which operators and clinicians are confident with positioning, protocol selection, viewer use, interpretation, and escalation?
- Who owns clinical standards, IT, service, capital approval, and rollout sequencing?
- What evidence would make “keep the current system” the right recommendation?
Neutral language that earns the next conversation
| Avoid saying | Use instead |
|---|---|
| “That unit is obsolete.” | “Can we verify the exact support, software, service, and parts status for this serial number?” |
| “It is ten years old, so it is due.” | “What does the actual reliability, service, QA, and continuity history show?” |
| “Your image quality means you need a new scanner.” | “Has positioning, protocol selection, calibration, service, software, and qualified performance review isolated the cause?” |
| “DICOM means it will integrate.” | “Which objects and workflows must move between which exact systems, and what test will count as success?” |
| “You already own CBCT, so there is no opportunity.” | “Does the installed system fully support acquisition, viewing, service, storage, sharing, training, and the downstream workflow?” |
| “A new scanner is the answer.” | “Which smallest change closes the verified gap, and what evidence would justify escalating to hardware?” |
When no equipment change is the right answer
A rep should be willing to recommend monitoring when the current referral or installed workflow meets the clinic's needs, quality and reliability are acceptable, support remains available, the software environment is supportable, appropriately selective use explains low volume, and no verified capability, continuity, security, workflow, or economic gap exists.
The FDA advises that dental CBCT be used only when necessary to provide clinical information unavailable from other imaging modalities. A procedure list or growth ambition should therefore begin a discovery conversation, not prove equipment need.
Research basis and limits
This guide synthesizes current U.S. clinical, quality-control, interoperability, security, and first-party product evidence into a seller routing framework. Strong evidence supports separating the opportunity paths and requiring exact-unit verification. Product upgradeability, support, software compatibility, state requirements, and service availability remain manufacturer-, configuration-, serial-, version-, region-, and jurisdiction-specific.
Primary references include the FDA dental CBCT overview, AAPM Task Group Report 261, the current DICOM conformance standard, and HHS security risk-analysis guidance. Exact equipment status should be verified through current manufacturer or authorized service evidence. Clinical, safety, regulatory, cybersecurity, financial, tax, reimbursement, and legal conclusions require qualified account-specific review.
Keep reading: understand how clinics clear the six CBCT buying gates, identify accounts with the CBCT opportunity framework, or broaden your timing view with dental equipment buying signals.
Find the account. Then route the opportunity.
Readout helps dental equipment teams identify product-relevant accounts, see why each one surfaced, and give the rep the next fact to verify before choosing a sales motion.