Creating online forms requests (WIP)

Overview

A sentence that talks about what an online forms request ~is~.

In Blueprint OMS, there are three places from which users can send online forms requests to patients. 

• Appointments in the scheduler
• The Patient drop-down menu
• The CREATE REQUEST button in the Online forms (what's it called? don't say "tab")

Creating a request in connection with an appointment

Appointments created by Blueprint OMS users

• Create an appointment as you normally would.
• If the event type has one or more associated forms, you will be prompted to send forms upon creating the event.
• If the appointment type has no associated forms, you can still send forms in connection with it, but none will be pre-selected in the menu.
• If online forms have been sent in connection with an appointment in the scheduler, that appointment will have a "view forms" menu option, and the names of the forms will appear in the third column in the panel.

Appointments created by the online booking system

This use case will be invoked when a user at the clinic verifies an incoming booking. It requires that:

• The appointment type has one or more associated forms which:
  
  • Isn't already included in an Incomplete forms request for the patient

  • If it has the Only required once property, it hasn't been completed by the patient yet.

Creating a request from the Patient drop-down menu

• With a patient selected, go to Patient > Send online forms.
• Wait until BPOMS standard online forms come out before adding more screenshots. Include status badges for past forms request in the screenshot.

Creating a request from the online forms panel

• Online forms > Create request, select the forms you'd like to send, supply a first name and last name for the recipient.

• Not associated with a patient, but if the form has the Requires processing property, then the form will ultimately be used to create a new patient file.
• May be attached to an existing patient after receiving it back, but only if the form does not have the Requires processing property.

What the recipient of an email containing an online forms request sees

Example: we have a patient named Alice Jones, whose caregiver is named Brenda Jones, and we're sending a form named "Intake form."

If the request was sent in connection with an existing patient/QuickAdd with no primary alternate contact

If Brenda is not set as Alice's primary alternate contact, Alice will receive an email that looks like this:

(picture - on hold)

If Alice has a date of birth on file, Alice will have to authenticate using her date of birth in order to view and complete the form, which may pre-populate the existing information from her file.

If the request was sent in connection with an existing patient/QuickAdd with a primary alternate contact

If Brenda is set as Alice's primary alternate contact, Brenda will receive an email that looks like this:

(picture - on hold)

If Alice has a date of birth on file, Brenda will have to authenticate using Alice's date of birth in order to complete the form, which may pre-populate the existing information from Alice's file.

If the request was not sent in connection with an existing patient/QuickAdd

Alice or Brenda will receive the email according as whether the Blueprint OMS user who sent the request set the recipient to be Alice or Brenda. The email will be addressed to the recipient, and the same template will be used as is the request was sent in connection with an existing patient/QuickAdd with no primary alternate contact. There will be no date-of-birth authentication, and the and the form will not pre-populate any fields.