client-source-reference · supabase_json
Patient Visit Advocate client-source-reference
client-source-reference artifact · for Patient Visit Advocate · status approved
Agent Handoff
Start Here
client-source-reference artifact · for Patient Visit Advocate · status approved
Completion Evidence
No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.
Artifact Shape
- files: 2 items
- source: client-provided kickoff documents
- product: Pocket Advocate / Patient Visit Advocate
- created at: 2026-05-07T13:21:40.696Z
- project id: 31d7f681-bed2-44e9-9a55-b9fadcbba0da
- schema version: 1.0
- core distinction: operating_line: string, allowed_patient_education: object, disallowed_medical_advice: object
- knowledge base workbook: note: string, categories: object, summary_claims: object, observed_sheets: object, compliance_banner: string
- content review checklist: 10 items
- language patterns to fix: 5 items
- future content principles: 5 items
- required structural changes: 4 items
Structured Payload
Machine-readable source fields
files
| date | name | path | status | purpose | version |
|---|---|---|---|---|---|
| May 2026 | pocket_advocate_dev_reference.docx | C:/Users/jstnk/Downloads/pocket_advocate_dev_reference.docx | Action required before public launch | Implement medical advice compliance across the Q&A knowledge base and app UI | 1.0 |
| pocket_advocate_all_waves.xlsx | C:/Users/jstnk/Downloads/pocket_advocate_all_waves.xlsx | Revised Q&A database framed as questions to ask a provider, not medical advice |
source
client-provided kickoff documents
product
Pocket Advocate / Patient Visit Advocate
created at
2026-05-07T13:21:40.696Z
project id
31d7f681-bed2-44e9-9a55-b9fadcbba0da
schema version
1.0
core distinction
operating line
The app gives patients the vocabulary and courage to ask questions. Their provider gives them the answers.
allowed patient education
- Helping patients ask better questions
- Explaining what a condition is in general
- Explaining patient rights and system navigation
- Providing vocabulary to use with providers
- Raising general awareness of warning signs
disallowed medical advice
- Telling a patient what treatment to pursue
- Stating specific clinical thresholds as universal facts
- Naming specific drugs as preferred or superior
- Providing triage criteria for emergencies
- Directing patients to take specific clinical actions
knowledge base workbook
note
Workbook summary claims 1,000+ Q&As, but direct sheetData extraction from the provided XLSX observed 253 nonempty rows on the master sheet. Treat this as a source-file verification item before implementation.
categories
- Preparation
- Your rights
- Safety
- Logistics
summary claims
waves
8
answer format
- What to Know
- Questions to Ask Your Provider
- What to Watch For
total qas label
1,000+
answer categories
4
specialist clusters label
50+
observed sheets
| name | observed nonempty rows | clusters |
|---|---|---|
| Summary & Index | 15 | |
| W1 OB?GYN & Adult | 44 | - OB/GYN - Cardiology - Neurology - Geriatrics - Endocrinology - Nephrology - Urology |
| W2 High-Priority | 38 | - Oncology - Orthopedic Surgery - Rheumatology - Pulmonology - Gastroenterology - Dermatology |
| W3 Surgical | 38 | - General Surgery - Vascular - Ophthalmology - ENT - Colorectal - Pain Management |
| W4 Women?Mental | 38 | - MFM - REI - Urogynecology - Psychiatry - Addiction Medicine - Palliative Care |
| W5 Pediatric | 38 | - Pediatric Cardiology - Pediatric Neurology - Developmental Pediatrics - Pediatric Endocrinology - Pediatric GI - Pediatric Orthopedics |
| W6 Hospital Nav | 38 | - ER - Discharge - Insurance Denial - Medical Records - Surgery Prep - Telehealth |
| W7 Emerging | 38 | - Genetic Counseling - Integrative Medicine - Rare Disease - Caregiver - Neuropsychology - Occupational Medicine |
| W8 Coverage | 44 | - DME - Prior Authorization - Prescription Coverage - Medicare - Medicaid - Medical Bills - Surprise Billing |
| Master ? All Q&As | 253 |
compliance banner
General educational information only ? not medical advice. All Q&As help patients ask better questions of their healthcare providers.
content review checklist
- Every actionable item uses question framing, not directives.
- No specific clinical numbers are stated as universal answer-text thresholds, doses, or targets.
- Drug names are not used as recommendations outside provider-question vocabulary.
- Emergency content does not contain clinical time windows or measurement thresholds as triage criteria.
- Comparative effectiveness claims are qualified and individualized.
- Content does not imply diagnosis from symptoms.
- Per-Q&A disclaimer is present via UI component.
- Section heading is Questions to ask your provider.
- Coverage clusters have recency caveat enabled.
- Content leans toward rights and navigation over clinical protocol.
language patterns to fix
| id | fix | pattern |
|---|---|---|
| LP-001 | Replace specific numbers with provider-personalized phrasing, such as asking what threshold applies to the user. | Specific clinical thresholds stated as facts |
| LP-002 | Reframe as questions to ask a provider about whether an action is safe or appropriate for the user. | Directive language: never, always, must, you need to, you should |
| LP-003 | Remove drug names from answer text as recommendations; allow drug names only as vocabulary in provider-question sections. | Specific drug names as recommendations |
| LP-004 | Remove specific thresholds/time windows, redirect to provider-specific emergency plan, and include the universal emergency fallback. | Emergency language with clinical specificity |
| LP-005 | Use qualified phrasing such as research suggests or some evidence indicates, then individualize to the patient/provider context. | Comparative effectiveness claims as settled fact |
future content principles
- Questions, not directives
- Education, not diagnosis
- Rights and navigation, not clinical protocols
- General information with individual caveats
- Emergency awareness without triage
required structural changes
| id | name | scope | priority | old heading | implementation |
|---|---|---|---|---|---|
| SC-001 | Rename section heading | All Q&As across all clusters | High before launch | What to do or ask | Database field name and UI display label must use the provider-question framing. |
| SC-002 | Persistent disclaimer on every Q&A card | High before launch | Build into Q&A card component as a non-removable footer; muted/secondary visible text; no smaller than 11px rendered on mobile. | ||
| SC-003 | Onboarding disclaimer screen | High before launch | Appear on first launch only; record acknowledgement timestamp; legal screen remains accessible; not a Terms/EULA replacement. | ||
| SC-004 | Coverage content recency caveat | Medium before launch | Tag coverage clusters and render an informational banner automatically; collapsible after reading; not a red/amber warning. |
impact on existing artifacts
plan
Add or revise a module/task for knowledge-base ingestion, compliance linting, persistent disclaimer UI, onboarding legal screen, coverage cluster tagging, and source-file row-count verification.
policy
Strengthen broad no-medical-advice rules with exact language-pattern constraints, required UI disclaimers, and coverage recency caveat.
module m00
M-00 should require these structural changes before any public Q&A launch or Q&A-card implementation approval.
source intake
Add client-provided Pocket Advocate compliance guide and Q&A knowledge base as explicit source material.