User Tools

Site Tools


documentation:next_cdm:add_person_to_cost

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
documentation:next_cdm:add_person_to_cost [2017/03/17 11:29]
gowtham_rao
documentation:next_cdm:add_person_to_cost [2017/07/10 16:43]
clairblacketer
Line 1: Line 1:
 ====== Cost Table Changes (Add Person_id, Dates and normalize) ====== ====== Cost Table Changes (Add Person_id, Dates and normalize) ======
 +===Proposals are now being tracked as github issues=== 
 +[[https://​github.com/​OHDSI/​CommonDataModel/​issues/​81|link to github issue]]
  
 **Proposal Owner:** Gowtham Rao, Chris Knoll, Klaus Bonadt **Proposal Owner:** Gowtham Rao, Chris Knoll, Klaus Bonadt
Line 49: Line 50:
  
  
-**3. Change structure of Cost table from current de-normalized (for cost variables) to normalized (for cost variables)**+**3. Leverage cost_type_concept_id and remove ​cost type columns ​**
   * Proposed structure of new table is below   * Proposed structure of new table is below
-  * The key idea here is that instead of making each cost-type a column (i.e. wide representation),​ lets convert to long representation. +  * The key idea here is that instead of making each cost-type a column (i.e. wide representation),​ lets convert to long representation. We will leverage cost_type_concept_id for this
-  * Introduced new standard ​concepts field:​cost_amount_type_concept_id for the following: cost_amount_type_concept_id to represent total_charge,​ total_cost, total_paid, paid_by_payer,​ paid_by_patient,​ paid_patient_coinsurance,​ paid_patient_deductible,​ paid_by_primary,​ paid_ingredient_cost,​ paid_dispensing_fee,​ payer_plan_period_id,​ amount_allowed. This allows to generalize the cost table and we represent arbitrary number of cost types. We can also represent international and custom use cases.cost_amount_type_concept_id to represent ​total_charge,​ total_cost, total_paid, paid_by_payer,​ paid_by_patient,​ paid_patient_coinsurance,​ paid_patient_deductible,​ paid_by_primary,​ paid_ingredient_cost,​ paid_dispensing_fee,​ payer_plan_period_id,​ amount_allowed. This allows to generalize the cost table and we represent arbitrary number of cost types. We can also represent international and custom use cases. +  * cost_type_concept_id will be used to identify ​standard cost typestotal_charge,​ total_cost, total_paid, paid_by_payer,​ paid_by_patient,​ paid_patient_coinsurance,​ paid_patient_deductible,​ paid_by_primary,​ paid_ingredient_cost,​ paid_dispensing_fee,​ payer_plan_period_id,​ amount_allowed. This allows to generalize the cost table and we represent arbitrary number of cost types. We can also represent international and custom use cases. 
-  * Change ​cost_domain_id ​from string to integer.+  * Should ​cost_domain_id ​be an integer ​or string? Currently it is a string.
  
 ^ Field                        ^ Required ​ | Type        | Description ​                                                                                                                                                                                                                                                | ^ Field                        ^ Required ​ | Type        | Description ​                                                                                                                                                                                                                                                |
Line 62: Line 63:
 | cost_type_concept_id ​        | Yes       | integer ​    | A foreign key identifier to a concept in the CONCEPT table for the provenance or the source of the COST data: Calculated from insurance claim information,​ provider revenue, calculated from cost-to-charge ratio, reported from accounting database, etc.  | | cost_type_concept_id ​        | Yes       | integer ​    | A foreign key identifier to a concept in the CONCEPT table for the provenance or the source of the COST data: Calculated from insurance claim information,​ provider revenue, calculated from cost-to-charge ratio, reported from accounting database, etc.  |
 | currency_concept_id ​         | Yes       | integer ​    | A foreign key identifier to the concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar. ​                                                                                                              | | currency_concept_id ​         | Yes       | integer ​    | A foreign key identifier to the concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar. ​                                                                                                              |
-cost_amount_type_concept_id ​ | Yes       | integer ​    | A foreign key identifier to the concept representing the type of cost.                                                                                                                                                                                      | +total_cost ​                 | Yes       | float       | The actual financial ​cost amount ​                                                                                                                                                                                                                    |
-| cost_amount ​                 | Yes       | float       | The actual financial ​transaction ​amount ​                                                                                                                                                                                                                    |+
 | incurred_date ​                | Yes       | date        | The first date of service of the clinical event as in table capturing the information (e.g. date of visit, date of procedure, date of condition, date of drug etc).                                                                                         | | incurred_date ​                | Yes       | date        | The first date of service of the clinical event as in table capturing the information (e.g. date of visit, date of procedure, date of condition, date of drug etc).                                                                                         |
 | incurred_datetime ​            | No        | datetime ​   |                                                                                                                                                                                                                                                             | | incurred_datetime ​            | No        | datetime ​   |                                                                                                                                                                                                                                                             |
documentation/next_cdm/add_person_to_cost.txt · Last modified: 2017/07/10 16:43 by clairblacketer