Page History

• Remember recording!

• None stated

Background

Draft editorial guidelines: Editorial Guidelines for Diagnostic Products Used for Susceptibility Testing

It was decided to recommend representation the physical form of the susceptibility test product, and also to use the | has presentation strenght... | attributes (as opposed to other strength attributes).

Two issues were discovered while re-reading the Inception/Elaboration document for susceptibility testing: 1. "oral form antibiotic susceptibility" exists as components in LOINC tests. 2. when other methods than culture are used, e.g. PCR or sequencing, to determine susceptibility, we might need to use another way of modeling, e.g. beta-lactamase producing ~ resistance towards beta-lactam antibiotics.

While the Susceptibility test products are needed for the mycobacteria tests (with strength-specified antibiotics), we might reconsider the approach for other cases, and use substances where products are not needed, together with a role chain | towards | o | ingredient | → | towards |.

Rob: Aren't all susceptibility tests strength-specified, even though the strength is not part of the definition?

Xavier: EUCAST breakpoint for diffusion disks : http://www.eucast.org/clinical_breakpoints/ the xls is at http://www.eucast.org/fileadmin/src/media/PDFs/EUCAST_files/Breakpoint_tables/Preliminary_v_9.0_Breakpoint_Tables_for_consultation.xlsxbreakpoint requires a definite antibio amount in the disk.

Most tests (mycobacteria tests being an exception) are based on there being a concentration gradient (e.g. disk diffusion, etest, MIC procedures) and thus not a single concentration.

2019-02-11:

An OWL ontology with Diagnostic test products and susceptibility observables is attached.

The combination substances are to be inactivated, so modeling cannot rely on use of such concepts.

2019-03-25:

An alternative version not using combination substances was presented and discussed.

Current objective

Presentation

Give recommendations on representation given two alternatives: (1) use | Susceptibility test product | as values of the | towards | attribute OR (2) use Substance together with | direct substance | = | Susceptibility test product | only when needed.

2019-04-08:

Presentation of alternatives for susceptibility observables modelling.

Has use with information models, e.g. FHIR Observation, been tested? No, but given that the observables are expression representations of LOINC content, for which there is ample experience, that is assumed not to be a problem.

Can Susceptibility test products be categorized as Pharmaceutical products, and thus be placed under 373873005 | Pharmaceutical / biologic product (product) |?

Comparison with allergy tests (skin or blood) can be explored further.

The project group voted to have a full example of using Test products as values for towards presented at next meeting (Motion: James R. Campbell , second: Raj Dash. Against: 0, Abstain: 1, For 5). Toni Morrison to be invited to discuss placement of Susceptibility test products.

At a meeting 2019-05-15 with the HoT Jim Case it was decided to again look into using Medicinal products, first checking with the Drug project.

2019-06-10:

There was agreement in the group that Medicinal Products should be used as value of the | towards | attribute for susceptibility observables. The Medicinal Products will be of the "containing only" flavor. No decision made yet about strength-specified susceptibilities.

2019-07-15:

Next steps: Update I&E document, editorial guide as well as the post-coordinated expressions in the expression refset.

2019-08-19:

A new version of the elaboration document added to this page. The new version was discussed and amended and the new version is attached.

2019-09-16:

•  Daniel Karlsson to contact Cathy Richardson and Jim Case about how to progress the susceptibility elaboration document.

Daniel Karlsson to update the I&E document

Farzaneh Ashrafi Suzanne Santamaria to update editorial guide and expression refset

See this page.

2019-04-08:

Presentation of work done by James R. Campbell et al. at UNMC. Observables had been developed for MMSE (Mini-mental state examination). Process, scale type, and property concepts had been created in order to define the MMSE observables. Also, the section about function observables in the Observables I/E document was expanded.

The level of detail of Observables for individual instrument parts, such as the individual questions of MMSE, was discussed. Alternatively, generic observables, not specific to the instrument, could be used. UNMC preferred having specific observables.

The function observables are, according to the current pattern, defined by reference to the processes which are realized by the function, e.g. Orientation in time is realized by the function Ability to orient in time. Other observables can be defined by reference to the processes, e.g. performance of processes. Alternatively, these observables could be defined in terms of the function rather than the process.

2019-05-20:

Updates to be presented.

Lab observables interoperability

X

See this page.

2019-04-08:

James R. Campbell presented a request to SNOMED International to publish an OWL ontology including the LOINC expressions and expressions for any other lab terminology (e.g. NPU Terminology or the NHS pathology subset and content in SNOMED to allow classification, and comparison, of lab content.

The group was supportive of the proposal.

2019-06-10: James R. Campbell will provide a report on progress so far and a presentation help for the LOINC comittee last week.

Modeling of TUSS | Timed unsupported steady stand time (observable entity) |.

http://www.calderdaleframework.com/wordpress/wp-content/uploads/2014/04/26.PT36-TUSS.pdf

https://www.physiotherapyjournal.com/article/S0031-9406(05)65775-6/pdf

2019-08-19:

A solution based on the process observable pattern was presented. The primitive stated parents were discussed and 282316001 | Ability to stand alone (observable entity) | or 363838007 | Balance observable (observable entity) | might be plausible candidates depending on how "ability" is to be interpreted.

Applying the function observable seems possible but difference (| has realization| in stead of | characterizes |) is small. It should be investigated if both patterns are really needed.

2019-09-16:

Agreement on modeling, although there were questions about the rather non-descriptive FSN.

•  Daniel Karlsson Suzanne Santamaria James R. Campbell to test both function and process ways of modeling for a select number of cases

Penni Hernandez

Daniel Karlsson

• Estimated protein intake in 24 hours (observable entity)
• Measured protein intake from oral nutrition in 24 hours (observable entity)
• Measured protein intake from enteral nutrition in 24 hours (observable entity)

As (almost) seen, these are rate observables (mass/time quantity) and those have previously been modeled as process observables. The examples highlight an issue with process observables in that the processes themselves do not have a concept model, but only those parts deemed relevant to observables. E.g. the administration route here cannot be represented using the model.

2019-07-15:

Sarah Harry compare with excretion observables in laboratory medicin, in what sens are they same or different.

A page for discussion: Nutrition observables

2019-08-19:

Sarah Harry presented a comparison of "output" observables (slides attached).

Possibly, "output" or "input" (e.g. intake) observables could be represented either using a process observable pattern (using process observable attributes such as | process output |) or a quality observable pattern (using quality observable attributes such as | inheres in | etc.). In order to determine if both patterns are needed or not, a list of example observables from SNOMED CT, LOINC and eNCPT should be collected and discussed.

SNOMED International is working to model nutrition observables together with dietitians' organizations. Results and questions will be posted on the Nutrition observables sub page.

2019-09-16:

Discussion of questions on this page.

The words "output" and "intake" makes the attribute use a bit intuitive. The attribute names were set when the processes discussed were mainly output processes such as excretion. From the perspective of the intake process, the input (of nutrition) becomes the output! A better name of the attribute 704324001 |Process output (attribute)|, e.g. "process result" could be considered.

The route of intake (oral, enteral, parenteral, intravenous) is currently in no range of any Observables attribute. Addition of a new attribute requires careful consideration of the concept model for processes included in the Observables model, and how that relates to other process concepts in SNOMED CT.

"Serving" observables, where intake is observed in the number of standardised servings are consumed, e.g. "Estimated dairy servings in 24 hours", were discussed. It was assumed that those were similar to previously discussed intake observables with the addition of "servings" as a unit. Penni Hernandez will explore the use of units for representing these observables.

•  Daniel Karlsson to collect a list of "input/output" observables from SNOMED, LOINC, and eNCPT.
•  Penni Hernandez to provide input from the nutrition observables work

Daniel Karlsson

•  Daniel Karlsson to produce modeling examples of process and quality versions of some sample of Observables