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

Create 2022-01-14-mobile-schedule-appointments-discovery.md #35452

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kpethtel
Copy link
Contributor

Copy link
Contributor Author

@kpethtel kpethtel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have the ability to approve this PR, but my one thought is that Andrew's recent work probably makes this doc irrelevant. It looks like he did a lot of the same investigation but started from a place of greater understanding and spent more time on it (this was all done in a day). At the time I wrote this, I didn't realize that direct scheduling and appointment requests were intermingled into a single flow, and I didn't understand the eligibility check process. Since then, we've done a lot of appointment request work, product planning, and also had multiple talks with the vaos team and our collective understanding of how this works and what we want has evolved. Looking at this doc, it looks like I was scheduling for major VA facilities, which seems to result in fewer eligibility checks. I don't even see the word "eligibility" in this doc. I think that may be a fundamental flaw in how I approached this investigation. It may be better to have Andrew review this doc and fold anything of value into his own work.

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

Successfully merging this pull request may close these issues.

None yet

1 participant