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 1 minute 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 1 of 1 (73 before filters) · summarised discussions only
| Question | Next step | Specifications | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 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.