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 just now. 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 | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| PAS Claim.Identifier.System (opens chat.fhir.org) | In the Claim resource, would there always be one identifier with system value urn:trnorg:<TRN03>? Why is the maximum Claim.identifier cardinality 2? | Receivers should accept one or two Claim identifiers and should not reject a Claim whose identifier system is not urn:trnorg, per the SHOULD wording; the TRN-mapping rationale is explained but no change to the standard is proposed. | Per a reply citing the published PAS 2.2.1 package: Claim.identifier is 1..2 (unsliced) in profile-claim and profile-claim-update, and 1..1 in profile-claim-inquiry. Claim.identifier.system is 1..1 with a SHOULD to use urn:trnorg:<TRN03> for the TRN. A later reply from the IG side says Claim.identifier maps to the X12 TRN segment (as does ClaimResponse.identifier). The maximum of 2 comes from X12, which allows an originating claim TRN plus one added by any clearinghouse. A SHALL was considered, | — The summary says nothing here. | Da Vinci PAS, Da Vinci PAS 2.2.1, X12 278 | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Nov 2, 2026 · inferred | Da Vinci PAS | FHIR Chat | 3 messages this week · 5 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.