> ## 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.

# Deployment terminology

> Terms and identifiers used throughout the HMIS deployment and operations guides.

| Term                | Meaning                                                                                                           |
| ------------------- | ----------------------------------------------------------------------------------------------------------------- |
| HMIS                | The Laravel web application, API, queue worker, scheduler, and primary database                                   |
| Dokploy             | The supported production deployment platform and HTTPS ingress layer                                              |
| Compose project     | The services defined by `docker-compose.yml` and managed as one Dokploy service                                   |
| Release             | A tested application commit deployed with its migrations and targeted permission updates                          |
| Foundational seeder | An explicitly named seeder that creates required master data without creating the known development administrator |
| Broad seeder        | `DatabaseSeeder`; development-only because it creates `admin@example.com` with a known password                   |
| OIE                 | Open Integration Engine, which transforms and routes laboratory and radiology messages                            |
| PACS                | Picture Archiving and Communication System; Orthanc provides this function in the supplied stack                  |
| OHIF                | The browser-based imaging viewer connected to Orthanc through DICOMweb                                            |
| RPO                 | Recovery point objective: the maximum acceptable data-loss window. The baseline is 24 hours.                      |
| RTO                 | Recovery time objective: the target time to restore service. The baseline is 8 hours.                             |
| Smoke test          | A short post-deployment check of health, authentication, queue, scheduler, and critical workflows                 |
| Restore drill       | A controlled restoration into an isolated environment that proves backups are usable                              |
| Forward fix         | A new corrective migration or release applied without rolling clinical data backward                              |
| PHI                 | Protected health information; never use it in local/staging examples, screenshots, or support messages            |

## Placeholder convention

Values enclosed in double braces must be replaced through the target environment's secret or configuration process.

```text theme={null}
{{HMIS_DOMAIN}}
{{HMIS_DATABASE_PASSWORD}}
{{BACKUP_REPOSITORY}}
{{RESULTS_TOKEN}}
```

Do not replace placeholders inside the documentation repository with real operational values.