Intent and StopReason of a Procedure

[SarehAghaei]

In MUG data, therapeutic procedures include several properties, such as intent and termination reason.

In this context, there are two classes found in SPHN:

1- sphn:Procedure: This class lacks the sphn:hasReasonToStopCode property. Also, sphn:Intent requires a sphn:Code, whereas intentions in MUG are in free-text format (not normalized).

2- sphn:DrugAdministrationEvent: Although this class has the property sphn:hasReasonToStopCode (a subproperty of sphn:hasCode), its range is limited to Code or Terminology, whereas stop reasons in MUG are in free-text format. Additionally, according to SPHN's meaning binding, this class is equivalent to SNOMED 182832007 | Procedure related to management of drug administration (procedure) |, yet some therapies, such as 1259201000 | Adjuvant drug therapy (procedure) |, do not fall under this category. Moreover, there is no sphn:hasIntent connected to sphn:DrugAdministrationEvent.

Note: According to the SNOMED CT-based meaning binding mentioned in SPHN, sphn:DrugAdministrationEvent is a subclass of sphn:Procedure.

What is recommended for modeling therapeutic procedures to capture both intents and termination reasons?

[KateSerafimova]

Add Intent (if it is available) - use the SNOMED code. ReasonToStop - To be addressed in G2

[KateSerafimova]

From 1. .. sphn:Intent requires a sphn:Code, whereas intentions in MUG are in free-text format (not normalized). will be resolved with issue #54