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

String search criteria for some fields from Payer plan period table #59

Closed
gowthamrao opened this issue Sep 30, 2018 · 1 comment
Closed

Comments

@gowthamrao
Copy link
Member

The CDM and vocabulary workgroup has an ongoing effort to standardize the vocabulary concepts for use with payer plan period table. This is a major effort because of absence of good external vocabulary that may be adopted by the community. We are exploring various candidate options.

Discussions here and here

One known limitation of standardizing concepts, is that the anticipated significant difference in how each administrative unit (e.g. US claims vs Eurpoean vs Korean claims systems) represents the constructs of a payer, plan (benefit design) or sponsor of benefit. While high level concepts (Medical vs dental) maybe standardized as OMOP vocabulary, low level concepts may never be.represented in OMOP vocabulary. Concepts are being vetted by the CDM and Vocabulary workgroup members right now, such as
image

In this issue, I am requesting the addition of 'String search' in Atlas/circe-be to support the fields

  • payer_source_value
  • plan_source_value
  • sponsor_source_value
  • contract_source_value

The UI in Atlas may be like a drop down such as below
image

There is precedence for this type of string search in Atlas - especially for drug_exposure and observation (see below)- because we cannot standardize using OMOP vocabulary concepts information such as LOT# of drug or Stop_reason
image

@chrisknoll
Copy link
Collaborator

This is a CDM V6 feature, which has been defunct. We can re-open this issue if it comes into a 5.x feature, or if it is re-introduced in future versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants