Integrations
Automatic CBCT exam upload
Three integration methods that move cone beam studies into CBCTHub without manual handling. This page compares them and defines which one applies to each installation.
The cost of the manual process
Operator time per study
Exporting, compressing, uploading and verifying takes around ten minutes. At fifteen studies a day that is more than two hours of clinical staff time per shift.
Studies that never get uploaded
Manual upload depends on someone remembering at the end of the shift. The study stays on the workstation and the gap is noticed only when the patient or the referring clinician asks for it.
Data entered twice
Patient identification is already recorded in the DICOM at acquisition. Re-entering it duplicates the work and produces records that may not match.
Three integration methods
All three produce the same result: the study is available in CBCTHub with the patient data recorded by the scanner itself. What differs is how it leaves the scanner.
Folder monitoring
Works with any scannerAn application installed on the cone beam workstation watches the directory where the vendor software stores its images and transfers each new study. It operates read-only: source files are never modified or deleted.
Requirements: None. Every scanner writes its DICOM files to a local directory.
Full CBCTHub Link guideNetworked DICOM server
Scanners with DICOM sendThe same application exposes a DICOM node on the clinic network. The scanner transmits the study when acquisition completes, exactly as it would to any PACS. It is the most direct method and does not depend on the vendor's folder structure.
Requirements: The scanner must support configurable DICOM destinations. Some vendors license the network module separately.
Full CBCTHub Link guideREST API
In-house software, PMS or marketplaceYour system uploads the study over HTTPS and receives the 3D viewer link under your center's branding, ready to embed in an existing workflow. API key authentication and per-exam access control.
Requirements: Development work. A full integration takes roughly two hours for an experienced developer.
API documentationChoosing a method
Three criteria, in this order.
- 1
Is there in-house software or a practice management system already in operation?
The API applies. It is the only method that brings upload into the existing system instead of running alongside it.
- 2
Does the scanner support DICOM network send, with configurable destinations?
The DICOM server applies. It is configured once on the scanner and is independent of folder structure.
- 3
Neither of the above, or not confirmed?
Folder monitoring applies. It works in any installation, requires no configuration on the scanner and can be migrated to another method later.
Common to all three methods
Patient data is read from the DICOM file itself. There is no manual re-entry.
Duplicate submissions are detected by the study identifier assigned by the scanner: no copies are created and no additional quota is consumed.
If the network drops, studies are queued and retried automatically.
Traffic is outbound over HTTPS. No inbound ports need to be opened.
Getting started
For a center with one or more scanners, the desktop application covers both folder monitoring and the DICOM server with no development required. To bring upload into an existing system, the API documentation is the starting point.