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 4 of 4 (73 before filters) · summarised discussions only
| Question | Next step | Specifications | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Determining what is In scope versus out-of-scope for PAS ver (opens chat.fhir.org) | Should the mapping support Loop 2000E SV3 and the claim.type 'oral' value, or is it out of scope? What determines transformation scope between PAS 2.2.1 and X12 005010 X217? | Implementers should treat SV3 and dental content as out of scope for PAS 2.2.1 to X12 278 5010 transformations, per the IG's supported use cases section. | Scope is determined by two things: X12 Glass documents what is currently mapped, but the spec has moved since the original maps, and a new mapping initiative is ongoing. The PAS 2.2.1 IG 'supported use cases' section lists items out of scope, and it names SV3 and dental as out of scope. Confirmed by a participant that this is the referenced section. Not stated explicitly whether 'oral' claim.type is out of scope. | The new mapping initiative is ongoing; no specific next action is stated in the thread. | Da Vinci PAS 2.2.1, Da Vinci PAS 1.2, X12 278 005010 X217 | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Nov 3, 2026 · inferred | Da Vinci PAS | FHIR Chat | 4 messages this week · 4 days ago |
| 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 |
| Mapping of claim.item.productOrService code to SV1 or SV2 (opens chat.fhir.org) | Can the Claim.type-based SV1/SV2 mapping pattern also be used for the PAS Response Bundle to 278-11 transformation (ClaimResponse.type institutional vs professional)? | Implementers may apply the same ClaimResponse.type-based SV1/SV2 mapping when transforming a PAS Response Bundle to 278-11, per the informal answer; no specification text change is recorded. | Earlier answer: Claim.type distinguishes institutional (SV2) from professional (SV1); dental (SV3) not supported in PAS 2.2.1; presence of Claim.item.revenue also indicates SV2. Follow-up: a participant asked if the same pattern applies to the Response Bundle using ClaimResponse.type, populating item and additem productOrService into SV2 or SV1. Respondent answered yes. No work group decision recorded. | — The summary says nothing here. | Da Vinci PAS 2.2.1, X12 278-13 005010X217, X12 278-11 005010X217 | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Nov 2, 2026 · inferred | Da Vinci PAS | FHIR Chat | 2 messages this week · 5 days ago |
| PAS Claim - careTeam:All Slices Provider References (opens chat.fhir.org) | Why does PAS Claim 2.2.1 require careTeam provider to be Organization or PractitionerRole rather than Practitioner, when X12 mappings point to Practitioner elements? Follow-up asks what PractitionerRole provides beyond Claim.careTeam.role and qualification. | Implementers cannot send a bare Practitioner as a careTeam provider in PAS Claim 2.2.1 and must use Organization or PractitionerRole; the X12 mapping inconsistency may be revisited. | A work group response said PAS allows the Organization as a PAS Organization and the Practitioner as a PAS PractitionerRole, because PractitionerRole identifies a practitioner working for a specific Organization. Contact details can differ per practitioner-organization combination, and one practitioner may work for several organizations, so a bare Practitioner is not allowed as a careTeam provider. A follow-up participant questioned whether PractitionerRole.code is what the 278 needs and whether | Await a work group response to the follow-up on what PractitionerRole adds over Claim.careTeam.role and qualification for the 278 mapping. | Da Vinci PAS 2.2.1 | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 31, 2026 · inferred | Da Vinci PAS | FHIR Chat | 4 messages this month · 7 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.