Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to determine the correct payer_plan_period.plan_concept_id to map to based on information in the source #157

Closed
burrowse opened this issue Apr 19, 2024 · 1 comment

Comments

@burrowse
Copy link

How to determine the correct payer_plan_period.plan_concept_id to map to based on information in the source

CDM or THEMIS convention?

Themis

Table or Field level?

Field

Is this a general convention?

No

Summary of issues

  • There are outstanding questions on the forum on how to populate plan_concept_id.
  • For example, a forum post asks the question if the following logic is accurate:
Plan Proposed Mapping
CDHP or HDHP concept_id= 267 Catastrophic Health Plan with <60% actuarial plan value
Basic/major medical concept_id = 270 Medical only plan
Comprehensive concept_id= 268 Broad Benefit (Medical, Drug, Dental, Vision plan
  • In the same post, another user has an unanswered question about differentiating medicare vs non medicare plans

Summary of answer

  • Based on findings, there doesn't appear to be general guidance on how these should be mapped for the plan_concept_id

Related links

Other comments/notes

  • This topic needs more discussion to provide guidance to the community.
@burrowse burrowse converted this from a draft issue Apr 19, 2024
@burrowse burrowse moved this from Hunters - In Progress to Cancelled/Needs more work in OMOP CDM & THEMIS Conventions Apr 19, 2024
@MelaniePhilofsky
Copy link
Collaborator

Archiving this issue. Please reopen this issue if there are still questions.

@github-project-automation github-project-automation bot moved this from Cancelled/Needs more work to Done in OMOP CDM & THEMIS Conventions Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants