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

Additional Information on Claims Dataset #4

Open
robi86 opened this issue Jan 10, 2020 · 2 comments
Open

Additional Information on Claims Dataset #4

robi86 opened this issue Jan 10, 2020 · 2 comments

Comments

@robi86
Copy link

robi86 commented Jan 10, 2020

For explainability purposes some recent papers have shown that stacking embeddings learned from claims/EHRs of different care settings can be valuable. Intuitively this also makes sense as the distribution and co-occurrence of diagnoses codes is different in the hospital versus the clinic. As such, can you provide additional information on the claims dataset used to learn these embeddings including the following:

  • Were these claims for commercial insurance or from public insurers (e.g., Medicare/Medicaid)?
  • Were these claims from a mix of care settings, inpatient only, or outpatient only?
@pandeyp
Copy link

pandeyp commented Aug 4, 2021

Hi @robi86, can you explain how we can stack/sum claims if a member has multiple claims lines that have multple ICD10 diagnosis and procedure codes in claim lines. I am trying to generate word embedding representation on a member-by-member basis looking at all the claim lines available for a member.

@temiwale88
Copy link

@pandeyp. This is obviously late but might be helpful: Maybe try generating the embeddings (which are real-valued vectors) for all ICD10 diagnoses and procedure codes, i.e., per claim line (or for all claims per member), then summing (sum-pooling), averaging (mean-pooling), or max-pooling over all the vectors / embeddings? Any of these pooling strategies will generate some representation of that patient's service and utilization history.

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

3 participants