The endpoint answered 2xx on this sweep, and its body did not self-report a problem.
It answered 503 or 504, or no health check of its own has been published behind the gateway yet — the only thing left to probe would be the host service, which would not prove this module is wired.
A real failure: 5xx, connection refused, or the probe timed out.
It answered 401, 403 or 404 — or its health check answers only a signed-in caller, so no request is sent at all. A refusal proves the service is reachable and proves nothing else, so it is excluded from the verdict in BOTH directions — it can neither raise an outage nor be counted as healthy.
Every operator session traverses these five. They are fetched directly from your browser, unauthenticated, which is why an authentication challenge here is the expected answer rather than a fault.
Probed server-side via /api/service-health, which forwards to each upstream service's hand-verified /healthz. Every row cites the upstream file and line where that route is declared.
Computer-aided dispatch board and unit assignment.
Crew-management aud on Crew-Service (legacy slug).
Crew scheduling, shift trades, certifications.
Electronic patient care reporting and chart capture.
Fire incident reporting, NERIS surface.
Vehicle fleet status, maintenance, telematics.
Air-medical (HEMS) dispatch and mission tracking.
Field mobile data terminal for crews in the rig.
Inter-facility transport request board.
Probed server-side via /api/service-health, which forwards to each upstream service's hand-verified /healthz. Every row cites the upstream file and line where that route is declared.
Billing engine — claims, denials, posting, statements.
Supply inventory tracking, par levels, restocking.
Medication inventory and drug-interaction surface.
Narcotic chain-of-custody and DEA-compliant audit log.
Patient self-service for statements and payments (a Billing module).
QA chart review, peer review, performance metrics.
Provider and resource scheduling.
HR, labor analytics, payroll signals.
Probed server-side via /api/service-health, which forwards to each upstream service's hand-verified /healthz. Every row cites the upstream file and line where that route is declared.
Cross-module analytics, executive dashboards.
Telephony, voice, SMS, agency communications backbone.
Compliance attestations, HIPAA audit, BAA management.
Document management, generation, archival, e-sign hand-off.
Founder operating-system surface (single-operator console).
Unified cross-module search index.
AdaptixCore publishes post-mortems for incidents lasting more than 30 minutes inside the operator console. For real-time security alerts, email security@adaptixcore.com.
