Facility Service — AI Integration
Status: populated Owner: TBD Last updated: 2026-04-17 Companion: SERVICE_TEMPLATE §8 · AI Gateway Service
1. Scope
The facility-service performs no direct AI inference. All future assistive features MUST route through the platform ai-gateway-service via Kong /v1/ai/* per AI Platform Tier B policy.
2. Future candidate assists (non-authoritative)
| Use case | Tier | HITL | Notes |
|---|---|---|---|
| Suggest hierarchy profile from free-text org description during onboarding | Tier A (draft/hint) | Required: tenant admin accepts | Template facility.onboarding.profile_suggest.v1 |
| De-duplicate location candidates across manually entered sites | Tier A (draft/hint) | Required: admin merges | Template facility.location.dedupe_hint.v1 |
| Normalize free-text facility address to structured admin subdivisions | Tier A | Required | Template facility.address.normalize.v1 |
All outputs are hints, never authoritative. Writes follow the normal command path with audit and access-policy checks.
3. Guarantees
- No direct vendor SDKs or model keys embedded in facility-service.
- No PHI in prompts (facility data is organisational, not patient-identifiable).
- All prompts, responses, and acceptance decisions captured as
AIProvenancerows in platform AI store. - Moderation via ai-gateway-service policy — facility-service never bypasses.
4. Current status
N/A for M0/M1. Ports reserved for M3+ when onboarding tooling expands.