Working with online forms

• The request is sent either to a patient, a QuickAdd, a primary alternate contact of a patient or QuickAdd, or to someone who does not yet have a file in the system. In the request's row in the Online forms pane, the icon to the left of the recipient's name indicates whether the request is linked to a patient file, a QuickAdd file, or no file. If the request was sent to a patient or QuickAdd's primary alternate contact, the Recipient column will display the name and relationship of the alternate contact after the patient or QuickAdd's name.
  • If the request is initially linked to a patient or QuickAdd file at the time of sending, an entry will appear in the journal to document the request. The status badge will update itself.
    
• The request is sent either in connection with an appointment or not. In the request's row in the Online forms pane, the calendar icon in the right-hand side of the column will indicate that the request was sent in connection with an appointment. The icon is grey if the linked appointment in the past, and colored if the linked appointment is in the future.
• The request has an expiration date. For a user-initiated forms request, the expiration date is set at the time of sending. By default, the expiration date is determined by the expiration period set at Setup > Online forms > Settings. If the request is linked to an event, the expiration period starts on the date of the event; if the request is not linked to an event, the expiration period starts on the date of sending.
• The request is sent either to the recipient's email address or to a clinic tablet.

• If the request was originally sent via email, it can be resent to the same email address or to a different one. If the request contained multiple forms, the user may choose to resend only a subset of those forms. The user will have a chance to write a message in the resending email to explain the resending.
• The request can be cancelled. Cancelled requests disappear from the Online forms pane. If the cancelled request was linked to a patient or QuickAdd, their journal entry for the online forms request will update to show the Cancelled badge.
  
• The incomplete request can be sent to a clinic tablet, to be completed at the clinic.

If the request is linked to a patient or QuickAdd, the journal entry documenting the request will reflect the current status of the request.

• The request can be resent, possibly to a new email address. If the request contained multiple forms, the user may choose to resend only a subset of those forms. The user will have a chance to write a message in the resending email to explain the resending.
• In most cases, the request can be cancelled.
  • If a request has at least one form that was individually processed and then not archived, then the request cannot be cancelled.
• The forms on the request can be individually viewed. The forms on the request that require processing can be individually processed. The forms on the request that either do not require processing or have already been processed can be individually archived.
• If no forms on the request require processing, the request will appear in the Completed status. A Completed request be archived all at once (i.e., in one step—if there are multiple forms on the request, then archiving the request will archive the forms as separate documents).
  • If a request has no forms that require processing, then:
    • The field data from the forms cannot be used to create a new patient file; if the request is not already associated with a patient, it can be archived to any patient's file.
      • To work around the scenario where a form that does require processing was mistakenly not marked as such, there is the option to create a new QuickAdd when choosing the patient to match the form to. When using this option, it is best to view the form and then archive using the Archive button so the form can be in view while the QuickAdd is being created.
    • If the request is already associated with a patient or QuickAdd, it can be archived to that patient or QuickAdd's Documents tab.
      • Any forms on the request with the Auto-archive property will automatically get archived to the patient's file once received; they will not appear in the Online forms pane.
  • If the request is linked to a patient or QuickAdd while in the Completed status, the request's journal entry will show the Completed status badge.
    
• If one or more forms on the request require processing, the request will appear in the Submitted status. A Submitted request can be processed all at once, and archived all at once immediately after.
  • If an incoming form requires processing, then:
    • If the request is not already associated with a patient or QuickAdd, the user can either link the request to an existing patient or QuickAdd file or use the request's field data to create a new patient.
    • If the request is already associated with a patient, the the form's fields data can replace or supplement the patient's existing data.
    • If the request is associated with a QuickAdd, the form's field data can replace or supplement the QuickAdd's existing data and, under the suitable settings, convert the QuickAdd to a patient.
  • If the request is linked to a patient or QuickAdd while in the Submitted status, the request's journal entry will show the Submitted status badge.
    

• An online forms request can be cancelled only if it does not contain a form that has been processed but not yet archived.
• Cancelled requests disappear from the Online forms pane.
• If an online forms request that is linked to a patient or QuickAdd is cancelled, its journal entry will reflect that it was cancelled.
  

• Once forms are archived, they disappear from the Online forms pane.
• Online forms are archived to the Documents tab as flat, uneditable documents, signified by the red PDF icon.
  
• If the form had the Display in audiology property, displays in audiology alongside the patient's audiological assessments and audiology-related journal entries.
  
• The journal entry for the forms request will show that the request is in Archived status.
  

If an appointment is booked through the Blueprint OMS online booking system for someone with an existing patient file, the online forms request will send to the contact's email address after the contact (either the patient or the patient's primary alternate contact) verifies the booking via email. In this special case, there is no need for a Blueprint OMS user to verify the incoming booking in order for the online forms request to send.

The following are the criteria used to match new bookings to existing patients:

• The first and last name entered in the online booking portal must match those on file; and
• The phone number or email address entered in the online booking portal must match that on file.

The online forms request will include the following forms:

• The forms associated with the appointment type, except:
  • Any forms that are already included in an incomplete forms request for the patient; and
  • Any forms with the Only required once property that the patient has already submitted.

Once these forms are submitted, Blueprint OMS users can handle them exactly the same way as they would Blueprint OMS-user-initiated online forms requests. 

When someone on the internet arrives at a form that is available online via its URL or iFrame, that person will be prompted to enter a first and last name to start a new instance of the form.

This action creates a new row in the Online forms pane, with the entered name as the recipient and Blueprint Online as the sender. The forms request will appear in Viewed status until the form is submitted. 

If the submitted form has the Processing required property, its status will update accordingly. In this case, the Blueprint OMS user can use the form's field data to update an existing patient file or to create a new patient file.

If the submitted form does not have the Processing required property, its status will update accordingly. In this case, the Blueprint OMS user can archive the form to an existing patient's file.