Alongside your EMR

Who this page is for: the practice manager worried this is another EMR project - it is not, and this page explains exactly where Refera sits.

Refera does not replace your EMR. Its connected Inbox and ready-to-enter cards sit beside the EMR rather than writing into it. That design holds for Best Practice, Genie, Gentu, Zedmed, Medical Director, and cloud-native EMRs with no local folder.

No EMR permission for the ready-to-enter path

The current connection uses the practice’s dedicated Microsoft 365 referrals mailbox, after its named setup, access and activation checks. Fax-to-email can enter through that mailbox when the practice already uses it; Refera does not supply a fax number or a new fax delivery route.

Gmail, IMAP, HealthLink, Medical-Objects and direct upload are not available to connect today. Request access to record the route your practice needs. Keep existing referral delivery in place.

Nothing is installed in your EMR - no plug-in, no database access, no vendor negotiation. HealthLink remains partner-gated. Do not grant a drop-folder path or redirect an EDI mailbox in anticipation of support.

The connected Inbox handoff

Refera does not write into your EMR. The current connected Inbox lays out a ready-to-enter card for each verified referral:

• The demographics field by field, in a consistent ready-to-enter order - surname, given names, DOB, Medicare number, phone, address, referrer and provider number.
• One-click copy per field, or copy all fields at once.
• The available source excerpt and attachment metadata alongside the extracted fields. Staff continue to use the practice’s existing original-document path until Refera’s source-object lifecycle is deployed and activated.
• A sealed filed-to-your-EMR confirmation once staff record the filing, so the chain of custody shows the loop ended inside the EMR record.

The source excerpt remains verbatim. Administrative fields are extracted and checked by staff; missing fields stay missing and are never invented. Write-back is a later step that needs EMR vendor permission - we say so plainly.

The separate Handoff route shown in the recording below is an evaluated design exploration. It is not included in the licensed connected artifact.

Design recording with fictional details and no patient information. The connected Inbox keeps the ready-to-enter field layout; the standalone route and any source-document tile shown here are not current connected-product claims.

The cloud-EMR note

A cloud-native EMR has no local folder - the vendor operates the HealthLink endpoint inside their cloud. Whether HealthLink will re-point an in-use address to a Refera relay endpoint is an open question being resolved through HealthLink’s written partner assessment and applicable technical profile and conformance process. Refera has no live SMD transport enabled and does not claim HealthLink conformance. Refera does not assume that a second EDI, parallel delivery or re-pointing is available; HealthLink must confirm the supported pattern in writing. We do not claim this works until that answer and the interface-specific evidence exist. Any post-delivery copy from a server or hosted EMR also needs a supported interface and those checks. Existing HealthLink delivery into the practice’s supported PMS interface stays in place.

The line that matters

Analytics that reads from your EMR can only see what was typed into it. Once a verified customer channel is explicitly activated, Refera can account for what reaches that channel before staff enter it into the EMR.