A proposal to replace many of the diet finding terms (e.g. high fat diet) with regime/therapy concepts has run into an obstacle with the current usage within the UKTC where these terms originated. In consultation with the UKTC, it has been proposed that we:

• continue with the addition of valid diet regimes (current diet findings are being reviewed for validity
• inactivate and replace diet findings with more precise terming (e.g. Follows X diet regime (finding)) to allow for graceful evolution and traceability

Discussion:

Diets are both prescribed and "followed". The regimes are driven by the needs of dietitians, the findings are required for observations about what diets are being followed by a patient, some of which would never be prescribed or endorsed.

If the FSN needs to be changed for the clinical findings. What should be the terming for the FSN and what should be the PT?

Regimes are sets of activities rather than a specific procedure. Should these be separated from the procedures hierarchy as a whole. Because they originated from the READ codes, moving them would cause issues with the current taxonomy.

More specific FSNs are desireable. The more general issue of what to do with regimes is needed since none of them have "actions" associated with them.

Is changing the FSN a technical correction? If the change to the FSN makes the implicit context explicit, then it would be a technical correction and no need to inactivate.

Unanimous agreement that the FSNs can be changed. Proposed FSN "Follows X diet (finding)" with PT of "Follows X diet". The implied meaning is this refers to Subject of record".

Additional discussion for a general model on regime/therapy is needed.

Discussion:

Propose way forward to address the apparent duplication between these two hierarchies:

• How to handle panels/batteries
• Order vs. result

Discussion:

Discussion in Observables group. Issues in a potential move of evaluation procedures to observables is that the observable model was developed as "single" observation types. In evaluation procedures there represent multiple observations, such as panels or batteries. Single value evaluation procedures could be moved to Observables as a first cut. However, the identification of which evaluation procedures represent single value observations is problematic due to inconsistent RG and modeling.

NHS also has the issue with creation of new observables that overlap with evaluation procedures. The real issue involves panels or batteries that represent multiple observations, which is not supported by the observable model. Another issue is that sometimes what is "ordered" is not the same as what is "resulted" by the laboratory. This is similar to what happens in pharmacy with substitutions.

The issue with tracking the order vs. the result is more of an operational or information model issue.

GRE - a prior discussion was that a model proposed was for orderable procedures and resultant observations. While this would appear to be duplication of concepts in procedures and observable, it makes the semantics explicit.

KCA - need a more consistent simplified model across finding, disorders and observables.

PAM - the use case for a separate orderable given the receipt of observations that differ from the order.

This can be addressed with a generalization hierarchy within a single hierarchy. It does not necessarily address the panel battery issue.

There is a need to write out the use cases for the laboratory space.

Evaluation procedures with an observation technique (e.g. ELISA) are often primitives with a few distinct techniques in the 129264002 | Action (qualifier value) | hierarchy (particularly the Imaging – actions). Observable entity has a technique attribute whereas evaluation procedures have none (with an overlap with some actions). Moving eval procedures to observables would possibly require being explicit about the technique.

Discussion:

Three places where techniques are represented: Techniques hierarchy, Action hierarchy, Procedures (primitive content).

UK and Sweden have done gap analysis and found substantial omissions. Very little hierarchical structure as well.

Techniques were developed prior to the observable hierarchy. Was to be used to define procedures, but the technique attribute was not added to the concept model. Approaches to consider would be to add a new attribute or to extend the Action hierarchy. Techniques could also be used to define actions. This would enable the SD of many procedures.

DKA would like a proposal for how to resolve the "mess" that currently exists. UK ans SE will be doing a gap analysis. This could be used to develop a proposal for addressing this issue. Might be available by the April business meeting.

As discussed in KL. Need a list of proposed description types to send to tech services for implementation. Guidance on use will need to be developed. Current use cases to consider are:

• near synonyms - these can be either "broader than" terms or non-semantically equivalent but related terms (e.g. vaccination (procedure) vs. immunization (a process following vaccination or administration of immunoglobulin)
• hypernyms
• search terms - colloquial terms
• "Patient-friendly" or consumer terminology
• abbreviations/truncation

Issues within our current synonyms was identified in an AMIA paper in 2003:

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC1480077/pdf/amia2003_0949.pdf

Discussion:

April business meeting in London

Discussion:

Potential agenda items:

• Update from concept inactivation group
• Update from source of truth project