Proposed changes to nursing findings

Briefing Note Purpose

A number of SNOMED CT Clinical Finding concepts used to record nursing observations — including those using the terms “disability,” “reduced,” “limited”/“limitation,” “impaired”/“impairment,” and “difficulty” — currently show inconsistent wording, inconsistent word order, and mixed modelling patterns. Some concepts also carry synonyms that diverge in meaning from their Fully Specified Name, which complicates translation and consistent implementation. This briefing note requests feedback on a proposed approach for resolving these issues.

Date created 01 09 2026
Action Request for feedback
Status For comment
Disposition Closed
Feedback by 30th September 2026

20260901 BN Nursing findings v1.0.pdf (1.5 MB)

Thanks.

It is hard to understand from this briefing note what changes are proposed, what problem they are expected to solve, or how success would be measured. As a result, it is difficult to assess or support the proposal in its current form.

While the challenges of translation and implementation are real, the note appears to assume that they can be addressed through the introduction of the definitions offered and associated content remediation. The evidence presented does not demonstrate that this approach will deliver meaningful benefit, nor does it adequately consider the possibility of unintended consequences for existing users of SNOMED CT.

More fundamentally, the proposal risks treating a characteristic of natural clinical language as if it were an editorial defect. Before proceeding with widespread content changes, it would be helpful to understand why the proposed definitions should be expected to improve translation, implementation, or clinical use (and be widely clinically acceptable), and how any such improvement would be demonstrated.

Scope and proposed changes remain unclear

The title, scope, problem statement and proposed solutions do not appear fully aligned. For example, ‘impairment’ is highlighted as one of the central concerns and included in the title, yet subsequently the briefing note appears to declare ‘impairment’ modelling and wording out of scope of this activity. Likewise, ‘word order’ inconsistency is presented as an issue, but there appears to be no general proposal regarding word-order normalisation beyond part of the solution intended to address six specific “Disability of [body part]” concepts.

It is also unclear how the scope of the 249 concepts in the spreadsheet was determined (and whether this set of 249 is, in any sense, ‘complete’) and what reviewers are expected to look for during the proposed concept-by-concept review. The review set includes many concepts that do not exhibit the synonym issues described in the paper, so it is hard to understand the value of their inclusion. Conversely, the set is defined by ‘limited’ and ‘limitation’ but only ‘reduced’; why no ‘reduction’ - the list includes 277007008 |a and b waves reduced (finding)| but does not include 277005000 |Selective b wave reduction (finding)|? Whatever, reviewing every concept may be the correct approach, but the rationale is not explained.

Success is defined as completion of editorial work

The briefing note is motivated by concerns regarding translation, implementation consistency and the construction of, for example, nursing assessment tools. Yet the proposed ‘success criteria’ simply mirror the stages of the proposed solution: review the concepts, remove selected synonyms, re-parent concepts, inactivate concepts and complete modelling review activities.

Those activities may be necessary, but they are not outcomes If the underlying concern is translation or implementation. Success might be more meaningfully assessed in terms of whether those activities become easier, more consistent or more reproducible following the proposed changes. The current success criteria do not appear to evaluate whether any of the stated problems have been reduced.

It would therefore be helpful to see concrete examples demonstrating:

  • how current content is causing translation problems and difficulties with assessment instrument construction and use
  • how the proposed definitions and content changes would resolve those difficulties
  • that the proposed definitions (and the resulting conceptual distinctions) are acceptable to clinical users in all affected contexts
  • how resulting improvement will be measured.

The proposed solution may not address the underlying problem

The paper introduces working definitions intended to distinguish terms such as “disability”, “difficulty”, “limited”, “reduced”, “dysfunction” and “deteriorating”.

‘Disability’ may well be the exception (international definitions are merged in the paper, and ‘disability’ has specific jurisdictional meanings - e.g. the UK’s 2010 Equality Act), but the rest are not highly specialised technical/clinical terms. They are words drawn from general language and used in a clinical context, where meanings often overlap and where usage varies according to context, profession, culture and language.

This raises a more fundamental question: is the problem that SNOMED CT lacks sufficiently precise definitions for these words, or is the problem that natural English clinical language itself does not consistently use them in the neat and mutually exclusive manner implied by the proposal?

The briefing note appears to assume that assigning editorial definitions and then restructuring content around those definitions will reduce translation problems. However, many translation challenges arise precisely because languages draw distinctions differently. It is therefore not clear that increasing semantic precision in the English content of SNOMED CT necessarily solves localisation challenges. There is a risk that the English content becomes less representative of natural English-language usage (and, for some purposes, less useful) while still leaving NRCs and implementers to address the underlying cross-language differences. It is understandable to want to minimise imprecise language, but this should be accompanied (and indeed led) by educational, cultural and clinical practice changes, not by simply changing the published terminology.

Alternative direction

I agree that translation and localisation challenges are real and deserve attention. However, I am not yet convinced that large-scale remediation of English-language content based on newly introduced editorial definitions is the right way to do this.

A more convincing case would demonstrate:

  • specific translation and implementation problems that exist today
  • why those problems arise
  • why the proposed content changes are expected to resolve them
  • how improvement will be measured, and
  • what assessment will be undertaken to identify unintended consequences for existing users, data, mappings, analytics and clinical workflows.

Without that evidence, the proposal currently appears to define success as simply completion of the remediation work itself, rather than demonstration that the stated translation and implementation problems have actually been improved.

Ed

2 Likes

These terms are different and defined in ICF (https://www.who.int/docs/default-source/classification/icf/icfbeginnersguide.pdf). The WHO ICF framework is very useful here because it formally distinguishes impairment, activity limitation, and disability.

Term Clinical meaning Example
Impairment / impaired A problem or abnormality in a body function or body structure Impaired muscle strength
Reduced A relative decrease in magnitude or level of a function/ability; generally requires an understood reference point Reduced grip strength
Limited / limitation A restriction in the extent or ability to perform an activity/function Limited ability to walk
Difficulty The person experiences a problem or effort when performing an activity, but may still accomplish it Difficulty dressing
Disability A much broader construct encompassing the negative aspects of functioning, including impairments, activity limitations, and participation restrictions, in interaction with context/environment Disability affecting independent community living
5 Likes

Thank you for the feedback on this topic so far. I’ve added some additional information below based on the questions raised.

Scope and “impairment”

The title reflects content tracker IHTSDO-1244’s original title. Concepts mentioning “impaired”/“impairment” are covered by IHTSDO-1010, planned as the next tracker after this one. Remodelling them was kept out of this briefing note so feedback here could stay focused on what’s proposed, in particular leaving 21134002 |Disability (finding)| and its subtypes primitive. It is a good point that was raised, because until both content trackers are complete, the work addressing the original Danish NRC request can’t be considered complete. Impairment is still defined in the working definitions table because the disability definition is WHO ICF-derived, and the ICF defines disability partly in relation to impairment. We needed a working definition of impairment even though remodelling impairment concepts is deferred.

That relationship is also why removing 21134002 |Disability (finding)|'s current model — INTERPRETS = General clinical state, HAS INTERPRETATION = Impaired — matters. Any ECL query, analytics pipeline, or CDS rule reasoning over disability via that attribute would stop matching once it’s removed. Queries using <<21134002 |Disability (finding)| will continue to return its stated subtypes. Leaving the concept primitive is a deliberate acknowledgement that no single computable definition of disability holds across contexts.

Word order

The original content tracker specifically raised inconsistent word order among concepts stating “disability,” citing 228152009 |Bathing disability (finding)| and 428349007 |Disability of arm (finding)| as examples; the latter is one of the six concepts proposed for inactivation, the former follows the future pattern. As raised in the feedback, the BN doesn’t propose a general word-order pass beyond those six. Checking the rest of the “disability” concepts against the two proposed patterns, most already fit, and <<116149007 |Disability percentage (finding)| and 105719004 |Body disability AND/OR failure state (finding)| are already covered by solutions 6 and 7. That leaves 9 concepts fitting neither pattern (three severity grades, Neurodisability, and five structurally different concepts like Retired because of disability). These don’t appear to be inherently ambiguous the way the six flagged concepts are, so are not currently planned for inactivation.

How the 249 was determined, and whether it’s “complete”

The set was built from four search patterns plus two named outliers, then de-duplicated to 249:

  • “Disability” (83)
  • “Reduced” (82)
  • “Limited”/“Limitation” (69)
  • subtypes of 105719004 |Body disability AND/OR failure state (finding)| (91)

It’s a term-match set scoped to the original request’s wording, not an exhaustive sweep, which is why 277005000 |Selective b wave reduction (finding)| falls outside it. We could either broaden the search to catch related word forms before finalising scope, or state plainly that the boundary is the terms named in the original content tracker. We’d welcome feedback on which of those is the better approach.

Reviewers will check each concept for:

  1. Synonym/FSN divergence. Non-synonymous synonyms will be removed and re-authored as separate concepts where clinically valid.
  2. Whether the FSN’s term matches its modelled meaning against the working definitions.
  3. For disability concepts, word order against the two proposed patterns.

Checks 2 and 3 apply regardless of check 1, which is why concepts with no obvious synonym issue are still in scope.

Success criteria

Under the heading of success criteria we mention that work will be considered complete when the review and remediation steps have been carried out. Success criteria, as mentioned in the feedback, will need to include whether the underlying translation and implementation issues have actually improved. This feedback period is itself part of how we’re trying to understand whether the changes proposed will lead to improvements in translation efforts — hearing directly from NRCs and implementers about whether the working definitions, the removal of non-synonymous synonyms, and removal of outdated modelling would actually help them choose concepts and translate consistently is a real test of the approach. We agree that we’d need to hear back from users about whether these changes solve translation issues — or cause unintended consequences for existing users — before any of this could be considered a success. In addition to this briefing note post, I’ve also presented these proposed changes to the Translation User Group.

We value all feedback received during consultation, especially where it points to meaningful benefit or risk we haven’t accounted for. After reviewing feedback, we’ll incorporate changes into whichever solutions we’re supported to proceed with, and any resulting changes would be publicised through our Early Visibility Notification Page and Release Notes.

Whether editorial definitions solve a translation problem

7973008 |Abnormal vision| carrying “Sight impaired,” and 225581002 |Sight deteriorating| carrying “Decreased vision,” are concrete concept-level divergences the Danish NRC mentioned directly — removing them fixes a demonstrated problem regardless of the broader question. On that broader question: it was raised that natural clinical language doesn’t use these words in a neat, mutually exclusive way, and that’s not unique to this part of the terminology. We don’t think introducing working definitions resolves that underlying variability in how clinicians and languages use these words. What this can do is narrower: one consistent term per modelled meaning, with the definitions made explicit (and, for disability, anchored to external standards), gives translators and implementers a fixed base to work from even as natural usage stays as varied as it is.

Thanks again for the feedback. Once the feedback period has ended we will review all responses and consider our next steps.

Sarah

Hi!

I’d like to provide som input on the translation difficulties and what would lower the risk of mistranslation of these concepts: The sorting in the hierarchy (a.k.a. the modelling) should be thought through and logical, and there must be consistency in the terms.

When different words are used, people rightly assume or suspect that there is also a difference in meaning. Here is a typical example of a translation challenge, with three concepts related to some sort of disability in relation to hand function:

These concepts are in the disability hierarchy, and the grouper concept is a “function disability” with the synonym “dysfunction”, and the modelling interprets the “general clinical state” as “impaired”. The sub concepts for left and right hand are modelled similarily, but have “dysfunction” in their FSN and no synonym with “function disability”. Should we still interpret this as one grouper concept and two laterality concepts for the same medical condition, or do the sub concepts represent something else? If a dysfunction is a more specific type of a function disability, the synonym of the first concept is wrong. If they are true synonyms, the FSNs should be aligned and the synonyms should be consistent.

The translators ended up using “nedsatt funksjon” (≈ “lowered function”) for both “function disability” and “dysfunction”, which at least makes the hiearchy look consistent. Looking at the hierarchy, I’m not 100 % sure this translation is actually correct. However, the meaning of the concepts themselves is unclear, so the translators are left with making pragmatic solutions like this.

Kind regards,
Vegard from Norway

4 Likes

The Norwegian NRC has reviewed the briefing note and the suggested project.

We support the efforts to clean up the uncovered ambiguity and remove the non-synonymous synonyms. Translation in the field of disability and reduced/altered function is a challenge in and of itself, as the clinical language might be inconsistent across different types of disabilities.

To improve the quality and ease of translation, our top two priorities are eliminating possible duplicates and improving the structure/model within the hierarchies. If the modeling and phrasing become more consistent throughout the hierarchies, this will make consistent translation easier as well, as shown by Vegard’s example above.

When it comes to the definitions proposed in the briefing note, we are of the opinion that the established, internationally accepted definitions from ICF (ref. Susan Matney’s comment) should be considered as a basis for the project, rather than stitching together “new” definitions for use in SNOMED CT.

We have also conferred with a cross-regional group of nursing experts, and asked for their input on the suggested definitions. They have responded positively to cleaning up the hierarchy, and support using the definitions from ICF as a reference to decipher/establish the clinical meaning of the different terms in play here.

They also mentioned that consolidating the definitions with terms used in OpenEHR Archetypes would be helpful for integration between different semantic tools. The OpenEHR Impairment summary references the ICF as well.

Best regards,
Hanne Johansen

1 Like

The Danish NRC supports the ICF definitions and are happy that SI will review these concepts, removing ambiguities, inconsistencies and hopefylly make translation easier.

1 Like

The U.S. NRC supports SI’s review of the meaning of this content and potential alignment with ICF definitions.

There also seems to be cross over with at least two other forum topics:

While these would be equivalent to LOINC answer list (LA) concepts and not standard LOINC codes for observations, at some point in the future, the answer list values will need to be either represented in or mapped to SNOMED CT as part of the LOINC ontology.

In the interest of countries using LOINC, the yet to be transferred concepts regarding activities of daily living into the LOINC ontology as part of the collaborative work, and those countries using SNOMED CT findings as reponse values for observable entities; It may be beneficial to convene a wider project group (i.e CPG or CRG) to determine the correct words and meanings for this particular domain.

1 Like

Thank you, @vopdahl . This is a very useful example that clearly shows how inconsistent synonyms and modelling create uncertainty for translators. The three concepts in your example are included in the planned review, and we will make sure their FSNs, synonyms and modelling are aligned so that their meaning is clear.

Sarah

1 Like

Thank you, @hjohansen , and thank you to the Norwegian NRC and the cross-regional nursing group for reviewing this topic.

Your priorities are very helpful: eliminating duplicates and making the modelling and structure within the hierarchies more consistent, with the expectation that consistent phrasing will follow and make translation easier. It is also useful to know that the nursing experts you consulted support using the ICF definitions as a reference for the clinical meaning of these terms, rather than new SNOMED CT-specific definitions. This is a suggestion I particularly like and is a consistent theme across the feedback.

Thank you also for the pointer to the openEHR Impairment summary archetype, which we will look at as part of this work.

Sarah

Thank you @jsnyder for your support for reviewing this content and aligning it with the ICF definitions. Using the ICF as a basis has been a consistent theme across the feedback, and it is an approach I welcome.

Thank you also for highlighting the overlap with the High level ADL Observables and Disability/Impairment topics, and the potential impact on LOINC answer lists and on countries using SNOMED CT findings as response values for observable entities. These are important considerations, and we will take them into account, along with how best to involve the wider community, going forward.

Sarah

The feedback period for this briefing note has now closed. Thank you to everyone who took the time to review the proposal and respond; the feedback has been really useful. We will review all the comments internally and will respond to this post with our next steps.

Sarah

Thank you to everyone who took the time to comment on this briefing note. The feedback has helped refine the approach to this work.

There was broad support for addressing the inconsistent wording, synonyms and modelling in these concepts, and several NRCs gave concrete examples of the translation problems the current content causes. The most consistent request was to base the work on established international definitions, specifically the WHO ICF, rather than on definitions created for SNOMED CT.

In response to the comments received, the following actions will be undertaken:

  1. ICF definitions will be used where ICF defines the terms.
  2. For terms that ICF does not define, the definitions proposed in the briefing note will be used, aligned with the definitions suggested in the feedback.
  3. Duplicate concepts will be identified and resolved as part of the FSN and synonym review.
  4. The scope will remain as outlined in the briefing note. The examples raised in the feedback as causing translation difficulties are already included in the concepts under review.
  5. Any concepts proposed for inactivation will be communicated through the usual release processes so that users of maps and extensions can plan updates.

The review will now begin on this basis, and this discussion will be marked as closed. Thank you again for your input.

Sarah

Thank you for summarising the outcome, and thankyou to others for providing examples.

I note that the questions I raised about how the proposed changes will be evaluated in terms of demonstrable benefit, including translation, implementation and user acceptability, and whether there will be any evaluation of the revised content before it is released, do not appear to have been addressed.

I think these remain important considerations, particularly where existing content is to be changed in pursuit of claimed improvements for all users.

Ed

Thanks, Ed.

In addition to this thread, the proposal was presented to the Translation User Group and reviewed separately by the Nursing CRG and the Mental and Behavioural Health CRG. Their feedback, including on the clinical acceptability of the definitions, is reflected in the actions above.

On evaluation: before release, we’ll share the revised content with the Translation User Group and with the NRCs who raised specific problems in this thread. We’ll ask them whether the revised concepts resolve the issues they reported, using their examples (e.g. the hand function/dysfunction concepts and the vision synonyms) as test cases. We’ll also ask whether the changes create new problems for existing translations, maps or value sets. If that review identifies problems, we’ll revise the content before release rather than after.

Best wishes, Sarah

Thanks.

The extent of the evaluation seems to be limited to those groups who have raised concerns. Given the likely widespread use of much of this content, what is going to be done to evaluate the impact of the changes on more general SNOMED CT users who, to date, have been happy to use the content as published? What does it really mean to impose ICF definitions on SNOMED CT terms which are then used outside of an ICF framework?

If, as we are told, ICF definitions (or any of the definitions offered) ‘distinguish between’ the words under discussion, what is to become of concepts on which they are currently applied synonymously? For example, will 82971005 | Impaired mobility | now be split into two concepts (‘impaired’ and ‘limited’) with (apparently) distinct meanings that for future use need to be understood by all users? Surely this risks degrading data quality if the resulting split concepts are used in arbitrary ways.

Ed

Thanks, Ed.

You’re right that we can’t directly evaluate the impact on every user before release. As with other content changes, we rely on consultation, advance notice through the Early Visibility page so implementers can assess the planned changes, and historical associations so that existing data can be followed. That’s a limit of the process, not a complete answer to your question.

Your point about terms that are currently used synonymously is an important one. The feedback from NRCs and the CRGs was that separating non-synonymous descriptions and using established ICF definitions were the changes they would find most useful, and the review will proceed on that basis, as set out in the outcome above. You’re right that the definitions can’t determine how people use these words outside an ICF framework, so we won’t use them to create new distinctions that clinicians don’t make in practice. Where a description clearly doesn’t match its concept’s meaning, removing it is an error fix rather than a change in meaning. Where terms are genuinely used interchangeably, the concept, its identifier and those descriptions will be kept, so existing patient data, value sets and maps remain valid. The definitions are a tool for identifying descriptions that clearly don’t belong together, not a requirement that every concept be reworded to fit them.

A further complexity is that many concepts don’t fit neatly into either “impairment of a body function or structure” or “limitation in the extent or ability to perform an activity or function”. Some mix the two, and your example is one of them. In 82971005 |Impaired mobility (finding)|, “impaired” describes an activity rather than a body function or structure. NANDA-I (2021–2023 edition), for example, defines Impaired physical mobility as a limitation in movement of the body or of one or more extremities (see Open RN Nursing Fundamentals, 13.3), so in established nursing usage “impaired mobility” and “limited mobility” refer to the same thing. The descriptions on this concept also differ: “Limited mobility” describes the ability to move about, while “Limitation of motion” usually refers to range of movement at a joint. No blanket approach will work here, so each concept will be assessed individually against its clinical usage and meaning. If any change is made, existing data will be protected through the usual inactivation and historical association mechanisms.

This is consistent with the outcome posted above. As the feedback period has now closed, progress on the review will be shared through the Early Visibility page as well with the Translation User Group and the NRCs who raised specific problems. I’m happy to discuss any of these points further directly.

Sarah