Representation of procedure settings observables, e.g. device settings but also treatment parameters such as dose, application area, etc.
Powered by a free Atlassian Confluence Community License granted to SNOMED International. Evaluate Confluence today.
1 Comment
Daniel Karlsson
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: