-
Notifications
You must be signed in to change notification settings - Fork 669
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
Synthea creates duplicate lab panels for the same date #1552
Comments
From a quick search, I see "Basic metabolic 2000 panel - Serum or Plasma" is used in metabolic_syndrome/kidney_conditions and uti/ed_bundle, and "Basic metabolic panel - Blood" is used in congestive_heart_failure and wellness_encounters, so if you're seeing both at the same time there might be some weird encounter interactions. We had and fixed a bug a while back related to overlapping encounters (#883) so I hope it's not something like that popping up again. Please feel free to take a look at those modules and suggest code changes if we have something wrong. |
@dehall I don't remember how to use the module builder repo that I modified in synthea. Can you remind me? I will try changing the BMPs to Serum and see if the problem goes away. |
The hosted version at https://synthetichealth.github.io/module-builder/ One other thought - can you see what else is included in this patient's record at the same encounter? Depending on which two encounters seem to be jammed together here there may be different ways to fix it |
What happened?
I am working on importing lab data. My destination system rejects it if it is a duplicate panel.
I have a feeling this is really a bug in the module itself, not in Synthea.
I created a Synthea Patient (very large... > 50MB, not attached). I used
jq
to analyze the data.time_analysis.csv
Rows 3-6 look like this:
The problem is that there are two BMPs taking place at the same time. The second BMP is in Blood. Labcorp and Quest both say it's a SERUM specimen, not a whole blood specimen. I think that's probably the root of the problem.
Let me know if you agree; and if so, I can try to modify the module and see if that fixes the problem.
Environment
Relevant log output
The text was updated successfully, but these errors were encountered: