,idx,requirement,label,conflict
0,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)
1,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)
2,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
3,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
4,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
5,100,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,No,No
6,56,The system shall require the entry of an access code to gain access to the system.,Yes,Yes(56)
7,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)
8,62,The system shall have pre-defined progress note templates.,No,No
9,63,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,No,No
10,101,The system shall stored the names of users who view remote data in the remote site's database.,No,No
11,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
12,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)
13,91,The system shall only display notifications for a user's patients or notifications that have been forwarded.,No,No
14,49,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Yes,Yes(48)
15,64,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Yes,Yes(65)
16,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)
17,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)
18,81,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Yes,Yes(80)
19,55,The system shall require the entry of an access code and a verify code to gain access to the system.,Yes,Yes(55)
20,80,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Yes,Yes(81)
21,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
22,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
23,77,The system shall ask the user if the user wants to continue using the system before timing out.,No,No
24,74,The system shall not release orders to services or activated until they are signed if they require a signature.,Yes,Yes(75)
25,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)
26,78,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,No,No
27,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)
28,102,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",No,No
29,67,The system shall allow users to enter time in several different formats.,Yes,Yes(70)
30,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
31,61,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",No,No
32,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
33,75,The system shall have a option to release unsigned orders to services,Yes,Yes(74)
34,66,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,No,No
35,65,The system shall require only a smart card to digitally sign an order.,Yes,Yes(64)
36,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
37,99,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,No,No
38,53,The system shall support the requirements for all codified data ,Yes,Yes(52)
39,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)
40,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
41,104,The system shall allow a user to foward notification to someone else at the site.,No,No
42,72,The system shall sort characters based on their numeric values in the character set that VistA uses.,No,No
43,85,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Yes,Yes(86)
44,52,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Yes,Yes(53)
45,87,The system shall display a message telling the user that the selected patient is deceased.,No,No
46,106,"The system shall define, populate, and retrieve information about user classes.",No,No
47,48,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Yes,Yes(49)
48,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)
49,112,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,No,No
50,113,"The system shall allow the CAC, or whoever is responsible for granting access to the CPRS GUI at each site, to assign the appropriate access each time a new user is added to the system, or if restricted access is needed for existing users.",No,No
51,138,The system shall include non-Standard Laboratory and Medication orderable files.,Yes,Yes(137)
52,110,The system shall allow concurrent membership in more than one User Class.,Yes,Yes(111)
53,134,The system shall provide the following pediatric functionality including: Pediatric progress note templates based on the Indian Health Services (IHS) progress note templates and American Academy of Pediatric Bright Futures templates.,No,No
54,143,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,No,No
55,94,The system shall use any protocol for transferring messages among packages.,Yes,Yes(93)
56,132,The system shall only delete history of recieved immunizations unless user specifies,Yes,Yes(131)
57,98,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Yes,Yes(97)
58,108,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Yes,Yes(107)
59,116,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",No,No
60,126,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,No,No
61,95,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Yes,Yes(96)
62,89,The system shall not allow mandatory notifications to be disabled.,Yes,Yes(90)
63,118,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Yes,Yes(119)
64,129,"The system shall have the capability to capture and store risk, social and medical factors; including, but not limited to the following: Tobacco use and history including number of years and packs per day (PPD), Alcohol use history, Drug use history, Occupational environment, Marital status, Occupation, Religious preference, Ethnicity, Healthcare surrogate with alert, Guardian/legal representative with alert.",No,No
65,146,The system shall only allow clinical users to have full access privileges to all problem list options.,Yes,Yes(145)
66,136,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",No,No
67,120,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Yes,Yes(121)
68,90,The system shall allow users to disable unwanted notifications as desired.,Yes,Yes(89)
69,144,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",No,No
70,135,The system will provide the ability to register patients of all types.,No,No
71,111,The system shall allow membership in only one User Class.,Yes,Yes(110)
72,117,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",No,No
73,121,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Yes,Yes(120)
74,107,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Yes,Yes(108)
75,137,The system shall include Standard Laboratory and Medication orderable files.,Yes,Yes(138)
76,147,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",No,No
77,97,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Yes,Yes(98)
78,96,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Yes,Yes(95)
79,141,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,No,No
80,119,The system shall make the traditional order entry processes more practical.,Yes,Yes(118)
81,125,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",No,No
82,124,"The system shall support the Ambulatory Care Date Capture project for capturing encounter data for workload credit, as well as capturing clinically relevant data for reminders and reports.",No,No
83,127,"The system shall include a report construction feature so each site can individually run related to patient data including: Health Summary, Vitals Cumulative, Nutritional Assessment, Daily Order Summary and Order Summary for a Date Range reports.",No,No
84,93,The system shall use HL-7 communications protocol for transferring messages among packages.,Yes,Yes(94)
85,131,The system shall delete history of received immunizations.,Yes,Yes(132)
86,145,The system shall allow users who hold any of the ORES/ORELSE/PROVIDER keys to be viewed as a clinical user and has full access privileges to all problem list options.,Yes,Yes(146)
87,133,The system shall include capabilities for ordering laboratory tests and reviewing results.,No,No
88,139,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,No,No
89,142,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,No,No
90,128,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",No,No
91,123,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",No,No
92,130,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",No,No
93,122,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,No,No
94,114,The system shall improve accessibility of online clinical information and results.,No,No
95,115,"The system shall provide a means to view patient demographics, allergies and adverse reactions, postings (cautions, warnings, allergies, and advance directives), clinical reminders, current medications, problems, appointments, etc.",No,No
96,140,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,No,No
97,148,"The system shall allow the creation ofpatient lists or team lists that simplify tasks such as reviewing patient charts, ordering, and signing orders and notes and theselists can be based on wards, clinics, teams, or other groups.",No,No