
Clinical pathway, portal and AI assistant
From assessment to the individual programme
Explore the pathwayProject in development · Pathways defined by the professionalFrom assessment to the individual programme
The pathway begins with defining the clinical profile and goals. The professional determines the areas of work, selects activities and sets difficulty, frequency and duration. Subsequent changes are informed by the person's feedback, caregiver observations and available data.
The project considers a session organised into a welcome, cognitive activities and a conclusion. A 30-minute reference format includes an initial 5 minutes of welcome and relaxation, 22 minutes of activities and 3 minutes of closing. This is an adaptable design framework: duration and frequency are defined individually and do not constitute a universal prescription.
Adaptable design framework: duration and frequency are defined individually by the professional.

A portal to document the pathway
The clinical portal is designed to collect the assigned programme and session information: activities performed, usage time, responses, accuracy, errors, assistance, breaks and completion. The availability of a history can support programme review and observation of session regularity.
Planned notifications may draw attention to persistent difficulties or missed sessions. They have no diagnostic value and do not replace clinical assessment. The software's outputs must remain distinguishable from the conclusions drawn by the professional.
Planned AI assistant functions
The project envisages an assistant able to explain instructions, rephrase them and respond to simple requests during the session. Graded assistance may include repetition, an example or guided practice, within defined rules.
Selection of the next activity must respect the repertoire and limits authorised by the professional. The assistant will not be able to change clinical goals independently. Session summaries must remain verifiable against the original data.
Responsibilities and development status
The professional retains control of the plan and its review. Integration between headset and portal, data recording, notifications and AI functions are planned components whose implementation and reliability require verification in the final system. The existence of a preview does not mean that a function is clinically available.

