Cathy’s spreadsheet format for tracking of initially stated goals for this project. This is fancy BA stuff, everyone else can ignore it unless they are into really really really nerdy PMI business analyst things.
Requirements (Pre-Planning)
Formal requirements matrix and links to the Confluence tickets. For clarity, the Treatment Sheet requirements will have the prefix of TS.
Requirement ID | Formal Requirement | Planned Work Association Link (Confluence) | Comments |
|---|---|---|---|
TS-1 | Must eliminate double entry of patient data between systems. | ||
TS-2 | Must allow for direct entry into VetView (no API required for initial entry.) | ||
TS-3 | Must log individual tasks as well as current assigned tasks. | ||
TS-4 | Must allow for bulk changes of events. | ||
TS-5 | Must be able to double click to open things up in a pop up box on all pages (no in-line editing boxes.) | ||
TS-6 | Any action performed in one screen must appear in all other screens. | This is similar to TS-1 but applies to within VetView, whereas TS-1 is about eliminating double entry into a separate treatment sheet system. | |
TS-7 | Must be able to stop and start treatment plans. | ||
TS-8 | Must display only open episodes on treatment sheet tabs. | Closed or discharged episodes will display in a History tab instead. | |
TS-9 | Must break up treatment sheets into pre-defined categories. | ||
TS-10 | Must show 16 hours of “work day” at a time. | ||
TS-11 | Must allow for transition from day to day instantly. | For tablets, could we incorporate a swipe for this? | |
TS-12 | Must be WCAG 2.2 AA compliant - this includes having a non-color visual indicator for every color indicator, meaningful sequence, and keyboard navigation in addition to full touch navigation. | We may not be able to do screen reader hooks for AAA but we can get to AA standards as long as we make sure it’s keyboard navigable | |
TS-13 | Tasks must support frequency inputs. | ||
TS-14 | Tasks must be repeatable. | ||
TS-15 | Must allow for basic pre-defined templates. | ||
TS-15 | Must allow for ala carte additions to the templates. | ||
TS-17 | Medication tasks must tie into MARS (part of no double entry in TS-6.) | ||
TS-18 | Must be able to print treatment sheets onto paper for physical medical records. | ||
TS-19 | Must group tasks and data entry by hours. | ||
TS-20 | Some tasks must have individual due dates assigned. | ||
TS-21 | All tasks must have at least one user assigned. | Users with supervisors (e.g. students) can have the chain fed up for a second level of assignment. | |
TS-22 | Tasks assigned to one user must be able to be transferred to another user during a shift change. | ||
TS-23 | Must include API commands for external interfaces to send their own tasks. | We’ll place nice with them - but it’ll be up to clients to use our APIs to write interfaces to competitors, or those competitors themselves, unless we have an MOU |
Workflows and Business Processes
Identified workflows that will be impacted or even created by this project. This will be used to assist with Jira ticket testing later on.
Workflow ID | Requirement ID Association | Workflow Description | Comments |
|---|---|---|---|
Jira Links (Active Development and Testing)
Jira ticket table for active development. This is for keeping track of the status of the tickets and where they are in testing.
Parent tickets are linked at the top.
Jira ticket ID | Requirement ID Association | Jira Ticket Status (Imported as Jira link) | Priority |
|---|---|---|---|
Out of Scope
Requirements identified but considered out of scope for this project and tabled for now. This can include requirements requested by clients that were not deemed urgent enough to include in the project for now.
Requirement | Description | Planned Version |
|---|---|---|