Added lists to tables

This commit is contained in:
clairblacketer 2018-09-06 16:02:47 -04:00 committed by GitHub
parent 7afa9583ba
commit eaa2768f59
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions

View File

@ -31,9 +31,9 @@ No.|Convention Description
| 2 | Condition records are typically inferred from diagnostic codes recorded in the source data. Such code systems, like ICD-9-CM, ICD-10-CM, Read etc., provide a comprehensive coverage of conditions. However, if the diagnostic code in the source does not define a condition, but rather an observation or a procedure, then such information is not stored in the CONDITION_OCCURRENCE table, but in the respective tables indicated by the domain.
| 3 | Source Condition identifiers are mapped to Standard Concepts for Conditions in the Standardized Vocabularies. When the source code cannot be translated into a Standard Concept, a CONDITION_OCCURRENCE entry is stored with only the corresponding SOURCE_CONCEPT_ID and SOURCE_VALUE, while the CONDITION_CONCEPT_ID is set to 0.
| 4 | Family history and past diagnoses ('history of') are not recorded in the CONDITION_OCCURRENCE table. Instead, they are listed in the OBSERVATION table.
| 4 | Codes written in the process of establishing the diagnosis, such as 'question of' of and 'rule out', are not represented here. Instead, they are listed in the OBSERVATION table, if they are used for analyses.
| 5 | A Condition Occurrence Type is assigned based on the data source and type of condition attribute, for example: * ICD-9-CM Primary Diagnosis from inpatient and outpatient claims * ICD-9-CM Secondary Diagnoses from inpatient and outpatient claims * Diagnoses or problems recorded in an EHR. |
| 6 | Valid Condition Occurrence Type Concepts belong to the 'Condition Type' vocabulary in the 'Type Concept' domain.
| 7 | The Stop Reason indicates why a Condition is no longer valid with respect to the purpose within the source data. Typical values include 'Discharged', 'Resolved', etc. Note that a Stop Reason does not necessarily imply that the condition is no longer occurring.
| 8 | Condition source codes are typically ICD-9-CM, Read or ICD-10-CM diagnosis codes from medical claims or discharge status/visit diagnosis codes from EHRs.
| 9 | Presently, there is no designated vocabulary, domain, or class that represents condition status. The following concepts from SNOMED are recommended: * Admitting diagnosis: 4203942 * Final diagnosis: 4230359 (should also be used for discharge diagnosis * Preliminary diagnosis: 4033240
| 5 | Codes written in the process of establishing the diagnosis, such as 'question of' of and 'rule out', are not represented here. Instead, they are listed in the OBSERVATION table, if they are used for analyses.
| 6 | A Condition Occurrence Type is assigned based on the data source and type of condition attribute, for example:<br> * ICD-9-CM Primary Diagnosis from inpatient and outpatient claims<br> * ICD-9-CM Secondary Diagnoses from inpatient and outpatient claims<br> * Diagnoses or problems recorded in an EHR. |
| 7 | Valid Condition Occurrence Type Concepts belong to the 'Condition Type' vocabulary in the 'Type Concept' domain.
| 8 | The Stop Reason indicates why a Condition is no longer valid with respect to the purpose within the source data. Typical values include 'Discharged', 'Resolved', etc. Note that a Stop Reason does not necessarily imply that the condition is no longer occurring.
| 9 | Condition source codes are typically ICD-9-CM, Read or ICD-10-CM diagnosis codes from medical claims or discharge status/visit diagnosis codes from EHRs.
| 10 | Presently, there is no designated vocabulary, domain, or class that represents condition status. The following concepts from SNOMED are recommended:<br> * Admitting diagnosis: 4203942<br> * Final diagnosis: 4230359 (should also be used for discharge diagnosis <br> * Preliminary diagnosis: 4033240