Scan Notifications
A scan notification is triggered with every change in the scan file(s). Scan cases can be changed in different scenarios.
The notification includes RXID and account number.
What triggers a notification?¶
A scan yields three artifacts:
- IDE file (zip)
- Thumbnails
- File that that can be viewed on myitero.com portal
The notification will be triggered for scans that are initiated by the Scan Request API or by the scanner or from myitero.com
When to expect a notification?¶
A DPMS should support all scan flows. A scan can trigger more than one notification or to re-appear again in the list returned from 'Get Orders for Practice' in different statuses.
The first event in the table 'After scanning' introduces a new scan with new scan ID. In case a scan continues with one of the flows, it will trigger another notification or be listed in the order's list again, and will keep its order ID.
| Number | Event | Description | Scan Status | Notifications |
|---|---|---|---|---|
| 1 | After scanning | / | Completed | Yes |
| 2 | After modeling | Lab sent to modeling | iTero Modeling | / |
| Modeling is completed | Lab Review | Yes | ||
| 3 | Scan is sent back to the doctor via API or myitero portal. The doctor rescans and send back to lab |
Lab send case back to doctor | Scanning | / |
| Re-Scan is completed | Completed | Yes | ||
| 4 | Case goes through interpretation 2 phase | Case goes to interpretation 2 | iTero Milling | / |
| Interpretation 2 is completed | Lab Review | Yes |
Note that a notification will be sent only when there is a change in the files.
Where will the notification be sent to?¶
A third party that is integrating to Align’s DPMS service can provide a notification URL upon registration, if it wishes to receive scan notifications. If no URL is provided, a URL can be provided in the pairing request for the account that is calling the pairing. If not URL is provided, the scan notification will not be sent.