# Clinical and operational signals

**Portal version:** 0.1.0  
**Updated:** 2026-08-28  
**Source menu item:** Stripe Signals  
**Availability:** Private preview · default-OFF

> The source foundation exists, but no general production activation or public self-service program is claimed.

medOS signals come from governed clinical events, CDS, worklist projections, and Decision Twin observations.

## What you can use now

- Subscribe only to approved FHIR events and derive app-local signals on the partner server.
- Treat recommendations as proposals that require the owning workflow and human authority.

## Current limits

- There is no general-purpose public Signals API matching Stripe Signals.

## Next step

Start with the [medOS Developer overview](/developers/platform/overview) and confirm the target hospital’s enabled contracts before production work.

## Canonical references

- [FHIR R4 integration](/integrations/fhir)
- [Public API](/backend/public-api)
- [Security and compliance](/architecture/security-and-compliance)
- [Developer portal status and coverage](/developers/platform/changelog)