,idx,requirement,label,conflict
0,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
1,138,The system shall include non-Standard Laboratory and Medication orderable files.,Yes,Yes(137)
2,110,The system shall allow concurrent membership in more than one User Class.,Yes,Yes(111)
3,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
4,143,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,No,No
5,94,The system shall use any protocol for transferring messages among packages.,Yes,Yes(93)
6,132,The system shall only delete history of recieved immunizations unless user specifies,Yes,Yes(131)
7,98,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Yes,Yes(97)
8,108,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Yes,Yes(107)
9,116,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",No,No
10,126,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,No,No
11,95,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Yes,Yes(96)
12,89,The system shall not allow mandatory notifications to be disabled.,Yes,Yes(90)
13,118,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Yes,Yes(119)
14,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
15,146,The system shall only allow clinical users to have full access privileges to all problem list options.,Yes,Yes(145)
16,136,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",No,No
17,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)
18,90,The system shall allow users to disable unwanted notifications as desired.,Yes,Yes(89)
19,144,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",No,No
20,135,The system will provide the ability to register patients of all types.,No,No
21,111,The system shall allow membership in only one User Class.,Yes,Yes(110)
22,117,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",No,No
23,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)
24,107,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Yes,Yes(108)
25,137,The system shall include Standard Laboratory and Medication orderable files.,Yes,Yes(138)
26,147,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",No,No
27,97,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Yes,Yes(98)
28,96,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Yes,Yes(95)
29,141,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,No,No
30,119,The system shall make the traditional order entry processes more practical.,Yes,Yes(118)
31,125,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",No,No
32,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
33,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
34,93,The system shall use HL-7 communications protocol for transferring messages among packages.,Yes,Yes(94)
35,131,The system shall delete history of received immunizations.,Yes,Yes(132)
36,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)
37,133,The system shall include capabilities for ordering laboratory tests and reviewing results.,No,No
38,139,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,No,No
39,142,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,No,No
40,128,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",No,No
41,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
42,130,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",No,No
43,122,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,No,No
44,114,The system shall improve accessibility of online clinical information and results.,No,No
45,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
46,140,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,No,No
47,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