# Batch jobs

**Portal version:** 0.1.0  
**Updated:** 2026-08-28  
**Source menu item:** Batch jobs  
**Availability:** Private preview · default-OFF

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

Scheduled operations use the existing cron/job registry and service-owned workers.

## What you can use now

- Design jobs to be idempotent, bounded, observable, and tenant-scoped.
- Use backend-owned queues or schedules; never schedule work from an embedded browser.

## Current limits

- There is no public self-service partner batch-job API.

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