UNMCCC / CRIIS_Source_Extracts_for_OMOP

Cancer Clinical Data integration - Set of SQL extractions from disparate health system sources targeting the OMOP data model
MIT License
0 stars 0 forks source link

CNExT drug exposure extract has possible issues #28

Open lvarnedoe opened 2 years ago

lvarnedoe commented 2 years ago

The cnext_drug_exposure extract only pulls from the chemo table. Per OMOP description, the drug exposure table is to include a drug ingested or otherwise introduced into the body. Drugs include prescription and over-the-counter medicines, vaccines, and large-molecule biologic therapies, but not radiation.

lvarnedoe commented 2 years ago

Drug exposure query - some other potential issues: PERSON_ID - pulled from PatExtended and returns only zeroes; value pulled from Hospital in visit details and visit occurrence - are the person_id values to be used to cross-reference result sets? VISIT_OCCURRENCE_ID - pulled from Patient. Pulled from Hospital in visit details and visit occurrence. Most of the records I checked have the same numbers, but not all. For cross-reference purposes, I would think this value should be the same across all result sets. Condition "CHM.F04755 is not null" in predicate limits number of rows returned and is not in the Chemo visit details query-shouldn't they be the same?

lvarnedoe commented 2 years ago

Should text field (F05229) in chemo table be included in extract? It contains info on the drug administered, amount, and location received.

lvarnedoe commented 2 years ago

Inigo, can you reopen this issue. Misunderstood a button and closed it by mistake. Thx.

lvarnedoe commented 2 years ago

Never mind. I was able to reopen it myself.

lvarnedoe commented 2 years ago

PERSON_ID and VISIT_OCCURRENCE_ID mentioned above have been moved to separate issues.

isangil commented 2 years ago

can we close this one? seems now as duplicate.

lvarnedoe commented 2 years ago

No, it's not a duplicate. the drug exposure script only pulls from chemo and I think it should pull from every therapy table - hormone, immuno, other, etc... Doing so would mean duplicate data coming from various scripts, though. Just the first comment applies anymore. The issues in the 2nd comment are in separate issues.