...
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. | 5.0: Updates to Catalog Setup have now allowed for this on Documents. | |
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 | |
TS-24 | Vitals must include reference ranges, alerts, and reflex checks | Update Wiki: Medical Record Setup | |
TS-25 | Vitals must be able to be linked at the unit level. | Update Wiki: Episode Type Setup | This is going to be accomplished in a roundabout way - through documents, through record groups, and through episoide requirements. You can have multiple vitals sets. |
...