Your avatar (live preview)
Updates as you select below
CHW Team Member 03
Queens · vehicle · English
Live
On route
CHW onboarding
Customize your field avatar.
The avatar you pick here is what providers see on the live field map and what your patients see when you arrive. All selections are held in-memory only — there's no backend, no persistence, and no credential stored. This is a simulated walk-through of the onboarding flow.
Step 1 · Pick an avatar style
20 portrait templates available · each can be combined with a uniform color below
Click any portrait to set it as your CHW avatar. Selections are not persisted.
Step 2 · Uniform / ring color
Used as the avatar ring on the field map
Evidence green
Healthcare blue
Caution amber
Critical red
Substrate navy
Color choice does not affect ring status semantics on the live field map.
Step 3 · Travel mode
Affects route summary & ETA
Vehicle
Walk
Transit
Bike
Mixed
Step 4 · Service region
Default patient panel for daily route
Queens Village + Cambria Hts
Jamaica + St. Albans
Laurelton + Springfield Gardens
Elmont + Valley Stream (LI edge)
Step 5 · Language preference
Affects on-screen labels & voice capture defaults
English
Spanish
Bengali
Mandarin
Haitian Creole
Punjabi
Step 6 · Accessibility & field preferences
Tunes the field workspace for you
Large-text mode
High-contrast map
Reduce motion
Voice capture by default
Save & continue (simulated)
In-memory only · no backend · no persistence
In the real deployment, this step would write your CHW field profile to the substrate, emit an audit-ledger entry into the Platform / Auth / Audit ledger, and provision your live field avatar on the provider command center. For this prototype the "Save" button is non-functional.
No selection is persisted. No localStorage. No cookies. No backend call.
Future onboarding posture
In a real deployment, this avatar wizard becomes part of the governed CHW onboarding flow. The selected avatar style and ring color are written to the Platform / Auth / Audit ledger. Travel mode, service region, and language preference are written to the Workforce / Payroll ledger. None of those writes happen in this prototype. There is no backend behind the wizard.