Separated public routes
Patient and clinician entry points remain distinct, which reduces ambiguity at the product edge.
Security
Public trust information, grounded in what is live today
Klark keeps the public trust surface measured. This page focuses on explicit controls and delivery practices that are reflected in the current product and deployment model.
- Separate patient and clinician routes
- Authenticated product surfaces
- Controlled production releases
Current posture
What is explicit in the current foundation
These points are grounded in the current repository and deployment model.
Authenticated product areas
Existing patient and clinician surfaces both rely on authenticated access before protected workflows load.
Invite-led clinician onboarding
Clinician onboarding is routed through organisation setup and secure invites rather than open public self-registration.
Controlled production releases
Production services are tracked through explicit service manifests and release metadata rather than ad hoc public routing.
Review process
How security review is handled
Public information comes first. Deeper assurance review stays in direct commercial and implementation conversations.
Public overview
Use this page for an initial trust read on route separation, access expectations, and production delivery discipline.
Direct assurance review
Detailed review materials should continue to be shared directly during procurement or implementation planning.
Operational context
Workflow, onboarding, and access questions are best reviewed alongside the clinician and demo routes.
Next Step
Need a deeper trust conversation?
Use the demo route when your team needs a fuller review of workflow, onboarding, or assurance material.