Connections and credentials
Each integration card states its real availability: Live, Beta, Planned, File import, or Partner required. Only start setup for a connection method your clinic can actually use.
- Create a dedicated vendor credential when the vendor supports it.
- Grant only the permissions listed in the setup flow.
- Never place a secret in a screenshot, support message, frontend file, or public document.
- Replacing credentials should be followed by a test connection and sync review.
Sync activity and freshness
A Connected status confirms credentials were accepted; Sync activity shows whether records are arriving. A report's source choice determines whether it can use stored synchronized data, retrieve live data, or fail when the requested mode is unavailable.
- Investigate repeated failures rather than reconnecting blindly.
- Check the vendor account for expired credentials or changed permissions.
- Confirm the affected date range and patient before retrying.
Patient matching
Patient matching links one Orvexa patient to one record in a connected system. Review name, date of birth, contact details, and the source-system identifier. Similar names are not enough to confirm a match.
- Do not link when identity is uncertain.
- Correct the source record when the source itself is wrong.
- Review the selected patient again before generating or filing a report.
Troubleshooting a connection
Start with the most specific evidence: connection status, the latest sync event, the vendor response, and the affected operation. Record the time and integration, but do not copy patient content or credentials into support notes.