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
PAS IG ClaimResponse.addItem.itemSequence cardinality (opens chat.fhir.org)
Is the PAS IG's intended cardinality for ClaimResponse.addItem.itemSequence 1..1 or 1..*, and why is it an array rather than a positiveInt?
Clarification
No change to the specification is indicated; implementers should treat itemSequence as an array constrained to at most one item, consistent with base R4 ClaimResponse.
Answered
A respondent said itemSequence is an array in the base FHIR definition, constrained in the profile to a maximum of one member. Asked why it is not a simple positiveInt, the respondent said FHIR resource schemas are fixed across all use cases, so if an element is an array anywhere it is an array everywhere, which lets systems process instances in a use-case-independent way. This is a common pattern across Da Vinci IGs. No formal decision or change to the profile was recorded.
— The summary says nothing here.
Da Vinci PAS, FHIR R4 ClaimResponse— Cites no HL7 Jira item.Machine summary · unreviewed · claude-haiku-5-5 · analysed Nov 7, 2026 · inferredDa Vinci PASFHIR Chat4 messages this week · 33 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.