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

insuranceExpenses field malformed on json export #1425

Open
hchorton opened this issue Mar 8, 2024 · 1 comment
Open

insuranceExpenses field malformed on json export #1425

hchorton opened this issue Mar 8, 2024 · 1 comment
Labels

Comments

@hchorton
Copy link

hchorton commented Mar 8, 2024

What happened?

When generating a patient and exporting via json format, the coverage.planHistory.insuranceExpenses field appears to be malformed. In every instance, it is either represented with an uneccesary amount of decimal places appended to the end, or is coming as scientific notation.

Attached is an example of a patient that was generated with the malformed fields.

Melissia267_Bambi5_Collins926_414cf344-3bae-0b21-9efd-4780b36b0aa5.json

Environment

- OS: Microsoft Windows 11 Pro, Version 10.0.22621 Build 22621
- Java: java version 18.0.1.1

Relevant log output

No response

@hchorton hchorton added the bug label Mar 8, 2024
@hchorton
Copy link
Author

hchorton commented Mar 8, 2024

Digging into this a little further, it looks like it has something to do with the payMonthlyPremium function; when the premium price is 0, and the condition for a private non-ACA plan is met, the premium price is multiplied by the employeeContribution and it returns 0E-53. If it returns this amount and doesn't add anything else this is the amount that saves on the json. So probably less malformed and more of a formatting thing.

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

No branches or pull requests

1 participant