Security · public boundary
Security is an operating condition.
MedXLine is designed around attributable authority, minimum access, reviewable automation, and evidence-led release. This page describes design and source posture; it does not assert external certification, a completed production assessment, or authorization in a specific jurisdiction.
The security contract
01
Least authority
Identity, role, tenant, and workflow context must be evaluated at the server boundary. A visible control never substitutes for authorization.
02
Human-owned clinical decisions
Assistive systems may organize or draft information. Qualified people retain decision authority, and consequential actions require attributable review.
03
Evidence before claims
Implemented source controls, deployment configuration, external assessment, and jurisdiction authorization are separate evidence states.
04
Fail-closed release
A jurisdiction remains unavailable for production use until its legal, clinical, security, privacy, residency, localization, operational, and release gates are recorded for that deployment.
Coordinated reporting
Report a vulnerability safely.
Read the disclosure boundary before testing. Submit only the minimum reproduction information and stop immediately if you encounter data that is not your own.