# Upgrade your medOS API contract

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

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

Use the target deployment CapabilityStatement and explicit contract versions instead of assuming a global date-pinned API.

## What you can use now

- Capture `/fhir/metadata`, compare supported resources/operations, run synthetic conformance tests, and obtain hospital approval before changing production traffic.
- Keep the old integration credential and rollback path until live receipts pass.

## Current limits

- medOS does not yet publish Stripe-style date-pinned API versions for every service.

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