OHDSI Home | Forums | Wiki | Github

Issue with Conventions description in CDM MEASUREMENT table

CDM Builders
#1

Sorry if this sounds naive, but I am looking into http://www.ohdsi.org/web/wiki/doku.php?id=documentation:cdm:measurement, and an example for “For some Measurement Concepts, the result is included in the test” seems to include missing/invalid concepts.
To quote:

For example, ICD10 concept_id 45595451 “Presence of alcohol in blood, level not specified” indicates a Measurement and the result (present). In those situations, the CONCEPT_RELATIONSHIP table in addition to the “Maps to” record contains a second record with the relationship_id set to “Maps to value”. In this example, the “Maps to” relationship directs to 4041715 “Blood ethanol measurement” as well as a “Maps to value” record to 4181412 “Present”.

But when I try

select * from omopv5.concept where concept_id = 45595451;

or

select * from omopv5.concept_relationship where concept_id_1 = 45595451;

the queries return no rows, and when I try

select * from omopv5.concept_relationship 
where concept_id_2 = 4041715 and relationship_id = 'Maps to' or concept_id_2 = 4181412 and relationship_id = 'Maps to value';

I only get

45468812	4041715	Maps to	01-JAN-1970 12:00	31-DEC-2099 12:00	
 4041715	4041715	Maps to	01-JAN-1970 12:00	31-DEC-2099 12:00
#2

I just tried the query
select * from concept where concept_id = 45595451;
and it returns
concept_id concept_name domain_id vocabulary_id
concept_class_id standard_concept concept_code valid_start_date
valid_end_date invalid_reason
45595451 Presence of alcohol in blood, level not specified
Measurement ICD10 ICD10 code Y90.9 1990-05-01
2099-12-31

You might want to update your vocabulary. To check the version run

select * from vocabulary where vocabulary_id = ‘None’

vocabulary_id vocabulary_name
vocabulary_reference vocabulary_version vocabulary_concept_id
None OMOP Standardized Vocabularies OMOP generated
v5.0 16-APR-16 44819096

#3

@apeshansky:

@DTorok is right. It’s all there.

#4

Sorry - I will make sure our vocabularies are updated before making fool of
myself again :frowning:

#5

It turns out our vocabulary database was downloaded in 2014 (vocabulary_version = ‘v5.0 2014-10-15’) and never updated since.
Sorry. As they say, no fool like an old fool :wink:

#6

I have version v5.0 20-JUN-16 and I dont see the entry.

#7

I now see all the values. Our version is v5.0 08-JUN-16

t