Access and data boundaries
The permissions that every workflow and extension must preserve.
Enforce scope on the server
Organization, study, enrollment and assignment boundaries apply in server commands and database/file policies. Possession of a UUID or a shared link never grants access.
Researchers see identified records in active studies. Clinicians require current patient assignment. Patients require a verified account link and may read their own allowed records. Revocation removes current access.
Keep collaboration permissions explicit
A shared dashboard, protocol or analysis module contains reusable definitions. It does not transfer patient data or grant permission to fetch it.
Private conversations and live calls require explicit participant membership. Patient-to-patient messaging is disabled. Clinical-record access is not private-conversation membership.
Preserve evidence without leaking it
Use synthetic fixtures for development, tests, screenshots and agent artifacts. Keep patient exports, credentials, signed URLs and production dumps out of source control, logs and graph caches.
Original recordings and accepted outputs retain their evidence identity. Reanalysis creates a new output with explicit versions and provenance. Never silently substitute patient identities, units, calibration or missing values.
Clinical readiness is a separate review
A running local stack, a vendor feature or passing synthetic tests does not establish application compliance or clinical readiness. The actual deployment, contracts, data flows and operational responsibilities require responsible review.