# Upgrade the medOS Developer Kit

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

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

Upgrade by unpacking a new kit version, reviewing the changelog, and re-running the generated app test and release-verification suites.

## What you can use now

- Compare `medos-app.schema.json`, release schema, bridge protocol, and helper changes before copying application code.
- Run `doctor`, `npm test`, preview, package checksum verification, and hospital handoff checks.

## Quick example

```bash
npm test
npm run doctor
npm run kit:pack
```

## Current limits

- The kit is currently distributed as a versioned source archive, not a public npm package.

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