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 36 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
Sources: All
Channels: All
Stage: All
Impact: All
More
Columns: All
Showing 3 of 3 (73 before filters) · summarised discussions only
| Question | Next step | Specifications | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| open quality (opens chat.fhir.org) | Will the project join a January Connectathon focused on shared libraries (CRMI-based), with the 69 shared libraries and further measures published for testing? | — The summary says nothing here. | A participant agreed to a January Connectathon focused on the shared-libraries question. The project is listed on the CQL community projects page. The 69 shared libraries and any ready measures will be published on openquality.us for testing. A read-only MCP server at openquality.us/mcp was also announced, returning measure CQL, provenance, known interpretation issues and the CRMI Bundle with commit references. No change to the CQL or CRMI standard was proposed or agreed. New: a Clinical Reasoni | Participants are invited to give input on the proposed Clinical Reasoning authoring scenario for the Open Quality repository. | CQL, CRMI, FHIR Library resource | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Nov 7, 2026 | cql | FHIR Chat | 2 messages this week · 13 hours ago |
| 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 |
| CRMI and Inheritance (opens chat.fhir.org) | Is there guidance on how to handle inheritance of CRMI lifecycle metadata, since inherited profiles carry the CRMI extensions and so show incorrect authors, reviewers and similar information for each module? | Implementers using CRMI lifecycle metadata with profile inheritance may publish inherited profiles with metadata that does not match their own authors and reviewers, unless guidance is given. | No answer yet. A participant reports that CRMI extensions applied for lifecycle metadata in the German MII Core Data Set are inherited by derived profiles, so module-specific authors and reviewers are wrong when inherited. | — The summary says nothing here. | CRMI, German MII Core Data Set | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Nov 2, 2026 · inferred | cql | FHIR Chat | 1 message this week · 6 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.