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
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 | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
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.