Skip to main content

Operations Runbook

This is the day-to-day operations manual for the MedSuite RCM platform. Where the New Customer Onboarding Guide takes you from a fresh install to first live claim, this runbook is what you reach for after that — when something is stuck, when a payer adds a rule, when a tenant needs to be moved to a new database server.

How this runbook is organized​

The runbook is broken into nine task-shaped categories. Pick the one that matches the work in front of you.

Page template​

Each chapter follows the same shape so you can scan it quickly:

  1. Outcome — what you'll have after this procedure.
  2. Prerequisites — what must already be true and links to predecessor work.
  3. Diagram — sequence or flow chart, where it helps.
  4. Steps — UI clicks first, with break-glass commands behind <details>.
  5. Validation — how to confirm success.
  6. Troubleshooting — common failures and fixes.
  7. Next — pointer to the related next chapter, where applicable.

Audience​

  • Platform admins (PLATFORM_ADMIN) — full provisioning and impersonation.
  • Support engineers (PLATFORM_SUPPORT) — read + limited write, can impersonate.
  • Tenant admins — most chapters that link out of an impersonation session apply.

If a chapter requires elevated rights beyond the reader's role, the Prerequisites section calls it out explicitly.

Daily-ops vs. incident response​

Most chapters are routine daily-ops procedures (configure a payer, publish a rule, refresh a view). A smaller set are incident-response playbooks flagged with a 🚨 next to the chapter title — those are the pages you want bookmarked when an alert fires.

Engineering reference​

The original engineering-flavored runbook (OPERATIONS_RUNBOOK.md at the repo root) remains as a SQL-heavy reference for engineers. This site is what platform staff and tenant admins should use day to day. When the two disagree, this site is canonical — file an issue against the engineering doc.

Categories​