decision-record · supabase_json

Patient Visit Advocate decision-record M-00

decision-record artifact · for Patient Visit Advocate · phase M-00 · status approved

Planning Surface

Use this to decide what happens next.

Status

approved

Phase

M-00

Agent Handoff

Start Here

decision-record artifact · for Patient Visit Advocate · phase M-00 · status approved

Completion Evidence

No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.

Artifact Shape

Structured Payload

phase

M-00 Safety and Product Boundary

decisions

id	status	decision	implications
D-001	accepted	Build V1 as mobile-first responsive web/PWA.	- No native app store review path for MVP - Responsive appointment-room readability still matters - Installable PWA can be evaluated after first prototype
D-002	accepted	Allow anonymous local-only prep only before server/model processing; require account and affirmative express consent before storage or AI generation involving health text.	- Local draft cannot sync across devices - User must consent before generated brief/question plan if generation is server-side - Account required for longitudinal memory
D-003	accepted	Realtime in-room mode remains post-MVP.	- MVP does not record live appointment audio - No ambient clinical capture in first slice - Post-visit notes are user-entered

created at

2026-05-05T13:54:44.019Z

project id

31d7f681-bed2-44e9-9a55-b9fadcbba0da

schema version

1.0

official sources

id	url	title	relevance
FDA-CDS-2026	https://www.fda.gov/media/191560/download	FDA Clinical Decision Support Software guidance transcript	Avoid outputs that provide specific diagnostic or treatment directives or replace clinician judgment.
HHS-MHEALTH	https://www.hhs.gov/hipaa/for-professionals/special-topics/health-apps/index.html	HHS/OCR Resources for Mobile Health Apps Developers	Use the federal mobile health app interactive tool to evaluate HIPAA, FTC Act, Health Breach Notification Rule, FD&C Act, COPPA, and related obligations.
FTC-MOBILE-HEALTH-BEST-PRACTICES	https://www.ftc.gov/business-guidance/resources/mobile-health-app-developers-ftc-best-practices	FTC Mobile Health App Developers: Best Practices	Requires clear notice/affirmative express consent, strong encryption, vulnerability management, data inventory, and transparent privacy/security statements.
FTC-HHS-TRACKING-RISK	https://www.ftc.gov/news-events/news/press-releases/2023/07/ftc-hhs-warn-hospital-systems-telehealth-providers-about-privacy-security-risks-online-tracking	FTC and HHS warning on health data tracking technologies	Health apps and telehealth surfaces must avoid impermissible or undisclosed disclosure of sensitive health data to third-party trackers.