> ## Documentation Index
> Fetch the complete documentation index at: https://hmis-docs.derrickmugabwa.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Production go-live checklist

> Final technical, operational, clinical, security, and recovery gates before HMIS handles live data.

Do not begin live clinical use until every applicable item is complete, evidenced, and approved. Record non-applicable items with a reason and owner.

## Infrastructure and deployment

* [ ] Production runs on the approved Dokploy server and commit.
* [ ] DNS and valid TLS are configured for every approved domain.
* [ ] The firewall exposes only approved SSH, HTTP, HTTPS, and private integration paths.
* [ ] `APP_ENV=production`, `APP_DEBUG=false`, secure cookies, and trusted proxies are verified.
* [ ] PostgreSQL, application storage, OIE, Orthanc, and OHIF are not publicly exposed except through approved routes.
* [ ] `mock-analyzer` and `mock-modality` are stopped, unrouted, and blocked.
* [ ] All required containers remain healthy without restart loops.
* [ ] Migration status is current and the deployment record is complete.

## Identity and security

* [ ] Default development credentials do not exist in production.
* [ ] Every administrator uses a named account and 2FA.
* [ ] Super-administrator membership has been reviewed by two authorized people.
* [ ] Staff roles, branches, departments, clinics, wards, and stock locations were access-tested.
* [ ] Password reset and email verification work through the approved mail service.
* [ ] Integration and backup secrets are stored in approved secret systems.
* [ ] Token abilities, owners, and rotation dates are documented.
* [ ] Incident contacts, evidence handling, and downtime procedures are approved.

## Hospital configuration

* [ ] Organization, branch, department, clinic, ward, bed, and location data is correct.
* [ ] Patient identifiers and duplicate-handling rules are approved.
* [ ] Users and roles match the staffing plan and segregation of duties.
* [ ] Payers, service catalogue, prices, diagnostic parameters, units, and account heads are approved.
* [ ] Pharmacy, stock, billing, appointment, outpatient, inpatient, and clinical forms are configured as applicable.
* [ ] Placeholder or demonstration records are removed, replaced, or clearly disabled.

## Integrations

* [ ] Vendor interface manuals and mappings are approved.
* [ ] OIE administration and listener networks are restricted.
* [ ] Laboratory normal, abnormal, duplicate, unknown, ASTM, HL7/MLLP, reconciliation, and downtime cases pass.
* [ ] Radiology worklist, acquisition, store, stable-study event, viewer, reconciliation, and downtime cases pass.
* [ ] Orthanc production authentication, storage, retention, and backup controls are enabled.
* [ ] Sanitized OIE channel exports are retained.

## Recovery and operations

* [ ] A successful encrypted off-site backup is younger than 24 hours.
* [ ] The selected recovery point covers all enabled databases and volumes.
* [ ] A restore drill completed within the 8-hour RTO during the current quarter.
* [ ] Backup retention is 30 daily, 12 weekly, and 12 monthly points.
* [ ] `/up`, external TLS, containers, queue, scheduler, databases, disk, backup age, certificates, and integrations are monitored.
* [ ] Warning and escalation thresholds reach staffed contacts.
* [ ] Release, rollback, incident, reconciliation, and maintenance owners are named.
* [ ] Paper or offline downtime procedures have been rehearsed.

## Final acceptance

<Steps>
  <Step title="Complete the synthetic workflow">
    Run the end-to-end scenario from registration through consultation, orders, billing, pharmacy/inventory, admission/discharge, and enabled integrations.
  </Step>

  <Step title="Review evidence">
    Technical, security, clinical, finance, laboratory, radiology, pharmacy, and operational owners review the evidence relevant to their scope.
  </Step>

  <Step title="Confirm rollback readiness">
    Record the recovery point, rollback authority, maintenance contact, and point after which a forward fix is required because live clinical data exists.
  </Step>

  <Step title="Authorize live traffic">
    Obtain written approval, announce the start time, monitor the first operational period closely, and keep downtime support available.
  </Step>
</Steps>

<Check>
  Go-live is authorized only when all applicable gates are complete and the named clinical and technical authorities approve live use.
</Check>