For clinicians
The consultation that begins where the last one ended.
You see your SCA patients for twenty to thirty minutes, twice a year. The clinical information available to you when they sit down is whatever they manage to reconstruct from memory under time pressure. The Continuous Care Layer gives you structured access to the intervening months.
The clinical encounter for SCA is episodic. The disease is not. What occurred between appointments — the falls, the functional decline, the medication responses, the progressive changes the patient has adapted around and stopped noticing — arrives at your desk, if at all, in fragments retrieved under time pressure from a patient who is also managing anxiety, fatigue, and the cognitive load of being in a clinical setting.
The information gap is not the patient's fault and it is not yours. It is structural. No tool has been built to close it — until now.
The Continuous Care Layer
What the clinical interface delivers
Pre-visit consultation package
Before each appointment, Wimly assembles a structured summary of the patient's observations since the last visit — organised by functional domain, temporally sequenced, and flagged by the patient for clinical significance. You review it before the consultation. The patient arrives knowing you have seen it. Neither of you starts from zero.
Asynchronous scheduled check-ins
Structured observational check-ins completed by the patient at regular intervals — not at scheduled clinic visits. The data accumulates continuously and is available in the clinical interface as a longitudinal record. You can review it before the appointment, during it, or between visits at your discretion.
Between-appointment message channel
A structured, non-urgent communication channel that replaces the ad-hoc phone calls, emails-to-secretaries, and corridor conversations that currently serve as the only between-appointment mechanism. Patient-initiated messages are threaded and context-linked to the relevant observations. Responses are at clinical discretion — there is no expectation of real-time availability.
Attention flags
Patients can flag observations they believe warrant your awareness before the next scheduled appointment. Flags appear in the clinical interface with the supporting observation record. They are not emergency alerts — they are patient-initiated signals that something has changed and the patient considers it clinically relevant.
By design
What the Continuous Care Layer is not
- It does not add to your task queue. You review what you choose, when you choose. No notifications requiring a response. No escalation pathway that routes to you without your consent.
- It does not bypass clinical judgement. All observations in the interface are patient-reported and labelled as such. Clinical assessment, interpretation, and decision-making remain with you.
- It is not an emergency pathway. The platform instructs patients clearly that it is not a substitute for emergency services or acute clinical contact. Attention flags are between-appointment signals, not urgent alerts routed to you.
- It is not a data extraction tool. The patient controls what is shared with you. Consent is patient-initiated, granular, and revocable. You receive what the patient has approved — nothing more.
I'm a neurologist. I see SCA patients for twenty minutes twice a year and I spend most of that time just trying to figure out what happened since last time. If a patient walks in with six months of organised observations, I skip the guesswork and go straight to the stuff that matters. Wimly doesn't just help patients. It helps me do my job properly.
Neurologist
Self-assessment
A short self-assessment to identify how the Continuous Care Layer fits your clinical context and patient population.
Clinical questions
Does this add to my workload?
The Continuous Care Layer is designed explicitly not to. The patient generates and organises the observations; you receive them in structured form before each visit, not as a continuous stream requiring your attention. There are no notifications demanding a response. The consultation package arrives as scheduled pre-visit prep. Your engagement with the record is at your discretion, at the times you choose.
What does the clinical interface actually show?
A structured summary of the patient's documented observations since your last visit, organised by functional domain and flagged for clinical significance by the patient. You have access to the full record if you want it, but the default view is a curated summary designed to inform your clinical reasoning — not to replace your assessment. You also see any messages the patient has marked for your attention and the pre-visit consultation package the patient has assembled.
How is patient consent handled?
Consent to share observations with you is patient-initiated and patient-controlled. The patient decides what to share, how much, and when — and can modify or withdraw consent at any time. You receive what the patient has approved for sharing. The platform creates no obligations on either side: if a patient does not connect their record to your clinical account, you see nothing. All patient-reported observations are labelled as such in the clinical interface.
What if something in the record needs urgent clinical attention?
The Continuous Care Layer is not designed for clinical emergencies — it is a structured between-appointment channel, not an urgent care pathway. Attention flags allow patients to signal that they believe something warrants your awareness before the next scheduled visit, but the platform includes a clear disclaimer that it does not replace emergency services or acute care pathways. Wimly is a clinical context tool, not a clinical monitoring tool.
Get early access
Wimly is here.
Wimly v1 is approaching. Founding supporters get access on day one and a role in shaping how the platform develops.