Development, test, and production modes

Ask about this pageView as MarkdownInstall tools

Portal version: 0.1.0
Updated: 2026-08-28
Source menu item: Handle different modes
Availability: Documented and testable

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

Separate synthetic loopback development, TEST certification fixtures, hospital UAT, and production configuration.

What you can use now

• Use different keys, origins, datasets, and release IDs for every mode.
• Make non-production mode visible in UI and evidence.

Current limits

• Never allow a TEST key, wildcard origin, or synthetic patient into production.

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