In various of the provided mockup data, a field with the label "Age" is provided. From a schema modelling perspective, this is a bit problematic. ie. What are the semantics behind those Age values. Is it age at admission, age at diagnosis, age at entry in the db, etc?
One mockup dataset provides both fields with the date of birth and an adjacent field with the Age. This helps, but yet remains a bit vague on its semantics. Again is it current age, age a diagnosis, etc.
Would it be possible to dictate a rule to prevent the use of age values in the linked data originating from the delta tissue project? When datestamps are provided for the different stages in the data collection together with the date of birth can be easily calculated on the fly when GUIs are rendered.
andrawaag
commented
2 years ago
In various of the provided mockup data, a field with the label "Age" is provided. From a schema modelling perspective, this is a bit problematic. ie. What are the semantics behind those Age values. Is it age at admission, age at diagnosis, age at entry in the db, etc?
One mockup dataset provides both fields with the date of birth and an adjacent field with the Age. This helps, but yet remains a bit vague on its semantics. Again is it current age, age a diagnosis, etc.
Would it be possible to dictate a rule to prevent the use of age values in the linked data originating from the delta tissue project? When datestamps are provided for the different stages in the data collection together with the date of birth can be easily calculated on the fly when GUIs are rendered.