documentation:next_cdm:add_person_to_cost
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| documentation:next_cdm:add_person_to_cost [2017/03/12 20:20] – gowtham_rao | documentation:next_cdm:add_person_to_cost [2017/07/10 16:43] (current) – clairblacketer | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Add Person_id and (financial) Dates to Cost Table ====== | + | ====== |
| + | ===Proposals are now being tracked as github issues=== | ||
| + | [[https:// | ||
| **Proposal Owner:** Gowtham Rao, Chris Knoll, Klaus Bonadt | **Proposal Owner:** Gowtham Rao, Chris Knoll, Klaus Bonadt | ||
| Line 19: | Line 20: | ||
| - | **2. Add billed_datetime, | + | **2. Add incurred_date, |
| - | * Add two new datetime fields in the cost table. billed_datetime and paid_datetime | + | * Add three new datetime fields in the cost table. billed_datetime and paid_datetime |
| - | * This is in-line with the design principle. | + | * Incurred_date or service_date (match event table) - This is in-line with the design principle. |
| * Both fields are optional (Required = No), they are date time fields (Type = DateTime - following OMOP conventions) | * Both fields are optional (Required = No), they are date time fields (Type = DateTime - following OMOP conventions) | ||
| * Costs are associated with a visit_occurrence, | * Costs are associated with a visit_occurrence, | ||
| 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 |
| * 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), | + | * The key idea here is that instead of making each cost-type a column (i.e. wide representation), |
| - | * Introduced new standard | + | * cost_type_concept_id will be used to identify |
| + | * Should cost_domain_id be an integer or string? Currently it is a string. | ||
| - | ^ Field ^ Required | + | ^ Field ^ Required |
| - | | cost_id | + | | cost_id |
| - | | person_id | + | | person_id |
| - | | cost_event_id | + | | cost_event_id |
| - | | cost_domain_id | + | | cost_domain_id |
| - | | cost_type_concept_id | + | | cost_type_concept_id |
| - | | currency_concept_id | + | | currency_concept_id |
| - | | cost_amount_type_concept_id | + | | total_cost |
| - | | cost_amount | + | | incurred_date |
| - | | billed_datetime | + | | incurred_datetime |
| - | | paid_datetime | + | | billed_datetime |
| - | | revenue_code_concept_id | + | | paid_datetime |
| - | | drg_concept_id | + | | revenue_code_concept_id |
| - | | revenue_code_source_value | + | | drg_concept_id |
| - | | drg_source_value | + | | revenue_code_source_value |
| + | | drg_source_value | ||
documentation/next_cdm/add_person_to_cost.1489350045.txt.gz · Last modified: by gowtham_rao
