From 088ee4d060357411482b1659ff1fab1de63ff9a5 Mon Sep 17 00:00:00 2001 From: clairblacketer Date: Tue, 2 Oct 2018 12:20:29 -0400 Subject: [PATCH] Added THEMIS issues to Payer_plan_period --- .../StandardizedHealthEconomicsDataTables/PAYER_PLAN_PERIOD.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/CommonDataModel_Wiki_Files/StandardizedHealthEconomicsDataTables/PAYER_PLAN_PERIOD.md b/Documentation/CommonDataModel_Wiki_Files/StandardizedHealthEconomicsDataTables/PAYER_PLAN_PERIOD.md index d501f3d..66a27e7 100644 --- a/Documentation/CommonDataModel_Wiki_Files/StandardizedHealthEconomicsDataTables/PAYER_PLAN_PERIOD.md +++ b/Documentation/CommonDataModel_Wiki_Files/StandardizedHealthEconomicsDataTables/PAYER_PLAN_PERIOD.md @@ -31,4 +31,5 @@ No.|Convention Description | 1 | Different Payers have different designs for their health benefit Plans. The PAYER_PLAN_PERIOD table does not capture all details of the plan design or the relationship between Plans or the cost of healthcare triggering a change from one Plan to another. However, it allows identifying the unique combination of Payer (insurer), Plan (determining healthcare benefits and limits) and Person. Typically, depending on healthcare utilization, a Person may have one or many subsequent Plans during coverage by a single Payer. | | 2 | Typically, family members are covered under the same Plan as the Person. In those cases, the payer_source_value, plan_source_value and family_source_value are identical. | | 3 | The contract_person_id is meant to refer to the owner of the plan, for instance, a parent who owns the plan under which the child is covered. Contract_person_id many times will be equal to person_id. | -| 4 | The fields contract_source_value and contract_concept_id justify the contract relationship.