mz-health/OMOP
mz-health
/
OMOP
mirror of https://github.com/OHDSI/CommonDataModel.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update PAYER_PLAN_PERIOD.md

This commit is contained in:
clairblacketer 2018-02-22 15:22:27 -05:00 committed by GitHub
parent 8ac00ca598
commit 91f8d70ddc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/CommonDataModel_Wiki_Files/StandardizedHealthEconomicsDataTables/PAYER_PLAN_PERIOD.md
View File

@ -2,15 +2,14 @@ The PAYER_PLAN_PERIOD table captures details of the period of time that a Person
Field|Required|Type|Description Field|Required|Type|Description
:------------------------------|:--------|:------------|:---------------------------------------------- :------------------------------|:--------|:------------|:----------------------------------------------
|payer_plan_period_id|Yes|integer|A identifier for each unique combination of payer, sponsor, plan, family code and time span.| |payer_plan_period_id|Yes|integer|A identifier for each unique combination of payer, sponsor, plan, family code and time span.|
|person_id|Yes|integer|A foreign key identifier to the Person covered by the payer. The demographic details of that Person are stored in the PERSON table.| |person_id|Yes|integer|A foreign key identifier to the Person covered by the payer. The demographic details of that Person are stored in the PERSON table.|
|payer_plan_period_start_date|Yes|date|The start date of the payer plan period.| |payer_plan_period_start_date|Yes|date|The start date of the payer plan period.|
|payer_plan_period_end_date|Yes|date|The end date of the payer plan period.| |payer_plan_period_end_date|Yes|date|The end date of the payer plan period.|
| payer_concept_id |No|integer|A foreign key that refers to a Standard Payer concept identifiers in the Standardized Vocabularies| |payer_concept_id |No|integer|A foreign key that refers to a Standard Payer concept identifiers in the Standardized Vocabularies|
|payer_source_value|No|varchar(50)|The source code for the payer as it appears in the source data.| |payer_source_value|No|varchar(50)|The source code for the payer as it appears in the source data.|
| payer_source_concept_id |No|integer|A foreign key to a payer concept that refers to the code used in the source.| |payer_source_concept_id |No|integer|A foreign key to a payer concept that refers to the code used in the source.|
| plan_concept_id|No|integer|A foreign key that refers to a Standard plan that represents the health benefit plan in the Standardized Vocabularies| |plan_concept_id|No|integer|A foreign key that refers to a Standard plan that represents the health benefit plan in the Standardized Vocabularies|
|plan_source_value|No|varchar(50)|The source code for the Person's health benefit plan as it appears in the source data.| |plan_source_value|No|varchar(50)|The source code for the Person's health benefit plan as it appears in the source data.|
| plan_source_concept_id |No|integer|A foreign key to a plan concept that refers to the code used in the source.| | plan_source_concept_id |No|integer|A foreign key to a plan concept that refers to the code used in the source.|
| sponsor_concept_id |No|integer|A foreign key that refers to a Standard plan that represents the sponsor in the Standardized Vocabularies| | sponsor_concept_id |No|integer|A foreign key that refers to a Standard plan that represents the sponsor in the Standardized Vocabularies|
@ -23,6 +22,9 @@ Field|Required|Type|Description
### Conventions ### Conventions
* 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), Sponsor (holds the financial risk), Family and Person. Typically, depending on healthcare utilization, a Person may have one or many subsequent Plans during coverage by a single Payer. * 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), Sponsor (holds the financial risk), Family and Person. Typically, depending on healthcare utilization, a Person may have one or many subsequent Plans during coverage by a single Payer.
* **sponsor:** who finances the transaction. **payer:** who administers the transaction. **plan:** the actual contract being administered by the payer and agreed by the sponsor. **stop reason:** reason for termination of the contract * **sponsor:** who finances the transaction.
* **payer:** who administers the transaction.
* **plan:** the actual contract being administered by the payer and agreed by the sponsor.
* **stop reason:** reason for termination of the contract
 * Source values of the Payer, Plan, Sponsor, Family are captured as the respective _source_value. Concept_id's are used to support standardized analysis, similar to other OMOP CDM tables that use _source_concept_id and _concept_id.  * Source values of the Payer, Plan, Sponsor, Family are captured as the respective _source_value. Concept_id's are used to support standardized analysis, similar to other OMOP CDM tables that use _source_concept_id and _concept_id.
* 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 * 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