v1 → v2 Gap Report
A read-only audit comparing PRD v1 (docs/prd/) against PRD v2 (docs/prd-v2/). The goal is to surface everything v1 specified that did not survive — fully or partially — into v2, so an explicit decision can be made about what to port forward.
1. Executive Summary
v1 ships ~55 source files: 14 foundation/reference pages, 10 modules × 3 views (exec / dev / icApplication) = 30 module pages, 10 React-prototype JSX files (pmr-design/), a 131 KB PMR Deep Exemplar, plus index/404/style-guide. v2 ships ~35 source pages: a single hero/landing, a five-level walkthrough (modules, personas, patient-journey, reference), a dev/ developer section with 6 cross-cutting pages + 10 dev/module pages, 9 persona pages, and a search/theme-matrix/experimental trio.
v2 is a deliberate restructure: it collapses v1's three module views into two (an L2 module page + an L3 dev page), merges every foundation/reference page into a single 885-line reference.html, and breaks the single v1 personas.html into one file per persona. As a result, "missing" rarely means an entire concept disappeared — it usually means a v1 worked example, a deep table, or a module-specific override was not carried over.
dev/ic-reference.html. Per-module overrides lost.style-guide.html (theme exploration) replaced by v2 theme-matrix.html — overlap onlyTop 10 most-impactful gaps
- 1. PMR Deep Exemplar (131 KB) — 29 noun-app AMI schemas, a worked Reminder example (VAL-CONTENT-042), an Allergy versioning example (VAL-CONTENT-043), Provenance Model with Trust-Tier definitions, Conflict-Handling rules. Nothing equivalent in v2. P0
- 2. PMR Design Prototype — interactive React/JSX UI prototype (10 files: app, shell, dashboard, today, primitives, components-page, data, tweaks-panel + app.css). No v2 equivalent; v2 demo lives in a separate
docs/demo/tree. P1 - 3. Per-module icApplication pages — 10 module-specific
ic-application.htmlfiles documented project-directory overrides, domain bindings, env cascade specifics. v2 has onlydev/ic-reference.html(shared template). Module-specific generator overrides are lost. P0 - 4. RBAC matrix per module — v1 dev pages carried a full IC 0–100 RBAC matrix per module. v2 dev/modules pages list only a tiny "RBAC" sub-section per noun-app — the cross-noun matrix is gone. P1
- 5. Trust-tier roll-up per module — v1 every module dev page had a Trust-Tier Roll-Up section. v2 mentions trust tiers in passing in the module L2 page header only. P1
- 6. Cross-module dependencies sections — v1 every module dev page had a "Cross-module dependencies" table. v2 has a thinner "Cross-Module Links" list. P2
- 7. Persona: Sam (Practice Manager) — v1 personas.html includes Sam with pain points / goals. v2 personas/ folder has no practice-manager.html. P1
- 8. Style guide — v1
style-guide.htmldocuments Hero gradient, typography, buttons, forms, cards, AMI tables, mermaid, callout, swatches across two visual variants. v2theme-matrix.htmlonly shows token swatches across four themes. P2 - 9. Glossary entries — ~25 v1 terms (EOB, RVU, QPP, NPPES, Rooming, Pajama time, Org, KMS/HSM, MDM, AMA, APM, CancelRx, gRPC, FCRA, Formulary, S3/Object Lock, OCR-HHS, OCR-card, ToS, EMR, VBC, HPI/ROS/PE, KLAS, DEA EPCS as a separate entry, WebAuthn as a separate entry, CMS, X12-275/276-277/278/999). P2
- 10. Provenance Model deep dive — v1 PMR Deep Exemplar enumerates internal vs inbound vs outbound provenance, trust-tier definitions, and conflict-handling rules. v2 mentions Trust Tier as a glossary term and surfaces it on some module-page headers, but the full taxonomy and conflict rules are gone. P1
2. Page-Level Matrix
Every v1 source file → equivalent v2 location. Status reflects content survival, not file count.
Top-level foundations & reference
| v1 path | v2 equivalent | Status | Note |
|---|---|---|---|
prd/index.html | prd-v2/index.html | ✓ migrated | Both are landing/hero pages. v2 reframes around L0–L4 walkthrough. |
prd/404.html | prd-v2/404.html | ✓ migrated | — |
prd/platform-overview.html | partly: prd-v2/index.html + reference.html#architecture | △ partial | Vision, Headline Differentiators, Module Composition survive on landing. Sections lost: "Target Market — Why this segment / Out of scope at launch", "Strategic Priorities — How the priorities cash out", "v1.0 Non-Goals", "Roadmap (high level)", "What this document is not". |
prd/personas.html | prd-v2/personas/{doctor,ma,nurse,reception,rcm,patient,pa-np,specialist}.html | △ partial | 7 of 8 personas migrated to dedicated pages. Sam (Practice Manager) missing. |
prd/regulatory-matrix.html | reference.html#regulatory-matrix | △ partial | v1 has a summary matrix + 15 individual sections per regulation. v2 keeps the summary matrix only; the per-regulation deep-dive sections are gone. |
prd/technical-architecture.html | dev/architecture.html + reference.html#architecture | △ partial | 9 subsystems are listed in v2 but each was a multi-paragraph section in v1; v2 collapses to a card-grid summary. Region strategy, Managed-services list, Backup/restore details, Observability flow diagram thinner. |
prd/integration-ecosystem.html | dev/integrations.html + reference.html#integration-ecosystem | △ partial | v1 had 13 vendor categories + Integration Health Flow diagram. v2 keeps the BUILD/BUY/HYBRID table but drops Telehealth, Devices, IIS & PDMP, Clinical Content, integration-health-flow diagram, "Excluded Vendors" rationale. |
prd/data-ownership-model.html | dev/data-model.html + reference.html#data-ownership | △ partial | Identity model, Short GUID, classification table all carried. v1's "Authorization Chain Visualized" diagram, "Flat HTML/JSON Serving with Embedded Access Records", and "rev.health as the Comprehensive Source" narrative are missing. |
prd/terms-of-service-care.html | reference.html#contract-topology | △ partial | v1 had 5 separate documents × multiple sections each (~30 H3s). v2 keeps the 5-document table + Why-separate + Consent Models summary. Lost: full per-document clauses for Service Terms / Data Ownership / Patient Rights / Portability / HIPAA / Part 2 / Retention / Dispute / SLA, Patient ToS messaging/payments clauses, ToC renewal cadence. |
prd/glossary.html | reference.html#glossary | △ partial | ~25 terms not migrated. See §5. |
prd/ic-rules-reference.html | reference.html#ic-rules + dev/ic-reference.html | △ partial | All 14 rules carried. Lost: "Naming & versioning conventions" deep dive (entity naming, field naming two display modes, type suffixes, field ordering, Versioning section). |
prd/ic-application-reference.html | dev/ic-reference.html + reference.html#icapplication | △ partial | v1 had 8 numbered sections (1 Stack, 2 Directory, 3 Naming, 4 Codegen flow, 5 Default bindings, 6 Env cascade, 7 RBAC, 8 Build/Test/Run). v2 keeps 1–6; Section 7 RBAC enforcement and Section 8 Build/Test/Run commands thinned to almost nothing. |
prd/architectural-decisions.html | dev/decisions.html + reference.html#arch-decisions | ✓ migrated | All 8 decisions present. v2 keeps choice + rationale + consequences. v1's "Affected Modules" cross-links partially lost in summary table; full container-key tables preserved. |
prd/known-contradictions.html | reference.html#contradictions | ✓ migrated | All 8 contradictions present. |
prd/pmr-deep-exemplar.html (131 KB) | — | ✗ missing | No equivalent in v2. 29 AMI schemas + Provenance model + Trust tiers + Reminder worked example + Allergy versioning example. |
prd/style-guide.html | partly: prd-v2/theme-matrix.html | △ partial | v2 theme-matrix.html shows only token swatches across 4 themes. v1 style-guide has Hero, Typography hierarchy, Buttons, Form inputs, Cards, Priority tags, AMI tables, Mermaid samples, Callouts, Color swatches across "Healthcare Clinical (Refined)" and "Modern Medical SaaS" variants. Decision summary missing. |
prd/pmr-design/* (10 jsx + app.css + index.html) | — | ✗ missing | Entire interactive React prototype absent. (v2 has its own docs/demo/ outside the PRD tree, but it's a different artifact.) |
prd/_partials/nav.html | v2 navigation is injected by assets/shell.js | ✓ migrated | Same intent, different delivery. |
prd/netlify.toml | prd-v2/netlify.toml | ✓ migrated | — |
prd/ui-mockup-todo.md | — | ✗ missing | v1-only working notes; ports unclear. |
prd/validation-report-73.md | — | ✗ missing | v1-only working notes; ports unclear. |
Module pages (3 views per module in v1)
v1 had three views per module: exec.html, dev.html, ic-application.html. v2 collapses to two: modules/{noun}.html (L2, exec-like) and dev/modules/{noun}.html (L3, dev-like). Per-module icApplication is folded into the single shared dev/ic-reference.html.
| v1 path | v2 equivalent | Status | Note |
|---|---|---|---|
modules/eligibility/exec.html | modules/eligibility.html | ✓ migrated | Pitch + capabilities + personas + roadmap survive. |
modules/eligibility/dev.html | dev/modules/eligibility.html | △ partial | 5 AMI schemas + FK diagram + FR/NFR migrated. Lost: Trust tier roll-up, RBAC matrix, Cross-module dependencies. Added: Prior Auth state machine. |
modules/eligibility/ic-application.html | only dev/ic-reference.html | △ partial | Module-specific bindings/overrides not migrated (shared template only). |
modules/scheduling/exec.html | modules/scheduling.html | ✓ migrated | — |
modules/scheduling/dev.html | dev/modules/scheduling.html | △ partial | 7 AMI schemas + Resource-Graph + Constraint Rules + Appointment state machine present. Lost: Trust tier roll-up, RBAC matrix. |
modules/scheduling/ic-application.html | only dev/ic-reference.html | ✗ missing | v1 had Scheduling code-gen details, Domain-Specific Override Bindings, Pre-Visit Reminder Ladder Dispatcher, Versioning worked example, Scheduling environment details, Scheduling RBAC notes — all lost. |
modules/clinical-doc/exec.html | modules/clinical-doc.html | ✓ migrated | — |
modules/clinical-doc/dev.html | dev/modules/clinical-doc.html | △ partial | 8 AMI schemas (Encounter, EncounterNote, Problem, ProblemList, ScribeSession/Utterance/StructuredOutput/ReviewState) + FK + Scribe Provenance pipeline survive. Lost: Canonical Framings binding section, full Provenance Model: Audio→Transcript→Structured→Review→Write-Back, Trust Tier Assignments, RBAC Permission Thresholds, Row-Level Security Notes. |
modules/clinical-doc/ic-application.html | only dev/ic-reference.html | ✗ missing | Module-specific overrides not migrated. |
modules/coding-cds/{exec,dev,ic-application}.html | modules/coding-cds.html + dev/modules/coding-cds.html | △ partial | L2 + dev page present. ic-application module-specific content lost. |
modules/referrals/{exec,dev,ic-application}.html | modules/referrals.html + dev/modules/referrals.html | △ partial | Same pattern — exec/dev carried, ic-application module-specific overrides lost. |
modules/patient-portal/{exec,dev,ic-application}.html | modules/patient-portal.html + dev/modules/patient-portal.html | △ partial | Same pattern. v2 patient-portal.html was refreshed (Jun 1) so may include net new material. |
modules/erx-epcs/{exec,dev,ic-application}.html | modules/erx-epcs.html + dev/modules/erx-epcs.html | △ partial | Same pattern. |
modules/rcm/{exec,dev,ic-application}.html | modules/rcm.html + dev/modules/rcm.html | △ partial | 5 AMI schemas + FK + Claim State Machine present. Lost: Trust tier roll-up, RBAC matrix, Cross-module dependencies. |
modules/task-mgmt/{exec,dev,ic-application}.html | modules/task-mgmt.html + dev/modules/task-mgmt.html | △ partial | Same pattern. |
modules/payer-opt/{exec,dev,ic-application}.html | modules/payer-opt.html + dev/modules/payer-opt.html | △ partial | 4 AMI schemas + FK present. Lost: Trust tier roll-up, RBAC matrix, Cross-module dependencies. |
Pages new in v2 (no v1 source)
| v2 path | Status | Note |
|---|---|---|
prd-v2/patient-journey.html | + new in v2 | L3 patient-journey walkthrough; no v1 source. |
prd-v2/search.html | + new in v2 | Lunr-based site search. |
prd-v2/theme-matrix.html | + new in v2 | Token swatches across 4 themes. |
prd-v2/modules/labs.html | + new in v2 | No v1 module; classification marked "planned — no v1 schema yet" in v2's own dev/index.html. |
prd-v2/modules/imaging.html | + new in v2 | No v1 module. |
prd-v2/modules/doc-workflows.html | + new in v2 | No v1 module by that name. Likely consolidates clinical-doc + referrals + tasks workflow flows. |
prd-v2/modules/patient-portal.html | △ partial | Maps to v1 patient-portal but file shape/content is restructured. |
prd-v2/dev/experimental/index.html | + new in v2 | "Architecture approaches, Azure service map, phasing" — no v1 source. |
prd-v2/personas/index.html | + new in v2 | Persona index for the new per-persona layout. |
3. Section-Level Gaps Grouped by Module
For each v1 module, the sections that are present in the v1 dev/exec/icApplication trio but not represented (or only thinly) in the corresponding v2 module + dev/module pair. Sections present in both are not repeated here.
Eligibility
- ✗ Trust tier roll-up (v1 dev.html) — full per-noun-app trust-tier table.
- ✗ RBAC matrix (IC 0–100 scale) (v1 dev.html) — cross-noun-app RBAC matrix.
- △ Cross-module dependencies (v1 dev.html) — v2 has a thinner "Cross-Module Links" list.
- ✗ Module-specific icApplication content (project layout overrides, env cascade specifics, RBAC notes).
- + Prior Auth state machine (v2 only).
Scheduling
- ✗ Trust tier roll-up (v1 dev.html).
- ✗ RBAC matrix per scheduling noun-app (v1 dev.html).
- ✗ Scheduling code-gen details (v1 ic-application.html §2).
- ✗ Domain-Specific Override Bindings (v1 ic-application.html §3).
- ✗ Pre-Visit Reminder Ladder Dispatcher worked example (v1 ic-application.html §4).
- ✗ Versioning — Worked Example for Scheduling (v1 ic-application.html §5).
- ✗ Scheduling environment details / Scheduling RBAC notes (v1 ic-application.html §6).
- ✓ Resource-Graph Model + Constraint Rules + Appointment State Machine all migrated.
Clinical Documentation
- ✗ "Canonical Framings (binding for this module)" intro section (v1 dev.html).
- △ Provenance Model: Audio → Transcript → Structured → Review → Write-Back — v2 keeps the pipeline diagram, drops the prose narrative.
- ✗ Trust Tier Assignments per noun-app (v1 dev.html).
- ✗ RBAC Permission Thresholds (v1 dev.html).
- ✗ Row-Level Security Notes (v1 dev.html) — superseded by Cosmos DB partition-key isolation but RLS notes were a useful migration record.
- ✗ Module-specific icApplication content.
- ✓ All 8 AMI schemas (Encounter, EncounterNote, Problem, ProblemList, Scribe×4) present.
Coding & CDS
- ✗ Trust tier roll-up + RBAC matrix (v1 dev.html).
- ✗ Module-specific icApplication content.
- ✓ Diagnosis, Procedure, OrderSet, CdsRule, CodeSet, CodeSetVersion, CodeMapping, CdsHookEvent AMI schemas migrated (per dev/index.html catalog).
Referrals
- ✗ Trust tier roll-up + RBAC matrix.
- ✗ Cross-module dependencies (thinned to Cross-Module Links).
- ✗ Module-specific icApplication content.
Patient Portal
- ✗ Trust tier roll-up + RBAC matrix.
- ✗ Module-specific icApplication content.
- △ v2 patient-portal.html was rewritten (Jun 1) — likely includes some net new material not present in v1.
eRx & EPCS
- ✗ Trust tier roll-up + RBAC matrix.
- ✗ Module-specific icApplication content.
- ✓ Prescription, ControlledSubstanceAuth, PdmpQuery, FormularyCheck schemas migrated.
RCM
- ✗ Trust tier roll-up + RBAC matrix (IC 0–100 scale).
- ✗ Cross-module dependencies.
- ✗ Module-specific icApplication content.
- ✓ Claim, ClaimLine, Payment, Denial, PatientStatement schemas + Claim State Machine migrated.
Task Management
- ✗ Trust tier roll-up + RBAC matrix.
- ✗ Module-specific icApplication content.
Payer Optimization
- ✗ Trust tier roll-up + RBAC matrix.
- ✗ Cross-module dependencies.
- ✗ Module-specific icApplication content.
- ✓ PayerOptimizationConfig, PayerRule, CodingOptimizationSuggestion, OptimizationAuditEntry schemas migrated.
4. Foundations / Reference Gaps
v2 collapsed v1's 11 foundation/reference pages into a single 885-line reference.html + 6 dev/* pages. Coverage is generally summary-level — full v1 deep-dive sections, worked examples, and per-document clause text are typically dropped.
Platform Overview
- ✗ Target Market — Why this segment / Out of scope at launch.
- ✗ Strategic Priorities — "How the priorities cash out".
- ✗ v1.0 Non-Goals (explicit non-goals list).
- ✗ "Roadmap (high level)" with phase grid.
- ✗ "What this document is not".
- ✓ Headline Differentiators + Module Composition migrated.
Personas
- ✗ Sam — Practice Manager (full persona).
- △ Per-persona "Goals within REV.health" sections present in v2 but tend to be lighter; v1 had paragraph-level pain points and goals per persona.
- ✓ Dr. M (doctor), Maria (pa-np), Tasha (nurse / ma — v1 had one MA/RN persona, v2 split into nurse + ma), Jordan (reception), Priya (rcm), Mr. K (patient), Dr. R (specialist) all carried.
Regulatory Matrix
- ✗ Per-regulation H2 deep-dive sections (HTI-1, HTI-2, HTI-3, HTI-4, USCDI v3/v5, CMS-0057-F, TEFCA/CA v2, 42 CFR Part 2, DEA EPCS, MIPS/MACRA, HIPAA, No Surprises Act/GFE, ADA/§508/WCAG, SOC 2, HITRUST).
- ✓ Summary matrix table preserved.
Technical Architecture
- △ 9 subsystems present in
dev/architecture.htmlas card-grid + summary; v1's multi-paragraph per-subsystem detail (e.g., Region strategy, Managed services list, Mobile Clinician vs Patient split, Backups & restore, Observability stack) is thinned. - ✗ Architecture flow diagram (Mermaid) detail from v1 §9.
Integration Ecosystem
- ✓ Eligibility & PA, Claims, eRx/EPCS/RTPB, HIE/TEFCA, Labs & Imaging, Patient Comms, AI Scribe & Coding QA, Compliance & Identity tables present in
dev/integrations.html+reference.html#integration-ecosystem. - ✗ Telehealth vendor table.
- ✗ Devices & Peripherals vendor table.
- ✗ IIS & PDMP vendor table.
- ✗ Clinical Content / Drug Knowledge / Code Sets vendor table.
- ✗ "Excluded / Not Recommended" rationale.
- ✗ Integration Health Flow diagram.
Data Ownership Model
- ✓ Patient = User identity, Short GUID convention, Data Ownership Classification, Read-Access Audit Trail, AuditLog AMI schema all migrated.
- ✗ "Authorization Chain — Visualized" diagram (separate from the model).
- ✗ "Flat HTML/JSON Serving with Embedded Access Records" — narrative on patient-facing audit display.
- ✗ "rev.health as the Comprehensive Source" framing paragraph.
- ✗ Second worked Short GUID example.
- ✗ "Distinction: Terms of Service vs. Terms of Care" callout.
Terms of Service & Care
- ✓ Contract topology — 5 documents × 3 parties table present.
- ✗ ToS clauses: Service Terms, Data Ownership, Patient Rights to Their Data, Data Portability, HIPAA Privacy Commitments, 42 CFR Part 2 SUD handling, Data Retention, Dispute Resolution, SLA Commitments.
- ✗ Patient ToS: Whitelabel Identity / Account & Access / Messaging clauses.
- ✗ Patient ToC: Your Data Rights / Consent Dashboard / How Your Data Moves Between Practices.
- ✗ Platform ToC: Authorization Chains / Consent Models / Break-the-Glass / Audit Commitments / Cross-Org Sharing Rules / ToC Acceptance & Renewal cadence.
IC Rules Reference
- ✓ All 14 hard rules present in
reference.html#ic-rules. - △ Companion conventions thinner: v1 has Field naming two display modes, Type suffixes, Field ordering within an entity, Versioning. v2 has compact bullet-list version.
icApplication Reference
- ✓ Sections 1–6 present (Stack, Directory, Naming, Codegen flow, Default bindings, Env cascade).
- ✗ Section 7 — Permissions / RBAC Enforcement (full).
- ✗ Section 8 — Build / Test / Run Commands.
- △ v2's
dev/ic-reference.htmlhas an extra "Module Root Nouns" section but drops the explicit "What is NOT in this doc" boundary statement.
5. Glossary Term Gaps
v1 glossary has ~115 entries (id="term-…"). v2 reference glossary has ~87 entries (id="glossary-…"). The following v1 terms are not represented in v2.
| v1 term | Category | Notes |
|---|---|---|
| AMA | Org / acronym | American Medical Association — owner of CPT. |
| APM | Payment model | Alternative Payment Model. |
| CancelRx | NCPDP SCRIPT message | One of the SCRIPT 2017071 messages REV.health implements. |
| CMS | Org / acronym | Centers for Medicare & Medicaid Services. |
| DEA EPCS (standalone entry) | Regulation | v2 has EPCS but not the separate DEA EPCS framing. |
| EMR | Concept | Distinction from EHR. |
| EOB | Document | Explanation of Benefits — human-readable form of X12 835. |
| FCRA | Regulation | Fair Credit Reporting Act. |
| Formulary | Concept | Payer drug list — referenced by RTPB. |
| gRPC | Tech | Internal service-to-service framework. |
| HPI / ROS / PE | Clinical | History of Present Illness / Review of Systems / Physical Exam. |
| KLAS | Org | Independent vendor-rating firm. |
| KMS / HSM | Tech / security | Key Management Service / Hardware Security Module. |
| MDM | Clinical | Medical Decision Making — driver of E/M code selection. |
| NPPES | Org / registry | National Plan and Provider Enumeration System (CMS NPI registry). |
| OCR (HHS) | Org | HHS Office for Civil Rights. |
| OCR (insurance card) | Concept | Optical Character Recognition for insurance-card capture. |
| Org | IC concept | The IC term for organization tenant. |
| Pajama time | Concept | After-hours charting — north-star metric for REV.health. |
| Prior Authorization (standalone entry) | Concept | v2 references PA in CMS-0057-F but no standalone glossary entry. |
| QPP | Program | Quality Payment Program — umbrella for MIPS + Advanced APMs. |
| Rooming | Workflow | MA workflow concept. |
| RVU | Finance | Relative Value Unit — CMS fee-schedule driver. |
| S3 / Object Lock | Tech | WORM Object Lock for PHI documents and audit log. |
| ToS (standalone entry) | Legal | v2 covers Contract Topology but doesn't define ToS as its own glossary entry. |
| VBC | Concept | Value-Based Care. |
| WebAuthn (standalone entry) | Tech | v2 folds WebAuthn into the FIDO2 entry; v1 had both. |
| X12 275 | Standard | Patient information / claim attachment. |
| X12 276/277 | Standard | Claim status request / response. |
| X12 278 | Standard | Health-care services review (prior authorization request). |
| X12 999 / 277CA | Standard | Functional acknowledgment / claims acknowledgment. |
davinci → v2 da-vinci; v1 part-2 → v2 part2; v1 wcag-2-2-aa → v2 wcag). These are not counted as gaps; only entries with no semantic equivalent in v2 reference glossary are listed above.
6. Decision-Level Gaps
Architectural Decisions
All 8 decisions migrated. dev/decisions.html uses a card layout per decision; reference.html#arch-decisions has a summary table.
| Decision | v1 → v2 status | Note |
|---|---|---|
DEC-RH-001 Users/Patients Global | ✓ migrated | Affected Modules cross-links from v1 collapsed to a single "All modules" line in v2 card. |
DEC-RH-002 Clinical Facts Global w/ Source OrgID | ✓ migrated | Same — Affected Modules collapsed. |
DEC-RH-003 Short GUID | ✓ migrated | Worked example present in both dev/data-model.html and reference.html#data-ownership. |
DEC-RH-004 Read-Access Audit w/ Authorization Chains | ✓ migrated | — |
DEC-RH-005 Patient = User Identity | ✓ migrated | — |
DEC-RH-006 Postgres as Primary OLTP | ✓ migrated | Marked superseded in both. v1 had longer consequences narrative; v2 keeps the supersession note. |
DEC-RH-007 Patient-scoped Audit | ✓ migrated | — |
DEC-RH-008 Azure Cosmos DB Primary | ✓ migrated | Full container/partition-key tables present in both. |
Known Contradictions
| Contradiction | v1 → v2 status | Note |
|---|---|---|
| 1. OrgID-on-everything vs global Patient/User | ✓ | — |
| 2. Clinical data org-scoped vs global | ✓ | — |
| 3. Cosmos vs PostgreSQL primary | ✓ | — |
| 4. "No SQL MONEY" rule vs Money AMI primitive | ✓ | — |
| 5. RCM as P1 module vs launch differentiator | ✓ | — |
| 6. TEFCA at launch vs P2 caution | ✓ | — |
| 7. Payer Optimization differentiator vs "one feature" | ✓ | — |
| 8. PRD pricing tiers vs mission "no dollar figures" | ✓ | — |
7. PMR & Prototypes
PMR Deep Exemplar (prd/pmr-deep-exemplar.html)
131 KB single-page deep dive. Nothing equivalent in v2. Content not migrated:
- Data classification (PMR-specific).
- FK relationship diagram across 29 noun-apps.
- 29 AMI schemas: Patient, Provider, Practice, Pharmacy, Specialty, Encounter, Allergy, Medication, Condition, Surgery, FamilyHistory, Vital, LabResult, Imaging, Order, Immunization, CarePlan, Screening, Reminder, Document, Referral, Message, ExternalInbound, ExternalOutbound, ExternalSourceSystem, ExternalRecipient, RuleVersion, User, AuditLog.
- Provenance Model — (a) Internal canonical provenance, (b) External inbound provenance, (c) External outbound provenance, (d) Trust tier definitions, (e) Conflict-handling rules.
- RBAC matrix (IC 0–100 scale) for the PMR.
- Worked Reminder example (VAL-CONTENT-042): Reminder AMI, ReminderAttempt AMI, Offset ladder, Dispatcher SQL query, Frequency cap, Supersession logic, Reminder lifecycle diagram.
- Worked Allergy versioning example (VAL-CONTENT-043): Allergy 1.0.0 (initial), 1.1.0 (feature bump), 2.0.0 (break bump).
dev/data-model.html and module dev pages, but the PMR-as-unified-exemplar narrative — and the two worked examples — has no v2 home.
PMR Design Prototype (prd/pmr-design/)
Interactive React/JSX prototype. Nothing equivalent in v2. Files not migrated:
index.html— entry point.app.jsx,shell.jsx— app shell.dashboard.jsx,today.jsx— provider views.primitives.jsx— UI primitives.components-page.jsx— component gallery.data.jsx— mock data.tweaks-panel.jsx— live theme tweaker.app.css— prototype styles.screenshots/directory — design captures.
v2 has a separate docs/demo/ persona-dashboard demo (referenced in reference.html#architecture) but it is a different artifact, not a port of the v1 PMR prototype.
8. Recommendations — Prioritized Port List
Based on impact (how much v1 content is lost) × downstream value (does the gap block reasonable reader questions?), here is the suggested port-forward order. Priorities use the project's existing P0/P1/P2 convention.
P0 — port before next release
- 1. PMR Deep Exemplar — port as
dev/pmr-deep-exemplar.html. It is the single largest unmigrated artifact, and the Reminder + Allergy-versioning worked examples are referenced by name as VAL-CONTENT-042/043. Without this page, the trust-tier and provenance vocabulary lacks a canonical example. - 2. Per-module Trust-Tier Roll-Up + RBAC matrix — restore the per-module Trust-Tier and RBAC tables in
dev/modules/{noun}.html. Currently every dev module page lists only "Schema / RBAC" sub-sections per noun-app, no cross-noun matrix. - 3. Per-module icApplication overrides — at minimum capture the Scheduling code-gen details, Domain-Specific Override Bindings, Pre-Visit Reminder Ladder Dispatcher, and per-module env-cascade notes. Either as inline sections in each
dev/modules/{noun}.htmlor as an "Overrides" subsection indev/ic-reference.html.
P1 — port within a milestone
- 4. PMR Design Prototype — either port the JSX prototype into the v2
docs/demo/tree, or write an explicit "superseded by docs/demo/" pointer indev/ic-reference.html. Without this, the PRD has no executable design artifact. - 5. Persona: Sam (Practice Manager) — add
personas/practice-manager.htmlwith the v1 pain-points / goals content. - 6. Per-regulation deep-dive sections — restore the H2 sections for each of the 15 regulations in
reference.html#regulatory-matrix. Currently only the summary table survives. - 7. Terms-of-Service + Terms-of-Care per-document clauses — at least port the Patient ToC clauses (Your Data Rights, Consent Dashboard, How Your Data Moves Between Practices) and the Platform ToC Authorization-Chains / Consent Models / Break-the-Glass / Audit Commitments clauses. These are core to the read-access-audit story.
- 8. Provenance Model deep dive — port the four-part Provenance Model (Internal / Inbound / Outbound / Trust-tier definitions / Conflict-handling) from PMR Deep Exemplar into
dev/data-model.htmlif PMR Deep Exemplar isn't ported as a whole. - 9. Cross-module dependency tables — restore the per-module "Cross-module dependencies" table in each
dev/modules/{noun}.html. The current "Cross-Module Links" is thinner. - 10. icApplication Section 7 (RBAC) + Section 8 (Build/Test/Run) — restore in
dev/ic-reference.html.
P2 — port when convenient
- 11. Glossary terms — add the ~25 missing entries to
reference.html#glossary. They are mostly clinical workflow / finance / standards acronyms a reader is likely to encounter elsewhere in the PRD. - 12. Integration Ecosystem missing categories — Telehealth, Devices, IIS & PDMP, Clinical Content, Excluded Vendors. Either restore in
dev/integrations.htmlor merge into the appropriate existing category. - 13. Style guide — port v1
style-guide.html's component gallery (Buttons, Form inputs, Cards, Priority tags, AMI table, Mermaid, Callout) intotheme-matrix.htmlor a newstyle-guide.htmlsibling. v2 currently has tokens but no live component examples. - 14. Platform Overview sections — Target Market, Strategic Priorities cash-out, v1.0 Non-Goals, Roadmap, "What this document is not". Could fit in
index.htmlor a newabout.html. - 15. Integration Health Flow diagram — port the Mermaid integration-health diagram from v1
integration-ecosystem.htmlintodev/integrations.html.
Out of scope (no port recommended)
prd/ui-mockup-todo.md— working notes; superseded.prd/validation-report-73.md— working notes; superseded.prd/shared.css,prd/shared.js— replaced byprd-v2/assets/shared.css+shell.js.prd/_partials/nav.html— replaced byshell.jsruntime injection.
This report is a static read-only audit generated by file-tree diff between docs/prd/ and docs/prd-v2/. Headings, section counts, and glossary term lists are derived directly from the source HTML. "Partial" determinations weigh both depth (paragraph count) and the presence of v1-specific worked examples.