MethodPearl-stated native integration
DirectionalityNot publicly documented in the cited source
Evidence ownerPearl
What this does not prove: Pearl lists Eaglesoft as a native Practice Intelligence integration, but the cited page does not document exact technical method, data direction, or write-back behavior.
MethodPearl-stated native integration
DirectionalityNot publicly documented in the cited source
Evidence ownerPearl
What this does not prove: Pearl lists Open Dental as a native Practice Intelligence integration, but the cited page does not document exact technical method, data direction, or write-back behavior.
MethodNative Dentrix Ascend integration embedded in the clinical imaging workflow
DirectionalityReal-time AI findings are surfaced inside Dentrix Ascend; broader bidirectional data write-back is not established by the cited source
Evidence ownerPearl
What this does not prove: The cited source establishes native workflow integration and real-time findings, but does not establish broad bidirectional PMS write-back across all Pearl modules.
MethodHenry Schein One API Exchange authorized integration
DirectionalityNot publicly documented for all Pearl modules
Evidence ownerPearl
What this does not prove: The cited source confirms authorized integration status but does not document every data object, direction, or write-back workflow.
MethodNative Pearl capabilities embedded in Curve Dental SuperHero
DirectionalityReal-time radiologic support and Practice Intelligence are embedded; general PMS write-back directionality is not publicly documented
Evidence ownerPearl
What this does not prove: The cited source confirms embedded Pearl capabilities in Curve but does not establish every data object or general-purpose bidirectional write-back.
MethodDirect PMS integration; technical connector not publicly described
DirectionalityNot publicly documented
Evidence ownerWeave
What this does not prove: Weave documents that it integrates with Curve in a customer case study, but the source does not specify protocol, data objects, directionality, or write-back behavior.
MethodPatterson Fuse integration
DirectionalityBidirectional: patient/appointment data sync + confirmation write-back
Evidence ownerWeave
What this does not prove: The source documents confirmation write-back and regular data synchronization; additional write-back behavior should be validated feature by feature.
MethodDirect DSN integration; exact technical method not publicly described
DirectionalityDSN → Weave synchronization documented; write-back not established
Evidence ownerWeave
What this does not prove: Weave says the systems synchronize throughout the day, but the source does not establish a specific API/protocol or broad bidirectional write-back.
MethodDirect Eaglesoft integration
DirectionalityReal-time bidirectional sync
Evidence ownerRevenueWell
What this does not prove: The cited first-party page describes real-time bidirectional syncing; module-level data behavior should still be validated during implementation.
MethodDirect Open Dental integration
DirectionalityBidirectional workflow with 15-minute patient-data sync and forms/document write-back
Evidence ownerRevenueWell
What this does not prove: RevenueWell documents a 15-minute sync cadence and data moving into Open Dental for forms/documents; exact behavior varies with Open Dental version.
MethodDirect Dentrix Ascend integration
DirectionalityBidirectional: scheduled appointment and forms/selected data write-back
Evidence ownerRevenueWell
What this does not prove: RevenueWell notes that write-back applies only to supported primary providers for direct scheduling and that some forms are PDF-only.
MethodDenticon integration; V2 API enables deeper form write-back
DirectionalityPrimarily Denticon → RevenueWell sync; selected form and verification PDF write-back with V2 API
Evidence ownerRevenueWell
What this does not prove: RevenueWell says new appointment requests are manually entered into Denticon; form write-back depth depends on the Denticon V2 API and requires in-PMS review/import for some data.
MethodDentrix Connected partner integration
DirectionalityBidirectional
Evidence ownerRevenueWell
What this does not prove: RevenueWell documents bidirectional syncing and several write-back workflows; exact behavior can vary by Dentrix version and RevenueWell module.
MethodHenry Schein One API Exchange / authorized integration
DirectionalitySchedule and patient-data sync; feature-specific write-back varies
Evidence ownerWeave
What this does not prove: First-party documentation confirms authorized integration and named workflows, but does not describe every data object or write-back behavior across all Weave modules.
MethodHenry Schein One API Exchange / authorized integration
DirectionalitySchedule and patient-data sync; feature-specific write-back varies
Evidence ownerWeave
What this does not prove: First-party documentation confirms the Dentrix Ascend integration and named workflows, but not every supported data object or write-back behavior.
MethodWeave PMS scheduling integration
DirectionalityBidirectional scheduling: PMS availability sync + appointment write-back
Evidence ownerWeave
What this does not prove: The cited source documents scheduling-related bidirectional behavior; it should not be interpreted as proof that every Weave feature writes back to Eaglesoft.
MethodWeave PMS scheduling integration
DirectionalityBidirectional scheduling: PMS availability sync + appointment write-back
Evidence ownerWeave
What this does not prove: The cited source documents scheduling-related bidirectional behavior; it should not be interpreted as proof that every Weave feature writes back to Open Dental.
MethodDocumented Carestream partnership / workflow access; exact technical method not publicly documented
DirectionalityNot publicly documented
Evidence ownerOverjet
What this does not prove: First-party source confirms Carestream Dental customer access to Overjet X-ray AI, but does not establish CS 1500/1600 visible-light intraoral-camera image analysis, bidirectional write-back, or a specific integration protocol.
MethodCBCT compatibility; exact import/connector method not publicly documented
DirectionalityNot publicly documented
Evidence ownerDiagnocat
What this does not prove: Diagnocat explicitly lists Carestream among compatible CBCT brands. Model-level support and technical method are not specified, and this does not establish support for CS 1500/1600 intraoral-camera photographs.