OHDSI Home | Forums | Wiki | Github

Multiple events per one cost


(Nadya Zvyagina) #1

I am trying to figure out how to convert cost data correctly.

Example: There is 1 source record (patient_id, date, drug_code, cost). This drug code maps to 2 (or more) OMOP concept_id.
As a result we have 2 OMOP records in drug_exposure, meaning they have 2 different event_id’s.

The question is how to fill in Cost table?
Solution 1: We can create 1 cost record and use one of these event_id.
In this case we partially lose the relation.
Solution 2: We can create 2 cost records using both event_id’s.
In this case the drug cost gets doubled.

Please share your experience how to solve the problem.


(Dmytry Dymshyts) #2

Well, let’s use an example:
Drug ‘A / B’ Maps to Drug ‘A’ and to Drug ‘B’.
Drug ‘A / B’ costs 10$

Cost
‘A’ - 10$
‘B’ - NULL

‘A’ - 10$
‘B’ - 10$,

So, in both cases ‘A’ costs 10$, while for 10$ you can buy whole ‘A / B’.
So, we have some data corruption anyway.

The solution I see here:
If the drug can’t be represented as one standard concept, you create for it 2 bill + standard concept,
and in concept_relationship there are ‘Has ingredient’, ‘Has component’, ‘Has Dose Form’ relationships depending on what drug was mapped to, instead of ‘Maps to’ relationship (like it’s now)
also we create concept_ancestor entries based on those relationships.
@aostropolets, thoughts?

So, 2 bill+ concepts for custom concepts and real concepts for vocabularies supported by OHDSI like Gemscript, for example.

Or, even we can say RxNorm Extension for everything


(Gowtham Rao) #3

This has been an issue, when using omop cdm for cost and utilization. Record count should be the same between source data and omop converted data. Instances like this causes inflation of record count after omop conversion.

Custom standard concepts are probably the best solution, to maintain referential integrity.


t