-
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
Updated natalsupplement-pregna... #87
base: dev
Are you sure you want to change the base?
Conversation
@sbuhovac @rachel0728 both the infant and pregnancy rule are in this pull request for Natal. |
Rachel (@rachel0728) and I did Validation Testing for both Natal Supplement rules (Pregnancy and Infant). Here's our feedback: Natal Supplement - both rules
Natal Supplement Pregnacy
Natal Supplement Infant
|
Updated both rules to include this, was thinking maybe this would exist in the parent rule, but we can visit that later.
We haven't built cancellation or end-dates into any of the rules yet, so I'm no sure what the approach will be yet, we'll have to discuss it.
This will need to be a klamm data validation, and won't be implemented right away but I will note this.
This will be a klamm data validation, Tim is already working on this for us.
I can change this to "The expected delivery date is prior to the benefit month."
This can be a klamm data validation.
Not sure how to build the parent rule at the moment, I'll need to discuss with the devs on how this can function. |
Clarification: Natal Supplement - Infant: Birth Date cannot be in the future (this is being completed by dev in klamm for data validation) |
rule is built to function this way
klamm validation has been updated and a future date cannot be assessed. @sbuhovac @rachel0728 this one now has the updated klamm validation and everything else isnt applicable in the rule in the current state |
Rachel (@rachel0728) and I did another round of validation testing, so here is our further feedback:
For @tekarrawilkinson to review. |
@rachel0728 I've updated the Estimated Delivery Date to include future dates, that's just my error. |
Thank you for fixing both @tekarrawilkinson. Upon retesting, I just realized there is no input for "Multiple Births" for the Natal Supplement - Infant rule. It should function like "Multiple Pregnancy" input in the Pregancy rule and approve $160 amount. |
@sbuhovac @tekarrawilkinson @rachel0728 @Iliana777 Quick question: If we are designing & building the natal supp rules to be contact based (per infant) rather than case based (family unit), I don't believe we would have to account for multiple births. I haven't run any validation tests yet but thought I would ask the question now just in case it helps this discussion. |
I was thinking we could capture this in the parent rule for Natal, but wanted to confirm the amount if there were multiple infants. |
Now I recall that discussion around Natal Supplement for infants being contact/child based (in the future). In that case, we don't need "Multiple Births" input. However, the regs limit the supplement to $160 so we'll need to have some sort of limit on triplets (or more), unless policy changes and allows $80 per child regardless of number. |
@prchristenson @sbuhovac @rachel0728 @Iliana777 After some discussion with devs and policy and reviewing these comments, I've added a Natal Supplement Parent Rule page on the hive https://thehive.apps.silver.devops.gov.bc.ca/business_rules_engine/rules_repository/natal_supplement_parent_rule The parent rule will need to provide a limit to the supplement of $160 for multiples as well as ensuring that the infant and pregnancy rule are not issued concurrently. Besides these items, I think we can move forward with this rule knowing the parent rule will handle these exceptions. |
Okay, in that case, validation testing is passed on our end. @prchristenson and @Iliana777 can proceed with their Validation Testing. |
@tekarrawilkinson @prchristenson |
I've updated the hive page to include these parameters as well. Thanks! |
@tekarrawilkinson @prchristenson @sbuhovac @rachel0728 Ran two tests:
I know we have discussed that this will be mitigated in KLAMM but noting it here for the record. Other concern that I have is the input 'Family unit in pay for month' in the context of these Natal (Pregnancy and Infant) rules as there are multiple dates (benefit month, estimated delivery date, date of birth). I know that the input is the standard input we have used for other rules but the other rules don't have so many dates. Just want to make sure that it is clear to the user which month the family unit is in pay for. |
This will now approve the supplement, and will need to be a klamm validation (added under user story 5572), the rule is now built to allow any delivery date in the future, this is ok for now.
This will need to be discussed as its own rule when it comes to the rolling 3 benefit months as we haven't incorporated this into other rules and I've added a user story under future enhancements (User story 5573).
This is a really good point that I'm should be incorporated into the above 3 benefit month rolling eligibility concept, I've added your comment to the user story I've created. |
@tekarrawilkinson @prchristenson @sbuhovac @rachel0728 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tekarrawilkinson @prchristenson @sbuhovac @rachel0728
Validation tests completed for both pregnancy and infant natal supplement rules. Approving both.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tekarrawilkinson @Iliana777 Validation testing completed for natal supplement - pregnancy and natal supplement - infant. Rules Approved. @sbuhovac - Both of these are ready for isolation testing.
@cevenden and I did isolation testing on both Natal Supplements and here's our feedback. Natal Supplement Pregnancy failed when the date within BenefitMonth input is after the date within the EstimatedDeliveryDate input but both dates are the same month. For example, if BenefitMonth date is 2025-07-28 and EstimatedDeliveryDate is 2025-07-17, the test should pass because it's the same month. Attached is our Isolation Tester file. Isolation Tester doesn't work for Natal Supplement Infant as it gives out an error message. |
@sbuhovac @cevenden @tekarrawilkinson I have updated the application and the isolation tester should now be working for Natal Supplement Infant. Handling of the 'today' restriction in validation hadn't yet been updated for scenario generation, but this should now be fixed in the application. Additionally, I added the specific scenario you gave as an example for the Natal Supplement Pregnancy and it appears to be passing. |
Isolation testing has passed for Natal Supplement Pregnancy. Isolation testing for Natal Supplement Infant fails when Benefit Month is the 14th month after DateOfBirth (example: BenefitMonth is March 2025 and DOB is February 2024). Output should be 'not eligible' but currently it shows eligible. |
@sbuhovac ok! the issue was that when the benefit month and thirteen monthdob addition are exactly the same, it evaluates as eligible under the prior implementation, good catch! this should be corrected now. |
@tekarrawilkinson Review state of the rule doesn't seem to be updated. |
@sbuhovac Review state should be updated now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sbuhovac Review state should be updated now.
Isolation testing for Natal Supplement Infant has passed.
health-supplements_natalsupplementinfant_testing_health-supplements_natalsupplementinfant_testing_natalsupplementinfant_isolation_testing_2025-01-03T17-11-52Z.csv
Adding natalsupplement-pregna....
Review: https://brms-simulator.apps.silver.devops.gov.bc.ca/rule/6670c911ae632fd69b926de0?version=inReview&_=1732725348941