outcomesinsights / generalized_data_model

Outcomes Insights' Data Model for Clinical Research
MIT License
16 stars 3 forks source link

Consider dividing the cost table into the cost details table and the collections costs table #98

Closed markdanese closed 7 years ago

markdanese commented 7 years ago

Joining through the contexts table is an elegant way to have a single table. But I think it might be cleaner to have cost tables at the two levels where costs are generally represented. It also makes it more clear that costs can be duplicated (for example at the claim and line levels).

The costs details table would be like the drug and measurement tables and would provide cost details for individual clinical codes records (generally procedures or prescriptions).

The collections costs table would be for summarized (claims) costs and visit costs.

markdanese commented 7 years ago

closing in favor of #104

Reporting all costs at the contexts level seems the most useful at the moment. The use case is not strong for reporting at the clinical codes level. Most costs will come from administrative billing data which reports costs at the line level or claim level. The context record can be used to distinguish these.