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 13 minutes ago. 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
CRD-inpatient behavioral health with no CPT/HCPCS (opens chat.fhir.org)
For inpatient behavioral health with no CPT/HCPCS, what should the EHR place in ServiceRequest.code in CRD; is an NUBC revenue code acceptable there or should revenue use another path; and how is a level-of-care selection translated into the draft order for pre-service PA? Follow-up asks what sites code today, whether NUBC codes sit in ServiceRequest.code, what works end-to-end, and when to use DT
Clarification
No specification change is proposed; implementers should expect CRD orders to carry whatever codes the health system already maps, and level-of-care or revenue data may need DTR or mapping setup rather than a new CRD field.
Open question
Earlier answer: EMRs do not change ordering when adopting CRD; orders keep existing codes (typically SNOMED or LOINC); payers needing extra data should use DTR; terminology mapping is done by each health system with payers. New messages: a participant summarized takeaways: CRD should not change order entry, US Core does not drive ordering, extra data should come via DTR rather than a new CRD field, and non-CPT/HCPCS services need CRD/PAS mapping setup at each health system. No confirmed pattern
Implementers with live inpatient behavioral health CRD and PAS workflows are asked to share what codes they use today, whether NUBC codes appear in ServiceRequest.code, and example ServiceRequests.
Da Vinci CRD, Da Vinci DTR, Da Vinci PAS, US Core— Cites no HL7 Jira item.Machine summary · unreviewed · claude-haiku-5-5 · analysed Nov 4, 2026 · inferredDa Vinci CRDFHIR Chat7 messages this week · 3 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.