Files and evidence · Product help and evaluation
A role selector is not an authenticated account
The local Clinic, Laboratory and Operations views illustrate responsibilities. Selecting a role does not identify a real person or establish organization-level access protection.
Follow the record
Test which actions appear for each role and whether blocked handoffs explain their dependencies. For a hosted service, separately test authenticated identity, organization membership, server-side authorization and forbidden cross-organization access. Hiding a button does not meet that requirement.
Interpret the result
Keep local workflow proof separate from production security proof. The demonstration can show a modeled sequence and preserve example records. It is not evidence that a live service is ready for patient information or that an organization has approved access.
Related reading
Attach file identity to a particular revision