diff --git a/docs/cdm54.html b/docs/cdm54.html index 85e613d..c473f3e 100644 --- a/docs/cdm54.html +++ b/docs/cdm54.html @@ -3898,13 +3898,15 @@ original prescription or dispensing record. Days supply can differ from actual drug duration (i.e. prescribed days supply vs actual exposure).”,“The field should be left empty if the source data does not contain a verbatim days_supply, and should not be calculated from other -fields.

Negative values are not allowed. Several actions are -possible: 1) record is not trustworthy and we remove the record -entirely. 2) we trust the record and leave days_supply empty or 3) -record needs to be combined with other record (e.g. reversal of -prescription). High values (>365 days) should be investigated. If -considered an error in the source data (e.g. typo), the value needs to -be excluded to prevent creation of unrealistic long eras. +fields.

Negative values are not allowed. If the source has +negative days supply the record should be dropped as it is unknown if +the patient actually took the drug. Several actions are possible: 1) +record is not trustworthy and we remove the record entirely. 2) we trust +the record and leave days_supply empty or 3) record needs to be combined +with other record (e.g. reversal of prescription). High values (>365 +days) should be investigated. If considered an error in the source data +(e.g. typo), the value needs to be excluded to prevent creation of +unrealistic long eras. integer @@ -5333,8 +5335,10 @@ domain that best represents the unit as given in the source data. There is no standardization requirement for units associated with DEVICE_CONCEPT_IDs, however, it is the responsibility of the ETL to -choose the most plausible unit. If there is no unit associated with a -Device record, set to NULL. +choose the most plausible unit. If the source unit is NULL (applicable +to cases when there’s no numerical value or when it doesn’t require a +unit), keep unit_concept_id NULL as well. If there’s no mapping of a +source unit, populate unit_concept_id with 0. integer @@ -5734,7 +5738,8 @@ from =. Operators are =, > and these concepts belong to the ‘Meas Value Operator’ domain. Accepted -Concepts. +Concepts. Leave it NULL if there’s an exact numeric value given +(instead of putting ‘=’) or there’s no numeric value at all. integer @@ -5814,7 +5819,10 @@ results for measurements, it is a valid ETL choice to preserve both values. The continuous value should go in the VALUE_AS_NUMBER field and the categorical value should be mapped to a standard concept in the ‘Meas Value’ domain and put in the VALUE_AS_CONCEPT_ID field. This is -also the destination for the ‘Maps to value’ relationship. +also the destination for the ‘Maps to value’ relationship. If there’s no +categorial result in a source_data, set value_as_concept_id to NULL, if +there is a categorial result in a source_data but without mapping, set +value_as_concept_id to 0. integer @@ -5848,7 +5856,10 @@ data. There is no standardization requirement for units associated with MEASUREMENT_CONCEPT_IDs, however, it is the responsibility of the ETL to -choose the most plausible unit. +choose the most plausible unit. If the source unit is NULL (applicable +to cases when there’s no numerical value or when it doesn’t require a +unit), keep unit_concept_id NULL as well. If there’s no mapping of a +source unit, populate unit_concept_id with 0. integer @@ -6586,7 +6597,10 @@ href="https://athena.ohdsi.org/search-terms/terms/4167217">4167217 ‘Family history of clinical finding’ as well as a ‘Maps to value’ record to 134057 -‘Disorder of cardiovascular system’. +‘Disorder of cardiovascular system’. If there’s no categorial result in +a source_data, set value_as_concept_id to NULL, if there is a categorial +result in a source_data but without mapping, set value_as_concept_id to +0. Integer @@ -6651,7 +6665,10 @@ data. There is no standardization requirement for units associated with OBSERVATION_CONCEPT_IDs, however, it is the responsibility of the ETL to -choose the most plausible unit. +choose the most plausible unit. If the source unit is NULL (applicable +to cases when there’s no numerical value or when it doesn’t require a +unit), keep unit_concept_id NULL as well. If there’s no mapping of a +source unit, populate unit_concept_id with 0. integer @@ -8446,7 +8463,10 @@ The unit for the quantity of the specimen. Map the UNIT_SOURCE_VALUE to a Standard Concept in the Unit domain. Accepted -Concepts +Concepts. If the source unit is NULL (applicable to cases when +there’s no numerical value or when it doesn’t require a unit), keep +unit_concept_id NULL as well. If there’s no mapping of a source unit, +populate unit_concept_id with 0. integer @@ -11074,7 +11094,8 @@ be exposed to a particular active ingredient. A Drug Era is not the same as a Drug Exposure: Exposures are individual records corresponding to the source when Drug was delivered to the Person, while successive periods of Drug Exposures are combined under certain rules to produce -continuous Drug Eras.

+continuous Drug Eras. Every record in the DRUG_EXPOSURE table should be +part of a drug era based on the dates of exposure.

User Guide

NA

ETL Conventions

@@ -11169,7 +11190,9 @@ PERSON drug_concept_id -The Concept Id representing the specific drug ingredient. +The drug_concept_id should conform to the concept class ‘ingredient’ as +the drug_era is an era of time where a person is exposed to a particular +drug ingredient. @@ -11563,8 +11586,9 @@ No

Table Description

A Condition Era is defined as a span of time when the Person is assumed to have a given condition. Similar to Drug Eras, Condition Eras -are chronological periods of Condition Occurrence. Combining individual -Condition Occurrences into a single Condition Era serves two +are chronological periods of Condition Occurrence and every Condition +Occurrence record should be part of a Condition Era. Combining +individual Condition Occurrences into a single Condition Era serves two purposes: