# Embedded components

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

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

The current external UI unit is the complete sandboxed remote-app frame, not arbitrary components injected into medOS pages.

## What you can use now

- Build a responsive embedded page and use bridge resize/toast/close messages.
- Keep clinical UI semantics accessible and make data provenance visible.

## Current limits

- Native host components are reserved for trusted first-party T-SEAM/T-KIT releases.

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