# How medOS apps work

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

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

The app server calls scoped FHIR, receives signed events, and serves a UI that medOS mounts only after exact certification and hospital activation.

## What you can use now

- The host sends bounded context through `medos-bridge/1` after a current disclosure decision.
- The integration key stays on the app server.

## Current limits

- The production bridge sends no invented medOS session token.

## 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)