OHDSI Home | Forums | Wiki | Github

Procedure or Measurement


(Tarun Shah) #1
  1. I was trying to map Myocardial Perfusion Scan (78452) code. what’s the correct way to map, as it can either be Procedure or measurement.

  2. Are we mapping radiology in procedure or measurement?

(Dmytry Dymshyts) #2
  1. This a Procedure as it stated in the OHDSI Vocabulary.
    The result of this Procedure is a text report usually. And it goes into NOTE table.
  2. In procedure if it’s the case above. If you get exact numerical or categorical value as a result, you put them into Measurement. If you have the example from your data for the second case, please provide, so we can undersand the case better.

(Manlik Kwong) #3

The way I approach these is first identify the Concept you want to map the data to, then look at the concept.domain_id - it will suggest whether its a procedure, observation, or measurement.


If I have ultrasound Carotid text as radiology, what would be the code, and table for the same?

(Manlik Kwong) #5

For the ultrasound data I’ve been importing I generally insert:

  1. Ultrasound procedure in the procedure table
  2. Ultrasound device exposure in the device_exposure table
  3. From the HL7/DICOM transaction or custom form where measurements can be parsed goes into the measurement table (ex LOINC.46234859 “Left ventricular End-diastolic volume by US.2D+Calculated by Teichholz method”)
  4. Other finding text that is not a ultrasound measurement goes into the note table - radiologist reading and findings in a narrative form.

I have not done so yet, but also use fact_relationship to link all these pieces together as coming from one procedure. Right now all the above use the source_value field to store say the ultrasound transaction GUID used to tie all these data elements to a single procedure or transaction source.

(Christian Reich) #6

Very clean.

(Manlik Kwong) #7

Thanks - the approach was on advice from Robert Miller one of our many resident OMOP experts.