todorprimov
commented
8 months ago We agreed that using sphn:AdverseEvent is not precise. This is a very similar case as post/pre-operative temporality modelling. Thus we would like to postpone it to G2
Open KateSerafimova opened 9 months ago
todorprimov
commented
8 months ago We agreed that using sphn:AdverseEvent is not precise. This is a very similar case as post/pre-operative temporality modelling. Thus we would like to postpone it to G2
Background
Some surgeries can have complications or other effects, but in SPHN there is no property to account for that. The class sphn:AdverseEvent can be used for that. It has a data property sphn:hasIntervention that can describe the suspected cause as literal.
Change Detail
[TO BE REFINED] The suggested change is to add an object property to sphn:AdverseEvent, that relates to sphn:Procedure. It can be similar to sphn:hasIntervention. Other option will be to add a new property to sphn:Procedure - aidava:hasAdverseEvent, that will connect to an effect from the procedure.
Why is this change needed?
In MUG data, there are the following data points:
They can be considered as a sphn:AdverseEvent and they are related to a specific procedure - Revision Surgery.
What is the impact if this change isn't made?
A new property is introduced.