DentalClinicsFor your practice
What you need, what you don't, which examinations we accept, and how the first weeks go. Written for the person who has to decide, not for the person who has to integrate.
Supported examinations
- Accepted
Bitewing
Posterior interproximal radiographs, single or paired.
- Accepted
Periapical
Single-tooth or small-segment intraoral radiographs.
- Accepted
Panoramic
Full-arch panoramic radiographs.
- Not accepted
CBCT
Excluded for now. Volumes are large and per-study vendor costs vary too much to price honestly.
Accepted formats: DICOM, PNG and JPEG. An examination being accepted here does not mean every platform reads it: each vendor states which images its product is built for, and we only route an image to products whose stated scope covers it.
What can be reported
Only what the platforms you use are built to report — typically caries, calculus, bone loss, periapical lesions or restoration margins, depending on the product. We add no finding of our own. Where a finding sits outside a platform's stated scope, we say so, rather than presenting that platform's silence as a negative reading.
What you need
· An internet connection and a current web browser.
· Imaging software able to export DICOM, PNG or JPEG.
· For CDSS Only: an active subscription to at least one dental AI platform, and that vendor's agreement to API access.
· Our data processing agreement, signed as published.
· In the United States: a HIPAA business associate agreement. Ours is in preparation — ask us before onboarding.
What you don't need
· New X-ray equipment. You keep your sensors and your imaging software.
· A local AI server, a GPU or any workstation upgrade.
· A data migration. We store no images, so there is nothing to move in or out.
· A minimum term. You can stop at any time.
How onboarding works
A thirty-minute demonstration
On the synthetic case, then on a de-identified radiograph of yours once your platforms are connected.
Your vendor, confirmed
With your consent, we check that the platform you already use grants API access to an integrator. Without that, nothing can be connected, and we will tell you so.
A connection test
One de-identified radiograph, sent end to end, readings returned side by side. You see the real output before anything else happens.
Your practice goes live
Per location, on the terms of the pricing page. Your first month is paid in advance when you sign; from the second month on, each month is billed at its end.
We do not quote a go-live date. The step that takes longest is the vendor's, not ours, and a date we do not control is not one we should promise you.
Integration
For the person who connects your imaging software. We list what exists today and, separately, what does not exist yet.
| Item | Status | Detail |
|---|---|---|
| HTTPS API | Available | One synchronous call per radiograph. JSON request, JSON response. |
| Image formats | Available | DICOM, PNG, JPEG, sent inside the request. |
| Authentication | Available | Secret bearer token, compared in constant time. Calls without it are refused. |
| Per-practice tokens | Available | One token per location, stored only as a hash, revocable individually by us on request. |
| Revocation from your own account page | Not available yet | Planned. |
| Network | Available | Outbound HTTPS on port 443 only. No inbound port, no VPN. |
| Response content | Available | Platforms queried with product version and stated scope, attributed findings, agreement and disagreement in words, formal notes. |
| Identifier removal on tags and on vendor responses | Available | Identifying keys in DICOM tags sent as fields, and in every payload a vendor returns, are removed, never masked. Every removal is listed in the response, so a missing field is never mistaken for a fault. |
| Identifier removal inside the DICOM file | Available | Identifying header fields and dates are removed, private manufacturer tags are removed, study and image identifiers are replaced by random ones, nested sequences included. Every change is listed in the response. |
| Images with burned-in text | Refused | A file that declares text burned into its pixels is refused, because that text cannot be removed. Text burned in without that declaration cannot be detected: remove it at source. |
| DICOMweb | Not available | No STOW-RS or WADO-RS endpoint today. |
| HL7 FHIR | Not available | Not implemented today. |
| PACS or practice-software plug-in | Not available | No native plug-in for any imaging or practice management system. |
If your imaging software can export a file and your IT provider can send an HTTPS request, that is enough. If it cannot, tell us before onboarding: better to know on day one.
DentalClinicsAIHub is an integration and access platform. It produces no clinical finding of its own and holds no regulatory clearance. Each platform's regulatory status belongs to its own vendor.