# SDKs and starter kits

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

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

The bare-shell partner kit is dependency-light Node.js with FHIR, webhook, bridge, signing, packaging, and handoff helpers.

## What you can use now

- Start from `tools/medos-app-template`; use bounded-context T-KIT packages only for trusted first-party runtime surfaces.
- Treat browser UI and server credentials as separate trust zones.

## Current limits

- There is no supported third-party native medOS React SDK that can run inside the host bundle.

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