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.
Sources
- FHIR Chat — 227 messages this week across 31 feeds · last message 14 minutes ago
- HL7 Mailing List — 10 messages this week across 2 feeds · last message 36 minutes ago
- HL7 Blog — 1 post this week · last post 5 days ago
Feed checked 8 minutes ago. Counts are the feed's own, for the last seven days.
Sources: All
Channels: All
Stage: All
Impact: All
More
Columns: All
Showing 67 of 67
| Question | Next step | Specifications | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| New message on the davincipublic list (opens lists.hl7.org) | davincipublic | HL7 Mailing List | 2 messages this week · 36 minutes ago | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — Cites no HL7 Jira item. | — The source keeps this topic private, so it has no summary here. |
| New message on the davincipublic list (opens lists.hl7.org) | davincipublic | HL7 Mailing List | 1 message this week · 54 minutes ago | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — Cites no HL7 Jira item. | — The source keeps this topic private, so it has no summary here. |
| Ballot (opens chat.fhir.org) | Announcements | FHIR Chat | 1 message this week · 1 hour ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| CRD Card Response (opens chat.fhir.org) · ✔ resolved | Da Vinci CRD | FHIR Chat | 1 message this week · 2 hours ago | Is it compliant for a CRD response to return only a context identifier (coverage-assertion-id) for DTR rather than a questionnaire or policy URL, and how does a non-payer DTR app resolve it? | Answered A CRD response need only point to the form to be filled out; no policy URL is required (detail.value may optionally point to one). CRD need not name specific Questionnaires; DTR determines forms. With CRD supported, EMRs should always call DTR with a context id; DTR can be launched without CRD in phased deployments. Each payer has one DTR server, which is the payer's responsibility. The DTR app never resolves context to questionnaires itself; the DTR client calls $questionnaire-package on the pa | — The summary says nothing here. | Clarification — The summary says nothing here. | Da Vinci CRD, Da Vinci DTR, SMART Backend Services | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| incorrect report of "unable to determine system" (opens chat.fhir.org) | implementers | FHIR Chat | 2 messages this week · 3 hours ago | Is the incorrect "unable to determine system" report still a problem with the complete guide, given the August workaround that removed the primitive binding? | Answered Implementer says the original failure came from binding PhdUnitCodeVS to the primitive origin.code, which receives a bare code and cannot resolve system. Tested on validator 7.0.2 with R5 and R6 ballot5 synthetic code systems: Quantity-level binding gives zero errors for qualified codes, unknown codes and missing systems still fail. The August workaround already removed the primitive binding, so the current downloaded profile is not a current failure. Mixed-system value set would need the Quanti | Not stated in the thread; the IG authors would need to decide whether to retain the mixed-system value set using the Quantity-level binding. | Change proposed Proposed: Observation.value[x].origin would carry the required binding to PhdUnitCodeVS in place of the origin.code binding, if the mixed-system value set is retained. Current guide already has the primitive binding removed. | PHD IG, FHIR R5, FHIR R6 ballot5, FHIR Validator 7.0.2 | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 20, 2026 |
| October 2026 - Block Vote 2 (opens chat.fhir.org) | bulk data | FHIR Chat | 3 messages this week · 3 hours ago | Whether any ticket in the second Bulk Data block vote should be pulled from the block for discussion. | A second block vote of 20 Bulk Data tickets is scheduled for the October 28 call. The post lists nine with proposed dispositions (mostly Persuasive, some Persuasive with Modification, one Considered for Future Use). No vote has taken place yet. | Participants may request that a ticket be pulled from the block; the work group votes on the block at the October 28 call. | Ballot If the block passes, the listed Bulk Data tickets will be resolved with the proposed dispositions, which may change the Bulk Data specification text. | Bulk Data (FHIR) | FHIR-58835 (Triaged), FHIR-58923 (Submitted), FHIR-58910 (Submitted), FHIR-58979 (Submitted), FHIR-58983 (Submitted) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 20, 2026 |
| New message on the Da Vinci Project list (opens lists.hl7.org) | Da Vinci Project | HL7 Mailing List | 2 messages this week · 12 hours ago | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — Cites no HL7 Jira item. | — The source keeps this topic private, so it has no summary here. |
| New Publication (opens chat.fhir.org) | Announcements | FHIR Chat | 3 messages this week · 12 hours ago | — The summary says nothing here. | Seventeen publication notices posted with no questions or discussion. Newest two add Domain Analysis Model: Nutrition Care ed. 4 (normative) and SMART Scheduling Links STU 1.0.0. Earlier items include retirement of HL7 V3 RCL R2, FHIR R6 6.0.0-snapshot1, US-PCS 1.0.0 STU, EHRS-FM Release 2.1, CQM 2.0.0 STU, DEQM 1.0.0 STU, and others. | — The summary says nothing here. | The V3 RCL R2 standard is retired, so implementers should no longer rely on it for new work; SMART Scheduling Links STU 1.0.0 and Nutrition Care DAM ed. 4 are newly published. | FHIR R6, US Core, US Patient Care Summary 1.0.0, CDC Opioid CPG Data Exchange Profiles 1.0.0, CDC Opioid CDS 2022.1.1, SDOH Clinical Care 3.0.0, Quality Measures (CQM) 2.0.0, Data Exchange for Quality Measures (DEQM) 1.0.0 | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 21, 2026 |
| PAS $submit / $inquire Format Clarification (opens chat.fhir.org) | Da Vinci PAS | FHIR Chat | 3 messages this month · 7 days ago | 1) Are servers expected to support both the direct Resource (Bundle) and Parameters formats for PAS $submit and $inquire requests? 2) For v2.2 $inquire with return 0..*, must servers return Parameters for multiple Bundles and may they return an unwrapped Bundle for exactly one, so clients must handle both? | Agreed A responder explained the v2.2 rules: $submit response MUST be a bare resource and never Parameters; $inquire response MUST be Parameters unless there is exactly one 'return' parameter of resource type with cardinality 1, in which case a bare resource is both allowed and mandated. Under 2.1 (return 1..1) bare resource was returned for both, so the 0..* change is breaking. For requests, clients may use either form and servers must accept both; the responder considers tightening clients to a singl | The work group triages change request FHIR-59693 to tighten request invocation and clarify response-format documentation in the specification. | Change proposed Expected: PAS spec documentation will state clearly when bare resource versus Parameters responses apply, and clients may be restricted to one request invocation form, simplifying servers. | Da Vinci PAS 2.1.0, Da Vinci PAS 2.2.0, FHIR R4 | FHIR-59693 (Triaged) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 20, 2026 |
| FHIR Extensions Pack peer review (opens chat.fhir.org) | fhir/infrastructure-wg | FHIR Chat | 10 messages this week · 20 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| Moving IG extensions to the Extension Pack (opens chat.fhir.org) | fhir/infrastructure-wg | FHIR Chat | 12 messages this week · 22 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| Proposed wide reaching bug fix in all versions (opens chat.fhir.org) | hapi | FHIR Chat | 19 messages this week · 22 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| October 2026 - Block Vote Request (opens chat.fhir.org) | bulk data | FHIR Chat | 6 messages this month · 15 days ago | Will the work group approve the block of Bulk Data ballot-comment tickets (Persuasive / Persuasive with Modification) at the October 14 2026 call, and which tickets are excluded? | Open question Block vote set for Oct 14 2026. FHIR-59160 pulled from block at a participant's request and moved to Oct 21 agenda; FHIR-59172 was never in the block. On Oct 9 the proposer pulled FHIR-58835, FHIR-59016, FHIR-58878, FHIR-59015 and FHIR-59148 from the block, with revised resolutions noted (FHIR-58835 to also cover the deleted element in the Export manifest; FHIR-59016 tied to FHIR-58834; FHIR-58878 conflicts with group.md; FHIR-59148 to be broader policy; FHIR-59015 to also address parameter defi | The work group holds the block vote on the remaining tickets at the October 14 2026 call, followed by the agenda items starting with FHIR-58962 includeAssociatedData. | Ballot — The summary says nothing here. | Bulk Data IG STU4 (export, submit, publish) | FHIR-58835 (Triaged), FHIR-59160 (Triaged), FHIR-58811 (Resolved - change required), FHIR-58834 (Resolved - change required), FHIR-58850 (Resolved - change required) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| October 2026 - Bulk Data Block Vote Announcement (opens chat.fhir.org) | fhir/infrastructure-wg | FHIR Chat | 1 message this month · 20 days ago | — The summary says nothing here. | Block vote on 24 Bulk Data tickets is planned for the October 14 2026 call. No vote has occurred yet. Listed tickets carry proposed dispositions (e.g. Persuasive, Persuasive with Modification) that are not yet adopted. Any ticket can be pulled from the block before the vote. | The work group votes on the block of Bulk Data tickets at the October 14 2026 call, unless a ticket is pulled beforehand. | Ballot — The summary says nothing here. | Bulk Data (FHIR) [FHIR-bulkdata] | FHIR-58835 (Triaged), FHIR-59160 (Triaged), FHIR-58811 (Resolved - change required), FHIR-58834 (Resolved - change required), FHIR-58850 (Resolved - change required) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| PAS STU 2.1.0 - extension-infoChanged on supportingInfo (opens chat.fhir.org) | Da Vinci PAS | FHIR Chat | 3 messages this week · 23 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | FHIR-59730 | — Not summarised yet. |
| Canonicalization discussion on the next FHIR-I call? (opens chat.fhir.org) | fhir/infrastructure-wg | FHIR Chat | 1 message this week · 46 hours ago | Can FHIR-52928 be considered on the next FHIR-I call? Was FHIR-52815 finished at WGM, given it has not been voted on? Can FHIR-59335 also be asked for on the 10/26 call? Can FHIR-58220 also be added? | Open question No decision yet. The requester agreed to the 10/26 call for the earlier items. A participant thinks the FHIR-52815 discussion went well at WGM but ran out of time, so it has not been voted on. On 10/19 a participant asked to add FHIR-59335 to the 10/26 call; no response is recorded. On 10/21 a participant added FHIR-58220 as another minor item, with no response recorded. | The work group is expected to consider FHIR-52928, FHIR-59335 and FHIR-58220 on the 10/26 FHIR-I call, and to confirm whether FHIR-52815 needs further discussion. | Clarification — The summary says nothing here. | FHIR | FHIR-52928 (Triaged), FHIR-59335 (Triaged), FHIR-58220 (Triaged), FHIR-52815 (Triaged) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 21, 2026 |
| HL7 Terminology (THO) v7.5.0 Release Announcement (opens chat.fhir.org) | implementers | FHIR Chat | 1 message this week · 27 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| HL7 Terminology (THO) v7.5.0 Release Announcement (opens chat.fhir.org) | Announcements | FHIR Chat | 1 message this week · 27 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| Appropriate field to map Request types in claim (opens chat.fhir.org) | Da Vinci PAS | FHIR Chat | 7 messages this week · 33 hours ago | Is there an existing Da Vinci PAS data element to convey behavioural health authorization request types (Admission, Change in Level of Care, Crisis, Discharge, Readmission, Update), and if not, what is the recommended approach? Is Claim.subType appropriate? | Open question No answer to the original question yet. A participant asked how this is handled today with X12 278, which is a clarifying question back to the original poster, not an answer. | A work group or IG author response is expected to identify the appropriate PAS field or mapping. | Clarification — The summary says nothing here. | Da Vinci PAS | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 21, 2026 |
| New message on the davincipublic list (opens lists.hl7.org) | davincipublic | HL7 Mailing List | 1 message this week · 36 hours ago | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — Cites no HL7 Jira item. | — The source keeps this topic private, so it has no summary here. |
| New message on the davincipublic list (opens lists.hl7.org) | davincipublic | HL7 Mailing List | 1 message this week · 36 hours ago | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — Cites no HL7 Jira item. | — The source keeps this topic private, so it has no summary here. |
| CDS Agendas (opens chat.fhir.org) | cds | FHIR Chat | 1 message this week · 37 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| CRMI Block Vote 1 - Terminology (opens chat.fhir.org) | cds | FHIR Chat | 1 message this week · 37 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | FHIR-52752, FHIR-53319, FHIR-57655, FHIR-57726, FHIR-57818 | — Not summarised yet. |
| PAS response including documents as attachments (opens chat.fhir.org) | Da Vinci PAS | FHIR Chat | 6 messages this week · 38 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| Seeking implementer feedback on FHIR-59695 (opens chat.fhir.org) | implementers | FHIR Chat | 2 messages this week · 42 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | FHIR-59695 | — Not summarised yet. |
| Provider-Selected ICD Codes (opens chat.fhir.org) | Da Vinci Risk Adjustment | FHIR Chat | 1 message this week · 43 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| Call link (opens chat.fhir.org) | workflow | FHIR Chat | 1 message this week · 44 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| Experimental flag not rendering on value set in FHIR Core (opens chat.fhir.org) | fhir/infrastructure-wg | FHIR Chat | 17 messages this week · 45 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| AI-Transparency require security tag? (opens chat.fhir.org) | Artificial Intelligence/Machine Learning (AI/ML) | FHIR Chat | Chat quiet since Aug 22 · FHIR-58669 moved 45 hours ago | Should the AI transparency IG make a security label (meta.security) mandatory to flag AI-created or AI-touched content, or is it better placed in meta.tag or Provenance? | Open question No consensus. One participant supports a SHALL on a single meta.security label as a quick signal, with fuller Provenance later. Others argue AI is not purely a security matter and fits meta.tag or Provenance better, and that responsibility and the degree of AI instruction and review are not captured by a binary flag. One participant argues AI assertions are trust-related and belong in meta.security. A participant says the AI level is covered in Provenance and the security label is only a coarse | The work group triages FHIR-58669 on the questionable value-set codes; no decision on the meta.security SHALL is recorded. | Change proposed No change to the specification is decided; a proposed SHALL on meta.security for AI-generated content is unresolved, and the value-set review may remove codes bound to meta.security. | FHIR security labels (meta.security), FHIR Provenance, FHIR meta.tag, AI Transparency IG | FHIR-58669 (Applied) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| topic for today or next week's agenda. (opens chat.fhir.org) | fhir/infrastructure-wg | FHIR Chat | 1 message this week · 46 hours ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | FHIR-59695 | — Not summarised yet. |
| DTR Questionnaire Response in PAS Bundle - CRD profiles (opens chat.fhir.org) | Da Vinci PAS | FHIR Chat | 2 messages this week · 46 hours ago | Which workaround is preferred for resources conforming to multiple profiles (remove CRD extensions, duplicate resources, or use only the CRD profile), and how are others handling it? | Answered Lloyd recommended stripping meta.profile from all instances and said not to duplicate resources; CRD extensions are not needed for PAS but a receiver should not treat them as an error. Later, a receiver rejected a request for lacking a PAS profile declaration (OperationOutcome). The reply states that receiver is non-conformant: the specification requires no meta.profile, and implementations may not add that requirement. Conformance rules: do not rely on meta.profile in BR IG instances, do not co | — The summary says nothing here. | Clarification Implementers are advised that meta.profile is not required by the specification and receivers must not reject instances for lacking it, so the rejecting receiver is non-conformant; the payer's own workaround is a local matter, not a spec change. | Da Vinci PAS, Da Vinci DTR 2.1.0, Da Vinci CRD, Da Vinci BR, CDex | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| Davinci PAS Claim (opens chat.fhir.org) | Da Vinci | FHIR Chat | 1 message this week · 2 days ago | Does the FHIR Claim resource support a code-level visit and billable unit quantity on one line item? If not, should the provider send separate lines, or aggregate units across service codes? | Open question No answer recorded. A participant had earlier stated the existing Claim resource does not appear to support a visit code and billable unit quantity together on one line item. A follow-up asked for a reply; the addressed party replied that they are on vacation and back the next day, so no reply on substance yet. | A Da Vinci team or CMS mapping direction is expected to be sought once the addressed party returns; no timing is firmly stated. | Clarification Unresolved: until direction is given, implementers may not know whether to split visit and unit lines or aggregate units for the prior authorization request. | Da Vinci PAS | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 20, 2026 |
| PAS Claim.Identifier.System (opens chat.fhir.org) | Da Vinci PAS | FHIR Chat | 2 messages this week · 2 days ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| Bundle type (opens chat.fhir.org) | workflow | FHIR Chat | 92 messages this week · 2 days ago | Should the bundle type 'subscription-notification' be generalised to 'notification' (or given a parent 'notification' type) for COW's use of a bundle sent upfront to execute an order, given that 'collection' might suffice? | Open question A participant said the subscription-notification bundle type is designed only for notifications from a subscription and is not meant to be used without a subscription, and asked why Bundle.type collection is not sufficient. No resolution recorded; the question is still unanswered by the proposer. | A response from the participants tagged at the end of the thread is awaited on whether collection suffices. | Change proposed Possible change: a generic notification bundle type could be added, but this is only proposed; no specification change is decided. | FHIR Bundle | FHIR-50292 | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 22, 2026 |
| Approved Terminology Server (opens chat.fhir.org) | Announcements | FHIR Chat | 1 message this week · 2 days ago | — The summary says nothing here. | A terminology server (HealthAll, Korea) is now listed as approved on the Terminology EcoSystem IG approved-servers page. It is stated to support the Korean SNOMED CT edition and other HL7 Korea authored content. No standard content change is indicated. | — The summary says nothing here. | — The summary says nothing here. | FHIR Terminology Ecosystem IG, SNOMED CT Korean edition | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| Searching on code US Core Observation Smoking Status (7.0+) (opens chat.fhir.org) | implementers | FHIR Chat | 2 messages this month · 20 days ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | Clarification — Not summarised yet. | — Not summarised yet. | FHIR-59514 (Submitted), FHIR-51829 (Applied) | — Not summarised yet. |
| FMM declaration (opens chat.fhir.org) | FHIR Mapping Language | FHIR Chat | 1 message this week · 4 days ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| Dealing with Large Resources (opens chat.fhir.org) | fhir/infrastructure-wg | FHIR Chat | 4 messages this week · 4 days ago | Can the work group be put on an upcoming FHIR-I meeting agenda to discuss options for normative resources that need to say something about large resources, given the discovery problem? | Open question No decision yet. Patient Admin is taking Encounter normative in R6 and needs to address large resources; FHIR-52912 moved to the incubator; List and Group address the issue inconsistently and neither covers initial discovery. | Get the topic onto an upcoming FHIR-I meeting agenda to discuss options. | Clarification Encounter in R6 may need normative text on how large resources are discovered, and List and Group wording may need to be aligned; no change is decided yet. | FHIR R6, FHIR List resource, FHIR Group resource, FHIR Encounter resource | FHIR-37648 (Triaged), FHIR-52912 (Triaged) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 20, 2026 |
| PAS: Practitioner Contact Name if different than provider. (opens chat.fhir.org) | Da Vinci PAS | FHIR Chat | 2 messages this week · 5 days ago | Wouldn't PractitionerRole.organization.contact hold the organization name rather than the person who entered the prior auth, and has Claim.enterer been considered for capturing the back-office person's name and contact? | Answered A participant clarified that Organization.name holds the organization's name, while Organization.contact.name holds a specific person to contact at the organization for a given purpose. A participant then said there is no use case for specifying who entered the preauth request, which is why Claim.enterer is not marked as must support. No decision recorded on Claim.enterer itself. | — The summary says nothing here. | Clarification Claim.enterer is not must support in PAS because no use case for recording the preauth entering person has been identified; implementers need not populate it for conformance. | Da Vinci PAS, Claim.enterer, Organization.contact | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 20, 2026 |
| Appointment Book Coverage Information Extension (opens chat.fhir.org) | Da Vinci CRD | FHIR Chat | Chat quiet since Sep 23 · FHIR-59401 moved 5 days ago | How should coverage-assertion-id be sent as context when no order is selected, given context is 0..1 but SHALL be included if coverage-information was available? Also whether an Appointment may be DTR launch context, and why QuestionnaireResponse.context is 0..*. | Open question Partly clarified: an Appointment can be sent when launching DTR, and the app would retrieve the ServiceRequest if the Appointment is tied to one. QuestionnaireResponse.context is 0..* because one response may apply to several orders while only one order is in context at launch. A participant asked for a change request; FHIR-59401 was submitted for discussion. Not settled: the no-order-selected case for the SHALL on coverage-assertion-id context. No decision recorded. | The work group discusses FHIR-59401 to resolve how coverage-assertion-id context is sent when no order is selected. | Change proposed — The summary says nothing here. | Da Vinci CRD, Da Vinci DTR 2.2.0, SMART App Launch | FHIR-59401 (Triaged), FHIR-59123 (Triaged) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| Industry Practices for Implementing Adaptive Questionnaires (opens chat.fhir.org) | Da Vinci DTR | FHIR Chat | 2 messages this week · 5 days ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Cites no HL7 Jira item. | — Not summarised yet. |
| New message on the davincipublic list (opens lists.hl7.org) | davincipublic | HL7 Mailing List | 1 message this week · 5 days ago | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — Cites no HL7 Jira item. | — The source keeps this topic private, so it has no summary here. |
| Immunization batch numbers (opens chat.fhir.org) | implementers | FHIR Chat | 2 messages this week · 5 days ago | Is there a reason batch numbers have not been modelled in Immunization, while lot numbers are? Do manufacturers label vaccines with both lot and batch numbers? | Open question No answer yet. One participant suggests lot and batch are currently treated as interchangeable, both held as a string. Another shares a blog explaining lot versus batch codes. A participant recalls no prior request for batch numbers and will seek more detail from a national immunization system. A tagged participant asked whether manufacturers label products with both numbers at unit of use or unit of sale. | Tagged participants are expected to answer whether manufacturers label products with both lot and batch numbers, and whether a modelling need exists. | Clarification — The summary says nothing here. | FHIR Immunization | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 19, 2026 |
| $inquire for pended requests without Auth# or AdminRef# (opens chat.fhir.org) | Da Vinci PAS | FHIR Chat | 5 messages this week · 5 days ago | How should a client use $inquire to check a pended request before the payer assigns authorizationNumber or administrationReferenceNumber? Is there another identifier or search mechanism, or a way to use the original Claim.identifier, since the PAS Inquiry Claim has no element for it? | Open question No answer yet. The message notes that in PAS v2.2 Claim.identifier on $inquire is the inquiry TRN and not used to find a prior authorization; the header/item authorizationNumber and administrationReferenceNumber extensions (X12 REF-NT, REF-BB) are the stated search route, but they may not exist yet after a queued response. | The work group or IG authors are expected to respond on whether another identifier or search route exists for pended requests. | Clarification Implementers may be left without a defined way to inquire on a pended request that lacks reference numbers, unless the IG clarifies an alternative identifier or search route. | Da Vinci PAS 2.2.0 | FHIR-59711 | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 21, 2026 |
| Unevaluated variables in the 6.0.0-snapshot1 spec (opens chat.fhir.org) | implementers | FHIR Chat | 2 messages this week · 5 days ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | FHIR-48987 | — Not summarised yet. |
| Building a Health Tech Ecosystem: Da Vinci in Action (opens blog.hl7.org) | HL7 blogFHIR, HL7, HL7 community | HL7 Blog | Published 5 days ago · FHIR, HL7, HL7 community | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Cites no HL7 Jira item. | — Publisher posts carry no summary. |
| Clarification on $next-question request and response formats (opens chat.fhir.org) | Da Vinci DTR | FHIR Chat | 4 messages this week · 5 days ago | Is a DTR server expected to return multiple relevant questions in a single $next-question response (per the SHOULD guidance), or generally one or a couple per call? Is the 'one at a time' statement a UX description rather than a per-call limit? | Open question No answer posted yet. The thread has only the question. | A DTR work group or IG author response is needed to clarify the intended interpretation of the two statements. | Clarification Unclear until answered; the answer would determine whether servers must limit $next-question responses to one or a few questions, or may return multiple relevant questions. | Da Vinci DTR | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 22, 2026 |
| PAS $Inquire (opens chat.fhir.org) | Da Vinci PAS | FHIR Chat | 3 messages this week · 6 days ago | Is a provider permitted to invoke $inquire for historical PAs (pre-1/1/27) or PAs submitted via the web portal? If so, what is the expected response mapping without an original FHIR PAS API request body: reconstruct the request from database elements, or convey status and line items without full request details? | Answered A participant answered that $inquire can return PAs submitted in multiple ways, including historical PAs. The response should create a Claim instance for the parts of the response that deal with the Claim and need to be returned. The reconstruction-versus-minimal-status question is only partly addressed; the Claim-based approach is stated, but no formal decision is recorded. | — The summary says nothing here. | Clarification Implementers may return historical and portal-submitted PAs through $inquire, building a Claim instance for the claim-related parts of the response; no change to the specification text is recorded. | Da Vinci PAS, CMS-0057-F | — Cites no HL7 Jira item. | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 22, 2026 |
| Using CQL With FHIR 2026-10-21 Block Vote 1 (opens chat.fhir.org) | cds | FHIR Chat | 1 message this week · 6 days ago | Is the work group asked to vote on the listed Jira items in the Block Vote for Using CQL With FHIR? The message is truncated. | A block vote list was prepared for the Using CQL With FHIR IG, covering items such as FHIR-59691, FHIR-59689, FHIR-59254, FHIR-59223, FHIR-59221, FHIR-59181, FHIR-59174, FHIR-59103, FHIR-59076, FHIR-59060, FHIR-58912 and FHIR-58911, with dispositions marked Persuasive or Persuasive with Modification. No vote result is recorded yet. | The work group votes on the block of Jira items. | If the block passes, the listed Using CQL With FHIR changes (for example documenting implicit conversions, fixing daysInPeriod and toDayNumbers behaviour, and promoting common library guidance) would be applied to the IG. | Using CQL With FHIR | FHIR-59689 (Triaged), FHIR-59691 (Triaged), FHIR-59103 (Triaged), FHIR-59174 (Triaged), FHIR-59060 (Triaged) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 22, 2026 |
| New message on the davincipublic list (opens lists.hl7.org) | davincipublic | HL7 Mailing List | 1 message this week · 6 days ago | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — The source keeps this topic private, so it has no summary here. | — Cites no HL7 Jira item. | — The source keeps this topic private, so it has no summary here. |
| What things can an AI do? (opens chat.fhir.org) | AI Transparency on FHIR | FHIR Chat | Chat quiet since Sep 8 · FHIR-58672 moved 6 days ago | Can an AI author resources it should be able to, e.g. be Observation.performer, given the R6 clinical resource model? Should clinical resources be reviewed for AI-authorship gaps? | Open question No decision recorded. Participants agree an AI making an observation is distinct from a device measuring one, and the line is hard to define. One view: an AI should be the performer only when acting for a liable human; a regulated device could be the performer. A later clarification: the Device resource is also used to represent software and other agents, so the question remains open. FHIR-58672 is referenced for the review. | — The summary says nothing here. | Clarification — The summary says nothing here. | FHIR R6 | FHIR-58672 (Resolved - change required) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| Representing local time without TZ in FHIR? (opens chat.fhir.org) | fhir/infrastructure-wg | FHIR Chat | Chat quiet since Sep 23 · FHIR-53336 moved 8 days ago | How should a device observation carry a local time without timezone information in FHIR, e.g. in the CoincidentTimeStamp profile? | Open question A proposal was made to use valueString in the CoincidentTimeStamp observation profile for local time without TZ, with a datetime-format constraint and no extension, to be discussed in the Devices WG under FHIR-53336. A follow-up participant noted FHIR cannot police gateways or devices, only convey clock and timestamp status, and argued gateways should be configured at deployment time, including the deployment location's timezone. No decision recorded. | The Devices WG is to discuss the valueString proposal under FHIR-53336. | Change proposed Expected: the CoincidentTimeStamp profile would allow a valueString carrying a timezone-less datetime when a PHD reports local time, with no extension; not yet decided. | FHIR | FHIR-53336 (Applied) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| Clinical Reasoning Track (opens chat.fhir.org) | cql | FHIR Chat | Chat quiet since Sep 20 · FHIR-59277 moved 14 days ago | None explicitly asked. A participant asked that updated JavaScript engine results be included in the report-out as appropriate. | Tracker FHIR-59277 posted for $cql trace. PRs submitted: cql-tests-runner PR 137 (updated JavaScript CQL engine config) and cql-tests-results PR 10 (latest JavaScript engine results). Two issues filed against cql-tests: #153 (decimals over 8 places not necessarily invalid) and #152 (wrong expected output for properly includes/included in at boundary values). One CQL spec issue filed: FHIR-59288 (ambiguous semantics for Date arithmetic overflow). No decisions recorded; thread ends with thanks. | — The summary says nothing here. | Change proposed The cql-tests issues and the FHIR-59288 spec issue may lead to test expectation corrections and clarification of Date arithmetic overflow semantics in CQL, but nothing is decided yet. | CQL | FHIR-59277 (Triaged), FHIR-59288 (Submitted) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| IG - Jan ballot (opens chat.fhir.org) | AI Transparency on FHIR | FHIR Chat | Chat quiet since Jan 26 · FHIR-54729 moved 15 days ago | No explicit question. Thread covers the January 2026 ballot of the AI Transparency IG and triage of its open Jira issues. | Ballot version posted at the 2026Jan build. Initial triage (posted 2026-01-26) lists open issues by category, e.g. Documentation & Clarity (31 issues) and Profile & Model Structure (19 issues), and notes 32 technical corrections already approved. No final resolution of the listed issues is recorded in the thread. | — The summary says nothing here. | Ballot — The summary says nothing here. | AI Transparency IG | FHIR-54729 (Resolved - change required), FHIR-54894 (Applied), FHIR-55024 (Applied), FHIR-54885 (Applied), FHIR-54893 (Applied) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| See the 2026 HL7 AI Challenge Winners in Action (opens blog.hl7.org) | HL7 blogFHIR, HL7, HL7 community | HL7 Blog | Published 19 days ago · FHIR, HL7, HL7 community | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Cites no HL7 Jira item. | — Publisher posts carry no summary. |
| ActivityDefinition (opens chat.fhir.org) | cds | FHIR Chat | Chat quiet since Jun 29 · FHIR-57774 moved 35 days ago | How to migrate Dosage to R6 ActivityDefinition steps; how timing[x] relates to dosage and MedicationRequest on apply; how RelativeTime, asNeeded and observation requirements map; where the invalid example maps should live. | Open question Partly resolved: the invalid example maps (work in progress) are to be marked informative and moved to the CPG IG, which ballots in September; Jira FHIR-57774 logged. One implementer shared an R4-to-R6 alteplase example (one step with multiple components, step texts concatenated into renderedInstruction). Timing, RelativeTime, asNeeded and condition questions remain unanswered. | — The summary says nothing here. | Change proposed The example maps are to be marked informative and relocated to the CPG IG; the timing, RelativeTime, asNeeded and condition mapping questions are still unresolved. | FHIR R4, FHIR R5, FHIR R6, ActivityDefinition, Dosage, DosageDetails, CPG IG, FML | FHIR-57774 (Triaged) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| The State of Electronic Prior Authorization: From Policy to Production (opens blog.hl7.org) | HL7 blogFHIR, HL7, HL7 community | HL7 Blog | Published 36 days ago · FHIR, HL7, HL7 community | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Cites no HL7 Jira item. | — Publisher posts carry no summary. |
| Beyond the Consent Form: Building Trust for Healthcare Data Exchange (opens blog.hl7.org) | HL7 blogFHIR, interoperability, FHIR Accelerator | HL7 Blog | Published 55 days ago · FHIR, interoperability, FHIR Accelerator | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Cites no HL7 Jira item. | — Publisher posts carry no summary. |
| Scaling Health Data Exchange Through Real-World Collaboration (opens blog.hl7.org) | HL7 blogFHIR, HL7, HL7 community | HL7 Blog | Published 77 days ago · FHIR, HL7, HL7 community | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Cites no HL7 Jira item. | — Publisher posts carry no summary. |
| Is vertical bar allowed in a Reference.reference? (opens chat.fhir.org) | conformance | FHIR Chat | Chat quiet since Aug 10 · FHIR-58165 moved 82 days ago | Is a vertical bar allowed unencoded in Reference.reference, and what algorithm should receivers use to decode, not decode, or detect syntax errors in such values? | Open question No decision. Participants agreed a pathological double-escaped example parses legally when the escaped form is used. They disagreed on whether unencoded vertical bars are valid; one said 'supposed to' is not 'must'. Tracker item FHIR-58165 raised to document the rule. Open question: how a receiver knows whether to decode what it receives, since the spec only clearly requires URI form for Reference.reference except internal fragment references (RFC 3986 fragments cannot contain a bar). The latest | The spec authors are expected to document the rule for vertical bars and decoding in response to FHIR-58165; no answer on the decode algorithm has been given yet. | Change proposed Proposed: the spec is to document whether unencoded vertical bars are valid in Reference.reference and how receivers decode such values; not yet decided. | FHIR Reference.reference, RFC 3986 | FHIR-58165 (Submitted) | Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 |
| Building the Consent Trust Stack: How Computable Consent Can Scale Privacy, Patient Choice, and Healthcare Data Exchange (opens blog.hl7.org) | HL7 blogFHIR, interoperability, CMS | HL7 Blog | Published 88 days ago · FHIR, interoperability, CMS | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Cites no HL7 Jira item. | — Publisher posts carry no summary. |
| HL7 Da Vinci Project Honors 2025 Community Champions, Opens Nominations for 2026 (opens blog.hl7.org) | HL7 blogFHIR, HL7, HL7 community | HL7 Blog | Published 97 days ago · FHIR, HL7, HL7 community | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Cites no HL7 Jira item. | — Publisher posts carry no summary. |
| Building Reusable, Scalable Prior Authorization Tools: A Case Study in Policy Digitization and HL7 Da Vinci DTR Implementation (opens blog.hl7.org) | HL7 blogFHIR, HL7, HL7 community | HL7 Blog | Published 131 days ago · FHIR, HL7, HL7 community | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Cites no HL7 Jira item. | — Publisher posts carry no summary. |
| A Shared Foundation for Digital Trust: HL7 FAST and the CARIN Alliance Align on FAST Identity STU 3 (opens blog.hl7.org) | HL7 blogFHIR, interoperability, CMS | HL7 Blog | Published 141 days ago · FHIR, interoperability, CMS | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Cites no HL7 Jira item. | — Publisher posts carry no summary. |
| Embracing AI as a Force Multiplier for Health Data Standards (opens blog.hl7.org) | HL7 blogFHIR, HL7, interoperability | HL7 Blog | Published 145 days ago · FHIR, HL7, interoperability | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Cites no HL7 Jira item. | — Publisher posts carry no summary. |
| In Memoriam: Clement J. McDonald, MD — A Founder, a Force, and a Friend (opens blog.hl7.org) | HL7 blogFHIR, HL7, HL7 community | HL7 Blog | Published 154 days ago · FHIR, HL7, HL7 community | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Publisher posts carry no summary. | — Cites no HL7 Jira item. | — Publisher posts carry no summary. |
| information related to future queries (opens chat.fhir.org) | subscriptions | FHIR Chat | Chat quiet since Mar 30 · FHIR-55980 moved 203 days ago | — Not summarised yet. | — Not summarised yet. | — Not summarised yet. | Clarification — Not summarised yet. | — Not summarised yet. | FHIR-55980 (Resolved - change required) | — Not summarised yet. |
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.