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

Allow initial call date to be after the appointment date #3138

Open
colinxfleming opened this issue Jan 23, 2024 · 2 comments · May be fixed by #3264
Open

Allow initial call date to be after the appointment date #3138

colinxfleming opened this issue Jan 23, 2024 · 2 comments · May be fixed by #3264

Comments

@colinxfleming
Copy link
Member

colinxfleming commented Jan 23, 2024

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

  • What are we trying to do?
    Some funds cover patients that reach out after their abortion care. For these funds we'd want to allow initial call date to be after the abortion date.

  • What feature or behavior is this required for?
    Accurate information tracking

  • How could we solve this issue? (Not knowing is okay!)
    I think we have one of two options here:
    ** Loosen the validation so that we no longer check for abortion date > initial call date OR
    ** Write a config that allows the above on a fund-to-fund basis.
    I don't think I have an opinion on which is better, but the former is definitely easier. Either way, this involves wrenching around in the Patient object's validations and then adjusting any tests necessary.

  • Anything else?
    (By request of a fund)

@colinxfleming colinxfleming added this to the Hacknights! milestone Jan 23, 2024
@colinxfleming colinxfleming changed the title Allow initial call date to be after the appointment date? Allow initial call date to be after the appointment date Apr 3, 2024
@colinxfleming
Copy link
Member Author

I'm less worried about data integrity issues here than I was when we put in the constraint originally. Let's do the first one (taking the constraint out entirely) and not worry about the config. Should be somewhere in the model.

@colinxfleming
Copy link
Member Author

(bumping to note that another fund asked for this today)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment