rubyforgood / rubyforgood/alongwithyou
Health Care Preferences screen
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 16
Description
Description
What the patient wants from their care day to day — communication preferences,
what matters to them, things a new clinician should know. Distinct from #45,
which is about legal documents.
This ticket needs scoping before it needs a developer. Nothing in the repo
defines it, and it is the vaguest of the seventeen. It may well be mostly
free-text prompts rather than structured fields, which is a legitimate answer
but should be a decision rather than a default.
Fields — need confirming, nothing in the repo specifies this screen
Suggested starting point, as prompts rather than a form:
- How I prefer to be communicated with
- What matters most to me in my care
- Things a new clinician should know
- Notes
Acceptance Criteria
- Scope agreed with the product owner before any code, including structured-vs-free-text
- Single-record profile, edited in place
- Persists to the encrypted local database and survives a relaunch
- Prompts phrased so they work for a caregiver typing on someone's behalf (0004)
- WCAG-aligned; long free-text fields remain usable with a screen reader
- Covered by unit tests
Additional Info and Resources
- 0004's open sub-question about tone and pronouns bites hardest here, because this screen is written in the first person. Decide once and apply everywhere rather than per-screen
- Free-text-heavy screens are the ones most likely to need the PDF export to reflow well (0002)
QA
- Enter long free text, relaunch, confirm nothing is truncated
- VoiceOver/TalkBack through the screen, including the long fields
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading docs/decisions/0004-primary-user-caregiver-role.md and docs/decisions/0002-pdf-export-legal-privacy.md, then resolve the product scope and structured-versus-free-text decision before locating implementation files. Done means the agreed single-record screen persists through relaunch, supports caregiver wording and accessibility, and has unit and long-text QA coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, database, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100