Choose a vendor route or use Abe separately
Who this is for
This guide is for a practice or hospital arranging non-patient reference access alongside its existing software. The vendor integrations listed here remain unavailable until their exact contract and acceptance evidence exist. Public API documentation is not an Abe partnership, a current price or permission to install in a customer environment.
Start here
- Identify the exact product, version, practice or hospital and reference purpose. Desktop and cloud products, separate sites and different clinician roles need their own acceptance.
- Use Abe separately through your own normal login while integration is gated. Start with Professional development, Rules and standards or the authorised Governance and readiness journey. There is no patient data exchange in this companion path.
- Open the specific product guide below. Ask for its written contract, supported route, scope, current fees and next acceptance deliverable. Fees remain unconfirmed; do not rely on historical tariffs or another vendor's approval.
- Before any installation, have the authorised owner approve the exact environment and witness correct identity/site, the intended reference or SOP, forbidden-scope denial, expiry, revocation and companion recovery. Paying for Abe does not complete these gates.
| Product | Guide and acceptance focus |
|---|---|
| MedicalDirector Clinical | Signed Sidebar panel |
| MedicalDirector Helix | Production SMART launch |
| Halaxy | Server-only practice credentials |
| Zedmed | Reference API scope and practice database |
| Best Practice | Partner Network and Halo |
| Cliniko | Server-held user key and separate person |
| coreplus | Reviewed server add-on |
| Gentu | Marketplace practice pairing |
| Genie | Separate desktop contract |
| Oracle Health | Hospital identity/reference launch |
| Epic | Hospital-approved clinician launch |
What success looks like
Companion use shows the intended Abe account, permitted service and current source-backed result. An integration route additionally needs a witnessed result for the exact vendor product, version, practice and permission, plus expiry/revoke denial. A menu item, API key, registration or sandbox result alone is insufficient. Governance remains organisation-bound; source redistribution must be permitted for the exact use.
If it does not work
If the integration route has no accepted contract or its account/site is wrong, keep it unavailable and use the companion. Do not paste patient information or vendor credentials into Abe, chat or support. Send the product name, version, intended non-patient task and safe error to support. No generic browser embed or clinician single sign-on is assumed.
Stop or change your choices
Use the vendor's confirmed revocation process and the affected Abe application's supported disconnection separately, then verify old access is denied. Until that process is accepted, do not activate the integration. Disconnection is not cancellation of funding or deletion of personal preferences. See Manage and cancel.