In order, and without dates

• The daily record, and the arithmetic on it

  A check-in that takes under a minute, the medications you are taking and when you started them, and the figures either side of each start date — computed by counting, with an explicit refusal when there is not enough data to say anything.

• Lab results, read and explained

  A two-stage pipeline that transcribes a report and then explains it, with the explanation checked before you see it, on a page that shows what the laboratory reported alongside what the panel measures.

• Beacon

  A companion for questions about tick-borne illness, gated on a switch you hold, that never computes a trend and whose every reply is read in full before any of it reaches you.

• Sharing with a clinician, and taking it back

  Two locks, both yours. Their view of your record ends on their next page load when you withdraw either one.

• The household, and the sentinel signal

  People and animals in one household. A positive routine tick-exposure test on a dog tells everyone in that household, once, gated by no sharing switch at all.

• The research commons, approval included

  Cohort feasibility counts, saved cohort definitions, an approval queue where every verdict is recorded against the person who made it, and an export a researcher downloads themselves once approved — enforced end to end in the database, so a released figure always describes five or more people, with no configuration that lowers that floor.

• The education library

  Twelve guides, an eleven-chapter guided course, a six-step path for someone newly diagnosed, and a glossary. All public, all free, no account.

• A directory of clinicians, each checked by a person

  Public and account-free, filtered on the two things the record actually holds — the states a clinician says they are licensed in, and whether they see patients remotely. A listing appears only when someone has reviewed a licence document and recorded that they did, on a trail that names them and cannot be edited afterwards. The state filter is self-reported and the page says so beside it.

• Findings, returned to the people who made them possible

  Group figures from the research commons, on your own dashboard, when your record matches the group they describe. Figures only — never a sentence claiming a treatment caused a change, and never your own numbers shown beside a group average. Nothing is sent to you and nothing is stored about which findings matched you.

• A map of where the disease actually is

  Every reported case by state and year, from the federal surveillance series, with the two definition changes drawn into the picture rather than smoothed over. A jurisdiction that published no count is drawn as no count — never as zero — because reading an absence as safety is the one mistake this map exists to prevent. Public, account-free, and it carries no patient data of any kind.

• A written description of what this record holds

  The element set behind the platform, published in full — including the thirteen things no existing standard has a place for — and a download of your own record in the standard format, with the file naming every element it does not carry rather than inventing one. A draft for discussion, submitted to nobody, and it says so on the page.

• A written summary for a visit

  Figures and dates from your record, composed when your clinician opens it and stored nowhere — so withdrawing the switch ends it on their next request, with no copy left behind. You read exactly what they read, before they can, on your own page. Dates, medication names and the readings either side of them; no dosages, and no sentence claiming anything caused anything.

• A map of the field, and a directory of everyone in it

  Where a patient’s data actually goes once it leaves them — six channels, six different owners, and the two of them that bring anything back. Beside it, every organisation in tick-borne disease we could verify from its own public material: advocacy, government, professional societies, laboratories, apps, assistance. Nothing is ranked, everything says when we last read it, and the tools that compete with this one are on the list.

• Help with what care costs

  The grant application, review and disbursement.

• Community, and shared aggregates between patients

  Moderated, and never public before review.

• Caregiver access

  Parked until the design question underneath it is answered rather than worked around.

• Tracking what treatment has cost you

  What the insurer paid can already arrive with an imported claim. What you paid — and appealing a denial — is the part that is not built.

• Matching to clinical trials

  The reference data exists; the match needs its own consent decision first.

• Standards

  Consent is enforced by the database, not by discipline: every change a patient makes appends to a ledger the application cannot edit, and revoking takes effect on the next request — no grace period, no cached copy.

• Aggregation

  The research commons answers in counts, five or nothing. A group small enough to count is a group small enough to identify, so below five the platform declines what it could compute — enforced beneath the application, where no query reaches around it.

• Visualization

  Every trend on every surface is arithmetic; language models only phrase what the arithmetic already decided. "Not enough data to say" is a row count, never a confidence — which means no one is ever told they are improving when the data cannot say.

• The platform

  One record, three roles. The same days a patient logs become what her clinician reads and what researchers count — and she decides, at every step, what leaves and to whom.

LymeHQ was selected for Phase 2 of the LymeX Innovation Accelerator. That is a program milestone, not an endorsement — nothing here is government-backed, and nothing above becomes true because a panel liked it. The order of work is the list on this page.