Workflows
medOS workflows are configuration-driven hospital process graphs owned by `workflow_templates` and backend transition validation.
Batch jobs
Scheduled operations use the existing cron/job registry and service-owned workers.
Event destinations
FHIR subscriptions and HMAC-signed webhook delivery are the partner event destination contract.
Deployment health alerts
Deployment Assurance source can distinguish ready, unknown, blocked, and stale evidence without trusting a service to certify itself.
Clinical and operational signals
medOS signals come from governed clinical events, CDS, worklist projections, and Decision Twin observations.
File uploads
medOS has a filestore service and document workflows, but partner upload access must be purpose- and site-approved.
AI tools
medOS AI tools are proposal-first and remain subordinate to clinical owners, policy gates, and human sign-off.
Agent plugins
Agent integrations must use bounded service capabilities and cannot inherit a user session or broad clinical role.
Model Context Protocol
A public medOS MCP server contract is planned rather than implied from internal agent tooling.
Agent skills
medOS engineering skills encode repository-specific operating rules and are not hospital runtime plugins.
App and connector directory
The generated medOS registry catalogs modules, connectors, editions, and deployment presets from repository truth.