Skip to main content

Virtual Care Service — Service Readiness

Status: populated Owner: TBD Last updated: 2026-04-18 Companion: Service Template · Definition of Done

1. Readiness Gate Checklist​

Documentation​

  • All 17 docs complete (no stubs remaining)
  • API contracts reviewed by tech lead
  • SECURITY_MODEL reviewed by security team
  • Jitsi Meet branding and JWT configuration documented

Code Quality​

  • TypeScript strict mode, zero errors
  • ESLint import-restriction passes
  • Coverage ≥ 80% overall; ≥ 90% domain layer
  • No critical/high Sonar findings

Mandatory Integration Tests​

  • tenant-isolation.integration.spec.ts passing
  • outbox.integration.spec.ts passing
  • inbox.integration.spec.ts passing
  • consent-gate.integration.spec.ts passing
  • video-backend-health.integration.spec.ts passing (no session row on 503)

Contract Tests​

  • OpenAPI diff gate — no breaking changes
  • Pact consumer tests green
  • Event schema conformance green
  • Jitsi adapter contract tests green

Security​

  • Jitsi JWT secret stored in KMS (never in config map or environment files in production)
  • Recording consent enforced and tested
  • Join token expiry tested (expired tokens rejected)
  • PHI redaction in logs verified
  • Consent fail-closed behavior tested (consent service unavailable → session blocked)

Observability​

  • OTel traces visible in Grafana Tempo (staging)
  • All SLOs declared in alerting system
  • Alert runbooks created and linked
  • Video backend health check alert configured

Jitsi Meet Integration​

  • Branded Jitsi Meet build deployed in staging
  • JWT authentication working end-to-end
  • Waiting room functionality tested
  • Multi-participant session tested (provider + patient + interpreter)
  • Jibri recording (if enabled for tenant) tested with consent gate

FHIR Integration​

  • FHIR Encounter created on session end in staging
  • Encounter class=VR confirmed
  • FHIR retry logic tested (FHIR Gateway unavailable → Encounter created on recovery)

Deployment​

  • Canary deploy completed (5% / 30 min) in staging
  • Rollback procedure verified
  • On-call rotation assigned

Sign-off​

  • Tech lead sign-off
  • SRE sign-off
  • Telemedicine regulatory compliance contact notified (consent flow reviewed)