Skip to main content
Reporting on all referrals sent out by your practice For reporting on but not limited to:
  • Your referral network
  • Count of who you are sending referrals out to
  • The status of your referrals
  • How many specialty referrals you are sending out
  • What type of diagnosis codes are used when sending out referrals
  • Which visit or non-visit note a referral was placed from

Key columns

signed_by_user_id records the provider the referral was signed under. When an authorized referrals delegate signs a referral on behalf of a provider, signed_by_user_id still holds the provider — not the staff member who performed the signing action. The referral_order table does not expose the delegate signer identity, and neither does the API’s signed_by field on the Referral Order object. created_by_user_id records the user who created the referral. When created_by_user_id differs from signed_by_user_id, a staff member prepared the referral for a provider to sign or signed it as a delegate. Comparing the two columns is the closest approximation available in HDB for identifying referrals handled by a delegate. prescribing_user_id records the provider responsible for the referral order and typically matches signed_by_user_id. visit_note_id and non_visit_note_id name the note each referral was placed from, and are empty for a referral created outside a note. See Orders placed from a note. If you have any questions about this topic please reach out to Elation Support Portal with the subject line HDB - <your_question>