Now

Everything moving in the standards community

Discussions and publisher posts from every source the feed publishes, newest first. Each entry links to its source; nothing here is a copy of what was said.

Curated by Nicholas J. Dugan.

Sources

  • FHIR Chat — 111 messages this week across 31 feeds · last message 5 hours ago
  • HL7 Mailing List — 3 messages this week across 2 feeds · last message 37 hours ago
  • HL7 Blog — 1 post this week · last post 3 days ago

Feed checked 4 minutes ago. Counts are the feed's own, for the last seven days.

Specification: 1 of 88
Specification
Sources: All
Sources
Channels: All
Channels
Stage: All
Stage
Impact: All
Impact
More
More filters
Columns: All
Columns

Showing 1 of 1 (73 before filters) · summarised discussions only

Discussions and posts: topic, channel, source, date of last activity, question, where it stands, next step, impact, specifications, HL7 Jira items and who wrote the summary.
QuestionNext stepSpecifications
R4B version of FHIR Tooling Extensions IG (opens chat.fhir.org)
What is the recommended way to use the additional-binding extension in an R4B project when no R4B release of the hl7.fhir.uv.tools package can be located?
Clarification
Implementers in an R4B project may use the R4 version of the Tooling Extensions IG to get the additional-binding extension, per this suggestion.
Answered
A participant suggested simply using the R4 version of the Tooling Extensions IG for the R4B project. This is an informal suggestion; no formal decision or IG change was recorded.
— The summary says nothing here.
FHIR R4B, FHIR Tooling Extensions IG, FHIR R4— Cites no HL7 Jira item.Machine summary · unreviewed · claude-haiku-5-5 · analysed Nov 4, 2026 · inferredconformanceFHIR Chat2 messages this week · 3 days ago

Links open the source, which asks you to sign in if the discussion needs it. This page shows the newest entries the feed returns, not a complete archive. Summaries, including the Impact sentence, are written by a model from the discussion and say so until they are reviewed; they name no one. Stages, Impact categories and Jira statuses come from the thread and from HL7 Jira, not from a work group's formal record. A discussion whose chat has gone quiet stays listed while its Jira items are open or moving.