# medOS APIs

**Portal version:** 0.1.0  
**Updated:** 2026-08-28  
**Source menu item:** API  
**Availability:** Documented and testable

> The source contract and local workflow exist. Access still depends on the target hospital deployment and its policy gates.

FHIR R4 is the partner-facing clinical interoperability standard; medOS service APIs remain behind the gateway and hospital policy.

## What you can use now

- Discover resources at `/fhir/metadata`, use a server-held scoped integration key, and send writes only through supported FHIR funnels.
- Queue rows are projections and are never a partner write API.

## Current limits

- Write access and scope enforcement are deployment-gated and must be proven on the target site.

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