Purpose and audience

Illustrate human-led clinical and safeguarding coordination with restricted information.

Intended users: Verified, appropriately licensed and authorized professionals. Intended benefit: Specialist support without making every module a clinical record system.

Access and prerequisites

The existing /clinical route is a public fictional demonstration, not staff authority. Real access would require: Professional verification, clinical permission, assignment and approved safeguarding protocols.

What you can explore

No diagnosis, treatment, child-protection decision or real consultation is performed by this prototype or its AI guide.

  • Illustrative consultation concepts
  • Human decision boundaries
  • Proposed escalation and confidentiality controls

Explore the prototype safely

Open the Clinical demonstration using the module link. Read its notice before interacting. Inspect the relevant example view; use fictional, non-sensitive input only. Local changes demonstrate an idea, not an operational action.

Use the Connected Ecosystem map to inspect the Clinical connections. Continue to a role tour to understand proposed approvals. Do not try to bypass unavailable registration, assignments or administrative controls.

Example scenario

In fictional Alex’s support scenario, Clinical contributes only its permitted task. The input would be: Minimum necessary clinical referral approved under an established lawful policy. The expected proposed output would be: A proposed restricted clinical response; only a permitted nonclinical summary may leave the clinical boundary.

Inputs, outputs and connections

Receives: Minimum necessary clinical referral approved under an established lawful policy.

Produces: A proposed restricted clinical response; only a permitted nonclinical summary may leave the clinical boundary.

Related modules: Central, Sites, Governance.

Privacy and approvals

Clinical information does not flow into donor views, public tours or general staff dashboards.

Professional verification, clinical permission, assignment and approved safeguarding protocols.

Troubleshooting and limitations

No diagnosis, treatment, child-protection decision or real consultation is performed by this prototype or its AI guide.

If a view is unavailable, do not submit personal details elsewhere to work around it. A simulated approval cannot activate a service or grant access. The help center cannot resolve an emergency or connect a live responder.

Status, evidence and operational dependencies

Current classification: Planned. Source review: 18 October 2026. src/routes/clinical.tsx; mem requirements reflected in project guidance

Before operation: validate professional verification, clinical permission, assignment and approved safeguarding protocols. and document recovery, audit, retention, user impact and separately approved tests. Source presence does not establish published-runtime or provider success.