Referral Management

Track specialist referrals from request through authorization, scheduling, consult, and follow-up with owner and status visible. This example brings Requested and Authorized together so patients and care teams can find the next task without losing context.

It includes representative records such as Cardiology referral and Dermatology consult. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Referral Management
Use this template in Figr

Template facts

Screen

Board

Primary action

Create referral

Pattern

Board

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Care team members need to create referral while keeping open referrals, awaiting auth and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Requested gives users an obvious place to start.
  • Supporting view: Authorized keeps the related context close.
  • Primary action: Create referral stays visible when people need it.
  • First signal: Open referrals shows a useful value (28).
  • Second signal: Awaiting auth gives additional context (7).
  • Sample record: Cardiology referral.
  • Next record: Dermatology consult.

States worth designing

  • No cards in this stage: say what changed, protect progress, and offer a clear next step.
  • Movement in progress: say what changed, protect progress, and offer a clear next step.
  • Move blocked by rules: say what changed, protect progress, and offer a clear next step.
  • Ownership updated: say what changed, protect progress, and offer a clear next step.
  • Archived item restored: say what changed, protect progress, and offer a clear next step.
  • Permission to edit missing: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Requested → Authorized → Create referral → Review outcome

Patterns used

Board, Requested, Authorized, contextual actions, error recovery

Why these choices work

Use real domain stages with a clear owner. Confirm high-impact moves and explain when permissions or missing work block an item.

Pay attention to requested and authorized. People need to distinguish Cardiology referral from Dermatology consult. Keep open referrals visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Create referral”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Insurance Verification, Telehealth Visit, Care Team Messaging.

Start from this in Figr

Design a referral management screen inside our existing product. Use our current components, tokens and content language. Include Requested and Authorized views, credible records like Cardiology referral, and a clear “Create referral” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr