Issue #1 implementation slice

Build the card, review the signal, preserve choice.

No PHI by default. This prototype uses fake residents, staff review, role-specific display, local browser storage, and a visible stale-data warning.

staff workspace

Resident profile

Resident

Preferred name Demo location label Consent status Last reviewed

What matters in the first 60 seconds? Calming cue Dining preference Activity or conversation spark Approach to avoid

CNA/aide note Nurse note Volunteer note

controlled intake

Family signal

This is not for emergencies, symptoms, medication, diagnosis, abuse reports, or time-sensitive clinical needs. Call the facility or emergency services for urgent issues.

Resident Category

Note for staff review I understand staff must review this before it appears on a card.

human gate

Staff review queue

0 pending

local portability

Export or import demo data

Demo JSON

privacy threat model

Risk checks

Does the card reveal more than a worker needs for their role?
Can the resident or representative pause, revise, or delete?
Is the review date visible before anyone acts on the card?
Would a family conflict, sponsor, or visitor gain improper access?
Could this preference be used to coerce rather than honor?

pilot guide

First facility conversation

Show one fake resident card to CNA, dining, activities, nurse, and family reviewers.
Ask what would save time in the first 60 seconds of care.
Ask what details would feel invasive, unsafe, or childish.
Print one card and test it at handoff distance.
Revise the schema before using any real resident data.