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 5 of 5 (73 before filters) · summarised discussions only
| Question | Next step | Specifications | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| FHIR Camp Hackathon (opens chat.fhir.org) | Null: a participant asked another to look at a GitHub issue about FHIRPath .resolve behaviour. | Expected: engine hooks will let hosts supply their own .resolve implementation, and hackathon cross-version maps will be added to the official map set; the extension is expected to add map testing against custom input folders with coverage reporting. | A FHIRPath .resolve issue in the fhirpath-lab project is acknowledged as a known issue tied to a common shortcut for search parameter processing. The engine maintainer plans to add hooks so hosts can supply the implementation. The engine and tools will move to their own repo and npm package after more testing. Cross-version map changes from the hackathon are to be contributed to the official set, with the participant to announce when they are there. A new extension feature is previewed to help c | The cross-version map changes are to be contributed to the official set, and the participant will announce when they are published. | FHIR R6, FHIRPath, FHIR Mapping Language | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Nov 8, 2026 | FHIR Mapping Language | FHIR Chat | 12 messages this week · 4 hours ago |
| Updated HL7 Terminology (THO) Freeze Date: January 17, 2027 (opens chat.fhir.org) | — The summary says nothing here. | Terminology content intended for THO must be ready by the January 17, 2027 freeze, though the dates are not yet officially confirmed by FMG. | THO freeze date is Jan 17, 2027 (moved from Feb 7, 2027), with release around Jan 31, 2027. New posts say the out-of-cycle FHIR R6 ballot is coming before May 2027, and that the dates are still based on proposed dates pending an official update from FMG. | An official date update from FMG is awaited, and a reminder is to be sent two weeks before the January 17, 2027 freeze. | HL7 Terminology (THO), FHIR R6, HL7 May 2027 ballot cycle | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Nov 7, 2026 · inferred | implementers | FHIR Chat | 3 messages this week · 34 hours ago |
| Updated HL7 Terminology (THO) Freeze Date: January 17, 2027 (opens chat.fhir.org) | — The summary says nothing here. | Terminology content submitters must have THO changes in by the earlier January 17, 2027 freeze, and the THO release moves earlier to support the FHIR R6 and May 2027 ballots. | THO content freeze is now January 17, 2027 (previously February 7, 2027), with a published release expected around January 31, 2027. TSMG approved the earlier timeline. A reminder will be sent two weeks before the freeze. | A reminder about the freeze is to be sent two weeks before January 17, 2027. | HL7 Terminology (THO), FHIR R6, May 2027 ballot cycle | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Nov 6, 2026 · inferred | Announcements | FHIR Chat | 1 message this week · 38 hours ago |
| What things can an AI do? (opens chat.fhir.org) · chat quiet | Can an AI author resources it should be able to, e.g. be Observation.performer, given the R6 clinical resource model? Should clinical resources be reviewed for AI-authorship gaps? | — The summary says nothing here. | No decision recorded. Participants agree an AI making an observation is distinct from a device measuring one, and the line is hard to define. One view: an AI should be the performer only when acting for a liable human; a regulated device could be the performer. A later clarification: the Device resource is also used to represent software and other agents, so the question remains open. FHIR-58672 is referenced for the review. | — The summary says nothing here. | FHIR R6 |
| Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 · inferred | AI Transparency on FHIR | FHIR Chat | chat quietChat quiet since Sep 8 · FHIR-58672 moved 17 days ago |
| ActivityDefinition (opens chat.fhir.org) · chat quiet | How to migrate Dosage to R6 ActivityDefinition steps; how timing[x] relates to dosage and MedicationRequest on apply; how RelativeTime, asNeeded and observation requirements map; where the invalid example maps should live. | The example maps are to be marked informative and relocated to the CPG IG; the timing, RelativeTime, asNeeded and condition mapping questions are still unresolved. | Partly resolved: the invalid example maps (work in progress) are to be marked informative and moved to the CPG IG, which ballots in September; Jira FHIR-57774 logged. One implementer shared an R4-to-R6 alteplase example (one step with multiple components, step texts concatenated into renderedInstruction). Timing, RelativeTime, asNeeded and condition questions remain unanswered. | — The summary says nothing here. | FHIR R4, FHIR R5, FHIR R6, ActivityDefinition, Dosage, DosageDetails, CPG IG, FML |
| Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 · inferred | cds | FHIR Chat | chat quietChat quiet since Jun 29 · FHIR-57774 moved 46 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.