Kulcare Docs

MAR and Recovery Staging Handoff

Named owners, deployment evidence, both-preset QA and separate clinical and pilot decisions for PR 2757.

Candidate And Current State

Application candidate: 445910c9917225c8d003042b7f30e0079a6856e4, draft PR 2757. Local backend/frontend CI, both-preset real-HTTP browser journeys and the final CodeRabbit follow-up pass. See the repair record. These are not staging results. No deployment or clinical approval is recorded here.

The replacement docs Pages build is green on that candidate. The old Workers check still reports failure. Its owner must inspect that integration; no Cloudflare setting was changed during this handoff.

Use the operator runbook before testing. Gate A permits approved deployment and policy-off smoke checks. Gate B requires approved facility-scoped policies and synthetic nursing QA authority. Missing Gate B evidence means blocked, not a failed feature or permission to bypass it.

Handoff Validation

This is documentation-only work on the application candidate above. Local checks confirmed three preflight queries match their migration, nine new-page links resolve, and all six SQL blocks execute in read-only transactions on an isolated synthetic database. The runtime metadata block ran as the non-bypass test role and returned ten table rows. This is not evidence of deployed runtime grants or of a clean staging preflight. Fumadocs built and indexed 520 pages.

Read-only document review found no issue. Worker 01a15ee9-f82f-7a60-91b4-bb942c09aef5 used the configured Hospital reviewer profile; actual served-model and effort receipts are unavailable. It was closed after its result. External review awaits approval for the new deployment details.

Owners And Evidence

Simmi is the deployment owner and the user's named approval contact. Record the qualified reviewer for each decision below. A contact name is not a completed clinical or pilot approval. QA closes the tracking issue after verification.

Decision or evidenceOwnerRecord
Deployment and writer-resume decisionSimmiPending
Database/migration identity, preflight and restore rehearsalSimmi names the approved operatorPending
Actual backend and frontend revisions, environment and database identityDeployment ownerPending
Surgery Center QAQA lead: name requiredPending
Hospital 50 QAQA lead: name requiredPending
D4 nursing/MAR/readiness/handoff policy and actor authorityQualified clinical/nursing reviewer: name requiredPending
D5 capacity classification and cutoverFacility operations reviewer: name requiredPending
Scoped pilot acceptancePilot owner: name requiredPending
Leftover Workers integration/checkCloudflare/repository owner: name requiredPending

For each result, record pass/fail/blocked, candidate revisions, preset, facility, actor/grants, policy reference/hash where applicable, expected/actual result, issue reference and private evidence location. Do not post credentials, patient rows, session files or real patient screenshots in this page or the PR.

Gate A: Deployment And Policy-Off Smoke

  • Record approved release artifacts and every pending migration, including base migrations.
  • Complete restore/rehearsal, write-pause, legacy preflight and T0/T1 aggregate checks in the operator runbook.
  • Verify all eight feature migrations and actual objects, not version rows alone.
  • Verify runtime role, RLS, grants, immutable history and current occupancy integrity.
  • Open Hospital through authenticated MFA. Confirm real HTTP, selected facility and preset; no silent mock fallback.
  • Check MAR capability without approved policy: reads remain authorized and writes unavailable. Check Recovery policy status and no false clinical clearance.
  • Confirm resource/stay/observation controls follow their own explicit grants and approved QA scope. Do not infer that all writes are policy-gated.
  • Compare an allowed viewer, a denied actor, a same-tenant foreign facility and a foreign tenant. Confirm non-disclosing errors and no leaked counts or records.
  • Verify existing OPD/encounter/admission care can still load and use supported operations. Preserve nullable legacy identity.
  • Record operator approval to resume affected writers and the actual monitoring locations.

Gate B: Both-Preset Clinical QA

Do not check these steps until qualified approval and synthetic QA scope are recorded. Use separate facilities or separately approved runs for both presets; never reset shared staging data. Use current facility-local dates, not an old demo day.

JourneySurgery CenterHospital 50Evidence or issue
Prescribe/enroll scheduled and PRN care, including object/array source instructionsPendingPendingPending
Administer, hold/resume, omit/refuse/missed and reasoned correction; reload original provenancePendingPendingPending
Stop/revise and retained-time non-dose correction; reject unauthorized changed time or physical dosePendingPendingPending
Lost response, exact receipt and failed refresh; no second clinical effectPendingPendingPending
Same-role user switch/logout during read/write/lookup; preserve original user's unresolved keyPendingPendingPending
Empty MAR page with nonzero summary; required audit failure discloses nothingPendingPendingPending
Resource provision/edit, stale draft, refetch and explicit reloadPendingPendingPending
Receive, canonical observations/correction, escalation and explicit current-evidence reviewPendingPendingPending
Move, cleaning and unavailable-target rejection; one physical ownerPendingPendingPending
Concurrent Settings/intake and admission/intake through supported requestsPendingPendingPending
Continuing-care handoff with retained obligations; reject second receive and preserve exact replayPendingPendingPending
Case/MAR/Recovery handoffs, source-backed dashboard, reload and narrow/keyboard layoutsPendingPendingPending
Restricted modules, revoked grants, disabled intake and authorized active-care continuation/recoveryPendingPendingPending

Use the detailed MAR checklist and Recovery checklist. Failure injection, writer races and audit-outage tests require operator approval and isolation. Run them in a separate controlled environment if shared staging cannot safely support them. Record that limitation instead of changing shared audit, grants or services.

Acceptance And Exit

  • QA records both-preset results and every open defect. Re-test fixes on the actual deployed revision.
  • Clinical/nursing owner records D4 approval for exact policy content, permitted actors and source scope.
  • Facility operations records D5 classification/counting and cutover acceptance.
  • Pilot owner records scoped acceptance, exclusions and ongoing support ownership.
  • Release owner records a go/no-go decision. Keep deployment distinct from clinical activation.
  • Keep PR draft/release gates until required evidence is accepted; do not close the tracking issue directly.

Signed patient discharge and ABDM report conformance are not acceptance claims for this candidate. Programme U8 must implement and validate them separately. Pharmacy, insurance, full ward operations, billing and reports also remain separate.

On this page