Avized separates a vendor-listed integration from what buyers actually need to know: method, directionality, write-back, capabilities, limitations, evidence, and last verification.
Vendor integration signals
735
Listed across Avized vendor profiles
Systems named
246
PMS, imaging, workflow, APIs, and other systems
Evidence-backed
19
Structured relationships with confidence and source fields
How to read this page
A vendor profile saying “Dentrix” is a discovery signal. Avized only calls a relationship evidence-backed when the relationship and source are captured separately. We do not assume “integration” means bidirectional, real-time, or write-back.
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.
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.
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.
Discovery layer
Listed integration signals
Useful for discovery. These have not yet been upgraded to evidence-backed relationships.