E2O 23rd meeting 20220223

Welcome

@Daniel Karlsson

Conflicts of interest

@Daniel Karlsson

Work plan

All

A state where part of the work is done may be a cause of concern for implementers, where part of a content is in EP and part in O hierarchies (which already is the case...).

There are separate concerns about re-representation as Observables and inactivation of Evaluation procedures and could be separate decisions. At least, inactivation may come after the Observables have been put in place. Inactivated content may be re-activated in extensions.

There are still Evaluation procedures for which there are yet no Observables solution proposed (e.g. panels), but such proposals can be developed.

There are several options, which will have to be developed and confirmed with the community.

Collection of issues in working with the current Evaluation procedures include under specification (both between FSNs and possible modeling as well as the concept in relation to requirements for use), some pure techniques, inconsistency in modeling, primitives which could be fully defined. A sub-page has been created.

Workplan should be documented in a SNOMED International proposal form. https://docs.google.com/document/d/1ug2piu_bYwuWJ96d1k-6J41aYDy0IDHbIAhAGZOp6rs/edit?usp=sharing (access can be provided by @Yongsheng Gao).

New Evaluation procedure lab concepts beyond the 1200 already modeled should be identified. @Karim Nashar and @Jim Campbell will explore possibilities of collecting more frequency-based content.

2022-02-23:

A discussion of options for bringing the project forward to fruition.

There are still the legal hurdles with the Agreement limiting what is possible.

Also, user having expressed the need to keep the current EPs (with SCTIDs) for use in "information-model poor" implementations also remains a hurdle, particularly for reusing existing SCTIDs.

Discussion Phase 1 dataset for migration trial

57 min

@Jim Campbell

@Former user (Deleted)

@Daniel Karlsson

• Review of progress with conversion file for UK labs

• Modelling issues suggested by classification of Phase 1 migration set 

• Followup on issues from last meeting:

  • Timed specimens shall be identified by instance time stamp of acquisition 

  • 24 hour urine testing deferred to committee deliberation

• Red cell indices such as Mean corpuscular volume. Representation of averages (or any aggregation) has not yet been finally agreed on,proceed with proposed model

• Anti-mitocondrial antobody pattern, Leukocyte ALP → items deferred to Observables deliberation

• Agglutination test. Property = Presence, , Technique = Latex agglutination

• Titre. How to represent titre in relation to presence and quantity concentration; deferred to committee

• Von Willebrand factor activity - likely a process observable and out of scope.

• Produce an OWL file based on decisions made and compare hierarchy of reclassified Observables to Evaluation procedures.

2021-11-03:

• @Jim Campbell presented work since last time.

• DK: additional, the differences found between the Evalualtion procedure hierarchy and the E2O Observable hierarchy have highlighted issues with the Evaluation procedure hierarchy.

• Discussion about future progress of E2O

• UK current decision is to use Procedures in the context of ordering

  • There would in the UK content not be duplicates between "ordering" and "result" concepts.

• Keeping two hierarchies with essentially the same meaning introduces maintenance challenges

• There would be modeling solutions to keep hierarchies in sync, IFF it is possible to write clear guidance on when to use which hierarchy

2021-11-17:

• Next steps would necessary include the creation of templates for the common lab areas

• Inactivations of groupers such as "Sodium measurement" - replacement with e.g. "Sodium ion quantity concentration in liquid substance"

• @Yongsheng Gao propose to create new SCTIDs for Observables and create "link" between Evaluation procedure and Observable concepts.

• Templates is a good way to get agreement on the application of the (generic) Observables model.

2021-12-15:

• Proposal: look for subsumees of high-frequency concepts @Daniel Karlsson will check

• Implementation process:

  • Inform CoP that the project is being done

    • Project statement (cf. project template)

    • Limit to reportables (for the time being...)

  • Keep both procedures and observables while under development

  • Maintain "map"/association refset between corresponding existing evalutation procedures and new observables

  • Develop in a community area

  • Steps:

    • Get moduleId

    • Set up community area

    • Develop templates

Next meeting 

2 min

@Daniel Karlsson

New meeting in two weeks

AOB

1 min

@Daniel Karlsson