Patient Visit Advocate plan MVP-01
plan artifact · for Patient Visit Advocate · phase MVP-01 · status approved
plan artifact · for Patient Visit Advocate · phase MVP-01 · status approved
No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.
- slices: 3 items
- status: ready_for_owner_review
- plan json: phases: object, version: string, project_id: string, project_name: string, execution_rule: string, recommended_slice: string
- plan name: Patient Visit Advocate Reviewable Build Plan
- project id: 31d7f681-bed2-44e9-9a55-b9fadcbba0da
- updated at: 2026-05-08T04:02:11.152Z
- owner review: approve_to_start: object, decisions_not_needed_now: object, decisions_needed_before_later_public_patient_work: object
- artifact type: plan
- planning goal: Move from accepted Q&A source/import specs to a bounded first build slice that can be approved without reopening broad product strategy.
- project title: Patient Visit Advocate
- recommendation: name: string, reason: string, approval_ask: string, first_slice_id: string
- schema version: 1.0
Machine-readable source fields
| id | goal | name | status | scope in | scope out |
|---|---|---|---|---|---|
| PVA-SLICE-01 | Create the product-data foundation for the accepted 250-row Q&A seed, run a dry-run import, and expose internal review state without making any content public. | Q&A Seed Ingestion and Internal Review Console | ready_for_owner_review | - Projects/Product DB migration for qna_import_batches, qna_clusters, qna_items, qna_lint_findings or accepted equivalent names - dry-run parser/importer contract with checksum and exact row-count guardrails - controlled import path that creates a batch and defaults all rows to blocked review state - internal review artifact or admin-console spec showing lint, review, provenance, and publish-blocked states - verification report proving accepted 250-row seed imported or dry-run validated as expected | - public patient UI - AI generation from Q&A rows - diagnosis or treatment recommendation features - legal launch approval - caregiver/family plan UI - full visit-prep conversational intake |
| PVA-SLICE-02 | Turn client compliance boundary into enforceable lint rules, review categories, and draft disclaimer copy. | Safety Copy and Lint Rules | planned_after_slice_01 | ||
| PVA-SLICE-03 | Prepare the patient-facing visit-prep implementation plan once model/provider, retention, caregiver, and launch-review decisions are resolved. | Visit Prep MVP Decision Package | owner_decision_required_later |
ready_for_owner_review
| id | name | tasks |
|---|---|---|
| phase-1 | Q&A Product Data Foundation | - Migration Safety Review: role: string, brief: string, title: string, local_id: string, depends_on: object, output_path: string, acceptance_criteria: object - Implement QNA Migration: role: string, brief: string, title: string, local_id: string, depends_on: object, output_path: string, acceptance_criteria: object - Build Dry Run Importer: role: string, brief: string, title: string, local_id: string, depends_on: object, output_path: string, acceptance_criteria: object - Review Console Spec: role: string, brief: string, title: string, local_id: string, depends_on: object, output_path: string, a |
1
31d7f681-bed2-44e9-9a55-b9fadcbba0da
Patient Visit Advocate
Do not start build until Justin approves this plan artifact. After approval, implementation tasks target Projects/Product DB only.
PVA-SLICE-01
Patient Visit Advocate Reviewable Build Plan
31d7f681-bed2-44e9-9a55-b9fadcbba0da
2026-05-08T04:02:11.152Z
- PVA-SLICE-01 only
- model/provider
- caregiver MVP
- public navigation
- retention default
- legal launch reviewer
- model/provider handling path
- legal/medical review owner
- retention policy
- caregiver MVP scope
- first-release patient screens
plan
Move from accepted Q&A source/import specs to a bounded first build slice that can be approved without reopening broad product strategy.
Patient Visit Advocate
Q&A Seed Ingestion and Internal Review Console
The Q&A source verification, ingestion/provenance model, and schema/migration spec are accepted. This slice moves the project forward without requiring model/provider selection, public patient UI, legal launch approval, caregiver scope, or retention decisions.
Approve this slice for implementation against the Projects/Product DB only, with no public launch and no medical advice generation.
PVA-SLICE-01
1.0
| role | artifact type | module | status |
|---|---|---|---|
| product goal and scope boundary | intent | ||
| Pocket Advocate client-source compliance boundary | client-source-reference | ||
| client-source integration requirements | compliance-gap-review | ||
| module-spec | M-02A Q&A Source Verification | accepted | |
| source-verification-report | accepted_for_v1_seed_scope | ||
| module-spec | M-02B Q&A Ingestion and Provenance Model | accepted | |
| schema-or-migration-spec | accepted | ||
| Q&A review and disclaimer UX acceptance criteria | feature-ux-spec | ||
| medical safety, privacy, consent, and output boundary rules | policy |
- Accepted source scope is the provided 250-row Pocket Advocate Q&A seed; the 1,000+ corpus claim is not V1 import scope.
- All Q&A product tables belong in the Projects/Product DB, not the RedKey platform DB.
- Imported Q&A rows default to lint pending, review pending, and publish blocked.
- No public UI, patient-facing Q&A library, or AI output path may consume rows until lint/review and legal/UX gates pass.
- Q&A content must preserve provider-question framing and cannot become diagnosis, treatment, or directive medical advice.
- model/provider path for health-sensitive generation
- public launch legal/medical reviewer assignment
- caregiver/family UI scope
- raw intake retention period decision
- patient-facing Q&A navigation decision
- conversational intake generation implementation