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
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
AI-Transparency require security tag? (opens chat.fhir.org) · chat quiet
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?
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.
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.
FHIR security labels (meta.security), FHIR Provenance, FHIR meta.tag, AI Transparency IG
  • FHIR-58669 (Applied) · jira verified Nov 8, 2026
    1. Discussed (reached)
    2. Filed (reached)
    3. Triaged (reached)
    4. Resolved (reached)
    5. Applied (reached)
    6. Published (not yet)

    Applied · version not recorded

Machine summary · unreviewed · claude-haiku-5-5 · analysed Oct 15, 2026 · inferredArtificial Intelligence/Machine Learning (AI/ML)FHIR Chatchat quietChat quiet since Aug 22 · FHIR-58669 moved 12 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.