Gap audit

Known gaps and incomplete implementations

This page tracks the remaining gaps that are still relevant after the 10-phase platform hardening pass. Historical runtime blockers that were already fixed are intentionally excluded. Each item lists its likely impact and the code or release evidence behind it.

Back to catalogOpen shell

Current tracked gaps

0

Highest risk area

External credentials and local bootstrap

Use this page for

Prioritizing implementation debt, release coverage debt, and places where shell UX still outruns the source of truth.

Section

Workflow implementation gaps

Functional gaps where the workflow shape exists but the implementation still falls short of a full production source-of-truth experience.

lowwatchhigh confidence

External payer credentials are required for real-world live submission

The app now runs the canonical claims and PA workflow through API-backed pilot payer rails; switching to real external payer/CoverMyMeds endpoints still requires contracted credentials.

Related apps

rejection-queue

Why it matters

Staff can validate the full claims queue, PA submission, status polling, and resubmit flow in test production, while real-world submission must wait for external provider onboarding.

Evidence

  • apps/api/src/routes/claims.ts exposes `/api/claims/rejections`, `/summary`, `/adjudicate`, `/pa/:paCaseId/submit`, `/status`, and `/resubmit` through auth and claims permissions.
  • packages/db/migrations/073_claims_pilot_queue.sql seeds representative canonical claims and PA rows for LAN/test-production validation.
  • packages/covermymeds-adapter/src/index.ts keeps the vendor boundary isolated so live credentials can replace deterministic pilot behavior without changing shell workflow code.

Section

Validation and release coverage gaps

Gaps that are less about user-facing functionality and more about how thoroughly the platform is verified and operated.

lowwatchhigh confidence

Packaged B10 acceptance still needs clean Ubuntu and air-gap evidence

LAN test-production deployment is verified, including deployed browser QA, promo video output, Lighthouse, and dependency audit evidence; strict B10 acceptance remains blocked until a clean Ubuntu 22.04 acceptance host, signed release bundle, and air-gap confirmation are available.

Related apps

patient-chart, pharm-call, waiter-board, controlled-substance, nninventory, pharmacy-directory

Why it matters

This is not a workflow blocker for current test-production validation, but packaged install acceptance still needs dedicated release infrastructure before it can be marked ready.

Evidence

  • docs/plans/acceptance/b10-acceptance-readiness-2026-04-29.md records the current BLOCKED strict B10 checks and the PASS LAN test-production evidence section.
  • docs/deployment/lan-test-production-handoff.md records the latest LAN deployment, deployed browser regression, video sweep, Lighthouse gate, and dependency audit evidence from 2026-05-08.