The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| When to exclude persons from the CDM | Page | Considerations for excluding persons from the CDM. |
| How to map gender identity | Page | Issue # and location Themis issue #102 Issue summary The term “gender_concept_id” is outdated and really should be “sex_concept_id”. Since changing gender_concept_id is a huge lift for developers and package maintainers, this change will be implemented at the next major release. In the meantime, how... |
| What to do when birth day, month or time are missing from the source | Page | Issue # and location Themis Issue #93 Issue Summary How to populate the birth_datetime field when any or all of day/month/time of birth is not provided in the source. Convention type Table CDM table PERSON CDM field birth_datetime... |
| How to populate day_of_birth when it is missing from the source | Page | Issue # and location Themis issue #96 Issue summary Day of Birth is not required in the CDM, but it is a component of birth_datetime. The CDM conventions have guidance listed for how to infer birth_datetime field, but not for the day_of_birth field itself. Convention type... |
| How to populate month_of_birth when it is missing from the source | Page | Issue # and location Themis issue #94 Issue summary How should month_of_birth be populated when it is not provided in the source data? Month of birth is not required in the CDM, but it is a component of birth_datetime. Convention type Table CDM... |
| How to populate year_of_birth when it is missing from the source | Page | Issue # and location Themis #92 Issue summary The lack of year_of_birth creates a dilemma on how to process those records. If an age group categorization is available, the approximate year of birth can be derived. I could not find guidance on how to estimate year of... |
| PERSON | Page | Conventions related to mapping data into the PERSON table. |