Pharmacy Workflow OS MVP

Case Workflow

Create a new injection case in a route built for intake and handoff.

This screen should feel procedural, not crowded: verify access, capture patient details, then move straight into the live case workspace.

Dedicated intake route

Role-aware routing

Direct case launch

Back to Home

Before You Submit

Keep intake clean and sequential.

Confirm the active Supabase role metadata or local fallback actor context.

Collect patient identity, DOB, and contact details before starting.

Switch to an address only when the injection location is in-home.

Session Access

Keep access visible before entering the workflow.

Loading session

Protected routes require a Supabase access token whose user metadata resolves to `Tech`, `Pharmacist`, or `Admin`, so this panel stays focused on authentication and role status only.

Primary sign-in

Use Google when the team already works from managed Supabase accounts.

Email and password

Password

Passwordless fallback

Send a magic-link sign-in email when passwordless access is enabled for the current Supabase project.

Intake Flow

01 · Access

Verify the authenticated user or local actor context first.

02 · Capture

Enter patient demographics and the injection setting cleanly once.

03 · Handoff

Create the case and move directly into the gated workflow workspace.

Intake Entry

Create a new injection case

Use this screen to capture the patient setup cleanly, then move straight into the gated workflow. Production case creation should run under a Supabase session with valid role metadata.

Use verified Supabase access when available.

Capture only the patient details needed to start the workflow.

Move directly into the case workspace after creation.

Execution context

No verified role metadata on session

Fallback actor context is available for local testing.

No Supabase session is active. Local environments can still use fallback actor headers when insecure header auth is enabled, but production should use the Supabase flow above.

Patient full name

DOB

MM/DD/YYYY

Phone

Format: (555) 555-5555

Injection location

Address is required if location is In-home.

Address

Start typing to search verified addresses through Google Places.

Fallback actor context

This is only useful in environments where header-based auth is intentionally enabled. When valid Supabase role metadata exists, the app will use that session instead.

Staff user ID

Role

Workflow outcome

On success, the app creates the case record and routes you directly into the case workspace for eligibility, education, consent, sign-off, and packet completion.

This screen should be the shortest part of the workflow.