# Migrate a plugin to medOS Apps

**Portal version:** 0.1.0  
**Updated:** 2026-08-28  
**Source menu item:** Migrate a plugin to Stripe Apps or Stripe Connect  
**Availability:** Private preview · default-OFF

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

Replace in-process or script-injected plugins with a hosted partner app or a reviewed first-party runtime surface.

## What you can use now

- External vendors use iframe/FHIR/webhooks; Ever internal modules use signed T-SEAM/T-KIT packaging.
- Move app-owned data to an approved profile/record/table lane when that platform is available.

## Current limits

- Do not port untrusted plugin JavaScript into the medOS 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)