Add ProblemConditon to the domains of sphn: hasStatus

[Wenjie225]

In UM's data, there are some variables representing a problem/condition and with values as Yes/No/Unknown.

Examples:

1. In the ''CTC'' table, there are variables about toxicities after radiotherapy, such as ''Dermatitis'' and ''Lymphedema'' in the DTS table, with a value as Yes/No/Unknown.

2. In the ''Follow up'' table, we have variables such as ''Distant Metastases'' and ''Regional recurrence'' with a status of Yes/No/Unknown.

3. In the ''Mammogram'' table, we have some variables as findings/disorders/problems, for instance, ''Hematoma'', ''Seroma'', ''Edema'', ''Axillary Infection'' etc. And they also have status values as results (Yes/No/Unknown).

So it would be good to add ProblemConditon to the domains of sphn: hasStatus, then add the status code to represent the values.

[KateSerafimova]

It is agreed to use the sphn:hasStatusCode to provide the verification status for ProblemCondition and constrain it to the following SNOMED codes: Unconfirmed |   | 410590009 |Known possible (qualifier value)| 415684004 |Suspected (qualifier value)| Provisional |   | 410592001|Probably present (qualifier value)| Confirmed | x | 410605003 |Confirmed present (qualifier value)| Refuted |   | (410594000 |Definitely NOT present (qualifier value)|) 410516002 |Known absent (qualifier value)| Entered-in-error |   | 723510000 |Entered in error (qualifier value)| Unknown |   | 261665006 |Unknown (qualifier value)|

We agreed to NOT add a class aidava:VerificationStatus with properties for date of assessment and verification status code.