Skip to main content

App security

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

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

medOS partner security relies on isolation, least privilege, immutable release proof, separate duties, current authorization, and visible fallback.

What you can use now

  • Keep credentials server-side; pin origins/keys; verify every webhook; reauthorize PHI disclosure; maintain revocation and rollback.
  • Threat-model both the partner server and embedded browser.

Current limits

  • Source compatibility is not security certification.

Next step

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

Canonical references