Resources · capability register
What is not built
Most platforms describe the finished version and let you discover the gaps. Every capability on LymeHQ carries one of four states, and this page is the register. If a page you are reading claims something this register contradicts, the register is right and the page is a bug.
WorkingYou can use it today, on invented data. The flow completes end to end.
Blocked upstreamBuilt and proven up to a boundary we do not control. The blocker is named, and so is what is waiting on it.
Designed, not builtThe screens and rules exist and are decided. Nothing behind them runs.
Ruled outDeliberately not doing this. The reason is stated, and it is not a roadmap item.
How this page stays true
Every row below names the thing that must exist — or must not — for it to be in the list it is in, and a check reads those names against the codebase on every push. A feature that ships while still listed as not built fails the build in the commit that ships it. That is the only reason to believe a page like this.
01 · The register
Your record
20 capabilities, each in the state its own evidence supports.
- WorkingThe tick-bite workflowSeven steps, no account. What to record, what to hand a clinician, and what to watch for. Names no medicine and no amount.
- WorkingTimeline, check-in, daily logFive words, three taps. A day not logged stays a gap, and nothing is interpolated across it.
- WorkingLabs — entry, reading, safety rulesRecorded and shown against the performing lab range. Nothing is scored against a criterion.
- WorkingMedications — a record, not an engineWhat you take and when you started. No interaction checking, by rule rather than by omission.
- WorkingPre-visit brief, patient and provider sidesThe same document both people see. Figures and dates, no interpretation.
- WorkingFindings returned, with suppression shownA suppressed cell renders as suppressed rather than as blank.
- WorkingHousehold record and the pet sentinelA dog positive says ticks are present where you live. It never says a person is infected.
- WorkingExport everythingOne file, FHIR. No wait, no request, no reason required.
- WorkingDelete your accountRemoves it from every surface and view. Not yet a hard erase, and /privacy says so.
- Blocked upstreamCanine positives aggregated into a local presence signalA household can record its own dog result today, and county context is a sourced lookup to CAPC.Waiting on · Aggregating across households needs veterinary practices contributing results, and that portal is not built.
- Designed, not builtThe consent ledger and receiptsThe rules run today — every switch starts off, and scoped sharing is enforced. The page that shows you the history, and a revocation propagating, is designed and not built.
- Designed, not builtThe diagnostic odyssey, with the seroconversion overlayBite, onset and test date on one line, with the antibody window drawn as a band. A fact about timing, never a verdict on the test.
- Designed, not builtThe cost-of-illness ledgerOut-of-pocket, lost work days, caregiver hours, travel. The instrument HHS says does not exist.
- Designed, not builtReading a lab result from a PDFThe reader and the validation-status model are designed. No parser runs.
- Designed, not builtTell it once, and the waiting-room stateOne narrative in your words, rendered for a clinician, an employer or a family member.
- Designed, not builtThe red-flag card and its escalationA printable handover for an emergency room, and a screen that looks like nothing else in the app.
- Designed, not builtBeacon reading a tick photoSpecies and engorgement as observations to hand a clinician, never a risk number. Needs image input and the same output floor as every other Beacon reply.
- Ruled outA wellness score, a streak, or any number that grades youColour here encodes verified, shared or flagged. It never encodes how well you are doing.
- Ruled outDrug-interaction checkingWe hold the record. We are not the engine that decides what is safe to combine.
- Ruled outAny risk score or probability about a personA place gets a presence lookup. A person never gets a meter.
02 · The register
Clinicians and research
12 capabilities, each in the state its own evidence supports.
- WorkingShared with me, scoped to what was grantedExactly what the patient shared, for exactly as long as they shared it.
- WorkingProvider verification and directoryAn approval means a person checked a licence and a practice. Nothing wider.
- WorkingCohort counts, k of at least five enforced before displayCounts only. The threshold is enforced in the query, not in the template.
- Designed, not builtThe clinician read pageOpened from a QR code, no login. A thirty-second read of a patient-reported exposure record. Expires.
- Designed, not builtPre-visit delta — what changed since last visit
- Designed, not builtThe clinical reasoning recordBoard-defensible documentation: the reasoning, the consent, the monitoring plan and the guideline version in effect. Designed in full, not built.
- Designed, not builtThe Research Priority CommonsIncluding the gap card — when a question cannot be answered yet, which data element is missing.
- Designed, not builtThe recruitment bridgePull, never push. A researcher sees a count and never a list; patients opt in from their own side.
- Ruled outRatings and reviews of cliniciansA listing will never mean a star rating.
- Ruled outAny export that could identify a personNot a setting, not an admin override, not a research exception.
- Ruled outBenchmarking clinicians against each other
- Ruled outRegimen composition — doses, durations, stop criteriaNot parked pending a better idea. Not our decision to make.
03 · The register
Data and standards
7 capabilities, each in the state its own evidence supports.
- WorkingCDC tickborne surveillance, 1992 to 2023Pulled under fixed published controls: if the 2019 figures do not match the published numbers, the extractor refuses to write. Case-definition changes are drawn into the charts rather than smoothed over.
- WorkingThe element set and codebookWhat each field means, and which code system it belongs to.
- Blocked upstreamCMS Blue Button 2.0 — your own Medicare claimsThe consent gate, the PKCE exchange and the redirect chain to CMS are built and proven against production.Waiting on · The sandbox synthetic beneficiary logins fail at medicare.gov SSO. Two published test seats fail identically, and the CMS sample client fails the same way with MissingPatientError. Reported. No claims data has ever moved.
- Blocked upstreamPathogen presence at block-group levelThe geography and the withholding rule are built — nothing under five is ever shown.Waiting on · The data needs a sharing agreement we do not have.
- Designed, not builtPatient portal importThe route is Epic Individual Access Services under TEFCA — patient-directed, USCDI v3, free to developers. Designed, not built.
- Ruled outNHANES as a population baselineProbed and retired in August: no released cycle carries Borrelia content, and the API path we had cited does not exist. It was named as a live source in two prototypes before that check ran.
- Ruled outCURE ID as a sourceIt is a destination, not a source — there is no API in either direction. The honest verb is to prepare a submission.
04 · The register
Products and the shelves
4 capabilities, each in the state its own evidence supports.
- Designed, not builtTwo shelves — prevention and supplementsGraded, never ranked. Commission disclosed, and with no effect on either the grade or the order.
- Designed, not builtA verified listing-level data sourceListing counts are illustrative until a real catalogue backs them.
- Ruled outPaid placement changing a grade or an orderCommission is disclosed and affects neither. If that ever changes, this line changes first.
- Ruled outDosing guidance on a product pageWhat a thing is, and what the evidence says. Never how much to take.
05 · The register
The Tick Offensive
5 capabilities, each in the state its own evidence supports.
- Designed, not builtThe Tick Offensive — landing, town page, trackerPets first, people second, yards last, then measure whether it worked.
- Designed, not builtOrganiser and volunteer coordinationTen further screens — enrolment, shifts, door cards, packing, backers, recognition. Designed in full. They only mean something with real towns in them.
- Designed, not builtA published post-season result for every townThe campaign promises measurement. That promise is not yet kept anywhere.
- Ruled outRanking towns or households against each otherStandings score participation on a street, and stop there.
- Ruled outApplication instructions for any pesticideWe log what was done and measure what followed. We never tell anyone how to apply anything.
Everything about a person here is invented
The flows complete, the states are real and the rules are enforced — but the people, labs, towns and results are not. Two things are not invented: the case counts come from CDC surveillance under fixed published controls, and the education library is finished and true.
Where to go next
- The loopHow LymeHQ worksWhat you put in, who can see it, and what comes back.
- What is nextPublic roadmapWhat is built, what is coming, and what has been dropped.
- Your controlsYour data, your rulesEvery sharing switch, and what still works if you leave it off.
- The mechanismsSecurityWhere each rule is enforced, and what we refuse to claim.