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

Facility Self Checkin via Link #154

Closed
18 of 19 tasks
blakenan-bellese opened this issue May 15, 2020 · 4 comments · Fixed by #167
Closed
18 of 19 tasks

Facility Self Checkin via Link #154

blakenan-bellese opened this issue May 15, 2020 · 4 comments · Fixed by #167
Assignees

Comments

@blakenan-bellese
Copy link
Contributor

blakenan-bellese commented May 15, 2020

User Story

As a Facility User
I'd like to respond to checkin questions directly
So that I can provide timely info to the city when most convenient to me

Acceptance Criteria

  • Facilities receive emails which will automatically log them into HealthCare RollCall UI - See New user roles to support facility self check in - facility #158 for details about the new facility role.
  • Emails will contain a link, which includes an embedded token.
  • Link leverages embedded token which automatically logs in as facility user for that facility
  • Embedded tokens are specific to the Date sent and the Facility associated with the token.
  • Email is sent to each contact of each facility. If a contact is associated with more than one facility, they will receive multiple emails with different tokens.
  • Email is sent to each contact of each facility. If a facility is associated with more than one contact, each contact will receive the same token.
  • Emails are generated by the Outreach Coordinator - Update user role to support facility self check-in - outreach coordinator (existing user role) #157, View Activity Summary #155
  • Link from email allows facility user to complete a check-in with questions associated with their facility type
  • Access is limited to JUST the check-in questionnaire
  • User is logged in via a new role specific to facility user - New user roles to support facility self check in - facility #158
  • Once check in is submitted user is logged out and link is invalidated.
  • Link is good for 24 hours from send
  • Email automatically logs facility role in. The facility role will not need to enter user/pass to log in. They will click the link and see the Facility check-in page appropriate for them only.
  • Facility should be able to view their responses before submitting
  • Facility should be able to revise only their own contact info (revise phone number and email)
  • Facility cannot view/edit other contacts
  • Facility should be able to edit their responses before their session ends
  • Session should have a limited timeframe (2-4 hours)
  • Facility Check-In page should show the Facility Name where the userid is now shown in UI
  • [ ]

Notes

Thinking that we may want to notify other contacts when checkin is complete and possibly invalidate their links too. Not sure how many facilities have multiple valid email contacts.

In future show history of many checkins for a factility.

@blakenan-bellese blakenan-bellese added this to the Self Checkin v1 milestone May 15, 2020
@msmith125 msmith125 changed the title Self Chekcin via Link Self Checkin via Link May 17, 2020
@msmith125 msmith125 changed the title Self Checkin via Link Facility Self Checkin via Link May 17, 2020
@stoopidJSON stoopidJSON self-assigned this Jun 4, 2020
stoopidJSON added a commit that referenced this issue Jun 4, 2020
This will allow contacts to check-in facilities based on a token sent by
Bmore-Responsive. This allows for check-in without a login/password by authorized
contacts.
resolves #154
@msmith125
Copy link

Performed some quick testing with the Simpson data. Was able to get email sent, perform a check-in, refresh and perform another check-in and validate that the data was written to the entity table. Followed these steps.
1.) update local env to Bmore PR 181 and HCRollcall PR 167
2.) updated .env to include-
SMTP_HOST=smtp.gmail.com
SMTP_PORT=587
SMTP_USER=[email protected]
SMTP_PASSWORD=nL7y5%o1LOWEKAH
TEST_EMAIL=[email protected]
3.) updated Leftorium to be an "Assisted Living Facility"
4.) added a New Contact to the Leftorium with my email via UI.
You cannot give a title when you add a new contact so I unlinked and then relinked this contact with my email with title "Primary Contact"
5.) Verified entity and contact were linked with RelationshipTitle "Primary Contact"
6.) using swagger doc, tried to send email using "Try it out" with updated Parms for
{
"entityIds": [
"05533f95-b440-4f9d-876d-653636dce0c8"
],
"contactIds": [
"05533f95-b440-4f9d-876d-653636dce0c8"
],
"relationshipTitle": [
"Primary Contact"
]
}
7.) I could not get it to work when using entityids or contactids. Tried all combinations. I only was able to send email when using just:
{

"relationshipTitle": [
"Primary Contact"
]
}
8.) Received the email and was able to perform a check-in.
9.) Refreshed and saw previous check-in was completed and performed another check-in.
10.) Queried Entities table and verified two check-ins were completed.
11.) tried to log into front-end as homer simpson but it seems that i am still a facility and cannot see contact/etc (Chrome). Cleared cache, logged in as homer and verified the check-ins.

It seems to be working with some minor issues. More detailed testing is definitely needed. Just wanted to share what I was able to complete. I can test more this weekend if needed. Thanks.

@stoopidJSON
Copy link
Member

I added the contact and entity id stuff early on but have pushed that functionality back to a future release. I've updated swagger to reflect this.

@msmith125
Copy link

Jason,

This looks really good. I tested and confirmed that:

  1. The same contact can have multiple entities and will receive an email for each one
  2. The same entity can have multiple contacts and emails are sent based on relationshipType
  3. Emails can be sent based on a single relationshipType or to all if no parms are sent
  4. Check-ins are stored properly in Entities.checkIn and accumulate correctly (created up to 6 and they are were stored in Entities.checkin correctly)
  5. Previous check-ins are shown in the UI and can be reviewed and look accurate
  6. Previous check-ins are shown when you click on the link in the email
  7. The same email address can be used for multiple contacts and emails are sent correctly
  8. An admin of the system can perform check-ins and can view check-ins done via email link
  9. When you click on check-in link via the email, you can see previous check-ins done by an admin via the UI

The only thing that I found to be confusing is that after a check-in is completed via the email link, no success message is displayed, it just appears to log the user out. I think a success message or success email may be helpful - #169

Overall, my opinion is that this looks great. I can validate that the check-in link expires after 24 hours tomorrow morning. Please let me know if there is anything else you would like for me to test related to this.

Thanks!
Marie

@stoopidJSON
Copy link
Member

That's a good idea! I'll see if I can add that real quick.

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 a pull request may close this issue.

3 participants