Skip to main content

Facility Service — Risk Register

Status: populated Owner: TBD Last updated: 2026-04-17 Companion: SERVICE_TEMPLATE §16

1. Register

IDRiskLikelihoodImpactOwnerMitigationResidual
R1Cycle-detection regression on deep graphs causes slow cycle-check and stale cacheMediumHighFacility leadRecursive-CTE micro-benchmark in CI; perf regression gate; depth cap of 15; alertsLow
R2Bed status race allows two patients on one bedLowCritical (clinical safety)Clinical ops + FacilitySerializable TX, domain invariant, E2E test, incident drillVery low
R3Profile schema drift invalidates existing nodes mid-operationsLowHighPlatform adminProfile updates non-retroactive; dry-run; review workflowLow
R4Context cache divergence from DB after NATS outageMediumMediumSRE + FacilityTTL cap 5min; event-driven invalidation; cache recomputation on missLow
R5Tenant cross-leak via bug in RLS or misset app.tenant_idLowCriticalSecurityMandatory tenant-isolation integration test; property-based tests; DB role restrictionsVery low
R6Large subtree response (>10 MB) causes OOM on edge clientsLowMediumFacilitymaxDepth default; pagination on subtree; response size capLow
R7Cross-region federation decisions delayed — tenants need shared regional nodes earlier than M3MediumMediumProductDocument workaround (per-tenant sub-hierarchy); schedule architecture spikeMedium
R8FHIR projection lag causes interop partners to see stale dataMediumMediumInteropOutbox + retry; health-check SLO; manual replay runbookLow
R9Licensing / access-policy coupling introduces hot-path latencyMediumHighPlatformTimeout budgets; circuit breaker; cache access decisions within requestMedium
R10Import of malformed facility definition corrupts tenant stateLowHighFacilityMandatory dry-run; schema validation; transactional applyVery low
R11Bed housekeeping state machine drifts across services (inpatient, housekeeping, scheduling)MediumMediumDomainState machine ownership lives only in facility-service; others emit commandsLow
R12DAG depth exceeded by a novel deployment (e.g., 20-level federated hierarchy)LowMediumProductConfigurable maxDepth; performance budgetLow
R13Post-merge module-mapping incorrectly routes legacy FR refsLowLowDocsLegacy-ref column in EPICS/USER_STORIES; migration-plan mappingVery low

2. Review cadence

  • Weekly during M0–M1.
  • Monthly steady-state.
  • On every major incident, residual risk re-evaluated.