Page tree

893 View 1 Comment In discussion Comments enabled In the category: Undefined

Representation of procedure settings observables, e.g. device settings but also treatment parameters such as dose, application area, etc.

Contributors (1)

1 Comment

  1. An example is here:

    IHTSDO-326 - Getting issue details... STATUS

    "Allow someone to specify the anatomical site at which topical aspirin is/to be applied."

    There are at least two aspects which need discussion: (1) location as related to procedures/processes, and (2) procedure settings in general.

    Previously, we have discussed observables for location of material entities, e.g. tumor location. We've also touched upon "site of excision of tumor" but decided that the use case was better represented as the site of the tumor. However, if there is no similar physical property, as in the aspirin case, we need to represent the (possibly intended) location of performance of the procedure. Other considerations are overlap with e.g. the procedure site/morphology attributes and the information model-terminology boundary.

    General procedure setting issues:

    • We have to determine how the inheres in attribute would be used for procedure setting observables. For devices, the setting may inhere in the device it self (or a part thereof). For "manual" procedures it is not as clear what the settings would inhere in.
    • What would be property types of procedure settings? E.g. for the flow setting of a ventilator would the property type be "flow" or "flow setting". A device can have a setting without the quality being realized, like a goal.
    • Difference between setting and readout of device sensors?