# Workflows

**Portal version:** 0.1.0  
**Updated:** 2026-08-28  
**Source menu item:** Workflows  
**Availability:** Hospital/Ever internal

> This capability is for trusted operators or first-party developers, not an external partner runtime contract.

medOS workflows are configuration-driven hospital process graphs owned by `workflow_templates` and backend transition validation.

## What you can use now

- Integrations create supported clinical resources or orders; the orchestrator projects the resulting worklists.
- Use configuration APIs and hospital approval rather than writing queue rows.

## Current limits

- Partner apps do not receive arbitrary workflow-transition authority.

## Next step

Coordinate with the hospital platform owner; do not expose this operator capability through a partner app.

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