# Components

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

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

External apps use ordinary accessible web components inside their frame; medOS native component kits remain trusted first-party code.

## What you can use now

- Reuse your own audited component system and align typography, density, keyboard, and status semantics.
- Use bridge messages for host-level toast, close, resize, and refresh requests.

## Current limits

- There is no public downloadable medOS clinical component library for third-party runtime use.

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