# Versioning

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

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

Version app metadata, immutable release bytes, bridge protocols, and API expectations independently.

## What you can use now

- Use semantic versions in `medos-app.json` and the signed `medos-remote-app-release/1` envelope.
- Treat `medos-bridge/1`, FHIR R4 capability statements, and schema `kind` fields as separate compatibility contracts.

## Current limits

- A project version is not certification, entitlement, installation, or activation authority.

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