Connections
Start with Oralstack. Connect only what your clinic needs.
The default path is a guided standalone pilot. Patient, schedule, clinical, checkout, and operations modules become the clinic's working record only after their setup and ownership boundaries are verified.
Optional clinic connection
Plato clinic API
How ownership works
Keep Plato authoritative when your clinic needs it.
Plato is an optional clinic-configured connection. When selected, Oralstack coordinates the reception, chairside, checkout, and manager handoffs around the Plato record without silently changing which system is authoritative.
Request a connection assessment- Connect01
Connect the existing clinic record
A clinic that chooses this path can use supported Plato-backed provider availability, patient context, and appointments inside the Oralstack workspace after connector review.
- Work02
Coordinate the handoffs around the record
Run reception, chair status, requests, patient context, checkout preparation, clinic operations, and manager review while Plato remains authoritative for the agreed records.
- Review03
Keep changes back to Plato explicit
Appointment creation and cancellation use reviewed Plato-backed paths. A reschedule remains a staff-applied proposal, and checkout work never implies a silent claim or payment posting.
Before a clinic goes live
- For clinics using this connection, Plato remains the system of record for patient identity, supported schedule writes, and invoice writeback.
- Sync health, update status, and audit history remain visible to staff.
- A local fallback is never described as a delivered Plato writeback.
- Clinic credentials, connector access, enabled modules, and rollout scope are reviewed before a pilot starts.
Production-state snapshot recorded 20 July 2026. This is product evidence, not a claim that every clinic connector is ready without review.
Other connections
Review every external capability by rollout state.
Open a category for the exact boundary. “Configured pilot” means credentials, deployment setup, and readiness review are still required; it does not mean general availability.
Patient communication1 configured pilot · 1 not enabled
The transport, credentials, consent, and sending mode determine what can be enabled for each clinic.
- Configured pilot
Meta WhatsApp Business Cloud API
Clinic-owned Meta credentials can enable webhooks, a shared inbox, manual replies, and approved templates after a readiness review.
- Not enabled
WhatsApp Flows and reminder automation
Automated intake, reminder, and live-send worker controls are off in the latest recorded production configuration.
Payer workflows1 available · 2 not enabled
Oralstack can support the clinic-side estimate and reconciliation workflow without claiming an external government submission.
- Available
CHAS estimate and payer tracking
Tier guidance, an Oralstack estimate, checkout splitting, and manual reconciliation. CHAS and the clinic's existing system remain authoritative.
- Not enabled
SmartCMS electronic submission
The claim lifecycle is implemented locally, but the outbound SmartCMS gateway is deliberately not connected.
- Not enabled
MediSave electronic claims
Eligibility can be represented in the local workflow; no production MediSave submission transport is claimed.
Accounting and exports2 available · 1 not enabled
Reviewed exports are available for handoff. Direct accounting-system posting is a separate capability and is not implied.
- Available
Finance reconciliation CSV
Copy reviewed finance reconciliation data as CSV for an accountant or an existing accounting workflow.
- Available
Clinic insights CSV
Export the currently displayed clinic-insights view for local review and analysis.
- Not enabled
Direct Xero OAuth and posting
There is no direct Xero connection or automatic posting. Use the reviewed CSV handoff instead.
Identity and access2 available · 2 not enabled
Current access controls are native to Oralstack. External identity-provider support is listed separately so it is not mistaken for active SSO.
- Available
Password sign-in and TOTP MFA
TOTP enrolment and sign-in checks are implemented. Clinic-wide MFA enforcement is not enabled in the latest recorded production configuration.
- Available
Organization and clinic access
Authorized organization owners and managers can administer membership and exact clinic access across a multi-clinic group.
- Not enabled
Google Workspace or Microsoft Entra SSO
No production Google or Microsoft staff SSO is currently represented.
- Not enabled
SCIM provisioning
The route surface is dark and the latest recorded production flag is off.
Imaging exchange3 not enabled
Generic DICOM work has been built and tested behind dark-launch controls; that is not the same as a production imaging integration.
- Not enabled
Generic DICOMweb ingest and viewer
Tenant-scoped ingest and viewing exist for controlled evaluation, but the latest recorded production flags are off.
- Not enabled
Calibrated image measurements
Requires calibration metadata plus clinical and regulatory approval; uncalibrated images do not fabricate millimetre values.
- Not enabled
Named sensor-device bridges
No production sensor SDK connector is currently advertised as available.
Plan the record model before connecting another system.
Start with the guided standalone path, then identify any existing records, exports, or optional connections the clinic needs before go-live.