How to use this page
Use Show controls for Help, Pages, Sections, Languages, Search, Play, and Voice. Major destinations open directly; full instructions are in Help.
Open Help for instructions. Open Languages for the language list.
School accessibility / EyeGaze branch
TL;DR — plain-language version
Project Fionigan started from the need to keep a complex medical journey and conference materials organized.
First and foremost, this work is for family, for the medical journey, for finding the right doctor, and for continuing to search for answers.
FND is still a learning journey. Understanding grows over time, and there is still more to learn. Clinicians may not always have the full FND picture either. That is where communication and continuity can break down fast.
This page first started as an online poster and handout. When the conference situation changed, the page became a lived report. That is what the one-page report is supposed to do: keep the important information together when things change.
The public website explains the program. Personal medical records and working continuity reports remain private and patient-controlled.
The rest of this page has the deeper detail.
De-identified public summary. Raw school-system records, raw visuals, and raw FOIA files are not deployed.
Project Fionigan keeps fragmented FND information connected, source-linked, and human-readable when lived communication becomes difficult.
New to FND? Functional Neurological Disorder (FND) is a real neurological condition that affects how the brain sends and receives signals, which can cause problems with movement, speech, sensation, thinking, or seizure-like episodes. NIH/NINDS overview.
I am not learning how to have FND. I am learning how to have FND publicly.
De-identified public branch
From medical continuity to school accessibility continuity
This page adds the Stafford school-accessibility material to the Project Fionigan journey without publishing raw records. The public site keeps the meaning: accessibility problems can be missed when a formal review, an incident record, video/still references, user experience, and later requests are split across different systems.
The public version is source-map based. Raw source ZIPs, raw email PDFs, raw visuals, staff contact details, and redaction-risk material stay private / DO NOT DEPLOY.
EyeGaze / school nutrition
Why this matters for EyeGaze and school systems
The school-accessibility branch shows how Project Fionigan can become a general access layer, not only a medical website. A student, staff member, family member, or visitor using eye-gaze, switch, keyboard, read-aloud, or low-motor-control access should be able to move through menus, nutrition information, accessibility instructions, forms, and emergency directions without relying on precise hand movement.
The overlay concept can support large buttons, read-all line-by-line, search, section jumps, language support, high-contrast controls, and fewer clicks. This is the same continuity problem in a new setting: the important information has to remain findable and usable when access is hard.
30-year IT / school nutrition logic
School nutrition audit logic became medical-record continuity logic
Project Fionigan carries forward more than 30 years of school-system technology and school-nutrition data work. That work included acting as a liaison between the school system and SNAP-related/direct-certification data flows, processing free and reduced-price meal applications, working direct-serve/direct-certification lists, and passing repeated federal, state, and local audits.
That background matters because the logic is the same: records have to be complete, matched, verified, corrected, auditable, and carried forward. I applied that school-nutrition and IT discipline to fragmented medical records, source trails, eligibility/status questions, complaint routes, and accessibility needs. That became Project Fionigan.
The public sources below are program context only. No student, household, SNAP case, school-system credential, application, or audit file is public here.
Every file represented
Four unique source packages represented without raw publication
Open de-identified item inventory
Accessibility study
The formal study and the lived access route have to be read together
The de-identified study summary preserves the key issue: the formal accessibility-review material and the later lived accessibility incident have to remain connected. The study branch is represented as source context, not as a raw PDF dump.
The public source map notes that the final high-school section lists interior/current-compliance items while the exterior accessible parking / curb-ramp / route-continuity area involved in the incident is preserved as an unresolved continuity question.
Open de-identified study summary
FOIA production
Document-by-document de-identified ledger
| Public item | Category | What is preserved publicly |
|---|---|---|
| FOIA-FILE-01 | Parking/accessibility email | Records a staff parking/accessibility concern and request for a closer non-visitor parking solution; public version removes names, emails, and exact internal addresses. |
| FOIA-FILE-02 | Parking/accessibility response thread | Contains ADA-related explanation and public-facility accessible-parking framing; public version preserves the accommodation issue without raw email metadata. |
| FOIA-FILE-03 | Accessibility-study email | References a final accessibility-study version and state-submission preparation; public version preserves existence of the study handoff. |
| FOIA-FILE-04 | HB2278/accessibility-study email | References submission of a finalized accessibility study and methodology discussion; public version preserves the legislative/accessibility-study connection. |
| FOIA-FILE-05 | FOIA request / preservation / incident thread | Contains forwarded preservation/request material and embedded incident images/screenshots; public version preserves that a preservation request existed without publishing raw images. |
| FOIA-FILE-06 | FOIA request follow-up thread | Includes internal handling around insurance/incident follow-up; public version preserves the response route without staff names. |
| FOIA-FILE-07 | Video/security request thread | References checking whether video was available; public version preserves the existence of a video-preservation/availability thread. |
| FOIA-FILE-08 | FOIA awareness thread | References awareness of the document request and internal routing; public version preserves routing, not raw correspondence. |
| FOIA-FILE-09 | FOIA clarification response | Requests specificity on scope and states preservation steps for potentially responsive surveillance footage; public version preserves the clarification/preservation status. |
| FOIA-FILE-10 | Video/still-shot thread | References video upload and still shots from an incident; public version preserves the native-video/native-still gap without displaying the raw images or identifying people. |
Open flat de-identified FOIA ledger
Evidence gap preserved
Native video / native stills are a preserved source gap
The public source map preserves the gap without publishing raw visuals: the reviewed production references video and still shots, while the native surveillance video and native still-image attachments were not present as separate produced files in the package available for this build.
This is a continuity problem: a PDF-rendered image is not the same as the native file, metadata, export log, timestamp trail, or custody chain.
Flat source files
Plain de-identified source files
Preservation anchor
Nothing substantive is deleted
When public display would expose identifying information or raw records, the line is not removed. It is compressed, de-identified, source-mapped, or moved to the private record. That rule applies here too.
Raw source packages remain private. Public page carries the de-identified meaning trail.