CommonDataModel
CommonDataModel copied to clipboard
OHDSI
payer_plan_period.plan_concept_id CDM Text Improvement
payer_plan_period.plan_concept_id Text Improvement
CDM or THEMIS convention?
CDM
Table or Field level?
Field
Is this a general convention?
No
Summary of issues
- A minor improvement to include the github link for how to contact the vocabulary team for persons who are unfamiliar could be helpful.
Summary of answer
| VERSION | ETL Convention |
|---|---|
| CURRENT | Map the Plan directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same health benefit Plan though the name of the Plan is not necessary. Accepted Concepts. |
| SUGGESTED | Map the Plan directly to a standard CONCEPT_ID. If one does not exist visit the Custom Concepts page for more information. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same health benefit Plan though the name of the Plan is not necessary. Accepted Concepts. |
Related links
- https://ohdsi.github.io/CommonDataModel/cdm53.html#payer_plan_period
@clairblacketer #672 #671 #666 are all related to a minor improvement in the CDM Documentation but I kept them separate based on our current workflow. I wonder if a blanket page/reference/link out to the vocabulary team for "what to do when the standard concept field is not from a controlled vocabulary but the vocabulary does not have a match for your data" would be helpful.
@clairblacketer #672 #671 #666 are all related to a minor improvement in the CDM Documentation but I kept them separate based on our current workflow. I wonder if a blanket page/reference/link out to the vocabulary team for "what to do when the standard concept field is not from a controlled vocabulary but the vocabulary does not have a match for your data" would be helpful.
Based on the conversation in our check in today, I updated the issues to reference the Custom Concepts page in the CDM documentation.
PLEASE COPY THIS TEMPLATE INTO ASSIGNED ISSUE Note: if no information available, put in 'NA'.
Issue # and location
CDM
Format as follows: CDM issue #665
Issue summary
A minor improvement to include the github link for how to contact the vocabulary team for persons who are unfamiliar could be helpful.
VERSION ETL Convention CURRENT Map the Plan directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same health benefit Plan though the name of the Plan is not necessary. Accepted Concepts.
Convention type
Field
CDM table
Payer Plan Period
CDM field
Plan_concept_id
Links to issue discussion
Links to location of discussion on forums, CDM GitHub, Themis GitHub, etc.
Format as follows: [CDM Documentation] (https://ohdsi.github.io/CommonDataModel/cdm53.html#payer_plan_period)
Provenance of data
Claims data which contains payer information
The ratified convention
VERSION ETL Convention
SUGGESTED Map the Plan directly to a standard CONCEPT_ID. If one does not exist visit the Custom Concepts page for more information. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same health benefit Plan though the name of the Plan is not necessary. Accepted Concepts.
Date of ratification/published
April 23, 2024
Downstream implications
No
Link to DQD check
No
Format as follows:
Related conventions/further information
#Tags #payerplanperiod #payer #payerplan #payerplanconceptid
Thanks @burrowse . What is weird is that we say there is no "globally controlled" vocabulary but I am not really sure what that means since there is a vocab with the vocabulary_id = 'Plan'. I may alter the wording a bit to say something like: We have a vocabulary called "Plan" but it is not exhaustive. If you need a new concept, consider creating either a custom concept or suggesting new concepts to the vocabulary team
