Verify installation
Run these tests from an approved administration host after deployment or upgrade.
Container and API checks
Section titled “Container and API checks”docker compose pscurl --fail --silent --show-error http://localhost:9000/api/health-checkcurl --fail --silent --show-error http://localhost:8080/fhir/metadataExpected: long-running services are Up, the Hospital API returns {}, and HAPI returns a FHIR CapabilityStatement.
Kong configuration
Section titled “Kong configuration”The Admin API is not published on host port 8001. Query it from the Kong container:
docker compose exec kong curl --fail --silent http://localhost:8001/servicesdocker compose exec kong curl --fail --silent http://localhost:8001/routesdocker compose exec kong curl --fail --silent http://localhost:8001/pluginsConfirm services/routes named fhir-api, fhir-api-route, fhir-api-key-auth, and fhir-api-key-auth-route. Confirm Basic Auth and CORS on fhir-api, and Key Auth on fhir-api-key-auth.
Authenticated request
Section titled “Authenticated request”The hospital must create the Kong consumer and FHIR_API_KEY; the setup scripts do not create either one. Verify the same key used by the Hospital API against the key-auth FHIR route. Replace all placeholders:
curl --fail --cacert /path/to/ca.pem \ -H 'apikey: <FHIR_API_KEY>' \ 'https://<NODE_HOST>/fhir-api-key-auth/metadata'Do not use --insecure in acceptance tests. Record the certificate subject, image versions, response status, and test time.
After validation, use the operations runbook for routine administration.

