Versions Compared
| Version | Old Version 11 | New Version 12 |
|---|---|---|
| Changes made by | ||
| Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
User Story Description:
| Anchor | ||||
|---|---|---|---|---|
|
As a UX/UI Designer I want to design the Bed Occupancy Data section so that it can be ready for development.
This Story focuses exclusively on the Bed Occupancy data section that was standardized with the Health Authorities.
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 | |||||||||
231 |
| Child | ||||||||
233 | Parent | |||||||||
|
|
Technical Details:
To get the details of the fields for Bed Occupancy, use the spreadsheet below:
Bed & Occupancy Spreadsheet - Revised Aug 8
| View file | ||
|---|---|---|
|
*May have to breakdown into separate forms for reviewers vs. operator submitter.
Will have to review the layout, tool tips and description with HAs.
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 Bed Occupancy data section of the spreadsheet |
|
3 | The design should show the mandatory and disabled fields | Conditionals
|
4 | The design should include the tooltips and instruction content |
|
5 |
|
|
Prototype/Mockups
Provide high fidelity prototype or mockup
[insert CHEFS link here]
Out of Scope:
Validation with external systemsCreation of the fields in CHEFS
Calculated fields
Mapping of the fields in Confluence: Field Mapping
Contact(s):
Table of Contents
| Table of Contents | ||||
|---|---|---|---|---|
|