Hi @Alexandra_Orlova. What data source are you working with to convert cost data to OMOP?
Unfortunately, you are in the middle of a big change to the COST table, between version CDM 5.3 and CDM 6.0. Unfortunately we have a disparity here. The CDM you are working on is CDM 5.3 but the current vocabulary files are written for CDM 6.0. And so you are trying to add cost_type_concept_id for CDM 6.0 into CDM 5.3. And it's not going to work - or it will be very messy.
The cost_type_concept_id in CDM 5.3 should denote that the data comes from a billing accounting system, a claims database, or whatever data set you are looking at. I'm assuming all three payments ($20, $6, $4 in the above example) all come from looking at the same data source? If all three of those costs come from the same data source, then all three payments need to reference the same cost_type_concept_id. My only suggestion is to pick a cost_type_concept_id and apply it across the board. Then make a note that because you are using the most updated vocabulary, you are using this type_concept_id to stay compliant, but in analysis, it means "xyz".
@Gowtham_Rao it looks like you requested to remove or change these type_concept_ids in a request. I didn't think it was that big of a deal because I didn't think anyone was using the CDM 5.3 Cost table. But it seems that there are more users than you and me So we may want to add in some cost_type_concept_ids that are CDM 5.3 compliant.