ITero Case Flow
Introduction¶
iTero cases can go through different flows and different statuses. The scan files can change along the different steps of the flow.
Third parties developing a connection to iTero should be ready to support all case flows and statuses.
If using the scan notification mechanism, a scan notification is triggered with every change in the scan file(s). The notification includes RXID and account number.
What triggers a notification?¶
A scan yields the following artifacts:
- IDE file (zip)
- Thumbnails
- A file that can be viewed on myitero.com portal
- Screen captures if taken
When the artifacts are ready, a scan notification will be triggered.
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 change in status or a notification?¶
A DPMS should support all scan flows. A scan can trigger more than one notification or to be listed in different statuses in the returned response of 'Get Orders for Practice'.
The first event in the table 'After scanning' introduces a new scan with a 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 with a new status (while keeping the same order ID).
| Event | Description | Scan Status | Notification | |
|---|---|---|---|---|
| 1 | After scanning | Completed | Yes | |
| 2 | After modeling | Lab sent to modeling | iTero Modeling | |
| Modeling is completed | Lab Review | Yes | ||
| 3 | The scan is sent back to the doctor via API or myitero portal. The doctor rescans and sends the case back to the lab. | Lab sends the case back to the doctor | Scanning (For the Dr) | |
| Re-Scan is completed | Completed | Yes | ||
| 4 | The case goes through an interpretation 2 phase | The 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 with Align’s 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 no URL is provided, the scan notification will not be sent.