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
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
coverage-info on adaptive QR, pre-2.2 (opens chat.fhir.org)
Does DTR 2.2 support an adaptive selector Questionnaire that identifies separate clinical Questionnaires for later completion, including when $questionnaire-package is called without CRD or coverage-information, before filing a Jira request? A participant also asked where the spec-43 text originated.
Clarification
— The summary says nothing here.
Open question
Responding participant explained the intended flow: the selector Questionnaire must be used as clinical evidence, 'S' is supplemented rather than replaced, and forms are retrieved via $questionnaire-package using coverage-assertion-id or the resource plus related resources. Users choose which forms to complete. A participant traced the spec-43 text to the STU 2.0.0 DTR formal specification, introduced in an August 2023 overhaul tracked under FHIR-41854; no ticket with the exact wording found yet
The search for the originating tracker for spec-43 continues, and the work group or other implementers are expected to confirm whether DTR 2.2 supports the handoff without CRD or coverage-information.
Da Vinci DTR 2.2, Da Vinci DTR STU 2.0.0, Da Vinci PAS
  • FHIR-41854 (Published) · jira verified Nov 8, 2026
    1. Discussed (reached)
    2. Filed (reached)
    3. Triaged (reached)
    4. Resolved (reached)
    5. Applied (reached)
    6. Published (reached)

    Published · version not recorded

Machine summary · unreviewed · claude-haiku-5-5 · analysed Nov 6, 2026 · inferredDa Vinci DTRFHIR Chat4 messages this week · 37 hours 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.