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

Payer_Plan_Period documentation #143

Closed
MelaniePhilofsky opened this issue Jan 5, 2018 · 3 comments
Closed

Payer_Plan_Period documentation #143

MelaniePhilofsky opened this issue Jan 5, 2018 · 3 comments

Comments

@MelaniePhilofsky
Copy link
Collaborator

The description for many fields in the Payer_Plan_Period table are ambigious. Adding an example of what is expected would be helpful.

Currently the description for the family_source_value field: "The source code for the Person's family as it appears in the source data."

A improvement would be: "The source code for the Person's family as it appears in the source data. The source code is usually the first 9 digits of a Member's ID.".

I'm tagging @gowthamrao. He is the author of the v5.3 of this table.

@gowthamrao
Copy link
Member

gowthamrao commented Jan 6, 2018

Thanks - I would be glad to. Could you make a list of the fields that you think should be prioritized, to reduce the ambiguity.

Regarding family-source-value, this is a legacy field and description, that has been in Omop from before v5 (I believe). The field is not usable as is. Plus, I don't think it is a "code", but is a "key value". Codes in my mind, goes into the vocabulary. Plus, the first 9-digits is a US convention, where many times the SSN (9 digit) of the primary subscriber is used as the key-value to indicate a family (i.e. this convention may not be generalizable, especially to international settings).

I proposed an improvement - please see
#107

Thoughts on this proposal?

Thank you

@MelaniePhilofsky
Copy link
Collaborator Author

It would be helpful if there was guidance on the vocabulary, domain, and concept class for the following fields: payer_concept_id, plan_concept_id, sponsor_concept_id, and stop_reason_concept_id. Even better would be a concept set of the allowed values for each field.

@gowthamrao
Copy link
Member

Thanks. I have addressed those here #120

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