FORMS-279: (UX/UI) Design Facility Information Data
- Miranda Stewart
User Story Description:
As a UX/UI Designer I want to design the Facility Information Data section so that it can be ready for development.
This Story focuses exclusively on the Facility Information data section that was standardized with the Health Authorities. Note: there were no major changes to this section.
In Scope:
Design of the form (wireframes) including the layout and the tooltips and help content
This design can be applied to the form in CHEFS directly
Business Rationale:
Priority: Must Have
Dependencies:
[List potential dependencies with other User Stories or Tasks]
# | Task or User Story | Type of Dependency |
6 | Parent | |
193 | Child | |
|
|
|
|
|
|
Technical Details:
To get the details of the fields for Bed Occupancy, use the spreadsheet below:
View Facility Information tab
Notes regarding Attributes - Updated Aug 23 w/ Bonnie
HCC Spreadsheet shared by Scott Gray
Version 6 of CHEFS Form (updated Aug 28)
Common Hosted Forms (gov.bc.ca)
Still to Explore (as of Aug 26):
Conditionals (disabling fields as user is inputting, switching fields to mandatory/optional, etc.)
Preparer Contact Info: We may be able to pre-populate the Preparer Name field, as the Edit/Audit functionality that CHEFS provides may be enough. But Bonnie would like to see the position and contact info (especially if it’s a new operator/submitter entering the info for the first time).
Attributes needing tool tips:
Owner Type: there is a fairly new type of facility that Interior Health has as of recent. Miranda put in a temporary definition as the tool tip for now but TBC with Paul Champness from IHA for the definition of “Operated & Leased” facilities.
Meet with Health Authority (likely FHA first):
ask whether Health Authority attribute needs to allow for multiple value selection or stick to one value. Only one value in HCC.
If checkbox is selected for Operator = Owner, then the Operator information should be greyed out. By default, the fields for Operator Info should be required but conditionals should be set to disable required input.
explore whether HCC’s “Contact Info (Phone Number)” field could be used to pre-populate owner and/or operator’s phone number fields. HCC just provides the one field for all content.
Acceptance Criteria:
[List the Acceptance Criteria]
# | Description | Notes |
1 | The design of the form is complete and can be developed in CHEFS |
|
2 | The design should show all the fields included in the Facility Info data section of the spreadsheet |
|
3 | The design should show the mandatory and disabled fields |
|
4 | The design should include the tooltips and instruction content |
|
Prototype/Mockups
Provide high fidelity prototype or mockup
Out of Scope:
Validation with external systems
Calculated fields
Contact(s):
Table of Contents