Review of proposed changes for February Vocabularies release and community contributions

Vocabulary Users
1

As we are approaching the holiday season, mark your calendars with the first meeting of the Vocabulary WG in 2026 where we will look at the proposed changes and additions to the Vocabularies outside of the roadmap for the February 2026 release.

The meeting will occur on Tuesday January 6th noon EST and we will look at the community contributions, proposed changes to the ATC and more. We will post the content of the changes closer to the date in this thread. As a reminder, the current cycle for error-free fully baked community contributions will end December 22nd to allow the team to properly incorporate them into the upcoming release. Shoot us a message if you have questions or need help getting it over the finish line.

Please come - we rely on the community to provide insights and comments regarding Vocabularies content!

1 Like
2

Attached file summarizes community contributions as well as proposed ATC change.

It contains:

  • changes to mappings (several additions, deduplications and mapping improvements)
  • new standard concepts proposed by the community (Obituary type, ICU visits, wearables measurements, visual acuity concepts)
  • links to the proposed refreshes or additions to the vocabs beyond the roadmap
  • an example of proposed change to ATC (removal of secondary uphill ingredients from the hierarchy)

Looking forward to fruitful discussion tomorrow at noon EST! Please feel free to also review the proposed changes in this thread.
contributions february release.xlsx (34.5 KB)

3

Summary of the recommendations from the call (recording available in MS Teams):

  1. Postpone implementation of #1191 (addition of mapping ‘Aphagia’ to ICD10CM ‘Dysphagia and Aphagia’): it is not AND but OR and therefore should be mapped to the broader term only)
  2. Assess impact of #1210 on hierarchy and estimate resources
  3. @Heidi_Schmidt1 and @Polina_Talapova to have a conversation on #1199 with the Visit CDM (@MPhilofsky) to discuss the use cases and figure out our path forward with more detailed visits
  4. Revamp names for wearable device measurements to be self-sufficient in #1182
  5. Proceed with the rest