Build hospital extensions

Ask about this pageView as MarkdownInstall tools

Portal version: 0.1.0
Updated: 2026-08-28
Source menu item: Build extensions
Availability: Documented and testable

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

Hospital IT should prefer existing forms, workflows, worklists, policies, branding, connectors, and deployment presets before writing code.

What you can use now

• Use configuration owners for no-code changes; use FHIR/webhooks for integration; use the partner kit only for a genuinely separate service/UI.
• Escalate trusted native surfaces to the Ever first-party runtime path.

Current limits

• Configuration cannot bypass backend workflow legality or clinical authority.

Next step

Start with the medOS Developer overview and confirm the target hospital’s enabled contracts before production work.

Canonical references

• FHIR R4 integration
• Public API
• Security and compliance
• Developer portal status and coverage