-
Notifications
You must be signed in to change notification settings - Fork 2
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
Payment Sources #68
Comments
We have some data available to us, but its hard for me to understand if it is enough:
|
TIL: Knox-Keene is shorthand for the "Knox-Keene Healthcare Service Plan Act of 1975."
Given that, I think we mostly expect Type of Service = 1. And in that case, it sounds like we'd have to dig in quite a bit ourselves to get the Plan Code Numbers. The list of California plan codes and insurance plans is quite detailed and definitely won't come from Synthea's default CSV. For realistic data, we probably also want some resource that can give us an idea of which plans work with which hospitals. |
I think the most relevant file is the list of insurance plans Each plan would need to be tagged with the category, code number, and type of coverage. After that, we would be able to pin each Claim to a payment source. Getting a match to real world statistics is far more trouble. As you can see from the list of plans, synthea only has a couple of plans per payer, heavily biased toward ACA, so we would have to also increase the fidelity of plans and providers. |
I've implemented a draft version of this that assigns Type of Coverage based on HMO/PPO/EPO/POS and assigns the plan codes for these payers: def hmo_plan_codes(col): |
[Katlyn] In CA, 54% of births are covered by private insurance and 40% by Medical (page 9 of this). In our data, we see 0% Medical (payer_cat ‘02’) but 40% “other government” (payer cat ‘06’). We also see the payer field missing about 6% of the time in our data. Is it possible to make the payer category distribution more closely align to the statewide data shared above? [Riley] Generally, there is a larger goal to add a program to the synthetic_discharges repository that queries a larger generated dataset to extract sample data that aligns with publicly available distributions (eg hospital volume, DRGs, payer mix). As Becky stated, that is a longer term goal that we do not have a plan for right now. |
June 18 - [Travis]: Synthea natively has no concept of medical which is why we do not see that payer catagory in the data. I'll try to figure out if it can be hard coded in the formatting somehow or if it can be added to the synthea input files in some way |
As a data analyst, I want the synthetic databases to contain information on the source of payment so that I can analyze any differences in treatment based on payment type.
Proposed Subtasks:
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: