Medical Portals — name/URL only

Description

The patient's online portals, recorded so they can find them — not so they
can log in from this app. Repeatable-entry list.

This screen is defined as much by what it excludes as what it holds, so read
0006 before starting.

Fields

• Portal name
• URL
• Notes

Excluded, per 0006:
passwords, secrets, and usernames. The password exclusion is the settled
boundary text; the username exclusion is the "known inconsistency" 0006 flags —
this ticket is where it already goes further than the written boundary, and 0006
recommends the boundary be extended to match. A username without a password is
low risk alone, but paired with the portal name and URL it tells someone exactly
which account to target.

No "log in" button, no WebView that captures credentials, no autofill
integration. A link that opens the system browser is fine.

Acceptance Criteria

• Add, edit, delete against the encrypted local database
• No username, password, PIN or secret field in the UI, the schema, or the types
• Opening a portal hands off to the system browser rather than an in-app authenticated view
• Built on the #49 component
• Ships its migration
• WCAG-aligned; copy neutral per 0004
• Covered by unit tests

Additional Info and Resources

• 0006 — this ticket is named in it as the one that already goes beyond the stated boundary
• If a reviewer asks for a username field "since it's encrypted anyway", the answer is in 0006's rationale and Paul's sign-off note: excluded means not in the data model today

QA

• Add a portal, relaunch, confirm it persists
• Tap the URL and confirm it opens outside the app
• Search the diff for password, username, login, secret — expect nothing
• VoiceOver/TalkBack through add, edit and delete

Read docs/decisions/0006-excluded-field-safety-boundary.md first, then locate the #49 component and the encrypted local database entry points. Verify how migrations, browser handoff, accessibility checks, and unit tests are organized before implementing the portal flow. Done means the listed acceptance criteria and QA checks pass without username or credential fields.