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 4 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 just now. Counts are the feed's own, for the last seven days.
Specification: 1 of 88
Sources: All
Channels: All
Stage: All
Impact: All
More
Columns: All
Showing 1 of 1 (73 before filters) · summarised discussions only
| Question | Next step | Specifications | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| CRMI Block Vote 1 - Terminology (opens chat.fhir.org) | Are there any items in the proposed CRMI Block Vote 1 that members want pulled for individual consideration? | If approved as a block, CRMI terminology items would be adopted together, including requiring dependency tracking for concept map and code system supplement production use and removing compose-createdBy from the Publishable Value Set Profile. | No decision yet. The project team proposes approving the block of eight items (seven Persuasive, one Persuasive with Modification, one Considered for Future Use) and plans to seek approval on the TI Tracker call on November 9th. | Members review the block and request any items be pulled for individual consideration before the TI Tracker vote on November 9th. | CRMI, FHIR Terminology Service (Tx), Publishable Value Set Profile, ShareableCodeSystem, evs-1 |
| Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 30, 2026 · inferred | cds | FHIR Chat | 1 message this month · 12 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.