Versions Compared
| Version | Old Version 2 | New Version Current |
|---|---|---|
| Changes made by | ||
| Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Feature Story Description:
| Anchor | ||||
|---|---|---|---|---|
|
As a Submitter, I want certain data points/fields to be pre-populated from HCC.
Define the data points can be pre-filled and ensure whatever can be pre-filled should be.
Background Info - HCC/HAMIS
HAMIS receives quarterly submissions from HAs. Team provides monthly reporting. ALR + BC Catalogue LTC licensing data.
On a monthly basis they look at the Open/Close at the facility level. Helen’s team makes adjustments only for the newly opened facilities.
Does not contain the bed numbers on a monthly basis.
HCC does not capture utilization of beds. In terms of bed capacity, HAMIS collects only “open to be used” beds. At a certain date, they want to know how many beds are open and available to be used.
Business Rationale:
Priority: Should Have
Some forms are filled out on a regular basis and some data points will have the same value from one submission to another. Having them pre-filled can simplify the user experience and help with data consistency.
Dependencies:
[List potential dependencies with other User Stories or Tasks]
# | Task or User Story | Type of Dependency |
| ||
|
| |
|
| |
|
|
Technical Details:
Custom feature.
Acceptance Criteria:
[List the Acceptance Criteria]
# | Description | Notes |
1 | The title of the data fields between forms will have to match exactly in order to enable pre-population. | For LTC, some data points will be pre-populated from the DSR, the HCC bed inventory and/or from previous submissions. |
2 |
|
|
3 |
|
|
4 |
|
|
5 |
|
|
Prototype/Mockups
Provide high fidelity prototype or mockup
Out of Scope:
Contact(s):
Table of Contents
| Table of Contents |
|---|