Closed aliciabeckett-gov closed 3 years ago
Features we've talked about that have some relationship to this, and should be concretely placed in or out of scope (with light editorializing because this conversation can get abstract quickly):
Here's my thoughts
logged-in patient experience (seems like a definite no) No this is a different epic coming later. It's being designed and user tested now
multiple facilities per org (seems like a probable yes) This would be great to have at the same time. If I can only have one I'd choose multiple orgs, but they really are both needed.
self-service user management (hoping this is still a no) and enrollment (clearly a no IMO) Not any time soon
sharing provider information between facilities (a little bit of an oddball, but maybe worth discussing) Nope, we can get duplicate records, it doesn't really matter.
multiple roles within an organization, to differentiate administrative functions from data entry (seems implied yes, but actually doesn't have to be) This is coming soon in a different epic. There's still user research being done on it.
Sounds good!
So, the obvious things we're going to have to clarify about facilities are
@hmyers-cms and @katiealoisi have a lot of these answers. If you have a chance it would be good to sync with them today.
We're full on integrating this and have broken it out into many tickets so closing this epic.
Although, apparently not quite enough tickets. 😆
Be able to have more than one facility use the application. We had to do some things to get the app out the door, and now that we got there it's time to go back and add support for multiple testing sites so we can expand beyond the first testing site.
We need to have: -Multiple organizations -Patients/People assigned to an organization -Users and their accounts/roles assigned to an organization -Organizations cannot see each other's data