How it works
What each label rests on
How to read a card
Only source_read, jira_verified and human_reviewed are checks ImOnFHIR made. machine_summary is a reading, not a check. inferred says nothing about current state. A machine summary is always shown with its model and date; where the feed did not record the model, the card says so.
| Chip | What it means | What it does not mean |
|---|---|---|
| Machine summary · unreviewed · <model> · analysed <date> | A model wrote the summary on that date; nobody has checked it against the thread. | That it is right. |
| Reviewed by Nick · <date> | Nick checked the summary against the thread’s messages on that date and approved or corrected it. | That the thread is closed. |
| Open question | The machine summary reads the thread as not yet having reached an answer. | A work-group decision, a ballot outcome or a published change. It is a reading of the chat, unreviewed unless the card says Reviewed summary. |
| Answered | The machine summary reads a clear answer as given, without a formal decision. | A work-group decision, a ballot outcome or a published change. It is a reading of the chat, unreviewed unless the card says Reviewed summary. |
| Agreed | The machine summary reads the matter as settled by a work group, an editor or a ticket resolution. The model’s word is "decided"; it is published as "Agreed" because a model’s reading must not be published as a formal decision. | A work-group decision, a ballot outcome or a published change. It is a reading of the chat, unreviewed unless the card says Reviewed summary. |
| Deferred | The machine summary reads the matter as explicitly postponed. | A work-group decision, a ballot outcome or a published change. It is a reading of the chat, unreviewed unless the card says Reviewed summary. |
| Reversed | The machine summary reads an earlier answer or decision as changed. | A work-group decision, a ballot outcome or a published change. It is a reading of the chat, unreviewed unless the card says Reviewed summary. |
| Change accepted · Change proposed · Change rejected · Implementation issue · Clarification · Ballot · Release · Meeting / schedule | The kind of effect the machine summary says the discussion has on a specification or on implementers. | That the change has been made. "Change accepted" in a chat is not a published change. |
| ✔ resolved | Someone in the chat marked the Zulip topic resolved (Zulip prefixes the topic with ✔). | That a specification changed, or that the HL7 Jira items it cites are closed. |
| chat quiet | No recent chat in the discussion. It stays listed because HL7 Jira items it cites are still open or recently moved. Its date is the later of its last message and its last Jira change. | That the matter is resolved. |
| <HL7 Jira key> <status> and the lifecycle strip under it | The item’s public status as HORIZON last fetched it from HL7 Jira. A key with no status beside it has not been fetched; no status is guessed. | That the fix is published. "Applied" is not "published". |
| Not summarised yet. / The summary says nothing here. | “Not summarised yet.”: no summary is published for this discussion, because none has been written or the one written fell below the confidence HORIZON publishes at. “The summary says nothing here.”: the summary left this field empty. | That nothing happened, or that the page is broken. |
| source read <time>Not on cards today. | HORIZON fetched the thread, post or Jira issue at that time. | That anything was understood. |
| jira verified <date>Appears on a card once the feed carries evidence records. | The Jira status shown was re-read from HL7 Jira on that date. | That the fix is published. |
| inferredAppears on a card once the feed carries evidence records. | The summary was written before HORIZON recorded evidence for each reading, so all that is known is when it stored the last message the summary read, if that. | Anything about current state. |
How a thread is summarised
HORIZON reads the sources listed on the sources page. A model then writes the summary: the model named on each card; HORIZON's default is claude-haiku-5-5. The summariser runs on 7 * * * * (hourly, at seven minutes past). Nobody reviews a summary unless the card says Reviewed by Nick, and until then it is a machine summary. “The summary says nothing here.” is a deliberate answer: the summary left that field empty. It is not a bug.
How Jira status is re-read
The HL7 Jira keys on a card are re-read by HORIZON's jira-poll on 45 */6 * * * (every six hours, at 45 minutes past). The strip under a key runs Discussed, Filed, Triaged, Resolved, Applied, Published, and it is read from HL7 Jira's own status word and nothing else. A key whose status has not been fetched shows as Filed, because the ticket exists and that is all that is known. Resolved with no change, Duplicate and Deferred end the track in their own words; none of them is a change on its way into a version. A status word with no step mapped to it is shown as written and claims no step past Filed.
“Applied” is not “Published”, and neither names a version: both say “version not recorded”.
How a payload is validated
The FHIR Analysis Workbench sends a pasted payload to our API, which forwards it to our hosted validation sidecar, with a body cap of 1,000,000 bytes. Use synthetic or de-identified FHIR only. The security page has the detail. Every finding carries one of four severities: fatal, error, warning or information, and findings are sorted by severity.
Not stated here yet: the order in which structural validation and the business-rule layer run, what that layer does and does not catch, and what the tool cannot tell you.
How an IG comparison is computed
IG Compare loads two implementation guide packages and compares their profile requirements, ValueSets, CapabilityStatements and OperationDefinitions. IG Stack Compare compares a stack of two to five IGs: profiles matched across packages, ValueSets and CapabilityStatements.
Not stated here yet: how duplicate HL7 profile noise is collapsed into findings, whether dependency pins are compared, and what is not compared.
What “analysed” means
A card's analysed date is when the model read the source, not when the thread moved. The date beside “Last activity” is when the thread or its Jira item last moved.
Measured
The plan, decided and not yet running: every two weeks, on the 1st and the 15th, 50 public claims will be sampled and re-checked against their sources. Each result will be listed on the sources page. No run has been published yet. The published share will be a 95% lower bound: the true share is at least that, with 95% confidence.
What changed
- November 2026 — This page published. The stage, impact, summary, resolved and chat-quiet labels on a digest card link to their rows above.