2.12 Go-live

Outcome

The customer is live in production, monitoring is on, and the on-call team is ready to respond.

Prerequisites

• 2.11 End-to-end test passed.

Go-live workflow

Pre go-live checklist

• UAT sign-off from the customer (email or signed PDF).
• EDI envelopes flipped from T (test) to P (production) in Admin → EDI → Envelopes.
• Trading partner test certifications in hand, in writing, for every partner.
• Payer effective dates verified — the customer is officially on each payer's panel.
• Banking — payer EFT enrollment complete (out of platform scope, but confirm).
• Fee schedules active and effective on go-live date.
• Modifier rules approved.
• Notification channels: customer's billing inbox subscribed to ERA-posted notifications.
• Tenant status = active (not read_only).

Smoke run

The morning of go-live, run a single live claim through and confirm the full path: encounter → submit → 277CA → 835 → posting. If it doesn't clear within the customer's SLA, hold and triage.

Hyper-care (first 5 business days)

• Daily standup with the customer's billing lead.
• Watch dashboards:
  • Claims throughput — submitted vs acknowledged.
  • Denial rate — investigate any denial > 1%.
  • ERA auto-match rate — should be > 90%.
  • Auto-correction success rate — should be > 60%.
• On-call platform admin available within 1 hour for escalations.

Rollback plan

Rollback is rare but possible:

Trigger	Action
Mass scrub failures	Revert active modifier rule version (Admin → Rules → History → Revert).
Mass envelope rejections	Revert envelope to test mode; resubmit after fix.
Tenant DB corruption	Restore via PITR runbook.
Catastrophic config error	Set tenant status = read_only via Platform Admin → Tenants → Suspend → Read-only (Suspension + read-only).

Definition of done

• Hyper-care window closed.
• Customer-facing retrospective completed.
• Onboarding tracking ticket closed.
• BAU on-call rotation includes the new tenant.
• Onboarding artifacts archived (intake doc, configs, test results).

Next

The customer is live. Hand them the Tenant Manual and the EDI ops team the EDI Manual.

For ongoing operations, see the platform-admin Operations Runbook — it is the canonical day-to-day manual; the legacy docs/operations/OPERATIONS_RUNBOOK.md is the engineering reference and remains SQL-heavy for backstop.