Looking for Feedback From Neurologists on Structured Migraine Summaries

This article is an open question, not a confident answer. It is an attempt to think carefully, in public, about something we are genuinely uncertain about: whether the structured migraine summaries that Migriscope helps patients prepare are actually useful to the neurologists and headache specialists who receive them.

We have a hypothesis. We have tried to build something thoughtful. But we have not run a clinical trial, and we are not claiming that our current format is validated or optimal. What we are doing is asking — and trying to ask in a way that is specific enough to be useful.

If you are a neurologist, headache specialist, or other clinician who regularly sees migraine patients, we would genuinely welcome your perspective. The invitation at the end of this article is serious.

Why the Idea Emerged

The starting point was straightforward: people with migraine often arrive at neurology appointments without a clear account of their own history. Not because they are careless, but because migraine is a condition that makes accurate recall genuinely difficult. Attacks vary. Medication responses are mixed and change over time. The cumulative impact on daily life is hard to estimate without prospective tracking.

The result, in many appointments, is that a significant portion of available time is spent on basic history-taking — extracting information that the patient possesses but struggles to organise and communicate quickly. This is inefficient for both parties, and leaves less room for the clinical questions that actually require a specialist’s expertise.

The hypothesis behind appointment preparation is that structured prompts — asking patients to think through attack frequency, medication history, symptom patterns, and functional impact before they arrive — might reduce this friction. The patient comes in with the key information already organised. The clinician can move through it quickly and spend more time on assessment and planning.

That is the hypothesis. What we genuinely do not know is how well it holds up in practice, and in whose practice.

Communication Fatigue Is Real

One thing we are fairly confident about is that the problem of communication fatigue is real. This is the experience — common among people with long-standing chronic conditions — of having explained their history many times, to different clinicians, in different settings, often starting from scratch because previous records were not available or not reviewed.

For someone with a ten-year migraine history, the task of reconstructing that history from memory at the start of an appointment with a new neurologist is not trivial. It is also emotionally wearing. There is a particular frustration in trying to convey the shape of a condition that has affected your life significantly, in the few minutes available, in a context where you may already be managing anxiety about the appointment itself.

Structured preparation does not solve all of this. But it may reduce the cognitive load of the moment — making it less about retrieval and more about conversation.

The Complexity of Medication History

Medication history is one of the areas where preparation seems most potentially valuable, and also where the risks of inaccuracy are most consequential.

People with chronic migraine may have tried multiple preventives, several acute treatments, and various combinations over many years. The names, dosages, approximate dates, and reasons for stopping are exactly the kind of information that a neurologist needs but that is hardest to recall accurately in the moment. Getting this wrong — or omitting it — can lead to duplicated efforts or unconsidered interactions.

At the same time, we are aware that patient recall of medication history is inherently imperfect. People remember that a medication caused problems more reliably than they remember which medication it was. Approximate dates are often very approximate. Dosages are frequently unknown.

What we try to do is prompt for honest uncertainty — asking patients to note what they are unsure about, rather than encouraging them to fill in gaps with guesses. Whether this approach produces summaries that are actually more useful than what clinicians receive without preparation is something we want to understand better.

What Information Is Actually Helpful to Clinicians?

This is the question we most want to ask neurologists directly.

Our current approach prompts patients to organise information across several areas: attack frequency and pattern, acute medication use and response, preventive medication history, associated symptoms, functional impact, and any identified triggers. We have tried to keep each section concise and to focus on what seems clinically relevant.

But we are making educated guesses about what is most useful. We do not know, for example:

• Whether a one-page summary is the right format, or whether something more structured — perhaps a table for medication history — would be easier to review quickly.
• Whether including functional impact data (missed workdays, disrupted activities) adds useful context or introduces noise.
• Whether trigger information, which patients often find meaningful but which is clinically uncertain, belongs in a pre-appointment summary at all.
• Whether the level of detail we prompt for is appropriate, or whether it tends to produce summaries that are too long to be useful within the constraints of a short appointment.
• Whether there are things we are not asking about that would be valuable to know before a specialist consultation.

These are not rhetorical questions. They reflect genuine uncertainty about whether the current format serves the people who are supposed to benefit from it.

The Risk of Becoming Noise

There is a version of structured patient-generated summaries that is counterproductive. If the output is too long, too detailed, or structured in a way that does not match clinical workflows, it creates work rather than reducing it. A neurologist who arrives at an appointment to find a three-page printout has not been helped by the preparation — they have been given a new task.

We think about this risk often. The tension between comprehensiveness and usability is real. A complete account of a patient’s migraine history might run to many pages if compiled carefully. A genuinely useful summary for a 25-minute appointment is probably much shorter.

The right balance is not something we can determine from our position as builders alone. It depends on clinical context, on individual clinician preferences, on the type of appointment, and on what information the clinician already has available through other channels. These are things that clinicians can speak to much better than we can.

Trying to Respect Clinical Workflows

One of our design principles is that Migriscope should support clinical workflows rather than create friction within them. This sounds obvious but has real implications.

It means the summaries patients prepare should be easy to review quickly, not just comprehensive. It means the language should be clear and unambiguous, not filtered through clinical terminology that patients may use imprecisely. It means the format should be something a clinician can scan in the first minute of an appointment, not something that requires careful reading to understand.

We have tried to build toward this, but we are working somewhat blind. Neurologists vary in how they structure appointments, what information they prioritise, and how much they rely on patient- provided history versus information in existing records. There is no single clinical workflow to design for.

What we can do is try to make the output as clear and scannable as possible, and to be honest about its limitations. The summary a patient generates through Migriscope is a starting point for a clinical conversation, not a clinical document. We try to make that clear in how the product communicates what it produces.

What We Are Not Trying to Do

It may be useful to be explicit about the scope of the problem we are working on, and what falls outside it.

Migriscope is not trying to replace clinical history-taking. A patient-prepared summary is a supplement to the clinical encounter, not a substitute for it. The examination, the differential, the clinical judgment — these belong to the neurologist.

We are also not trying to standardise the information that patients present to clinicians in a way that constrains clinical judgment. The goal is to help patients communicate what they know more clearly, not to tell clinicians what to do with that information.

And we are not trying to create a medical record. The summaries patients generate are informal documents intended for use in a specific appointment. They are not archival, not validated, and not equivalent to information in an electronic health record.

Being clear about these limits is, we think, part of respecting the clinical context in which the tool is used.

Uncertainty We Are Sitting With

There are a few areas where we are genuinely uncertain and where we think that uncertainty is honest rather than false modesty.

First, we do not know whether patients who use structured preparation tools actually arrive at appointments better prepared in ways that clinicians notice and value. The assumption seems reasonable, but assumptions are not evidence.

Second, we do not know whether structured summaries reduce appointment time spent on history-taking, increase the quality of clinical decisions, or improve patient experience in measurable ways. These would be meaningful outcomes to demonstrate, and we have not demonstrated them.

Third, we do not know whether our current format is the right one. It represents our best thinking about what is useful, informed by reading about migraine management and clinical consultation, but not validated through systematic feedback from the clinicians who would use it.

We are publishing this uncertainty because we think it is more honest than presenting Migriscope as a solved problem. It is a reasonable attempt at addressing a real challenge. Whether it succeeds, and in what ways, is still an open question.

An Open Invitation

If you are a neurologist, headache specialist, general practitioner with a migraine patient population, or any other clinician with a view on what helps and what does not in patient-prepared appointment summaries, we would genuinely like to hear from you.

Specifically, we are interested in:

• What information in a patient-prepared migraine summary do you actually find useful when reviewing it before or at the start of an appointment?
• What information tends to be noisy, unhelpful, or potentially misleading?
• What format — length, structure, level of detail — would work best within the time constraints of a typical consultation?
• Is there information that patients rarely think to include but that you consistently find yourself needing?
• Do you have concerns about how patient-prepared summaries might affect the dynamics of a clinical encounter?

We are also interested in hearing from patients about their experience of preparing for neurology appointments — what is hard, what feels useful, and what is missing from tools like this one.

There is no form to fill in, no data we are collecting. We are simply asking. If you have views, we will read them carefully. You can reach us here.

We do not claim to have built the right thing. We have built a considered attempt at something useful, and we are genuinely open to being told where it falls short.