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
Appointment Book Coverage Information Extension (opens chat.fhir.org) · chat quiet
How should coverage-assertion-id be sent as context when no order is selected, given context is 0..1 but SHALL be included if coverage-information was available? Also whether an Appointment may be DTR launch context, and why QuestionnaireResponse.context is 0..*.
Change proposed
— The summary says nothing here.
Open question
Partly clarified: an Appointment can be sent when launching DTR, and the app would retrieve the ServiceRequest if the Appointment is tied to one. QuestionnaireResponse.context is 0..* because one response may apply to several orders while only one order is in context at launch. A participant asked for a change request; FHIR-59401 was submitted for discussion. Not settled: the no-order-selected case for the SHALL on coverage-assertion-id context. No decision recorded.
The work group discusses FHIR-59401 to resolve how coverage-assertion-id context is sent when no order is selected.
Da Vinci CRD, Da Vinci DTR 2.2.0, SMART App LaunchMachine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 · inferredDa Vinci CRDFHIR Chatchat quietChat quiet since Sep 23 · FHIR-59401 moved 8 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.