In patient-reported registries, we do not suggest that the individual/caregiver should answer this question. Ideally this item will be managed/entered by the Registry Curator, following review of the registration or communication from individual's family.
Yes
means that the individual was known to be alive at the datestamp of this value. No
means that the individual is known to be deceased; in this case, the datestamp of this value is irrelevant and may be omitted. If known, the date of death is to be provided in the item Date of death
.
It should not be necessary to store an explicit datestamp for this item. Instead, a registry may use the date of the last update or contact with the individual as the datestamp.
Item type: | yes/no |
Related items in previous version: | 3.00 |
Usage in other datasets: | DMDLGMD |
In version 2.0, the value Loss of follow-up
was removed. In its place, the item was changed to being datestamped, which allows applying a specific criterion across all registries for judging loss of follow-up (for example, two years after the last contact).
Cause of death as code of the classification specified in Cause of death classification
.
Item type: | restricted text |
Consistency rules: | May only be provided if the value of |
Related items in previous version: | 3.02 |
Usage in other datasets: | DMDLGMD |
As of version 2.0, it is no longer possible to use the ICD-10 chapter headings instead of specific codes. However, registries are free to offer common causes of death in their data collection form which are automatically mapped to their respective codes.
Classification used in the item Cause of death code
.
Item type: | single selection |
Consistency rules: | Must be provided if |
Related items in previous version: | 3.02 |
Usage in other datasets: | DMDLGMD |
Value ID | Description |
---|---|
ICD-10 | ICD-10 |
ICD-11 | ICD-11 |
This item was added in version 2.0 to allow for future use of other classifications than ICD-10.