Referrals

Referrals (inbound + outbound)

Two-direction referral tracking — patients you send out, patients sent to you. Lives inside any chart’s Referrals tab and the practice-wide worklist at /admin/referrals.

Outbound referrals

From an encounter, refer the patient to a specialist:

• Pick a specialist from your network directory (or external by NPI + name).
• Reason for referral + relevant clinical context.
• Sets a tickler at the target return date — if no records back by the date, the patient surfaces in the referral worklist for follow-up.

Persisted as a FHIR ServiceRequest with category referral.

Inbound referrals

External providers refer patients in via either:

• DirectTrust S/MIME secure messaging (clinician-to-clinician). Encrypted multipart MIME with detached PKCS#7 signature — spec conformant, not a gateway service.
• A web intake form at /refer/{practice-slug} (analogous to the public booking widget but for clinician referrals).

Inbound referrals create a Patient record (if new) + a Referral row + a pending-appointment task in the front-desk worklist.

Referral loop closure

After the consult, the consultant sends a note back through DirectTrust. Pollen8 parses the inbound document into a FHIR DocumentReference and attaches it to the original Referral. The loop closes — the originating PCP sees the consult note inline.

Network previsit

Before a referred patient arrives, Pollen8 runs:

• Eligibility check.
• Intake form delivery (capture demographics + ROS + medications + insurance card).
• Prior-auth check if the planned visit type requires it.

Patient walks in already verified.