timepointkind
- Parent
- dataset
- Identified by
:timepoint/uidcontext id- Attributes
- 8
- Referenced by
- 5 attributes
Attributes
| Attribute | Type | Cardinality | Description |
|---|---|---|---|
| cycle :timepoint/cycle | long | one | If applicable, the cycle of clinical-trial-therapy that this timepoint represents |
| day :timepoint/day | long | one | If applicable, the day in the cycle of clinical-trial-therapy that this timepoint represents |
| id :timepoint/id | string | one | The id of the timepoint. This is unique within the dataset, but not necessarily within the database. If this timepoint is associated with a treatment regimen, the id must to start with the treatment regimen followed by the character '/'. The rest of the id is free format |
| offset :timepoint/offset | long | one | The offset in number of days (positive or negative) between this specific timepoint and the nominal timepoint indicate by its :timepoint/attribute. For instance to indicate two timepoints that are 5 days before and after the first treatment, you would create two timepoint entities both with type :timepoint/treatment1 and with offsets -5 and +5 respectively |
| offset-from-diagnosis :timepoint/offset-from-diagnosis | long | one | The offset in number of days from the initial diagnosis. This date should not be stored in the database |
| relative-order :timepoint/relative-order | long | one | The relative order of this timepoint within its treatment regimen. This field is mandatory for timepoints that have a :timepoint/treatment-regimen attribute |
| type :timepoint/type | timepoint.type | one | The type of this timepoint, refers to idents in the 'timepoint' namespace. The type of the timepoint is meant to represent both logical timepoints that exist outside of any chronological timeline (e.g. 'baseline'), as well as nominal timepoints within a treatment regimen (e.g. 'treatment1'). This field is mandatory |
| uid :timepoint/uid | [string …] | oneunique identity | Synthetic unique ID for timepoints |