,idx,requirement,label,conflict
0,54,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",No,No
1,25,The system shall store which column the user sorted by when the user exits or changes patients and sorts by that column again when the Patient Selection/Notifications screen is next displayed.,No,No
2,15,The system shall only auto-select(highlights in blue and places that entry in the field) a patient name if the user types enough characters to uniquely identify a name in the list.,No,No
3,2,The system shall allow medication orders to be placed and filled from local stocks of medications while providing auditing of most medication orders within the medication profile.,Yes,Yes(1)
4,8,The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Yes,Yes(7)
5,16,The system shall display a box listing possible matches if CPRS finds more than one patient with the same last name and same last four digits of the social security numbers.,Yes,Yes(18)
6,30,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Yes,Yes(31)
7,26,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Yes,Yes(27)
8,11,"The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",No,No
9,34,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,No,No
10,7,The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Yes,Yes(8)
11,13,"The system shall require service connection, provider name, location, date, diagnosis, procedure, and visit information to be entered in the enounter form to receive workload credit.",No,No
12,38,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",No,No
13,58,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,No,No
14,4,The system shall allow physician offices to only use social security numbers to identify patients.,Yes,Yes(3)
15,31,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Yes,Yes(30)
16,21,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Yes,Yes(22)
17,43,The system shall allow complete order sets to be predefined and personalized.,No,No
18,51,The system shall support audit capability.,No,No
19,41,The system shall improve efficiency of entering orders.,Yes,Yes(42)
20,14,"The system shall require a unique match in the Medication, Dosage, Route, and Schedule fields for inpatient medications before CPRS will auto-select an item from the list. The system shall require the Medication and Schedule fields to be an item from the list for inpatient medications, but the Dosage and Route can be a free-text entry (the route must be in the MEDICATION ROUTES file #51.2).",No,No
21,33,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,No,No
22,24,"The system shall retain notifications for a predetermined amount of time (more than 30 days), after which they may be sent to another destination, such as your MailMan surrogate or your supervisor.",Yes,Yes(23)
23,47,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,No,No
24,42,The system shall improve efficiency of entering orders by atleast 20 percent.,Yes,Yes(41)
25,18,The system shall display a message of possible matches if more than one match is found when a user partially enters a patient's name and last four digits of a social security number.,Yes,Yes(16)
26,32,The system shall require an OEER List to be defined to contain the selected patients in order to grant restricted access to the CPRS GUI.,No,No
27,37,"The system shall sort notifications based on column heading: Alert Date/Time (date/time the alert was triggered, newest to oldest or oldest to newest).",No,No
28,36,"The system shall sort notifications based on column heading: Urgency (valued HIGH, Moderate, or low as indicated by the CPRS parameter ORB URGENCY. TIU alerts are given a Moderate urgency value. Other alerts without a parameter value are given an urgency of low).",No,No
29,57,The system shall enforce these access levels when problems are entered via the encounter form.,No,No
30,9,The system's pilot program shall use a smart card to digitally sign medication orders.,Yes,Yes(10)
31,20,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Yes,Yes(19)
32,28,"The system shall check ICD and CPT code validity as of a specified date when codes are entered, when a new code set is implemented, and whenever CACs or IRM personnel choose to run the option.",Yes,Yes(29)
33,5,The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,No,No
34,35,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",No,No
35,1,The system shall allow medication orders to be placed and filled from local stocks of medications while providing full auditing of all medication orders within the medication profile.,Yes,Yes(2)
36,3,The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,Yes,Yes(4)
37,50,The system shall support role-based access for security controls.,No,No
38,6,The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,No,No
39,23,"The system shall retain notifications for a predetermined amount of time (up to 30 days), after which they may be sent to another destination, such as your MailMan surrogate or your supervisor.",Yes,Yes(24)
40,44,The system shall allow order checking.,No,No
41,12,"The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",No,No
42,17,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,No,No
43,19,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Yes,Yes(20)
44,27,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Yes,Yes(26)
45,39,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,No,No
46,22,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Yes,Yes(21)
47,10,The system's pilot program shall require a handwritten signature for medication orders.,Yes,Yes(9)
48,40,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,No,No
49,29,"The system shall only check ICD code validity as of a specified date when codes are entered, when a new code set is implemented, and whenever CACs or IRM personnel choose to run the option.",Yes,Yes(28)
50,69,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Yes,Yes(68)
51,60,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Yes,Yes(59)
52,84,The system shall display a message that a patient has data from the legacy system used before the site was consolidated that is not being displayed which a user may want to access.,No,No
53,103,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,No,No
54,92,The system will abort when the user tries to login if tabs are not assigned to the user in their NEW PERSON file or if the RESTRICT PATIENT SELECTION prompt does not contain a Yes or No.,No,No
55,100,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,No,No
56,56,The system shall require the entry of an access code to gain access to the system.,Yes,Yes(56)
57,45,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Yes,Yes(46)
58,62,The system shall have pre-defined progress note templates.,No,No
59,63,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,No,No
60,101,The system shall stored the names of users who view remote data in the remote site's database.,No,No
61,79,"The system shall view users who hold the OREMAS key to be a clerical user, and, consequently, the verify, remove, restore, and view removed options will not be available.",No,No
62,83,The system shall select the item at the top of the list if the user does not enter enough characters to uniquely identify an item.,Yes,Yes(82)
63,91,The system shall only display notifications for a user's patients or notifications that have been forwarded.,No,No
64,49,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Yes,Yes(48)
65,64,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Yes,Yes(65)
66,86,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Yes,Yes(85)
67,68,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Yes,Yes(69)
68,81,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Yes,Yes(80)
69,55,The system shall require the entry of an access code and a verify code to gain access to the system.,Yes,Yes(55)
70,80,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Yes,Yes(81)
71,105,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,No,No
72,76,"The system shall not require a signature for an order if the order is designated as ""signed on chart"" or a generic order that does not require a signature.",No,No
73,77,The system shall ask the user if the user wants to continue using the system before timing out.,No,No
74,74,The system shall not release orders to services or activated until they are signed if they require a signature.,Yes,Yes(75)
75,82,The system shall wait until the user explicitly selects an item using the mouse or the keyboard if the user does not enter enough characters to uniquely identify an item.,Yes,Yes(83)
76,78,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,No,No
77,59,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Yes,Yes(60)
78,102,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",No,No
79,67,The system shall allow users to enter time in several different formats.,Yes,Yes(70)
80,109,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,No,No
81,61,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",No,No
82,73,"The system shall allow multiple use and integration of information, including cutting and pasting among components, boilerplate capabilities, templates, etc., thus decreasing the amount of duplicate entry of data.",No,No
83,75,The system shall have a option to release unsigned orders to services,Yes,Yes(74)
84,66,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,No,No
85,65,The system shall require only a smart card to digitally sign an order.,Yes,Yes(64)
86,88,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,No,No
87,99,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,No,No
88,53,The system shall support the requirements for all codified data ,Yes,Yes(52)
89,70,"The system shall require times to be entered as a 24-hour time, not with a 12-hour clock and an a.m. and p.m.",Yes,Yes(67)
90,71,"The system shall use a set of characters that include uppercase and lowercase Latin alphabetic characters (A-Z, a-z), numbers (0-9), and other special characters.",No,No
91,104,The system shall allow a user to foward notification to someone else at the site.,No,No
92,72,The system shall sort characters based on their numeric values in the character set that VistA uses.,No,No
93,85,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Yes,Yes(86)
94,52,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Yes,Yes(53)
95,87,The system shall display a message telling the user that the selected patient is deceased.,No,No
96,106,"The system shall define, populate, and retrieve information about user classes.",No,No
97,48,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Yes,Yes(49)
98,46,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Yes,Yes(45)
99,112,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,No,No