# Migrate an existing integration

**Portal version:** 0.1.0  
**Updated:** 2026-08-28  
**Source menu item:** Migrate or build a Connect extension  
**Availability:** Documented and testable

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

Move proprietary integration calls to scoped FHIR/HL7 contracts, signed events, and a separate hosted UI when needed.

## What you can use now

- Inventory data reads/writes, events, secrets, UI placements, and operational dependencies.
- Replace direct database and queue writes with canonical service funnels.

## Current limits

- Some legacy interfaces need site-specific coexistence plans before cutover.

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