Articles in this section

See more

Form Development Standards

  • Updated

Settings and Other
Font Formats
Form Elements
Auto-populations
     Client Print Variables
     POS/Clinician Print Variables

Settings and Other

Form Category & Folder Placement

Forms must be categorized and placed in the respectively location based on the definitions in Form Development Guide.

Name of the Form

  • Once Placement and Name complete, note this information in the Description of the JIRA ticket for QA tester to be able to quickly get to the form in Test Env. 
  • Name of forms should include the form Category and exclude the word form at the end of the title
    (i.e. Vancouver Outreach Referral)

Modify the JIRA to reflect the work being done during development

  • Standardize JIRA naming convention as well (New Form - , Update Form -, Remove Form -) 
  • Attach the pdf/doc of the form requested to be built
  • Embed link to test run in TestRail under the testing subtask's description

Testing

For Simple Forms, copy over all test cases found under the Form Checklist Templates\Simple Form into the CR's test folder. Reminder to update the first step of the copied over Form Standards test case, to replace <Form Name> with the actual form name.

For Complex Forms, the Simple Form template can be used as guidance, however ultimately test cases will need to be created with respective specifications for design.

Font Formats

Font box

  • Height: 21
  • Width: Adjust based on needs unique to each form

Font Styles

  • Calibri or Tahoma Regular Font Size 10 - Please do not use other fonts, as they may cause issues for our users. 
  • Use General Standards every time.

Exceptions for sizing and dimensions: 

  • Headers
  • Fine Print/ Disclaimers
  • Information segments

Form Elements

Alignment, Sizing and Position Of Fields

  • General standard that all fields should be aligned and sizes of fields that are similar should be the same.

Tab Order 

This property allows users to use the tab key to cycle through all editable fields, allowing for fast entry without mouse usage.

  • Tab order should be set for all forms. 
  • Tab Stop property must always be set to true
  • Exception: For Office Use Only section or read-only fields

For tips on how to set the tab order, see the Tab Order subsection of the Timing Saving Shortcuts section of the Form Development Guide

Save/Print/Close buttons

  • If single-paged form, remove [Print This Page] button since [Print] does the same thing
  • If multi-paged form, have buttons on each page
  • Order of buttons match our standard: [Print] [Print This Page] [Print, Save, Close] [Save & Close]
  • Functionality of all buttons related to saving/closing/printing are working as expected
  • Exceptions:
    • If information/ reference page requested, analyst must always confirm with requestor if it should be printed every time or never printed.
    • Set Page Properties accordingly:
      • Print all the time
      • Turn off print of that particular page

Creating Boxes and Lines using Shapes

  • Should always use shape object to create boxes into lines with width or height = 1 depending on if you want to create a horizontal or vertical line.

Radio Button

  • To be used only when users are allowed to only select one option, it must be grouped with the relevant title.

Checkboxes

  • To used when users can select more than one option 

Free text Fields

  • To be used when users only require 1 line of text.

Multi Line Text Fields

  • To be used when users need to write more than 1 line of text. 
  • Optional functionality: Can turn on scroll bar functionality so users can scroll down to see all text in this field.
  • Only caveat is that on print it will push text to next page if there isn't enough room on the first page.

Date Field

  • Should always have Calendar Dropdown
  • Today's Date should auto populate in relevant fields.

Slice Image

  • To be used when an image needs to be inserted onto a Form with the ability to select areas of diagnosis

Signature Box

  • Use the RichText Object to insert a box with the print variable to auto populate the logged on clinician's digital signature with resize macro functionality.  Click here to go to instructions article. 

Macro Print Variables for Results

  • To be used to pull in result dates and values.

Auto-populations

Client Print Variables

Read-Only Patient Demographics

  • First names
  • Last Name
  • PARIS ID
  • PHN
  • DOB
  • Age
  • Address

If any fields above need to changed. It should be corrected in the patient record level via Client Registration/PARIS.

Exceptions:

  • Gender Standards: 
    Auto-populate the Field with that is provided in Client Medical Record with the ability to edit this field. If the original design has radio buttons and/or free text field for other, replace with the single auto-populated text field.
  • Client Phone Standards:
    If only one field is provide for phone number, the field should use the auto populate phone number by hierarchy macro print variable with the ability to edit.
  • Email Standards: 
    To auto populate with client's email if they have one in their medical record with the ability to edit.

POS/Clinician Print Variables

Read-Only POS/Clinician Information

  • POS Name
  • POS Address
  • POS Phone
  • POS Fax

POS information: In theory a user should not be filling in a form for a clinic they are not logged into. Again, if any POS info needs to be changed, it should be fixed in Organization & Places and not corrected in the form.

Exceptions 

  • Clinician Name
  • Clinician MSP 
  • Clinician Specialty

These fields should auto populate with logged on user information with ability to edit.