,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,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