,Pair_id,Text1,Text2,Class
0,"(1, 2)",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.,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.,Conflict
1,"(1, 3)",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.,The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,Neutral
2,"(1, 4)",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.,The system shall allow physician offices to only use social security numbers to identify patients.,Neutral
3,"(1, 5)",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.,The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,Neutral
4,"(1, 6)",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.,The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,Neutral
5,"(1, 7)",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.,The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Neutral
6,"(1, 8)",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.,The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Neutral
7,"(1, 9)",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.,The system's pilot program shall use a smart card to digitally sign medication orders.,Neutral
8,"(1, 10)",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.,The system's pilot program shall require a handwritten signature for medication orders.,Neutral
9,"(1, 11)",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.,"The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",Neutral
10,"(1, 12)",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.,"The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Neutral
11,"(1, 13)",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.,"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.",Neutral
12,"(1, 14)",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.,"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).",Neutral
13,"(1, 15)",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.,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.,Neutral
14,"(1, 16)",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.,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.,Neutral
15,"(1, 17)",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.,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
16,"(1, 18)",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.,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.,Neutral
17,"(1, 19)",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.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
18,"(1, 20)",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.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
19,"(1, 21)",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.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
20,"(1, 22)",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.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
21,"(1, 23)",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.,"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.",Neutral
22,"(1, 24)",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.,"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.",Neutral
23,"(1, 25)",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.,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.,Neutral
24,"(1, 26)",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.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
25,"(1, 27)",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.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
26,"(1, 28)",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.,"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.",Neutral
27,"(1, 29)",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.,"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.",Neutral
28,"(1, 30)",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.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
29,"(1, 31)",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.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
30,"(1, 32)",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.,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.,Neutral
31,"(1, 33)",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.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
32,"(1, 34)",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.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
33,"(1, 35)",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.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
34,"(1, 36)",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.,"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).",Neutral
35,"(1, 37)",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.,"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).",Neutral
36,"(1, 38)",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.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
37,"(1, 39)",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.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
38,"(1, 40)",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.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
39,"(1, 41)",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.,The system shall improve efficiency of entering orders.,Neutral
40,"(1, 42)",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.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
41,"(1, 43)",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.,The system shall allow complete order sets to be predefined and personalized.,Neutral
42,"(1, 44)",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.,The system shall allow order checking.,Neutral
43,"(1, 45)",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.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
44,"(1, 46)",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.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
45,"(1, 47)",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.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
46,"(1, 48)",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.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
47,"(1, 49)",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.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
48,"(1, 50)",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.,The system shall support role-based access for security controls.,Neutral
49,"(1, 51)",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.,The system shall support audit capability.,Neutral
50,"(1, 52)",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.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
51,"(1, 53)",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.,The system shall support the requirements for all codified data ,Neutral
52,"(1, 54)",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.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
53,"(1, 55)",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.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
54,"(1, 56)",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.,The system shall require the entry of an access code to gain access to the system.,Neutral
55,"(1, 57)",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.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
56,"(1, 58)",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.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
57,"(1, 59)",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.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
58,"(1, 60)",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.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
59,"(1, 61)",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.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
60,"(1, 62)",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.,The system shall have pre-defined progress note templates.,Neutral
61,"(1, 63)",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.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
62,"(1, 64)",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.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
63,"(1, 65)",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.,The system shall require only a smart card to digitally sign an order.,Neutral
64,"(1, 66)",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.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
65,"(1, 67)",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.,The system shall allow users to enter time in several different formats.,Neutral
66,"(1, 68)",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.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
67,"(1, 69)",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.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
68,"(1, 70)",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.,"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.",Neutral
69,"(1, 71)",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.,"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.",Neutral
70,"(1, 72)",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.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
71,"(1, 73)",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.,"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.",Neutral
72,"(1, 74)",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.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
73,"(1, 75)",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.,The system shall have a option to release unsigned orders to services,Neutral
74,"(1, 76)",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.,"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.",Neutral
75,"(1, 77)",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.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
76,"(1, 78)",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.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
77,"(1, 79)",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.,"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.",Neutral
78,"(1, 80)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
79,"(1, 81)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
80,"(1, 82)",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.,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.,Neutral
81,"(1, 83)",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.,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.,Neutral
82,"(1, 84)",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.,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.,Neutral
83,"(1, 85)",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.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
84,"(1, 86)",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.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
85,"(1, 87)",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.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
86,"(1, 88)",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.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
87,"(1, 89)",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.,The system shall not allow mandatory notifications to be disabled.,Neutral
88,"(1, 90)",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.,The system shall allow users to disable unwanted notifications as desired.,Neutral
89,"(1, 91)",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.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
90,"(1, 92)",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.,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.,Neutral
91,"(1, 93)",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.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
92,"(1, 94)",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.,The system shall use any protocol for transferring messages among packages.,Neutral
93,"(1, 95)",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.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
94,"(1, 96)",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.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
95,"(1, 97)",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.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
96,"(1, 98)",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.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
97,"(1, 99)",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.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
98,"(1, 100)",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.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
99,"(1, 101)",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.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
100,"(1, 102)",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.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
101,"(1, 103)",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.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
102,"(1, 104)",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.,The system shall allow a user to foward notification to someone else at the site.,Neutral
103,"(1, 105)",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.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
104,"(1, 106)",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.,"The system shall define, populate, and retrieve information about user classes.",Neutral
105,"(1, 107)",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.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
106,"(1, 108)",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.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
107,"(1, 109)",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.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
108,"(1, 110)",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.,The system shall allow concurrent membership in more than one User Class.,Neutral
109,"(1, 111)",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.,The system shall allow membership in only one User Class.,Neutral
110,"(1, 112)",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.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
111,"(1, 113)",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.,"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.",Neutral
112,"(1, 114)",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.,The system shall improve accessibility of online clinical information and results.,Neutral
113,"(1, 115)",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.,"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.",Neutral
114,"(1, 116)",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.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
115,"(1, 117)",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.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
116,"(1, 118)",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.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
117,"(1, 119)",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.,The system shall make the traditional order entry processes more practical.,Neutral
118,"(1, 120)",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.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
119,"(1, 121)",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.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
120,"(1, 122)",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.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
121,"(1, 123)",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.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
122,"(1, 124)",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.,"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.",Neutral
123,"(1, 125)",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.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
124,"(1, 126)",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.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
125,"(1, 127)",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.,"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.",Neutral
126,"(1, 128)",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.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
127,"(1, 129)",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.,"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.",Neutral
128,"(1, 130)",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.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
129,"(1, 131)",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.,The system shall delete history of received immunizations.,Neutral
130,"(1, 132)",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.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
131,"(1, 133)",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.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
132,"(1, 134)",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.,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.,Neutral
133,"(1, 135)",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.,The system will provide the ability to register patients of all types.,Neutral
134,"(1, 136)",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.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
135,"(1, 137)",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.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
136,"(1, 138)",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.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
137,"(1, 139)",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.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
138,"(1, 140)",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.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
139,"(1, 141)",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.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
140,"(1, 142)",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.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
141,"(1, 143)",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.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
142,"(1, 144)",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.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
143,"(1, 145)",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.,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.,Neutral
144,"(1, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
145,"(1, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
146,"(1, 148)",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.,"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.",Neutral
147,"(2, 3)",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.,The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,Neutral
148,"(2, 4)",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.,The system shall allow physician offices to only use social security numbers to identify patients.,Neutral
149,"(2, 5)",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.,The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,Neutral
150,"(2, 6)",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.,The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,Neutral
151,"(2, 7)",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.,The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Neutral
152,"(2, 8)",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.,The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Neutral
153,"(2, 9)",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.,The system's pilot program shall use a smart card to digitally sign medication orders.,Neutral
154,"(2, 10)",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.,The system's pilot program shall require a handwritten signature for medication orders.,Neutral
155,"(2, 11)",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.,"The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",Neutral
156,"(2, 12)",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.,"The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Neutral
157,"(2, 13)",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.,"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.",Neutral
158,"(2, 14)",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.,"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).",Neutral
159,"(2, 15)",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.,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.,Neutral
160,"(2, 16)",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.,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.,Neutral
161,"(2, 17)",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.,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
162,"(2, 18)",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.,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.,Neutral
163,"(2, 19)",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.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
164,"(2, 20)",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.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
165,"(2, 21)",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.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
166,"(2, 22)",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.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
167,"(2, 23)",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.,"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.",Neutral
168,"(2, 24)",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.,"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.",Neutral
169,"(2, 25)",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.,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.,Neutral
170,"(2, 26)",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.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
171,"(2, 27)",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.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
172,"(2, 28)",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.,"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.",Neutral
173,"(2, 29)",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.,"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.",Neutral
174,"(2, 30)",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.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
175,"(2, 31)",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.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
176,"(2, 32)",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.,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.,Neutral
177,"(2, 33)",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.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
178,"(2, 34)",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.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
179,"(2, 35)",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.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
180,"(2, 36)",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.,"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).",Neutral
181,"(2, 37)",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.,"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).",Neutral
182,"(2, 38)",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.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
183,"(2, 39)",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.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
184,"(2, 40)",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.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
185,"(2, 41)",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.,The system shall improve efficiency of entering orders.,Neutral
186,"(2, 42)",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.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
187,"(2, 43)",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.,The system shall allow complete order sets to be predefined and personalized.,Neutral
188,"(2, 44)",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.,The system shall allow order checking.,Neutral
189,"(2, 45)",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.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
190,"(2, 46)",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.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
191,"(2, 47)",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.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
192,"(2, 48)",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.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
193,"(2, 49)",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.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
194,"(2, 50)",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.,The system shall support role-based access for security controls.,Neutral
195,"(2, 51)",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.,The system shall support audit capability.,Neutral
196,"(2, 52)",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.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
197,"(2, 53)",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.,The system shall support the requirements for all codified data ,Neutral
198,"(2, 54)",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.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
199,"(2, 55)",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.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
200,"(2, 56)",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.,The system shall require the entry of an access code to gain access to the system.,Neutral
201,"(2, 57)",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.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
202,"(2, 58)",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.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
203,"(2, 59)",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.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
204,"(2, 60)",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.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
205,"(2, 61)",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.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
206,"(2, 62)",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.,The system shall have pre-defined progress note templates.,Neutral
207,"(2, 63)",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.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
208,"(2, 64)",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.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
209,"(2, 65)",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.,The system shall require only a smart card to digitally sign an order.,Neutral
210,"(2, 66)",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.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
211,"(2, 67)",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.,The system shall allow users to enter time in several different formats.,Neutral
212,"(2, 68)",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.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
213,"(2, 69)",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.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
214,"(2, 70)",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.,"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.",Neutral
215,"(2, 71)",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.,"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.",Neutral
216,"(2, 72)",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.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
217,"(2, 73)",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.,"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.",Neutral
218,"(2, 74)",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.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
219,"(2, 75)",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.,The system shall have a option to release unsigned orders to services,Neutral
220,"(2, 76)",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.,"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.",Neutral
221,"(2, 77)",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.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
222,"(2, 78)",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.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
223,"(2, 79)",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.,"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.",Neutral
224,"(2, 80)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
225,"(2, 81)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
226,"(2, 82)",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.,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.,Neutral
227,"(2, 83)",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.,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.,Neutral
228,"(2, 84)",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.,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.,Neutral
229,"(2, 85)",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.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
230,"(2, 86)",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.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
231,"(2, 87)",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.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
232,"(2, 88)",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.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
233,"(2, 89)",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.,The system shall not allow mandatory notifications to be disabled.,Neutral
234,"(2, 90)",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.,The system shall allow users to disable unwanted notifications as desired.,Neutral
235,"(2, 91)",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.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
236,"(2, 92)",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.,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.,Neutral
237,"(2, 93)",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.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
238,"(2, 94)",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.,The system shall use any protocol for transferring messages among packages.,Neutral
239,"(2, 95)",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.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
240,"(2, 96)",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.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
241,"(2, 97)",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.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
242,"(2, 98)",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.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
243,"(2, 99)",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.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
244,"(2, 100)",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.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
245,"(2, 101)",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.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
246,"(2, 102)",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.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
247,"(2, 103)",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.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
248,"(2, 104)",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.,The system shall allow a user to foward notification to someone else at the site.,Neutral
249,"(2, 105)",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.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
250,"(2, 106)",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.,"The system shall define, populate, and retrieve information about user classes.",Neutral
251,"(2, 107)",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.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
252,"(2, 108)",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.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
253,"(2, 109)",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.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
254,"(2, 110)",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.,The system shall allow concurrent membership in more than one User Class.,Neutral
255,"(2, 111)",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.,The system shall allow membership in only one User Class.,Neutral
256,"(2, 112)",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.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
257,"(2, 113)",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.,"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.",Neutral
258,"(2, 114)",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.,The system shall improve accessibility of online clinical information and results.,Neutral
259,"(2, 115)",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.,"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.",Neutral
260,"(2, 116)",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.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
261,"(2, 117)",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.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
262,"(2, 118)",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.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
263,"(2, 119)",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.,The system shall make the traditional order entry processes more practical.,Neutral
264,"(2, 120)",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.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
265,"(2, 121)",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.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
266,"(2, 122)",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.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
267,"(2, 123)",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.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
268,"(2, 124)",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.,"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.",Neutral
269,"(2, 125)",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.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
270,"(2, 126)",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.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
271,"(2, 127)",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.,"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.",Neutral
272,"(2, 128)",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.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
273,"(2, 129)",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.,"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.",Neutral
274,"(2, 130)",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.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
275,"(2, 131)",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.,The system shall delete history of received immunizations.,Neutral
276,"(2, 132)",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.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
277,"(2, 133)",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.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
278,"(2, 134)",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.,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.,Neutral
279,"(2, 135)",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.,The system will provide the ability to register patients of all types.,Neutral
280,"(2, 136)",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.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
281,"(2, 137)",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.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
282,"(2, 138)",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.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
283,"(2, 139)",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.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
284,"(2, 140)",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.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
285,"(2, 141)",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.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
286,"(2, 142)",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.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
287,"(2, 143)",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.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
288,"(2, 144)",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.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
289,"(2, 145)",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.,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.,Neutral
290,"(2, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
291,"(2, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
292,"(2, 148)",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.,"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.",Neutral
293,"(3, 4)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow physician offices to only use social security numbers to identify patients.,Conflict
294,"(3, 5)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,Neutral
295,"(3, 6)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,Neutral
296,"(3, 7)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Neutral
297,"(3, 8)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Neutral
298,"(3, 9)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system's pilot program shall use a smart card to digitally sign medication orders.,Neutral
299,"(3, 10)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system's pilot program shall require a handwritten signature for medication orders.,Neutral
300,"(3, 11)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",Neutral
301,"(3, 12)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Neutral
302,"(3, 13)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
303,"(3, 14)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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).",Neutral
304,"(3, 15)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,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.,Neutral
305,"(3, 16)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,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.,Neutral
306,"(3, 17)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
307,"(3, 18)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,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.,Neutral
308,"(3, 19)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
309,"(3, 20)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
310,"(3, 21)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
311,"(3, 22)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
312,"(3, 23)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
313,"(3, 24)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
314,"(3, 25)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,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.,Neutral
315,"(3, 26)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
316,"(3, 27)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
317,"(3, 28)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
318,"(3, 29)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
319,"(3, 30)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
320,"(3, 31)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
321,"(3, 32)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,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.,Neutral
322,"(3, 33)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
323,"(3, 34)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
324,"(3, 35)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
325,"(3, 36)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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).",Neutral
326,"(3, 37)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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).",Neutral
327,"(3, 38)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
328,"(3, 39)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
329,"(3, 40)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
330,"(3, 41)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall improve efficiency of entering orders.,Neutral
331,"(3, 42)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
332,"(3, 43)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow complete order sets to be predefined and personalized.,Neutral
333,"(3, 44)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow order checking.,Neutral
334,"(3, 45)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
335,"(3, 46)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
336,"(3, 47)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
337,"(3, 48)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
338,"(3, 49)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
339,"(3, 50)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall support role-based access for security controls.,Neutral
340,"(3, 51)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall support audit capability.,Neutral
341,"(3, 52)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
342,"(3, 53)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall support the requirements for all codified data ,Neutral
343,"(3, 54)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
344,"(3, 55)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
345,"(3, 56)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall require the entry of an access code to gain access to the system.,Neutral
346,"(3, 57)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
347,"(3, 58)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
348,"(3, 59)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
349,"(3, 60)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
350,"(3, 61)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
351,"(3, 62)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall have pre-defined progress note templates.,Neutral
352,"(3, 63)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
353,"(3, 64)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
354,"(3, 65)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall require only a smart card to digitally sign an order.,Neutral
355,"(3, 66)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
356,"(3, 67)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow users to enter time in several different formats.,Neutral
357,"(3, 68)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
358,"(3, 69)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
359,"(3, 70)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
360,"(3, 71)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
361,"(3, 72)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
362,"(3, 73)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
363,"(3, 74)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
364,"(3, 75)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall have a option to release unsigned orders to services,Neutral
365,"(3, 76)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
366,"(3, 77)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
367,"(3, 78)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
368,"(3, 79)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
369,"(3, 80)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
370,"(3, 81)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
371,"(3, 82)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,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.,Neutral
372,"(3, 83)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,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.,Neutral
373,"(3, 84)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,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.,Neutral
374,"(3, 85)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
375,"(3, 86)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
376,"(3, 87)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
377,"(3, 88)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
378,"(3, 89)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall not allow mandatory notifications to be disabled.,Neutral
379,"(3, 90)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow users to disable unwanted notifications as desired.,Neutral
380,"(3, 91)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
381,"(3, 92)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,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.,Neutral
382,"(3, 93)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
383,"(3, 94)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall use any protocol for transferring messages among packages.,Neutral
384,"(3, 95)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
385,"(3, 96)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
386,"(3, 97)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
387,"(3, 98)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
388,"(3, 99)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
389,"(3, 100)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
390,"(3, 101)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
391,"(3, 102)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
392,"(3, 103)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
393,"(3, 104)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow a user to foward notification to someone else at the site.,Neutral
394,"(3, 105)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
395,"(3, 106)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall define, populate, and retrieve information about user classes.",Neutral
396,"(3, 107)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
397,"(3, 108)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
398,"(3, 109)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
399,"(3, 110)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow concurrent membership in more than one User Class.,Neutral
400,"(3, 111)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow membership in only one User Class.,Neutral
401,"(3, 112)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
402,"(3, 113)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
403,"(3, 114)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall improve accessibility of online clinical information and results.,Neutral
404,"(3, 115)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
405,"(3, 116)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
406,"(3, 117)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
407,"(3, 118)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
408,"(3, 119)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall make the traditional order entry processes more practical.,Neutral
409,"(3, 120)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
410,"(3, 121)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
411,"(3, 122)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
412,"(3, 123)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
413,"(3, 124)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
414,"(3, 125)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
415,"(3, 126)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
416,"(3, 127)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
417,"(3, 128)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
418,"(3, 129)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
419,"(3, 130)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
420,"(3, 131)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall delete history of received immunizations.,Neutral
421,"(3, 132)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
422,"(3, 133)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
423,"(3, 134)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,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.,Neutral
424,"(3, 135)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system will provide the ability to register patients of all types.,Neutral
425,"(3, 136)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
426,"(3, 137)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
427,"(3, 138)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
428,"(3, 139)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
429,"(3, 140)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
430,"(3, 141)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
431,"(3, 142)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
432,"(3, 143)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
433,"(3, 144)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
434,"(3, 145)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,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.,Neutral
435,"(3, 146)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
436,"(3, 147)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
437,"(3, 148)",The system shall allow physician offices to use social security numbers or medical record numbers to identify patients.,"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.",Neutral
438,"(4, 5)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,Neutral
439,"(4, 6)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,Neutral
440,"(4, 7)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Neutral
441,"(4, 8)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Neutral
442,"(4, 9)",The system shall allow physician offices to only use social security numbers to identify patients.,The system's pilot program shall use a smart card to digitally sign medication orders.,Neutral
443,"(4, 10)",The system shall allow physician offices to only use social security numbers to identify patients.,The system's pilot program shall require a handwritten signature for medication orders.,Neutral
444,"(4, 11)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",Neutral
445,"(4, 12)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Neutral
446,"(4, 13)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
447,"(4, 14)",The system shall allow physician offices to only use social security numbers to identify patients.,"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).",Neutral
448,"(4, 15)",The system shall allow physician offices to only use social security numbers to identify patients.,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.,Neutral
449,"(4, 16)",The system shall allow physician offices to only use social security numbers to identify patients.,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.,Neutral
450,"(4, 17)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
451,"(4, 18)",The system shall allow physician offices to only use social security numbers to identify patients.,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.,Neutral
452,"(4, 19)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
453,"(4, 20)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
454,"(4, 21)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
455,"(4, 22)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
456,"(4, 23)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
457,"(4, 24)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
458,"(4, 25)",The system shall allow physician offices to only use social security numbers to identify patients.,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.,Neutral
459,"(4, 26)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
460,"(4, 27)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
461,"(4, 28)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
462,"(4, 29)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
463,"(4, 30)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
464,"(4, 31)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
465,"(4, 32)",The system shall allow physician offices to only use social security numbers to identify patients.,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.,Neutral
466,"(4, 33)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
467,"(4, 34)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
468,"(4, 35)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
469,"(4, 36)",The system shall allow physician offices to only use social security numbers to identify patients.,"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).",Neutral
470,"(4, 37)",The system shall allow physician offices to only use social security numbers to identify patients.,"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).",Neutral
471,"(4, 38)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
472,"(4, 39)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
473,"(4, 40)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
474,"(4, 41)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall improve efficiency of entering orders.,Neutral
475,"(4, 42)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
476,"(4, 43)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow complete order sets to be predefined and personalized.,Neutral
477,"(4, 44)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow order checking.,Neutral
478,"(4, 45)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
479,"(4, 46)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
480,"(4, 47)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
481,"(4, 48)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
482,"(4, 49)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
483,"(4, 50)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall support role-based access for security controls.,Neutral
484,"(4, 51)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall support audit capability.,Neutral
485,"(4, 52)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
486,"(4, 53)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall support the requirements for all codified data ,Neutral
487,"(4, 54)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
488,"(4, 55)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
489,"(4, 56)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall require the entry of an access code to gain access to the system.,Neutral
490,"(4, 57)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
491,"(4, 58)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
492,"(4, 59)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
493,"(4, 60)",The system shall allow physician offices to only use social security numbers to identify patients.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
494,"(4, 61)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
495,"(4, 62)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall have pre-defined progress note templates.,Neutral
496,"(4, 63)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
497,"(4, 64)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
498,"(4, 65)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall require only a smart card to digitally sign an order.,Neutral
499,"(4, 66)",The system shall allow physician offices to only use social security numbers to identify patients.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
500,"(4, 67)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow users to enter time in several different formats.,Neutral
501,"(4, 68)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
502,"(4, 69)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
503,"(4, 70)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
504,"(4, 71)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
505,"(4, 72)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
506,"(4, 73)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
507,"(4, 74)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
508,"(4, 75)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall have a option to release unsigned orders to services,Neutral
509,"(4, 76)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
510,"(4, 77)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
511,"(4, 78)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
512,"(4, 79)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
513,"(4, 80)",The system shall allow physician offices to only use social security numbers to identify patients.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
514,"(4, 81)",The system shall allow physician offices to only use social security numbers to identify patients.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
515,"(4, 82)",The system shall allow physician offices to only use social security numbers to identify patients.,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.,Neutral
516,"(4, 83)",The system shall allow physician offices to only use social security numbers to identify patients.,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.,Neutral
517,"(4, 84)",The system shall allow physician offices to only use social security numbers to identify patients.,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.,Neutral
518,"(4, 85)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
519,"(4, 86)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
520,"(4, 87)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
521,"(4, 88)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
522,"(4, 89)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall not allow mandatory notifications to be disabled.,Neutral
523,"(4, 90)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow users to disable unwanted notifications as desired.,Neutral
524,"(4, 91)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
525,"(4, 92)",The system shall allow physician offices to only use social security numbers to identify patients.,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.,Neutral
526,"(4, 93)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
527,"(4, 94)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall use any protocol for transferring messages among packages.,Neutral
528,"(4, 95)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
529,"(4, 96)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
530,"(4, 97)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
531,"(4, 98)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
532,"(4, 99)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
533,"(4, 100)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
534,"(4, 101)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
535,"(4, 102)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
536,"(4, 103)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
537,"(4, 104)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow a user to foward notification to someone else at the site.,Neutral
538,"(4, 105)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
539,"(4, 106)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall define, populate, and retrieve information about user classes.",Neutral
540,"(4, 107)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
541,"(4, 108)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
542,"(4, 109)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
543,"(4, 110)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow concurrent membership in more than one User Class.,Neutral
544,"(4, 111)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow membership in only one User Class.,Neutral
545,"(4, 112)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
546,"(4, 113)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
547,"(4, 114)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall improve accessibility of online clinical information and results.,Neutral
548,"(4, 115)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
549,"(4, 116)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
550,"(4, 117)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
551,"(4, 118)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
552,"(4, 119)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall make the traditional order entry processes more practical.,Neutral
553,"(4, 120)",The system shall allow physician offices to only use social security numbers to identify patients.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
554,"(4, 121)",The system shall allow physician offices to only use social security numbers to identify patients.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
555,"(4, 122)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
556,"(4, 123)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
557,"(4, 124)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
558,"(4, 125)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
559,"(4, 126)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
560,"(4, 127)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
561,"(4, 128)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
562,"(4, 129)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
563,"(4, 130)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
564,"(4, 131)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall delete history of received immunizations.,Neutral
565,"(4, 132)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
566,"(4, 133)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
567,"(4, 134)",The system shall allow physician offices to only use social security numbers to identify patients.,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.,Neutral
568,"(4, 135)",The system shall allow physician offices to only use social security numbers to identify patients.,The system will provide the ability to register patients of all types.,Neutral
569,"(4, 136)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
570,"(4, 137)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
571,"(4, 138)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
572,"(4, 139)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
573,"(4, 140)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
574,"(4, 141)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
575,"(4, 142)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
576,"(4, 143)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
577,"(4, 144)",The system shall allow physician offices to only use social security numbers to identify patients.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
578,"(4, 145)",The system shall allow physician offices to only use social security numbers to identify patients.,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.,Neutral
579,"(4, 146)",The system shall allow physician offices to only use social security numbers to identify patients.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
580,"(4, 147)",The system shall allow physician offices to only use social security numbers to identify patients.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
581,"(4, 148)",The system shall allow physician offices to only use social security numbers to identify patients.,"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.",Neutral
582,"(5, 6)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,Neutral
583,"(5, 7)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Neutral
584,"(5, 8)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Neutral
585,"(5, 9)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system's pilot program shall use a smart card to digitally sign medication orders.,Neutral
586,"(5, 10)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system's pilot program shall require a handwritten signature for medication orders.,Neutral
587,"(5, 11)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",Neutral
588,"(5, 12)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Neutral
589,"(5, 13)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
590,"(5, 14)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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).",Neutral
591,"(5, 15)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,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.,Neutral
592,"(5, 16)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,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.,Neutral
593,"(5, 17)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
594,"(5, 18)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,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.,Neutral
595,"(5, 19)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
596,"(5, 20)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
597,"(5, 21)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
598,"(5, 22)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
599,"(5, 23)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
600,"(5, 24)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
601,"(5, 25)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,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.,Neutral
602,"(5, 26)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
603,"(5, 27)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
604,"(5, 28)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
605,"(5, 29)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
606,"(5, 30)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
607,"(5, 31)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
608,"(5, 32)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,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.,Neutral
609,"(5, 33)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
610,"(5, 34)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
611,"(5, 35)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
612,"(5, 36)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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).",Neutral
613,"(5, 37)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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).",Neutral
614,"(5, 38)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
615,"(5, 39)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
616,"(5, 40)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
617,"(5, 41)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall improve efficiency of entering orders.,Neutral
618,"(5, 42)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
619,"(5, 43)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow complete order sets to be predefined and personalized.,Neutral
620,"(5, 44)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow order checking.,Neutral
621,"(5, 45)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
622,"(5, 46)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
623,"(5, 47)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
624,"(5, 48)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
625,"(5, 49)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
626,"(5, 50)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall support role-based access for security controls.,Neutral
627,"(5, 51)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall support audit capability.,Neutral
628,"(5, 52)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
629,"(5, 53)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall support the requirements for all codified data ,Neutral
630,"(5, 54)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
631,"(5, 55)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
632,"(5, 56)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall require the entry of an access code to gain access to the system.,Neutral
633,"(5, 57)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
634,"(5, 58)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
635,"(5, 59)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
636,"(5, 60)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
637,"(5, 61)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
638,"(5, 62)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall have pre-defined progress note templates.,Neutral
639,"(5, 63)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
640,"(5, 64)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
641,"(5, 65)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall require only a smart card to digitally sign an order.,Neutral
642,"(5, 66)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
643,"(5, 67)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow users to enter time in several different formats.,Neutral
644,"(5, 68)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
645,"(5, 69)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
646,"(5, 70)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
647,"(5, 71)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
648,"(5, 72)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
649,"(5, 73)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
650,"(5, 74)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
651,"(5, 75)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall have a option to release unsigned orders to services,Neutral
652,"(5, 76)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
653,"(5, 77)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
654,"(5, 78)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
655,"(5, 79)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
656,"(5, 80)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
657,"(5, 81)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
658,"(5, 82)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,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.,Neutral
659,"(5, 83)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,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.,Neutral
660,"(5, 84)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,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.,Neutral
661,"(5, 85)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
662,"(5, 86)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
663,"(5, 87)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
664,"(5, 88)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
665,"(5, 89)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall not allow mandatory notifications to be disabled.,Neutral
666,"(5, 90)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow users to disable unwanted notifications as desired.,Neutral
667,"(5, 91)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
668,"(5, 92)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,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.,Neutral
669,"(5, 93)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
670,"(5, 94)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall use any protocol for transferring messages among packages.,Neutral
671,"(5, 95)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
672,"(5, 96)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
673,"(5, 97)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
674,"(5, 98)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
675,"(5, 99)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
676,"(5, 100)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
677,"(5, 101)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
678,"(5, 102)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
679,"(5, 103)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
680,"(5, 104)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow a user to foward notification to someone else at the site.,Neutral
681,"(5, 105)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
682,"(5, 106)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall define, populate, and retrieve information about user classes.",Neutral
683,"(5, 107)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
684,"(5, 108)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
685,"(5, 109)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
686,"(5, 110)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow concurrent membership in more than one User Class.,Neutral
687,"(5, 111)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow membership in only one User Class.,Neutral
688,"(5, 112)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
689,"(5, 113)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
690,"(5, 114)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall improve accessibility of online clinical information and results.,Neutral
691,"(5, 115)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
692,"(5, 116)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
693,"(5, 117)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
694,"(5, 118)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
695,"(5, 119)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall make the traditional order entry processes more practical.,Neutral
696,"(5, 120)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
697,"(5, 121)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
698,"(5, 122)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
699,"(5, 123)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
700,"(5, 124)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
701,"(5, 125)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
702,"(5, 126)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
703,"(5, 127)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
704,"(5, 128)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
705,"(5, 129)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
706,"(5, 130)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
707,"(5, 131)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall delete history of received immunizations.,Neutral
708,"(5, 132)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
709,"(5, 133)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
710,"(5, 134)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,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.,Neutral
711,"(5, 135)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system will provide the ability to register patients of all types.,Neutral
712,"(5, 136)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
713,"(5, 137)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
714,"(5, 138)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
715,"(5, 139)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
716,"(5, 140)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
717,"(5, 141)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
718,"(5, 142)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
719,"(5, 143)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
720,"(5, 144)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
721,"(5, 145)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,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.,Neutral
722,"(5, 146)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
723,"(5, 147)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
724,"(5, 148)",The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program.,"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.",Neutral
725,"(6, 7)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Neutral
726,"(6, 8)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Neutral
727,"(6, 9)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system's pilot program shall use a smart card to digitally sign medication orders.,Neutral
728,"(6, 10)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system's pilot program shall require a handwritten signature for medication orders.,Neutral
729,"(6, 11)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",Neutral
730,"(6, 12)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Neutral
731,"(6, 13)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
732,"(6, 14)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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).",Neutral
733,"(6, 15)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,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.,Neutral
734,"(6, 16)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,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.,Neutral
735,"(6, 17)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
736,"(6, 18)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,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.,Neutral
737,"(6, 19)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
738,"(6, 20)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
739,"(6, 21)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
740,"(6, 22)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
741,"(6, 23)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
742,"(6, 24)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
743,"(6, 25)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,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.,Neutral
744,"(6, 26)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
745,"(6, 27)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
746,"(6, 28)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
747,"(6, 29)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
748,"(6, 30)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
749,"(6, 31)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
750,"(6, 32)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,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.,Neutral
751,"(6, 33)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
752,"(6, 34)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
753,"(6, 35)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
754,"(6, 36)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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).",Neutral
755,"(6, 37)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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).",Neutral
756,"(6, 38)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
757,"(6, 39)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
758,"(6, 40)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
759,"(6, 41)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall improve efficiency of entering orders.,Neutral
760,"(6, 42)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
761,"(6, 43)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow complete order sets to be predefined and personalized.,Neutral
762,"(6, 44)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow order checking.,Neutral
763,"(6, 45)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
764,"(6, 46)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
765,"(6, 47)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
766,"(6, 48)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
767,"(6, 49)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
768,"(6, 50)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall support role-based access for security controls.,Neutral
769,"(6, 51)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall support audit capability.,Neutral
770,"(6, 52)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
771,"(6, 53)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall support the requirements for all codified data ,Neutral
772,"(6, 54)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
773,"(6, 55)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
774,"(6, 56)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall require the entry of an access code to gain access to the system.,Neutral
775,"(6, 57)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
776,"(6, 58)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
777,"(6, 59)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
778,"(6, 60)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
779,"(6, 61)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
780,"(6, 62)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall have pre-defined progress note templates.,Neutral
781,"(6, 63)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
782,"(6, 64)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
783,"(6, 65)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall require only a smart card to digitally sign an order.,Neutral
784,"(6, 66)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
785,"(6, 67)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow users to enter time in several different formats.,Neutral
786,"(6, 68)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
787,"(6, 69)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
788,"(6, 70)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
789,"(6, 71)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
790,"(6, 72)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
791,"(6, 73)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
792,"(6, 74)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
793,"(6, 75)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall have a option to release unsigned orders to services,Neutral
794,"(6, 76)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
795,"(6, 77)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
796,"(6, 78)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
797,"(6, 79)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
798,"(6, 80)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
799,"(6, 81)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
800,"(6, 82)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,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.,Neutral
801,"(6, 83)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,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.,Neutral
802,"(6, 84)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,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.,Neutral
803,"(6, 85)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
804,"(6, 86)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
805,"(6, 87)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
806,"(6, 88)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
807,"(6, 89)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall not allow mandatory notifications to be disabled.,Neutral
808,"(6, 90)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow users to disable unwanted notifications as desired.,Neutral
809,"(6, 91)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
810,"(6, 92)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,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.,Neutral
811,"(6, 93)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
812,"(6, 94)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall use any protocol for transferring messages among packages.,Neutral
813,"(6, 95)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
814,"(6, 96)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
815,"(6, 97)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
816,"(6, 98)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
817,"(6, 99)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
818,"(6, 100)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
819,"(6, 101)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
820,"(6, 102)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
821,"(6, 103)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
822,"(6, 104)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow a user to foward notification to someone else at the site.,Neutral
823,"(6, 105)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
824,"(6, 106)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall define, populate, and retrieve information about user classes.",Neutral
825,"(6, 107)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
826,"(6, 108)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
827,"(6, 109)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
828,"(6, 110)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow concurrent membership in more than one User Class.,Neutral
829,"(6, 111)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow membership in only one User Class.,Neutral
830,"(6, 112)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
831,"(6, 113)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
832,"(6, 114)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall improve accessibility of online clinical information and results.,Neutral
833,"(6, 115)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
834,"(6, 116)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
835,"(6, 117)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
836,"(6, 118)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
837,"(6, 119)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall make the traditional order entry processes more practical.,Neutral
838,"(6, 120)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
839,"(6, 121)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
840,"(6, 122)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
841,"(6, 123)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
842,"(6, 124)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
843,"(6, 125)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
844,"(6, 126)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
845,"(6, 127)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
846,"(6, 128)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
847,"(6, 129)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
848,"(6, 130)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
849,"(6, 131)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall delete history of received immunizations.,Neutral
850,"(6, 132)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
851,"(6, 133)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
852,"(6, 134)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,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.,Neutral
853,"(6, 135)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system will provide the ability to register patients of all types.,Neutral
854,"(6, 136)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
855,"(6, 137)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
856,"(6, 138)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
857,"(6, 139)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
858,"(6, 140)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
859,"(6, 141)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
860,"(6, 142)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
861,"(6, 143)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
862,"(6, 144)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
863,"(6, 145)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,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.,Neutral
864,"(6, 146)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
865,"(6, 147)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
866,"(6, 148)",The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature.,"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.",Neutral
867,"(7, 8)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Conflict
868,"(7, 9)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system's pilot program shall use a smart card to digitally sign medication orders.,Neutral
869,"(7, 10)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system's pilot program shall require a handwritten signature for medication orders.,Neutral
870,"(7, 11)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",Neutral
871,"(7, 12)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Neutral
872,"(7, 13)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
873,"(7, 14)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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).",Neutral
874,"(7, 15)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
875,"(7, 16)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
876,"(7, 17)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
877,"(7, 18)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
878,"(7, 19)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
879,"(7, 20)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
880,"(7, 21)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
881,"(7, 22)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
882,"(7, 23)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
883,"(7, 24)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
884,"(7, 25)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
885,"(7, 26)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
886,"(7, 27)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
887,"(7, 28)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
888,"(7, 29)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
889,"(7, 30)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
890,"(7, 31)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
891,"(7, 32)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
892,"(7, 33)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
893,"(7, 34)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
894,"(7, 35)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
895,"(7, 36)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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).",Neutral
896,"(7, 37)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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).",Neutral
897,"(7, 38)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
898,"(7, 39)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
899,"(7, 40)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
900,"(7, 41)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall improve efficiency of entering orders.,Neutral
901,"(7, 42)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
902,"(7, 43)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow complete order sets to be predefined and personalized.,Neutral
903,"(7, 44)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow order checking.,Neutral
904,"(7, 45)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
905,"(7, 46)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
906,"(7, 47)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
907,"(7, 48)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
908,"(7, 49)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
909,"(7, 50)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall support role-based access for security controls.,Neutral
910,"(7, 51)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall support audit capability.,Neutral
911,"(7, 52)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
912,"(7, 53)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall support the requirements for all codified data ,Neutral
913,"(7, 54)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
914,"(7, 55)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
915,"(7, 56)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require the entry of an access code to gain access to the system.,Neutral
916,"(7, 57)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
917,"(7, 58)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
918,"(7, 59)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
919,"(7, 60)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
920,"(7, 61)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
921,"(7, 62)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall have pre-defined progress note templates.,Neutral
922,"(7, 63)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
923,"(7, 64)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
924,"(7, 65)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require only a smart card to digitally sign an order.,Neutral
925,"(7, 66)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
926,"(7, 67)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow users to enter time in several different formats.,Neutral
927,"(7, 68)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
928,"(7, 69)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
929,"(7, 70)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
930,"(7, 71)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
931,"(7, 72)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
932,"(7, 73)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
933,"(7, 74)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
934,"(7, 75)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall have a option to release unsigned orders to services,Neutral
935,"(7, 76)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
936,"(7, 77)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
937,"(7, 78)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
938,"(7, 79)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
939,"(7, 80)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
940,"(7, 81)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
941,"(7, 82)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
942,"(7, 83)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
943,"(7, 84)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
944,"(7, 85)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
945,"(7, 86)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
946,"(7, 87)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
947,"(7, 88)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
948,"(7, 89)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall not allow mandatory notifications to be disabled.,Neutral
949,"(7, 90)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow users to disable unwanted notifications as desired.,Neutral
950,"(7, 91)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
951,"(7, 92)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
952,"(7, 93)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
953,"(7, 94)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall use any protocol for transferring messages among packages.,Neutral
954,"(7, 95)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
955,"(7, 96)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
956,"(7, 97)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
957,"(7, 98)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
958,"(7, 99)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
959,"(7, 100)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
960,"(7, 101)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
961,"(7, 102)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
962,"(7, 103)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
963,"(7, 104)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow a user to foward notification to someone else at the site.,Neutral
964,"(7, 105)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
965,"(7, 106)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall define, populate, and retrieve information about user classes.",Neutral
966,"(7, 107)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
967,"(7, 108)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
968,"(7, 109)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
969,"(7, 110)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow concurrent membership in more than one User Class.,Neutral
970,"(7, 111)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow membership in only one User Class.,Neutral
971,"(7, 112)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
972,"(7, 113)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
973,"(7, 114)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall improve accessibility of online clinical information and results.,Neutral
974,"(7, 115)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
975,"(7, 116)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
976,"(7, 117)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
977,"(7, 118)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
978,"(7, 119)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall make the traditional order entry processes more practical.,Neutral
979,"(7, 120)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
980,"(7, 121)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
981,"(7, 122)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
982,"(7, 123)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
983,"(7, 124)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
984,"(7, 125)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
985,"(7, 126)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
986,"(7, 127)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
987,"(7, 128)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
988,"(7, 129)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
989,"(7, 130)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
990,"(7, 131)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall delete history of received immunizations.,Neutral
991,"(7, 132)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
992,"(7, 133)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
993,"(7, 134)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
994,"(7, 135)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system will provide the ability to register patients of all types.,Neutral
995,"(7, 136)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
996,"(7, 137)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
997,"(7, 138)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
998,"(7, 139)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
999,"(7, 140)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
1000,"(7, 141)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
1001,"(7, 142)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
1002,"(7, 143)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
1003,"(7, 144)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
1004,"(7, 145)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
1005,"(7, 146)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
1006,"(7, 147)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
1007,"(7, 148)",The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1008,"(8, 9)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system's pilot program shall use a smart card to digitally sign medication orders.,Neutral
1009,"(8, 10)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system's pilot program shall require a handwritten signature for medication orders.,Neutral
1010,"(8, 11)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",Neutral
1011,"(8, 12)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Neutral
1012,"(8, 13)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1013,"(8, 14)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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).",Neutral
1014,"(8, 15)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
1015,"(8, 16)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
1016,"(8, 17)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
1017,"(8, 18)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
1018,"(8, 19)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1019,"(8, 20)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1020,"(8, 21)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
1021,"(8, 22)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
1022,"(8, 23)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1023,"(8, 24)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1024,"(8, 25)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
1025,"(8, 26)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1026,"(8, 27)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1027,"(8, 28)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1028,"(8, 29)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1029,"(8, 30)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
1030,"(8, 31)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
1031,"(8, 32)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
1032,"(8, 33)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
1033,"(8, 34)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
1034,"(8, 35)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
1035,"(8, 36)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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).",Neutral
1036,"(8, 37)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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).",Neutral
1037,"(8, 38)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
1038,"(8, 39)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
1039,"(8, 40)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
1040,"(8, 41)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall improve efficiency of entering orders.,Neutral
1041,"(8, 42)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
1042,"(8, 43)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow complete order sets to be predefined and personalized.,Neutral
1043,"(8, 44)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow order checking.,Neutral
1044,"(8, 45)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1045,"(8, 46)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1046,"(8, 47)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
1047,"(8, 48)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
1048,"(8, 49)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
1049,"(8, 50)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall support role-based access for security controls.,Neutral
1050,"(8, 51)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall support audit capability.,Neutral
1051,"(8, 52)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
1052,"(8, 53)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall support the requirements for all codified data ,Neutral
1053,"(8, 54)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
1054,"(8, 55)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
1055,"(8, 56)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require the entry of an access code to gain access to the system.,Neutral
1056,"(8, 57)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
1057,"(8, 58)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
1058,"(8, 59)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1059,"(8, 60)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1060,"(8, 61)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
1061,"(8, 62)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall have pre-defined progress note templates.,Neutral
1062,"(8, 63)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
1063,"(8, 64)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
1064,"(8, 65)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require only a smart card to digitally sign an order.,Neutral
1065,"(8, 66)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
1066,"(8, 67)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow users to enter time in several different formats.,Neutral
1067,"(8, 68)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1068,"(8, 69)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1069,"(8, 70)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1070,"(8, 71)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1071,"(8, 72)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
1072,"(8, 73)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1073,"(8, 74)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
1074,"(8, 75)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall have a option to release unsigned orders to services,Neutral
1075,"(8, 76)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1076,"(8, 77)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
1077,"(8, 78)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
1078,"(8, 79)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1079,"(8, 80)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
1080,"(8, 81)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
1081,"(8, 82)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
1082,"(8, 83)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
1083,"(8, 84)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
1084,"(8, 85)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
1085,"(8, 86)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
1086,"(8, 87)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
1087,"(8, 88)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
1088,"(8, 89)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall not allow mandatory notifications to be disabled.,Neutral
1089,"(8, 90)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow users to disable unwanted notifications as desired.,Neutral
1090,"(8, 91)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
1091,"(8, 92)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
1092,"(8, 93)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
1093,"(8, 94)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall use any protocol for transferring messages among packages.,Neutral
1094,"(8, 95)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
1095,"(8, 96)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
1096,"(8, 97)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
1097,"(8, 98)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
1098,"(8, 99)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
1099,"(8, 100)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
1100,"(8, 101)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
1101,"(8, 102)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
1102,"(8, 103)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
1103,"(8, 104)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow a user to foward notification to someone else at the site.,Neutral
1104,"(8, 105)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
1105,"(8, 106)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall define, populate, and retrieve information about user classes.",Neutral
1106,"(8, 107)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1107,"(8, 108)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1108,"(8, 109)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
1109,"(8, 110)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow concurrent membership in more than one User Class.,Neutral
1110,"(8, 111)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow membership in only one User Class.,Neutral
1111,"(8, 112)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
1112,"(8, 113)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1113,"(8, 114)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall improve accessibility of online clinical information and results.,Neutral
1114,"(8, 115)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1115,"(8, 116)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
1116,"(8, 117)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
1117,"(8, 118)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
1118,"(8, 119)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall make the traditional order entry processes more practical.,Neutral
1119,"(8, 120)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
1120,"(8, 121)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
1121,"(8, 122)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
1122,"(8, 123)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
1123,"(8, 124)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1124,"(8, 125)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
1125,"(8, 126)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
1126,"(8, 127)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1127,"(8, 128)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
1128,"(8, 129)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1129,"(8, 130)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
1130,"(8, 131)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall delete history of received immunizations.,Neutral
1131,"(8, 132)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
1132,"(8, 133)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
1133,"(8, 134)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
1134,"(8, 135)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system will provide the ability to register patients of all types.,Neutral
1135,"(8, 136)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
1136,"(8, 137)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
1137,"(8, 138)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
1138,"(8, 139)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
1139,"(8, 140)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
1140,"(8, 141)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
1141,"(8, 142)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
1142,"(8, 143)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
1143,"(8, 144)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
1144,"(8, 145)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,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.,Neutral
1145,"(8, 146)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
1146,"(8, 147)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
1147,"(8, 148)",The system shall require digital signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy.,"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.",Neutral
1148,"(9, 10)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system's pilot program shall require a handwritten signature for medication orders.,Conflict
1149,"(9, 11)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",Neutral
1150,"(9, 12)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Neutral
1151,"(9, 13)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1152,"(9, 14)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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).",Neutral
1153,"(9, 15)",The system's pilot program shall use a smart card to digitally sign medication orders.,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.,Neutral
1154,"(9, 16)",The system's pilot program shall use a smart card to digitally sign medication orders.,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.,Neutral
1155,"(9, 17)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
1156,"(9, 18)",The system's pilot program shall use a smart card to digitally sign medication orders.,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.,Neutral
1157,"(9, 19)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1158,"(9, 20)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1159,"(9, 21)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
1160,"(9, 22)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
1161,"(9, 23)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1162,"(9, 24)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1163,"(9, 25)",The system's pilot program shall use a smart card to digitally sign medication orders.,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.,Neutral
1164,"(9, 26)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1165,"(9, 27)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1166,"(9, 28)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1167,"(9, 29)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1168,"(9, 30)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
1169,"(9, 31)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
1170,"(9, 32)",The system's pilot program shall use a smart card to digitally sign medication orders.,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.,Neutral
1171,"(9, 33)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
1172,"(9, 34)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
1173,"(9, 35)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
1174,"(9, 36)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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).",Neutral
1175,"(9, 37)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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).",Neutral
1176,"(9, 38)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
1177,"(9, 39)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
1178,"(9, 40)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
1179,"(9, 41)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall improve efficiency of entering orders.,Neutral
1180,"(9, 42)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
1181,"(9, 43)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow complete order sets to be predefined and personalized.,Neutral
1182,"(9, 44)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow order checking.,Neutral
1183,"(9, 45)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1184,"(9, 46)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1185,"(9, 47)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
1186,"(9, 48)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
1187,"(9, 49)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
1188,"(9, 50)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall support role-based access for security controls.,Neutral
1189,"(9, 51)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall support audit capability.,Neutral
1190,"(9, 52)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
1191,"(9, 53)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall support the requirements for all codified data ,Neutral
1192,"(9, 54)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
1193,"(9, 55)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
1194,"(9, 56)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall require the entry of an access code to gain access to the system.,Neutral
1195,"(9, 57)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
1196,"(9, 58)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
1197,"(9, 59)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1198,"(9, 60)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1199,"(9, 61)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
1200,"(9, 62)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall have pre-defined progress note templates.,Neutral
1201,"(9, 63)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
1202,"(9, 64)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
1203,"(9, 65)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall require only a smart card to digitally sign an order.,Neutral
1204,"(9, 66)",The system's pilot program shall use a smart card to digitally sign medication orders.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
1205,"(9, 67)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow users to enter time in several different formats.,Neutral
1206,"(9, 68)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1207,"(9, 69)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1208,"(9, 70)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1209,"(9, 71)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1210,"(9, 72)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
1211,"(9, 73)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1212,"(9, 74)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
1213,"(9, 75)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall have a option to release unsigned orders to services,Neutral
1214,"(9, 76)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1215,"(9, 77)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
1216,"(9, 78)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
1217,"(9, 79)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1218,"(9, 80)",The system's pilot program shall use a smart card to digitally sign medication orders.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
1219,"(9, 81)",The system's pilot program shall use a smart card to digitally sign medication orders.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
1220,"(9, 82)",The system's pilot program shall use a smart card to digitally sign medication orders.,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.,Neutral
1221,"(9, 83)",The system's pilot program shall use a smart card to digitally sign medication orders.,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.,Neutral
1222,"(9, 84)",The system's pilot program shall use a smart card to digitally sign medication orders.,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.,Neutral
1223,"(9, 85)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
1224,"(9, 86)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
1225,"(9, 87)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
1226,"(9, 88)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
1227,"(9, 89)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall not allow mandatory notifications to be disabled.,Neutral
1228,"(9, 90)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow users to disable unwanted notifications as desired.,Neutral
1229,"(9, 91)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
1230,"(9, 92)",The system's pilot program shall use a smart card to digitally sign medication orders.,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.,Neutral
1231,"(9, 93)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
1232,"(9, 94)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall use any protocol for transferring messages among packages.,Neutral
1233,"(9, 95)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
1234,"(9, 96)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
1235,"(9, 97)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
1236,"(9, 98)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
1237,"(9, 99)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
1238,"(9, 100)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
1239,"(9, 101)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
1240,"(9, 102)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
1241,"(9, 103)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
1242,"(9, 104)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow a user to foward notification to someone else at the site.,Neutral
1243,"(9, 105)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
1244,"(9, 106)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall define, populate, and retrieve information about user classes.",Neutral
1245,"(9, 107)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1246,"(9, 108)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1247,"(9, 109)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
1248,"(9, 110)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow concurrent membership in more than one User Class.,Neutral
1249,"(9, 111)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow membership in only one User Class.,Neutral
1250,"(9, 112)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
1251,"(9, 113)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1252,"(9, 114)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall improve accessibility of online clinical information and results.,Neutral
1253,"(9, 115)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1254,"(9, 116)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
1255,"(9, 117)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
1256,"(9, 118)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
1257,"(9, 119)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall make the traditional order entry processes more practical.,Neutral
1258,"(9, 120)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
1259,"(9, 121)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
1260,"(9, 122)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
1261,"(9, 123)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
1262,"(9, 124)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1263,"(9, 125)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
1264,"(9, 126)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
1265,"(9, 127)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1266,"(9, 128)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
1267,"(9, 129)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1268,"(9, 130)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
1269,"(9, 131)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall delete history of received immunizations.,Neutral
1270,"(9, 132)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
1271,"(9, 133)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
1272,"(9, 134)",The system's pilot program shall use a smart card to digitally sign medication orders.,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.,Neutral
1273,"(9, 135)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system will provide the ability to register patients of all types.,Neutral
1274,"(9, 136)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
1275,"(9, 137)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
1276,"(9, 138)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
1277,"(9, 139)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
1278,"(9, 140)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
1279,"(9, 141)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
1280,"(9, 142)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
1281,"(9, 143)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
1282,"(9, 144)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
1283,"(9, 145)",The system's pilot program shall use a smart card to digitally sign medication orders.,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.,Neutral
1284,"(9, 146)",The system's pilot program shall use a smart card to digitally sign medication orders.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
1285,"(9, 147)",The system's pilot program shall use a smart card to digitally sign medication orders.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
1286,"(9, 148)",The system's pilot program shall use a smart card to digitally sign medication orders.,"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.",Neutral
1287,"(10, 11)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",Neutral
1288,"(10, 12)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Neutral
1289,"(10, 13)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1290,"(10, 14)",The system's pilot program shall require a handwritten signature for medication orders.,"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).",Neutral
1291,"(10, 15)",The system's pilot program shall require a handwritten signature for medication orders.,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.,Neutral
1292,"(10, 16)",The system's pilot program shall require a handwritten signature for medication orders.,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.,Neutral
1293,"(10, 17)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
1294,"(10, 18)",The system's pilot program shall require a handwritten signature for medication orders.,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.,Neutral
1295,"(10, 19)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1296,"(10, 20)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1297,"(10, 21)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
1298,"(10, 22)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
1299,"(10, 23)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1300,"(10, 24)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1301,"(10, 25)",The system's pilot program shall require a handwritten signature for medication orders.,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.,Neutral
1302,"(10, 26)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1303,"(10, 27)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1304,"(10, 28)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1305,"(10, 29)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1306,"(10, 30)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
1307,"(10, 31)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
1308,"(10, 32)",The system's pilot program shall require a handwritten signature for medication orders.,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.,Neutral
1309,"(10, 33)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
1310,"(10, 34)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
1311,"(10, 35)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
1312,"(10, 36)",The system's pilot program shall require a handwritten signature for medication orders.,"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).",Neutral
1313,"(10, 37)",The system's pilot program shall require a handwritten signature for medication orders.,"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).",Neutral
1314,"(10, 38)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
1315,"(10, 39)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
1316,"(10, 40)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
1317,"(10, 41)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall improve efficiency of entering orders.,Neutral
1318,"(10, 42)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
1319,"(10, 43)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow complete order sets to be predefined and personalized.,Neutral
1320,"(10, 44)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow order checking.,Neutral
1321,"(10, 45)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1322,"(10, 46)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1323,"(10, 47)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
1324,"(10, 48)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
1325,"(10, 49)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
1326,"(10, 50)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall support role-based access for security controls.,Neutral
1327,"(10, 51)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall support audit capability.,Neutral
1328,"(10, 52)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
1329,"(10, 53)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall support the requirements for all codified data ,Neutral
1330,"(10, 54)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
1331,"(10, 55)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
1332,"(10, 56)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall require the entry of an access code to gain access to the system.,Neutral
1333,"(10, 57)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
1334,"(10, 58)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
1335,"(10, 59)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1336,"(10, 60)",The system's pilot program shall require a handwritten signature for medication orders.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1337,"(10, 61)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
1338,"(10, 62)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall have pre-defined progress note templates.,Neutral
1339,"(10, 63)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
1340,"(10, 64)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
1341,"(10, 65)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall require only a smart card to digitally sign an order.,Neutral
1342,"(10, 66)",The system's pilot program shall require a handwritten signature for medication orders.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
1343,"(10, 67)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow users to enter time in several different formats.,Neutral
1344,"(10, 68)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1345,"(10, 69)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1346,"(10, 70)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1347,"(10, 71)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1348,"(10, 72)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
1349,"(10, 73)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1350,"(10, 74)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
1351,"(10, 75)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall have a option to release unsigned orders to services,Neutral
1352,"(10, 76)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1353,"(10, 77)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
1354,"(10, 78)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
1355,"(10, 79)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1356,"(10, 80)",The system's pilot program shall require a handwritten signature for medication orders.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
1357,"(10, 81)",The system's pilot program shall require a handwritten signature for medication orders.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
1358,"(10, 82)",The system's pilot program shall require a handwritten signature for medication orders.,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.,Neutral
1359,"(10, 83)",The system's pilot program shall require a handwritten signature for medication orders.,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.,Neutral
1360,"(10, 84)",The system's pilot program shall require a handwritten signature for medication orders.,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.,Neutral
1361,"(10, 85)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
1362,"(10, 86)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
1363,"(10, 87)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
1364,"(10, 88)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
1365,"(10, 89)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall not allow mandatory notifications to be disabled.,Neutral
1366,"(10, 90)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow users to disable unwanted notifications as desired.,Neutral
1367,"(10, 91)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
1368,"(10, 92)",The system's pilot program shall require a handwritten signature for medication orders.,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.,Neutral
1369,"(10, 93)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
1370,"(10, 94)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall use any protocol for transferring messages among packages.,Neutral
1371,"(10, 95)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
1372,"(10, 96)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
1373,"(10, 97)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
1374,"(10, 98)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
1375,"(10, 99)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
1376,"(10, 100)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
1377,"(10, 101)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
1378,"(10, 102)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
1379,"(10, 103)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
1380,"(10, 104)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow a user to foward notification to someone else at the site.,Neutral
1381,"(10, 105)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
1382,"(10, 106)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall define, populate, and retrieve information about user classes.",Neutral
1383,"(10, 107)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1384,"(10, 108)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1385,"(10, 109)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
1386,"(10, 110)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow concurrent membership in more than one User Class.,Neutral
1387,"(10, 111)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow membership in only one User Class.,Neutral
1388,"(10, 112)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
1389,"(10, 113)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1390,"(10, 114)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall improve accessibility of online clinical information and results.,Neutral
1391,"(10, 115)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1392,"(10, 116)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
1393,"(10, 117)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
1394,"(10, 118)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
1395,"(10, 119)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall make the traditional order entry processes more practical.,Neutral
1396,"(10, 120)",The system's pilot program shall require a handwritten signature for medication orders.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
1397,"(10, 121)",The system's pilot program shall require a handwritten signature for medication orders.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
1398,"(10, 122)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
1399,"(10, 123)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
1400,"(10, 124)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1401,"(10, 125)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
1402,"(10, 126)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
1403,"(10, 127)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1404,"(10, 128)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
1405,"(10, 129)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1406,"(10, 130)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
1407,"(10, 131)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall delete history of received immunizations.,Neutral
1408,"(10, 132)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
1409,"(10, 133)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
1410,"(10, 134)",The system's pilot program shall require a handwritten signature for medication orders.,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.,Neutral
1411,"(10, 135)",The system's pilot program shall require a handwritten signature for medication orders.,The system will provide the ability to register patients of all types.,Neutral
1412,"(10, 136)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
1413,"(10, 137)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
1414,"(10, 138)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
1415,"(10, 139)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
1416,"(10, 140)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
1417,"(10, 141)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
1418,"(10, 142)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
1419,"(10, 143)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
1420,"(10, 144)",The system's pilot program shall require a handwritten signature for medication orders.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
1421,"(10, 145)",The system's pilot program shall require a handwritten signature for medication orders.,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.,Neutral
1422,"(10, 146)",The system's pilot program shall require a handwritten signature for medication orders.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
1423,"(10, 147)",The system's pilot program shall require a handwritten signature for medication orders.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
1424,"(10, 148)",The system's pilot program shall require a handwritten signature for medication orders.,"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.",Neutral
1425,"(11, 12)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Neutral
1426,"(11, 13)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1427,"(11, 14)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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).",Neutral
1428,"(11, 15)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",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.,Neutral
1429,"(11, 16)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",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.,Neutral
1430,"(11, 17)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
1431,"(11, 18)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",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.,Neutral
1432,"(11, 19)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1433,"(11, 20)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1434,"(11, 21)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
1435,"(11, 22)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
1436,"(11, 23)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1437,"(11, 24)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1438,"(11, 25)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",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.,Neutral
1439,"(11, 26)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1440,"(11, 27)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1441,"(11, 28)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1442,"(11, 29)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1443,"(11, 30)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
1444,"(11, 31)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
1445,"(11, 32)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",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.,Neutral
1446,"(11, 33)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
1447,"(11, 34)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
1448,"(11, 35)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
1449,"(11, 36)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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).",Neutral
1450,"(11, 37)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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).",Neutral
1451,"(11, 38)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
1452,"(11, 39)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
1453,"(11, 40)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
1454,"(11, 41)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall improve efficiency of entering orders.,Neutral
1455,"(11, 42)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
1456,"(11, 43)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow complete order sets to be predefined and personalized.,Neutral
1457,"(11, 44)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow order checking.,Neutral
1458,"(11, 45)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1459,"(11, 46)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1460,"(11, 47)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
1461,"(11, 48)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
1462,"(11, 49)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
1463,"(11, 50)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall support role-based access for security controls.,Neutral
1464,"(11, 51)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall support audit capability.,Neutral
1465,"(11, 52)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
1466,"(11, 53)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall support the requirements for all codified data ,Neutral
1467,"(11, 54)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
1468,"(11, 55)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
1469,"(11, 56)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall require the entry of an access code to gain access to the system.,Neutral
1470,"(11, 57)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
1471,"(11, 58)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
1472,"(11, 59)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1473,"(11, 60)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1474,"(11, 61)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
1475,"(11, 62)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall have pre-defined progress note templates.,Neutral
1476,"(11, 63)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
1477,"(11, 64)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
1478,"(11, 65)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall require only a smart card to digitally sign an order.,Neutral
1479,"(11, 66)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
1480,"(11, 67)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow users to enter time in several different formats.,Neutral
1481,"(11, 68)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1482,"(11, 69)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1483,"(11, 70)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1484,"(11, 71)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1485,"(11, 72)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
1486,"(11, 73)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1487,"(11, 74)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
1488,"(11, 75)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall have a option to release unsigned orders to services,Neutral
1489,"(11, 76)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1490,"(11, 77)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
1491,"(11, 78)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
1492,"(11, 79)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1493,"(11, 80)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
1494,"(11, 81)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
1495,"(11, 82)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",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.,Neutral
1496,"(11, 83)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",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.,Neutral
1497,"(11, 84)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",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.,Neutral
1498,"(11, 85)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
1499,"(11, 86)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
1500,"(11, 87)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
1501,"(11, 88)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
1502,"(11, 89)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall not allow mandatory notifications to be disabled.,Neutral
1503,"(11, 90)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow users to disable unwanted notifications as desired.,Neutral
1504,"(11, 91)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
1505,"(11, 92)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",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.,Neutral
1506,"(11, 93)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
1507,"(11, 94)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall use any protocol for transferring messages among packages.,Neutral
1508,"(11, 95)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
1509,"(11, 96)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
1510,"(11, 97)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
1511,"(11, 98)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
1512,"(11, 99)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
1513,"(11, 100)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
1514,"(11, 101)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
1515,"(11, 102)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
1516,"(11, 103)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
1517,"(11, 104)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow a user to foward notification to someone else at the site.,Neutral
1518,"(11, 105)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
1519,"(11, 106)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall define, populate, and retrieve information about user classes.",Neutral
1520,"(11, 107)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1521,"(11, 108)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1522,"(11, 109)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
1523,"(11, 110)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow concurrent membership in more than one User Class.,Neutral
1524,"(11, 111)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow membership in only one User Class.,Neutral
1525,"(11, 112)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
1526,"(11, 113)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1527,"(11, 114)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall improve accessibility of online clinical information and results.,Neutral
1528,"(11, 115)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1529,"(11, 116)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
1530,"(11, 117)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
1531,"(11, 118)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
1532,"(11, 119)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall make the traditional order entry processes more practical.,Neutral
1533,"(11, 120)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
1534,"(11, 121)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
1535,"(11, 122)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
1536,"(11, 123)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
1537,"(11, 124)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1538,"(11, 125)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
1539,"(11, 126)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
1540,"(11, 127)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1541,"(11, 128)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
1542,"(11, 129)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1543,"(11, 130)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
1544,"(11, 131)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall delete history of received immunizations.,Neutral
1545,"(11, 132)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
1546,"(11, 133)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
1547,"(11, 134)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",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.,Neutral
1548,"(11, 135)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system will provide the ability to register patients of all types.,Neutral
1549,"(11, 136)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
1550,"(11, 137)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
1551,"(11, 138)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
1552,"(11, 139)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
1553,"(11, 140)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
1554,"(11, 141)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
1555,"(11, 142)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
1556,"(11, 143)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
1557,"(11, 144)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
1558,"(11, 145)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",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.,Neutral
1559,"(11, 146)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
1560,"(11, 147)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
1561,"(11, 148)","The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature.","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.",Neutral
1562,"(12, 13)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1563,"(12, 14)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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).",Neutral
1564,"(12, 15)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",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.,Neutral
1565,"(12, 16)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",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.,Neutral
1566,"(12, 17)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
1567,"(12, 18)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",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.,Neutral
1568,"(12, 19)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1569,"(12, 20)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1570,"(12, 21)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
1571,"(12, 22)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
1572,"(12, 23)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1573,"(12, 24)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1574,"(12, 25)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",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.,Neutral
1575,"(12, 26)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1576,"(12, 27)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1577,"(12, 28)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1578,"(12, 29)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1579,"(12, 30)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
1580,"(12, 31)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
1581,"(12, 32)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",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.,Neutral
1582,"(12, 33)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
1583,"(12, 34)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
1584,"(12, 35)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
1585,"(12, 36)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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).",Neutral
1586,"(12, 37)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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).",Neutral
1587,"(12, 38)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
1588,"(12, 39)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
1589,"(12, 40)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
1590,"(12, 41)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall improve efficiency of entering orders.,Neutral
1591,"(12, 42)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
1592,"(12, 43)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow complete order sets to be predefined and personalized.,Neutral
1593,"(12, 44)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow order checking.,Neutral
1594,"(12, 45)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1595,"(12, 46)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1596,"(12, 47)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
1597,"(12, 48)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
1598,"(12, 49)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
1599,"(12, 50)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall support role-based access for security controls.,Neutral
1600,"(12, 51)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall support audit capability.,Neutral
1601,"(12, 52)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
1602,"(12, 53)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall support the requirements for all codified data ,Neutral
1603,"(12, 54)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
1604,"(12, 55)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
1605,"(12, 56)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall require the entry of an access code to gain access to the system.,Neutral
1606,"(12, 57)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
1607,"(12, 58)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
1608,"(12, 59)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1609,"(12, 60)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1610,"(12, 61)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
1611,"(12, 62)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall have pre-defined progress note templates.,Neutral
1612,"(12, 63)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
1613,"(12, 64)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
1614,"(12, 65)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall require only a smart card to digitally sign an order.,Neutral
1615,"(12, 66)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
1616,"(12, 67)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow users to enter time in several different formats.,Neutral
1617,"(12, 68)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1618,"(12, 69)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1619,"(12, 70)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1620,"(12, 71)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1621,"(12, 72)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
1622,"(12, 73)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1623,"(12, 74)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
1624,"(12, 75)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall have a option to release unsigned orders to services,Neutral
1625,"(12, 76)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1626,"(12, 77)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
1627,"(12, 78)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
1628,"(12, 79)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1629,"(12, 80)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
1630,"(12, 81)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
1631,"(12, 82)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",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.,Neutral
1632,"(12, 83)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",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.,Neutral
1633,"(12, 84)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",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.,Neutral
1634,"(12, 85)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
1635,"(12, 86)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
1636,"(12, 87)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
1637,"(12, 88)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
1638,"(12, 89)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall not allow mandatory notifications to be disabled.,Neutral
1639,"(12, 90)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow users to disable unwanted notifications as desired.,Neutral
1640,"(12, 91)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
1641,"(12, 92)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",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.,Neutral
1642,"(12, 93)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
1643,"(12, 94)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall use any protocol for transferring messages among packages.,Neutral
1644,"(12, 95)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
1645,"(12, 96)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
1646,"(12, 97)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
1647,"(12, 98)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
1648,"(12, 99)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
1649,"(12, 100)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
1650,"(12, 101)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
1651,"(12, 102)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
1652,"(12, 103)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
1653,"(12, 104)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow a user to foward notification to someone else at the site.,Neutral
1654,"(12, 105)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
1655,"(12, 106)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall define, populate, and retrieve information about user classes.",Neutral
1656,"(12, 107)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1657,"(12, 108)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1658,"(12, 109)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
1659,"(12, 110)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow concurrent membership in more than one User Class.,Neutral
1660,"(12, 111)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow membership in only one User Class.,Neutral
1661,"(12, 112)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
1662,"(12, 113)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1663,"(12, 114)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall improve accessibility of online clinical information and results.,Neutral
1664,"(12, 115)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1665,"(12, 116)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
1666,"(12, 117)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
1667,"(12, 118)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
1668,"(12, 119)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall make the traditional order entry processes more practical.,Neutral
1669,"(12, 120)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
1670,"(12, 121)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
1671,"(12, 122)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
1672,"(12, 123)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
1673,"(12, 124)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1674,"(12, 125)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
1675,"(12, 126)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
1676,"(12, 127)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1677,"(12, 128)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
1678,"(12, 129)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1679,"(12, 130)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
1680,"(12, 131)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall delete history of received immunizations.,Neutral
1681,"(12, 132)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
1682,"(12, 133)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
1683,"(12, 134)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",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.,Neutral
1684,"(12, 135)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system will provide the ability to register patients of all types.,Neutral
1685,"(12, 136)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
1686,"(12, 137)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
1687,"(12, 138)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
1688,"(12, 139)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
1689,"(12, 140)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
1690,"(12, 141)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
1691,"(12, 142)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
1692,"(12, 143)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
1693,"(12, 144)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
1694,"(12, 145)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",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.,Neutral
1695,"(12, 146)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
1696,"(12, 147)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
1697,"(12, 148)","The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient.","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.",Neutral
1698,"(13, 14)","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.","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).",Neutral
1699,"(13, 15)","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.",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.,Neutral
1700,"(13, 16)","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.",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.,Neutral
1701,"(13, 17)","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.",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
1702,"(13, 18)","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.",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.,Neutral
1703,"(13, 19)","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.",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1704,"(13, 20)","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.",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1705,"(13, 21)","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.",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
1706,"(13, 22)","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.",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
1707,"(13, 23)","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.","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.",Neutral
1708,"(13, 24)","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.","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.",Neutral
1709,"(13, 25)","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.",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.,Neutral
1710,"(13, 26)","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.",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1711,"(13, 27)","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.",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1712,"(13, 28)","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.","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.",Neutral
1713,"(13, 29)","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.","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.",Neutral
1714,"(13, 30)","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.",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
1715,"(13, 31)","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.",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
1716,"(13, 32)","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.",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.,Neutral
1717,"(13, 33)","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.",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
1718,"(13, 34)","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.",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
1719,"(13, 35)","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.","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
1720,"(13, 36)","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.","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).",Neutral
1721,"(13, 37)","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.","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).",Neutral
1722,"(13, 38)","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.","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
1723,"(13, 39)","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.",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
1724,"(13, 40)","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.",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
1725,"(13, 41)","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.",The system shall improve efficiency of entering orders.,Neutral
1726,"(13, 42)","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.",The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
1727,"(13, 43)","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.",The system shall allow complete order sets to be predefined and personalized.,Neutral
1728,"(13, 44)","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.",The system shall allow order checking.,Neutral
1729,"(13, 45)","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.","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1730,"(13, 46)","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.","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1731,"(13, 47)","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.",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
1732,"(13, 48)","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.",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
1733,"(13, 49)","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.",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
1734,"(13, 50)","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.",The system shall support role-based access for security controls.,Neutral
1735,"(13, 51)","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.",The system shall support audit capability.,Neutral
1736,"(13, 52)","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.",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
1737,"(13, 53)","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.",The system shall support the requirements for all codified data ,Neutral
1738,"(13, 54)","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.","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
1739,"(13, 55)","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.",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
1740,"(13, 56)","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.",The system shall require the entry of an access code to gain access to the system.,Neutral
1741,"(13, 57)","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.",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
1742,"(13, 58)","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.",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
1743,"(13, 59)","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.",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1744,"(13, 60)","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.",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1745,"(13, 61)","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.","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
1746,"(13, 62)","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.",The system shall have pre-defined progress note templates.,Neutral
1747,"(13, 63)","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.",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
1748,"(13, 64)","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.","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
1749,"(13, 65)","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.",The system shall require only a smart card to digitally sign an order.,Neutral
1750,"(13, 66)","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.",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
1751,"(13, 67)","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.",The system shall allow users to enter time in several different formats.,Neutral
1752,"(13, 68)","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.",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1753,"(13, 69)","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.",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1754,"(13, 70)","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.","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.",Neutral
1755,"(13, 71)","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.","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.",Neutral
1756,"(13, 72)","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.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
1757,"(13, 73)","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.","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.",Neutral
1758,"(13, 74)","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.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
1759,"(13, 75)","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.",The system shall have a option to release unsigned orders to services,Neutral
1760,"(13, 76)","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.","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.",Neutral
1761,"(13, 77)","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.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
1762,"(13, 78)","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.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
1763,"(13, 79)","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.","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.",Neutral
1764,"(13, 80)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
1765,"(13, 81)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
1766,"(13, 82)","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.",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.,Neutral
1767,"(13, 83)","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.",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.,Neutral
1768,"(13, 84)","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.",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.,Neutral
1769,"(13, 85)","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.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
1770,"(13, 86)","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.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
1771,"(13, 87)","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.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
1772,"(13, 88)","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.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
1773,"(13, 89)","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.",The system shall not allow mandatory notifications to be disabled.,Neutral
1774,"(13, 90)","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.",The system shall allow users to disable unwanted notifications as desired.,Neutral
1775,"(13, 91)","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.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
1776,"(13, 92)","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.",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.,Neutral
1777,"(13, 93)","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.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
1778,"(13, 94)","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.",The system shall use any protocol for transferring messages among packages.,Neutral
1779,"(13, 95)","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.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
1780,"(13, 96)","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.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
1781,"(13, 97)","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.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
1782,"(13, 98)","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.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
1783,"(13, 99)","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.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
1784,"(13, 100)","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.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
1785,"(13, 101)","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.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
1786,"(13, 102)","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.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
1787,"(13, 103)","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.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
1788,"(13, 104)","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.",The system shall allow a user to foward notification to someone else at the site.,Neutral
1789,"(13, 105)","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.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
1790,"(13, 106)","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.","The system shall define, populate, and retrieve information about user classes.",Neutral
1791,"(13, 107)","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.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1792,"(13, 108)","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.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1793,"(13, 109)","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.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
1794,"(13, 110)","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.",The system shall allow concurrent membership in more than one User Class.,Neutral
1795,"(13, 111)","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.",The system shall allow membership in only one User Class.,Neutral
1796,"(13, 112)","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.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
1797,"(13, 113)","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.","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.",Neutral
1798,"(13, 114)","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.",The system shall improve accessibility of online clinical information and results.,Neutral
1799,"(13, 115)","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.","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.",Neutral
1800,"(13, 116)","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.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
1801,"(13, 117)","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.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
1802,"(13, 118)","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.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
1803,"(13, 119)","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.",The system shall make the traditional order entry processes more practical.,Neutral
1804,"(13, 120)","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.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
1805,"(13, 121)","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.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
1806,"(13, 122)","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.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
1807,"(13, 123)","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.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
1808,"(13, 124)","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.","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.",Neutral
1809,"(13, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
1810,"(13, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
1811,"(13, 127)","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.","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.",Neutral
1812,"(13, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
1813,"(13, 129)","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.","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.",Neutral
1814,"(13, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
1815,"(13, 131)","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.",The system shall delete history of received immunizations.,Neutral
1816,"(13, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
1817,"(13, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
1818,"(13, 134)","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.",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.,Neutral
1819,"(13, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
1820,"(13, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
1821,"(13, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
1822,"(13, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
1823,"(13, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
1824,"(13, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
1825,"(13, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
1826,"(13, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
1827,"(13, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
1828,"(13, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
1829,"(13, 145)","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.",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.,Neutral
1830,"(13, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
1831,"(13, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
1832,"(13, 148)","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.","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.",Neutral
1833,"(14, 15)","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).",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.,Neutral
1834,"(14, 16)","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).",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.,Neutral
1835,"(14, 17)","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).",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
1836,"(14, 18)","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).",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.,Neutral
1837,"(14, 19)","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).",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1838,"(14, 20)","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).",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1839,"(14, 21)","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).",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
1840,"(14, 22)","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).",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
1841,"(14, 23)","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).","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.",Neutral
1842,"(14, 24)","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).","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.",Neutral
1843,"(14, 25)","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).",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.,Neutral
1844,"(14, 26)","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).",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1845,"(14, 27)","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).",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1846,"(14, 28)","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).","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.",Neutral
1847,"(14, 29)","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).","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.",Neutral
1848,"(14, 30)","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).",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
1849,"(14, 31)","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).",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
1850,"(14, 32)","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).",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.,Neutral
1851,"(14, 33)","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).",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
1852,"(14, 34)","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).",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
1853,"(14, 35)","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).","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
1854,"(14, 36)","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).","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).",Neutral
1855,"(14, 37)","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).","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).",Neutral
1856,"(14, 38)","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).","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
1857,"(14, 39)","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).",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
1858,"(14, 40)","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).",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
1859,"(14, 41)","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).",The system shall improve efficiency of entering orders.,Neutral
1860,"(14, 42)","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).",The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
1861,"(14, 43)","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).",The system shall allow complete order sets to be predefined and personalized.,Neutral
1862,"(14, 44)","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).",The system shall allow order checking.,Neutral
1863,"(14, 45)","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).","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1864,"(14, 46)","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).","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1865,"(14, 47)","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).",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
1866,"(14, 48)","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).",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
1867,"(14, 49)","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).",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
1868,"(14, 50)","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).",The system shall support role-based access for security controls.,Neutral
1869,"(14, 51)","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).",The system shall support audit capability.,Neutral
1870,"(14, 52)","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).",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
1871,"(14, 53)","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).",The system shall support the requirements for all codified data ,Neutral
1872,"(14, 54)","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).","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
1873,"(14, 55)","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).",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
1874,"(14, 56)","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).",The system shall require the entry of an access code to gain access to the system.,Neutral
1875,"(14, 57)","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).",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
1876,"(14, 58)","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).",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
1877,"(14, 59)","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).",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1878,"(14, 60)","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).",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
1879,"(14, 61)","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).","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
1880,"(14, 62)","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).",The system shall have pre-defined progress note templates.,Neutral
1881,"(14, 63)","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).",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
1882,"(14, 64)","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).","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
1883,"(14, 65)","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).",The system shall require only a smart card to digitally sign an order.,Neutral
1884,"(14, 66)","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).",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
1885,"(14, 67)","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).",The system shall allow users to enter time in several different formats.,Neutral
1886,"(14, 68)","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).",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1887,"(14, 69)","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).",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
1888,"(14, 70)","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).","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.",Neutral
1889,"(14, 71)","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).","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.",Neutral
1890,"(14, 72)","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).",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
1891,"(14, 73)","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).","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.",Neutral
1892,"(14, 74)","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).",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
1893,"(14, 75)","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).",The system shall have a option to release unsigned orders to services,Neutral
1894,"(14, 76)","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).","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.",Neutral
1895,"(14, 77)","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).",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
1896,"(14, 78)","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).",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
1897,"(14, 79)","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).","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.",Neutral
1898,"(14, 80)","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).",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
1899,"(14, 81)","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).",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
1900,"(14, 82)","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).",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.,Neutral
1901,"(14, 83)","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).",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.,Neutral
1902,"(14, 84)","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).",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.,Neutral
1903,"(14, 85)","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).",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
1904,"(14, 86)","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).",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
1905,"(14, 87)","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).",The system shall display a message telling the user that the selected patient is deceased.,Neutral
1906,"(14, 88)","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).",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
1907,"(14, 89)","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).",The system shall not allow mandatory notifications to be disabled.,Neutral
1908,"(14, 90)","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).",The system shall allow users to disable unwanted notifications as desired.,Neutral
1909,"(14, 91)","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).",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
1910,"(14, 92)","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).",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.,Neutral
1911,"(14, 93)","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).",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
1912,"(14, 94)","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).",The system shall use any protocol for transferring messages among packages.,Neutral
1913,"(14, 95)","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).",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
1914,"(14, 96)","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).",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
1915,"(14, 97)","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).",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
1916,"(14, 98)","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).",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
1917,"(14, 99)","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).",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
1918,"(14, 100)","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).",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
1919,"(14, 101)","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).",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
1920,"(14, 102)","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).","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
1921,"(14, 103)","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).",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
1922,"(14, 104)","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).",The system shall allow a user to foward notification to someone else at the site.,Neutral
1923,"(14, 105)","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).",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
1924,"(14, 106)","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).","The system shall define, populate, and retrieve information about user classes.",Neutral
1925,"(14, 107)","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).",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1926,"(14, 108)","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).",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
1927,"(14, 109)","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).",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
1928,"(14, 110)","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).",The system shall allow concurrent membership in more than one User Class.,Neutral
1929,"(14, 111)","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).",The system shall allow membership in only one User Class.,Neutral
1930,"(14, 112)","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).",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
1931,"(14, 113)","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).","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.",Neutral
1932,"(14, 114)","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).",The system shall improve accessibility of online clinical information and results.,Neutral
1933,"(14, 115)","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).","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.",Neutral
1934,"(14, 116)","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).","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
1935,"(14, 117)","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).","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
1936,"(14, 118)","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).",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
1937,"(14, 119)","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).",The system shall make the traditional order entry processes more practical.,Neutral
1938,"(14, 120)","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).",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
1939,"(14, 121)","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).",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
1940,"(14, 122)","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).",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
1941,"(14, 123)","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).","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
1942,"(14, 124)","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).","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.",Neutral
1943,"(14, 125)","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).","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
1944,"(14, 126)","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).",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
1945,"(14, 127)","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).","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.",Neutral
1946,"(14, 128)","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).","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
1947,"(14, 129)","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).","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.",Neutral
1948,"(14, 130)","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).","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
1949,"(14, 131)","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).",The system shall delete history of received immunizations.,Neutral
1950,"(14, 132)","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).",The system shall only delete history of recieved immunizations unless user specifies,Neutral
1951,"(14, 133)","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).",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
1952,"(14, 134)","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).",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.,Neutral
1953,"(14, 135)","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).",The system will provide the ability to register patients of all types.,Neutral
1954,"(14, 136)","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).","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
1955,"(14, 137)","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).",The system shall include Standard Laboratory and Medication orderable files.,Neutral
1956,"(14, 138)","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).",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
1957,"(14, 139)","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).",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
1958,"(14, 140)","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).",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
1959,"(14, 141)","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).",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
1960,"(14, 142)","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).",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
1961,"(14, 143)","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).",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
1962,"(14, 144)","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).","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
1963,"(14, 145)","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).",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.,Neutral
1964,"(14, 146)","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).",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
1965,"(14, 147)","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).","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
1966,"(14, 148)","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).","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.",Neutral
1967,"(15, 16)",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.,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.,Neutral
1968,"(15, 17)",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.,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
1969,"(15, 18)",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.,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.,Neutral
1970,"(15, 19)",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.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1971,"(15, 20)",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.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
1972,"(15, 21)",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.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
1973,"(15, 22)",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.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
1974,"(15, 23)",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.,"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.",Neutral
1975,"(15, 24)",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.,"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.",Neutral
1976,"(15, 25)",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.,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.,Neutral
1977,"(15, 26)",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.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1978,"(15, 27)",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.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
1979,"(15, 28)",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.,"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.",Neutral
1980,"(15, 29)",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.,"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.",Neutral
1981,"(15, 30)",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.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
1982,"(15, 31)",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.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
1983,"(15, 32)",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.,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.,Neutral
1984,"(15, 33)",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.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
1985,"(15, 34)",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.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
1986,"(15, 35)",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.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
1987,"(15, 36)",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.,"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).",Neutral
1988,"(15, 37)",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.,"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).",Neutral
1989,"(15, 38)",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.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
1990,"(15, 39)",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.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
1991,"(15, 40)",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.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
1992,"(15, 41)",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.,The system shall improve efficiency of entering orders.,Neutral
1993,"(15, 42)",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.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
1994,"(15, 43)",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.,The system shall allow complete order sets to be predefined and personalized.,Neutral
1995,"(15, 44)",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.,The system shall allow order checking.,Neutral
1996,"(15, 45)",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.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1997,"(15, 46)",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.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
1998,"(15, 47)",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.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
1999,"(15, 48)",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.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
2000,"(15, 49)",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.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
2001,"(15, 50)",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.,The system shall support role-based access for security controls.,Neutral
2002,"(15, 51)",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.,The system shall support audit capability.,Neutral
2003,"(15, 52)",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.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
2004,"(15, 53)",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.,The system shall support the requirements for all codified data ,Neutral
2005,"(15, 54)",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.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
2006,"(15, 55)",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.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
2007,"(15, 56)",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.,The system shall require the entry of an access code to gain access to the system.,Neutral
2008,"(15, 57)",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.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
2009,"(15, 58)",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.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
2010,"(15, 59)",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.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2011,"(15, 60)",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.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2012,"(15, 61)",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.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
2013,"(15, 62)",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.,The system shall have pre-defined progress note templates.,Neutral
2014,"(15, 63)",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.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
2015,"(15, 64)",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.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
2016,"(15, 65)",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.,The system shall require only a smart card to digitally sign an order.,Neutral
2017,"(15, 66)",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.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
2018,"(15, 67)",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.,The system shall allow users to enter time in several different formats.,Neutral
2019,"(15, 68)",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.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2020,"(15, 69)",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.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2021,"(15, 70)",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.,"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.",Neutral
2022,"(15, 71)",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.,"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.",Neutral
2023,"(15, 72)",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.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
2024,"(15, 73)",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.,"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.",Neutral
2025,"(15, 74)",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.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
2026,"(15, 75)",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.,The system shall have a option to release unsigned orders to services,Neutral
2027,"(15, 76)",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.,"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.",Neutral
2028,"(15, 77)",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.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
2029,"(15, 78)",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.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
2030,"(15, 79)",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.,"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.",Neutral
2031,"(15, 80)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
2032,"(15, 81)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
2033,"(15, 82)",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.,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.,Neutral
2034,"(15, 83)",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.,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.,Neutral
2035,"(15, 84)",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.,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.,Neutral
2036,"(15, 85)",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.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
2037,"(15, 86)",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.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
2038,"(15, 87)",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.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
2039,"(15, 88)",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.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
2040,"(15, 89)",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.,The system shall not allow mandatory notifications to be disabled.,Neutral
2041,"(15, 90)",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.,The system shall allow users to disable unwanted notifications as desired.,Neutral
2042,"(15, 91)",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.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
2043,"(15, 92)",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.,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.,Neutral
2044,"(15, 93)",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.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
2045,"(15, 94)",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.,The system shall use any protocol for transferring messages among packages.,Neutral
2046,"(15, 95)",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.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
2047,"(15, 96)",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.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
2048,"(15, 97)",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.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
2049,"(15, 98)",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.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
2050,"(15, 99)",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.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
2051,"(15, 100)",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.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
2052,"(15, 101)",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.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
2053,"(15, 102)",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.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
2054,"(15, 103)",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.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
2055,"(15, 104)",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.,The system shall allow a user to foward notification to someone else at the site.,Neutral
2056,"(15, 105)",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.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
2057,"(15, 106)",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.,"The system shall define, populate, and retrieve information about user classes.",Neutral
2058,"(15, 107)",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.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2059,"(15, 108)",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.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2060,"(15, 109)",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.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
2061,"(15, 110)",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.,The system shall allow concurrent membership in more than one User Class.,Neutral
2062,"(15, 111)",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.,The system shall allow membership in only one User Class.,Neutral
2063,"(15, 112)",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.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
2064,"(15, 113)",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.,"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.",Neutral
2065,"(15, 114)",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.,The system shall improve accessibility of online clinical information and results.,Neutral
2066,"(15, 115)",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.,"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.",Neutral
2067,"(15, 116)",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.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
2068,"(15, 117)",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.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
2069,"(15, 118)",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.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
2070,"(15, 119)",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.,The system shall make the traditional order entry processes more practical.,Neutral
2071,"(15, 120)",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.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
2072,"(15, 121)",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.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
2073,"(15, 122)",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.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
2074,"(15, 123)",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.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
2075,"(15, 124)",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.,"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.",Neutral
2076,"(15, 125)",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.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
2077,"(15, 126)",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.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
2078,"(15, 127)",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.,"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.",Neutral
2079,"(15, 128)",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.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
2080,"(15, 129)",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.,"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.",Neutral
2081,"(15, 130)",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.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
2082,"(15, 131)",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.,The system shall delete history of received immunizations.,Neutral
2083,"(15, 132)",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.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
2084,"(15, 133)",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.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
2085,"(15, 134)",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.,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.,Neutral
2086,"(15, 135)",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.,The system will provide the ability to register patients of all types.,Neutral
2087,"(15, 136)",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.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
2088,"(15, 137)",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.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
2089,"(15, 138)",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.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
2090,"(15, 139)",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.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
2091,"(15, 140)",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.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
2092,"(15, 141)",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.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
2093,"(15, 142)",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.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
2094,"(15, 143)",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.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
2095,"(15, 144)",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.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
2096,"(15, 145)",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.,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.,Neutral
2097,"(15, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
2098,"(15, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
2099,"(15, 148)",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.,"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.",Neutral
2100,"(16, 17)",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.,The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Neutral
2101,"(16, 18)",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.,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.,Conflict
2102,"(16, 19)",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.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
2103,"(16, 20)",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.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
2104,"(16, 21)",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.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
2105,"(16, 22)",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.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
2106,"(16, 23)",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.,"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.",Neutral
2107,"(16, 24)",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.,"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.",Neutral
2108,"(16, 25)",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.,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.,Neutral
2109,"(16, 26)",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.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2110,"(16, 27)",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.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2111,"(16, 28)",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.,"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.",Neutral
2112,"(16, 29)",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.,"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.",Neutral
2113,"(16, 30)",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.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
2114,"(16, 31)",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.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
2115,"(16, 32)",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.,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.,Neutral
2116,"(16, 33)",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.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
2117,"(16, 34)",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.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
2118,"(16, 35)",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.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
2119,"(16, 36)",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.,"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).",Neutral
2120,"(16, 37)",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.,"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).",Neutral
2121,"(16, 38)",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.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
2122,"(16, 39)",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.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
2123,"(16, 40)",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.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
2124,"(16, 41)",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.,The system shall improve efficiency of entering orders.,Neutral
2125,"(16, 42)",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.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
2126,"(16, 43)",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.,The system shall allow complete order sets to be predefined and personalized.,Neutral
2127,"(16, 44)",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.,The system shall allow order checking.,Neutral
2128,"(16, 45)",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.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2129,"(16, 46)",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.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2130,"(16, 47)",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.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
2131,"(16, 48)",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.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
2132,"(16, 49)",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.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
2133,"(16, 50)",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.,The system shall support role-based access for security controls.,Neutral
2134,"(16, 51)",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.,The system shall support audit capability.,Neutral
2135,"(16, 52)",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.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
2136,"(16, 53)",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.,The system shall support the requirements for all codified data ,Neutral
2137,"(16, 54)",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.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
2138,"(16, 55)",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.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
2139,"(16, 56)",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.,The system shall require the entry of an access code to gain access to the system.,Neutral
2140,"(16, 57)",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.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
2141,"(16, 58)",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.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
2142,"(16, 59)",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.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2143,"(16, 60)",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.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2144,"(16, 61)",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.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
2145,"(16, 62)",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.,The system shall have pre-defined progress note templates.,Neutral
2146,"(16, 63)",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.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
2147,"(16, 64)",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.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
2148,"(16, 65)",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.,The system shall require only a smart card to digitally sign an order.,Neutral
2149,"(16, 66)",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.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
2150,"(16, 67)",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.,The system shall allow users to enter time in several different formats.,Neutral
2151,"(16, 68)",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.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2152,"(16, 69)",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.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2153,"(16, 70)",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.,"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.",Neutral
2154,"(16, 71)",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.,"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.",Neutral
2155,"(16, 72)",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.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
2156,"(16, 73)",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.,"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.",Neutral
2157,"(16, 74)",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.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
2158,"(16, 75)",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.,The system shall have a option to release unsigned orders to services,Neutral
2159,"(16, 76)",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.,"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.",Neutral
2160,"(16, 77)",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.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
2161,"(16, 78)",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.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
2162,"(16, 79)",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.,"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.",Neutral
2163,"(16, 80)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
2164,"(16, 81)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
2165,"(16, 82)",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.,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.,Neutral
2166,"(16, 83)",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.,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.,Neutral
2167,"(16, 84)",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.,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.,Neutral
2168,"(16, 85)",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.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
2169,"(16, 86)",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.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
2170,"(16, 87)",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.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
2171,"(16, 88)",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.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
2172,"(16, 89)",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.,The system shall not allow mandatory notifications to be disabled.,Neutral
2173,"(16, 90)",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.,The system shall allow users to disable unwanted notifications as desired.,Neutral
2174,"(16, 91)",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.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
2175,"(16, 92)",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.,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.,Neutral
2176,"(16, 93)",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.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
2177,"(16, 94)",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.,The system shall use any protocol for transferring messages among packages.,Neutral
2178,"(16, 95)",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.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
2179,"(16, 96)",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.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
2180,"(16, 97)",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.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
2181,"(16, 98)",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.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
2182,"(16, 99)",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.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
2183,"(16, 100)",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.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
2184,"(16, 101)",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.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
2185,"(16, 102)",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.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
2186,"(16, 103)",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.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
2187,"(16, 104)",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.,The system shall allow a user to foward notification to someone else at the site.,Neutral
2188,"(16, 105)",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.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
2189,"(16, 106)",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.,"The system shall define, populate, and retrieve information about user classes.",Neutral
2190,"(16, 107)",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.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2191,"(16, 108)",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.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2192,"(16, 109)",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.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
2193,"(16, 110)",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.,The system shall allow concurrent membership in more than one User Class.,Neutral
2194,"(16, 111)",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.,The system shall allow membership in only one User Class.,Neutral
2195,"(16, 112)",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.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
2196,"(16, 113)",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.,"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.",Neutral
2197,"(16, 114)",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.,The system shall improve accessibility of online clinical information and results.,Neutral
2198,"(16, 115)",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.,"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.",Neutral
2199,"(16, 116)",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.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
2200,"(16, 117)",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.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
2201,"(16, 118)",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.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
2202,"(16, 119)",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.,The system shall make the traditional order entry processes more practical.,Neutral
2203,"(16, 120)",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.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
2204,"(16, 121)",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.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
2205,"(16, 122)",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.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
2206,"(16, 123)",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.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
2207,"(16, 124)",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.,"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.",Neutral
2208,"(16, 125)",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.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
2209,"(16, 126)",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.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
2210,"(16, 127)",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.,"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.",Neutral
2211,"(16, 128)",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.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
2212,"(16, 129)",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.,"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.",Neutral
2213,"(16, 130)",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.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
2214,"(16, 131)",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.,The system shall delete history of received immunizations.,Neutral
2215,"(16, 132)",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.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
2216,"(16, 133)",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.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
2217,"(16, 134)",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.,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.,Neutral
2218,"(16, 135)",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.,The system will provide the ability to register patients of all types.,Neutral
2219,"(16, 136)",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.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
2220,"(16, 137)",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.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
2221,"(16, 138)",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.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
2222,"(16, 139)",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.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
2223,"(16, 140)",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.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
2224,"(16, 141)",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.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
2225,"(16, 142)",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.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
2226,"(16, 143)",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.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
2227,"(16, 144)",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.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
2228,"(16, 145)",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.,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.,Neutral
2229,"(16, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
2230,"(16, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
2231,"(16, 148)",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.,"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.",Neutral
2232,"(17, 18)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,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.,Neutral
2233,"(17, 19)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
2234,"(17, 20)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
2235,"(17, 21)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
2236,"(17, 22)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
2237,"(17, 23)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2238,"(17, 24)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2239,"(17, 25)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,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.,Neutral
2240,"(17, 26)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2241,"(17, 27)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2242,"(17, 28)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2243,"(17, 29)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2244,"(17, 30)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
2245,"(17, 31)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
2246,"(17, 32)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,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.,Neutral
2247,"(17, 33)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
2248,"(17, 34)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
2249,"(17, 35)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
2250,"(17, 36)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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).",Neutral
2251,"(17, 37)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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).",Neutral
2252,"(17, 38)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
2253,"(17, 39)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
2254,"(17, 40)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
2255,"(17, 41)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall improve efficiency of entering orders.,Neutral
2256,"(17, 42)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
2257,"(17, 43)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow complete order sets to be predefined and personalized.,Neutral
2258,"(17, 44)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow order checking.,Neutral
2259,"(17, 45)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2260,"(17, 46)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2261,"(17, 47)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
2262,"(17, 48)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
2263,"(17, 49)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
2264,"(17, 50)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall support role-based access for security controls.,Neutral
2265,"(17, 51)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall support audit capability.,Neutral
2266,"(17, 52)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
2267,"(17, 53)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall support the requirements for all codified data ,Neutral
2268,"(17, 54)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
2269,"(17, 55)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
2270,"(17, 56)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall require the entry of an access code to gain access to the system.,Neutral
2271,"(17, 57)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
2272,"(17, 58)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
2273,"(17, 59)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2274,"(17, 60)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2275,"(17, 61)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
2276,"(17, 62)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall have pre-defined progress note templates.,Neutral
2277,"(17, 63)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
2278,"(17, 64)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
2279,"(17, 65)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall require only a smart card to digitally sign an order.,Neutral
2280,"(17, 66)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
2281,"(17, 67)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow users to enter time in several different formats.,Neutral
2282,"(17, 68)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2283,"(17, 69)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2284,"(17, 70)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2285,"(17, 71)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2286,"(17, 72)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
2287,"(17, 73)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2288,"(17, 74)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
2289,"(17, 75)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall have a option to release unsigned orders to services,Neutral
2290,"(17, 76)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2291,"(17, 77)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
2292,"(17, 78)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
2293,"(17, 79)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2294,"(17, 80)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
2295,"(17, 81)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
2296,"(17, 82)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,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.,Neutral
2297,"(17, 83)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,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.,Neutral
2298,"(17, 84)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,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.,Neutral
2299,"(17, 85)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
2300,"(17, 86)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
2301,"(17, 87)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
2302,"(17, 88)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
2303,"(17, 89)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall not allow mandatory notifications to be disabled.,Neutral
2304,"(17, 90)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow users to disable unwanted notifications as desired.,Neutral
2305,"(17, 91)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
2306,"(17, 92)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,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.,Neutral
2307,"(17, 93)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
2308,"(17, 94)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall use any protocol for transferring messages among packages.,Neutral
2309,"(17, 95)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
2310,"(17, 96)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
2311,"(17, 97)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
2312,"(17, 98)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
2313,"(17, 99)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
2314,"(17, 100)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
2315,"(17, 101)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
2316,"(17, 102)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
2317,"(17, 103)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
2318,"(17, 104)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow a user to foward notification to someone else at the site.,Neutral
2319,"(17, 105)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
2320,"(17, 106)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall define, populate, and retrieve information about user classes.",Neutral
2321,"(17, 107)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2322,"(17, 108)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2323,"(17, 109)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
2324,"(17, 110)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow concurrent membership in more than one User Class.,Neutral
2325,"(17, 111)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow membership in only one User Class.,Neutral
2326,"(17, 112)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
2327,"(17, 113)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2328,"(17, 114)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall improve accessibility of online clinical information and results.,Neutral
2329,"(17, 115)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2330,"(17, 116)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
2331,"(17, 117)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
2332,"(17, 118)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
2333,"(17, 119)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall make the traditional order entry processes more practical.,Neutral
2334,"(17, 120)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
2335,"(17, 121)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
2336,"(17, 122)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
2337,"(17, 123)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
2338,"(17, 124)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2339,"(17, 125)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
2340,"(17, 126)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
2341,"(17, 127)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2342,"(17, 128)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
2343,"(17, 129)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2344,"(17, 130)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
2345,"(17, 131)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall delete history of received immunizations.,Neutral
2346,"(17, 132)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
2347,"(17, 133)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
2348,"(17, 134)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,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.,Neutral
2349,"(17, 135)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system will provide the ability to register patients of all types.,Neutral
2350,"(17, 136)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
2351,"(17, 137)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
2352,"(17, 138)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
2353,"(17, 139)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
2354,"(17, 140)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
2355,"(17, 141)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
2356,"(17, 142)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
2357,"(17, 143)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
2358,"(17, 144)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
2359,"(17, 145)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,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.,Neutral
2360,"(17, 146)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
2361,"(17, 147)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
2362,"(17, 148)",The system shall display a message indicating the patient’s ability to pay for medical services must be evaluated.,"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.",Neutral
2363,"(18, 19)",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.,The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
2364,"(18, 20)",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.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Neutral
2365,"(18, 21)",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.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
2366,"(18, 22)",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.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
2367,"(18, 23)",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.,"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.",Neutral
2368,"(18, 24)",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.,"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.",Neutral
2369,"(18, 25)",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.,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.,Neutral
2370,"(18, 26)",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.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2371,"(18, 27)",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.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2372,"(18, 28)",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.,"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.",Neutral
2373,"(18, 29)",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.,"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.",Neutral
2374,"(18, 30)",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.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
2375,"(18, 31)",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.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
2376,"(18, 32)",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.,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.,Neutral
2377,"(18, 33)",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.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
2378,"(18, 34)",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.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
2379,"(18, 35)",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.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
2380,"(18, 36)",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.,"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).",Neutral
2381,"(18, 37)",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.,"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).",Neutral
2382,"(18, 38)",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.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
2383,"(18, 39)",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.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
2384,"(18, 40)",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.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
2385,"(18, 41)",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.,The system shall improve efficiency of entering orders.,Neutral
2386,"(18, 42)",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.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
2387,"(18, 43)",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.,The system shall allow complete order sets to be predefined and personalized.,Neutral
2388,"(18, 44)",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.,The system shall allow order checking.,Neutral
2389,"(18, 45)",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.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2390,"(18, 46)",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.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2391,"(18, 47)",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.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
2392,"(18, 48)",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.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
2393,"(18, 49)",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.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
2394,"(18, 50)",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.,The system shall support role-based access for security controls.,Neutral
2395,"(18, 51)",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.,The system shall support audit capability.,Neutral
2396,"(18, 52)",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.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
2397,"(18, 53)",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.,The system shall support the requirements for all codified data ,Neutral
2398,"(18, 54)",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.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
2399,"(18, 55)",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.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
2400,"(18, 56)",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.,The system shall require the entry of an access code to gain access to the system.,Neutral
2401,"(18, 57)",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.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
2402,"(18, 58)",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.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
2403,"(18, 59)",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.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2404,"(18, 60)",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.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2405,"(18, 61)",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.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
2406,"(18, 62)",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.,The system shall have pre-defined progress note templates.,Neutral
2407,"(18, 63)",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.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
2408,"(18, 64)",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.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
2409,"(18, 65)",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.,The system shall require only a smart card to digitally sign an order.,Neutral
2410,"(18, 66)",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.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
2411,"(18, 67)",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.,The system shall allow users to enter time in several different formats.,Neutral
2412,"(18, 68)",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.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2413,"(18, 69)",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.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2414,"(18, 70)",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.,"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.",Neutral
2415,"(18, 71)",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.,"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.",Neutral
2416,"(18, 72)",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.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
2417,"(18, 73)",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.,"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.",Neutral
2418,"(18, 74)",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.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
2419,"(18, 75)",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.,The system shall have a option to release unsigned orders to services,Neutral
2420,"(18, 76)",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.,"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.",Neutral
2421,"(18, 77)",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.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
2422,"(18, 78)",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.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
2423,"(18, 79)",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.,"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.",Neutral
2424,"(18, 80)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
2425,"(18, 81)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
2426,"(18, 82)",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.,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.,Neutral
2427,"(18, 83)",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.,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.,Neutral
2428,"(18, 84)",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.,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.,Neutral
2429,"(18, 85)",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.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
2430,"(18, 86)",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.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
2431,"(18, 87)",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.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
2432,"(18, 88)",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.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
2433,"(18, 89)",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.,The system shall not allow mandatory notifications to be disabled.,Neutral
2434,"(18, 90)",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.,The system shall allow users to disable unwanted notifications as desired.,Neutral
2435,"(18, 91)",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.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
2436,"(18, 92)",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.,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.,Neutral
2437,"(18, 93)",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.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
2438,"(18, 94)",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.,The system shall use any protocol for transferring messages among packages.,Neutral
2439,"(18, 95)",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.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
2440,"(18, 96)",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.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
2441,"(18, 97)",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.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
2442,"(18, 98)",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.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
2443,"(18, 99)",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.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
2444,"(18, 100)",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.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
2445,"(18, 101)",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.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
2446,"(18, 102)",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.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
2447,"(18, 103)",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.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
2448,"(18, 104)",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.,The system shall allow a user to foward notification to someone else at the site.,Neutral
2449,"(18, 105)",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.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
2450,"(18, 106)",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.,"The system shall define, populate, and retrieve information about user classes.",Neutral
2451,"(18, 107)",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.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2452,"(18, 108)",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.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2453,"(18, 109)",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.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
2454,"(18, 110)",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.,The system shall allow concurrent membership in more than one User Class.,Neutral
2455,"(18, 111)",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.,The system shall allow membership in only one User Class.,Neutral
2456,"(18, 112)",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.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
2457,"(18, 113)",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.,"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.",Neutral
2458,"(18, 114)",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.,The system shall improve accessibility of online clinical information and results.,Neutral
2459,"(18, 115)",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.,"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.",Neutral
2460,"(18, 116)",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.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
2461,"(18, 117)",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.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
2462,"(18, 118)",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.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
2463,"(18, 119)",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.,The system shall make the traditional order entry processes more practical.,Neutral
2464,"(18, 120)",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.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
2465,"(18, 121)",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.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
2466,"(18, 122)",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.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
2467,"(18, 123)",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.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
2468,"(18, 124)",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.,"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.",Neutral
2469,"(18, 125)",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.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
2470,"(18, 126)",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.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
2471,"(18, 127)",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.,"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.",Neutral
2472,"(18, 128)",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.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
2473,"(18, 129)",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.,"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.",Neutral
2474,"(18, 130)",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.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
2475,"(18, 131)",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.,The system shall delete history of received immunizations.,Neutral
2476,"(18, 132)",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.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
2477,"(18, 133)",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.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
2478,"(18, 134)",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.,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.,Neutral
2479,"(18, 135)",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.,The system will provide the ability to register patients of all types.,Neutral
2480,"(18, 136)",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.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
2481,"(18, 137)",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.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
2482,"(18, 138)",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.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
2483,"(18, 139)",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.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
2484,"(18, 140)",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.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
2485,"(18, 141)",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.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
2486,"(18, 142)",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.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
2487,"(18, 143)",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.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
2488,"(18, 144)",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.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
2489,"(18, 145)",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.,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.,Neutral
2490,"(18, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
2491,"(18, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
2492,"(18, 148)",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.,"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.",Neutral
2493,"(19, 20)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Conflict
2494,"(19, 21)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
2495,"(19, 22)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
2496,"(19, 23)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2497,"(19, 24)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2498,"(19, 25)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2499,"(19, 26)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2500,"(19, 27)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2501,"(19, 28)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2502,"(19, 29)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2503,"(19, 30)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
2504,"(19, 31)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
2505,"(19, 32)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2506,"(19, 33)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
2507,"(19, 34)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
2508,"(19, 35)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
2509,"(19, 36)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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).",Neutral
2510,"(19, 37)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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).",Neutral
2511,"(19, 38)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
2512,"(19, 39)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
2513,"(19, 40)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
2514,"(19, 41)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall improve efficiency of entering orders.,Neutral
2515,"(19, 42)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
2516,"(19, 43)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow complete order sets to be predefined and personalized.,Neutral
2517,"(19, 44)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow order checking.,Neutral
2518,"(19, 45)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2519,"(19, 46)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2520,"(19, 47)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
2521,"(19, 48)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
2522,"(19, 49)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
2523,"(19, 50)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall support role-based access for security controls.,Neutral
2524,"(19, 51)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall support audit capability.,Neutral
2525,"(19, 52)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
2526,"(19, 53)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall support the requirements for all codified data ,Neutral
2527,"(19, 54)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
2528,"(19, 55)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
2529,"(19, 56)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall require the entry of an access code to gain access to the system.,Neutral
2530,"(19, 57)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
2531,"(19, 58)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
2532,"(19, 59)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2533,"(19, 60)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2534,"(19, 61)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
2535,"(19, 62)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall have pre-defined progress note templates.,Neutral
2536,"(19, 63)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
2537,"(19, 64)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
2538,"(19, 65)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall require only a smart card to digitally sign an order.,Neutral
2539,"(19, 66)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
2540,"(19, 67)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow users to enter time in several different formats.,Neutral
2541,"(19, 68)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2542,"(19, 69)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2543,"(19, 70)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2544,"(19, 71)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2545,"(19, 72)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
2546,"(19, 73)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2547,"(19, 74)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
2548,"(19, 75)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall have a option to release unsigned orders to services,Neutral
2549,"(19, 76)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2550,"(19, 77)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
2551,"(19, 78)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
2552,"(19, 79)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2553,"(19, 80)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
2554,"(19, 81)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
2555,"(19, 82)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2556,"(19, 83)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2557,"(19, 84)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2558,"(19, 85)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
2559,"(19, 86)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
2560,"(19, 87)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
2561,"(19, 88)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
2562,"(19, 89)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall not allow mandatory notifications to be disabled.,Neutral
2563,"(19, 90)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow users to disable unwanted notifications as desired.,Neutral
2564,"(19, 91)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
2565,"(19, 92)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2566,"(19, 93)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
2567,"(19, 94)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall use any protocol for transferring messages among packages.,Neutral
2568,"(19, 95)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
2569,"(19, 96)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
2570,"(19, 97)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
2571,"(19, 98)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
2572,"(19, 99)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
2573,"(19, 100)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
2574,"(19, 101)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
2575,"(19, 102)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
2576,"(19, 103)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
2577,"(19, 104)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow a user to foward notification to someone else at the site.,Neutral
2578,"(19, 105)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
2579,"(19, 106)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall define, populate, and retrieve information about user classes.",Neutral
2580,"(19, 107)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2581,"(19, 108)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2582,"(19, 109)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
2583,"(19, 110)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow concurrent membership in more than one User Class.,Neutral
2584,"(19, 111)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow membership in only one User Class.,Neutral
2585,"(19, 112)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
2586,"(19, 113)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2587,"(19, 114)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall improve accessibility of online clinical information and results.,Neutral
2588,"(19, 115)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2589,"(19, 116)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
2590,"(19, 117)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
2591,"(19, 118)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
2592,"(19, 119)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall make the traditional order entry processes more practical.,Neutral
2593,"(19, 120)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
2594,"(19, 121)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
2595,"(19, 122)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
2596,"(19, 123)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
2597,"(19, 124)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2598,"(19, 125)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
2599,"(19, 126)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
2600,"(19, 127)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2601,"(19, 128)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
2602,"(19, 129)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2603,"(19, 130)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
2604,"(19, 131)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall delete history of received immunizations.,Neutral
2605,"(19, 132)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
2606,"(19, 133)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
2607,"(19, 134)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2608,"(19, 135)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system will provide the ability to register patients of all types.,Neutral
2609,"(19, 136)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
2610,"(19, 137)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
2611,"(19, 138)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
2612,"(19, 139)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
2613,"(19, 140)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
2614,"(19, 141)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
2615,"(19, 142)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
2616,"(19, 143)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
2617,"(19, 144)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
2618,"(19, 145)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2619,"(19, 146)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
2620,"(19, 147)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
2621,"(19, 148)",The system shall allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2622,"(20, 21)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Neutral
2623,"(20, 22)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Neutral
2624,"(20, 23)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2625,"(20, 24)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2626,"(20, 25)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2627,"(20, 26)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2628,"(20, 27)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2629,"(20, 28)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2630,"(20, 29)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2631,"(20, 30)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
2632,"(20, 31)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
2633,"(20, 32)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2634,"(20, 33)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
2635,"(20, 34)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
2636,"(20, 35)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
2637,"(20, 36)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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).",Neutral
2638,"(20, 37)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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).",Neutral
2639,"(20, 38)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
2640,"(20, 39)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
2641,"(20, 40)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
2642,"(20, 41)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall improve efficiency of entering orders.,Neutral
2643,"(20, 42)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
2644,"(20, 43)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow complete order sets to be predefined and personalized.,Neutral
2645,"(20, 44)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow order checking.,Neutral
2646,"(20, 45)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2647,"(20, 46)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2648,"(20, 47)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
2649,"(20, 48)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
2650,"(20, 49)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
2651,"(20, 50)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall support role-based access for security controls.,Neutral
2652,"(20, 51)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall support audit capability.,Neutral
2653,"(20, 52)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
2654,"(20, 53)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall support the requirements for all codified data ,Neutral
2655,"(20, 54)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
2656,"(20, 55)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
2657,"(20, 56)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall require the entry of an access code to gain access to the system.,Neutral
2658,"(20, 57)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
2659,"(20, 58)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
2660,"(20, 59)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2661,"(20, 60)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2662,"(20, 61)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
2663,"(20, 62)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall have pre-defined progress note templates.,Neutral
2664,"(20, 63)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
2665,"(20, 64)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
2666,"(20, 65)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall require only a smart card to digitally sign an order.,Neutral
2667,"(20, 66)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
2668,"(20, 67)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow users to enter time in several different formats.,Neutral
2669,"(20, 68)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2670,"(20, 69)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2671,"(20, 70)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2672,"(20, 71)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2673,"(20, 72)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
2674,"(20, 73)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2675,"(20, 74)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
2676,"(20, 75)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall have a option to release unsigned orders to services,Neutral
2677,"(20, 76)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2678,"(20, 77)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
2679,"(20, 78)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
2680,"(20, 79)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2681,"(20, 80)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
2682,"(20, 81)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
2683,"(20, 82)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2684,"(20, 83)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2685,"(20, 84)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2686,"(20, 85)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
2687,"(20, 86)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
2688,"(20, 87)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
2689,"(20, 88)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
2690,"(20, 89)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall not allow mandatory notifications to be disabled.,Neutral
2691,"(20, 90)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow users to disable unwanted notifications as desired.,Neutral
2692,"(20, 91)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
2693,"(20, 92)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2694,"(20, 93)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
2695,"(20, 94)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall use any protocol for transferring messages among packages.,Neutral
2696,"(20, 95)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
2697,"(20, 96)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
2698,"(20, 97)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
2699,"(20, 98)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
2700,"(20, 99)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
2701,"(20, 100)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
2702,"(20, 101)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
2703,"(20, 102)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
2704,"(20, 103)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
2705,"(20, 104)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow a user to foward notification to someone else at the site.,Neutral
2706,"(20, 105)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
2707,"(20, 106)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall define, populate, and retrieve information about user classes.",Neutral
2708,"(20, 107)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2709,"(20, 108)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2710,"(20, 109)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
2711,"(20, 110)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow concurrent membership in more than one User Class.,Neutral
2712,"(20, 111)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow membership in only one User Class.,Neutral
2713,"(20, 112)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
2714,"(20, 113)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2715,"(20, 114)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall improve accessibility of online clinical information and results.,Neutral
2716,"(20, 115)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2717,"(20, 116)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
2718,"(20, 117)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
2719,"(20, 118)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
2720,"(20, 119)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall make the traditional order entry processes more practical.,Neutral
2721,"(20, 120)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
2722,"(20, 121)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
2723,"(20, 122)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
2724,"(20, 123)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
2725,"(20, 124)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2726,"(20, 125)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
2727,"(20, 126)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
2728,"(20, 127)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2729,"(20, 128)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
2730,"(20, 129)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2731,"(20, 130)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
2732,"(20, 131)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall delete history of received immunizations.,Neutral
2733,"(20, 132)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
2734,"(20, 133)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
2735,"(20, 134)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2736,"(20, 135)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system will provide the ability to register patients of all types.,Neutral
2737,"(20, 136)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
2738,"(20, 137)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
2739,"(20, 138)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
2740,"(20, 139)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
2741,"(20, 140)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
2742,"(20, 141)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
2743,"(20, 142)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
2744,"(20, 143)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
2745,"(20, 144)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
2746,"(20, 145)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,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.,Neutral
2747,"(20, 146)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
2748,"(20, 147)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
2749,"(20, 148)",The system shall only allow clinicians to create patient lists for who can sign or cosign for each other.,"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.",Neutral
2750,"(21, 22)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Conflict
2751,"(21, 23)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2752,"(21, 24)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2753,"(21, 25)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2754,"(21, 26)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2755,"(21, 27)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2756,"(21, 28)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2757,"(21, 29)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2758,"(21, 30)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
2759,"(21, 31)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
2760,"(21, 32)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2761,"(21, 33)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
2762,"(21, 34)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
2763,"(21, 35)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
2764,"(21, 36)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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).",Neutral
2765,"(21, 37)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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).",Neutral
2766,"(21, 38)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
2767,"(21, 39)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
2768,"(21, 40)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
2769,"(21, 41)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall improve efficiency of entering orders.,Neutral
2770,"(21, 42)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
2771,"(21, 43)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow complete order sets to be predefined and personalized.,Neutral
2772,"(21, 44)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow order checking.,Neutral
2773,"(21, 45)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2774,"(21, 46)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2775,"(21, 47)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
2776,"(21, 48)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
2777,"(21, 49)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
2778,"(21, 50)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall support role-based access for security controls.,Neutral
2779,"(21, 51)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall support audit capability.,Neutral
2780,"(21, 52)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
2781,"(21, 53)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall support the requirements for all codified data ,Neutral
2782,"(21, 54)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
2783,"(21, 55)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
2784,"(21, 56)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall require the entry of an access code to gain access to the system.,Neutral
2785,"(21, 57)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
2786,"(21, 58)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
2787,"(21, 59)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2788,"(21, 60)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2789,"(21, 61)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
2790,"(21, 62)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall have pre-defined progress note templates.,Neutral
2791,"(21, 63)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
2792,"(21, 64)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
2793,"(21, 65)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall require only a smart card to digitally sign an order.,Neutral
2794,"(21, 66)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
2795,"(21, 67)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow users to enter time in several different formats.,Neutral
2796,"(21, 68)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2797,"(21, 69)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2798,"(21, 70)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2799,"(21, 71)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2800,"(21, 72)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
2801,"(21, 73)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2802,"(21, 74)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
2803,"(21, 75)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall have a option to release unsigned orders to services,Neutral
2804,"(21, 76)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2805,"(21, 77)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
2806,"(21, 78)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
2807,"(21, 79)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2808,"(21, 80)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
2809,"(21, 81)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
2810,"(21, 82)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2811,"(21, 83)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2812,"(21, 84)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2813,"(21, 85)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
2814,"(21, 86)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
2815,"(21, 87)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
2816,"(21, 88)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
2817,"(21, 89)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall not allow mandatory notifications to be disabled.,Neutral
2818,"(21, 90)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow users to disable unwanted notifications as desired.,Neutral
2819,"(21, 91)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
2820,"(21, 92)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2821,"(21, 93)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
2822,"(21, 94)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall use any protocol for transferring messages among packages.,Neutral
2823,"(21, 95)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
2824,"(21, 96)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
2825,"(21, 97)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
2826,"(21, 98)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
2827,"(21, 99)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
2828,"(21, 100)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
2829,"(21, 101)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
2830,"(21, 102)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
2831,"(21, 103)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
2832,"(21, 104)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow a user to foward notification to someone else at the site.,Neutral
2833,"(21, 105)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
2834,"(21, 106)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall define, populate, and retrieve information about user classes.",Neutral
2835,"(21, 107)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2836,"(21, 108)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2837,"(21, 109)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
2838,"(21, 110)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow concurrent membership in more than one User Class.,Neutral
2839,"(21, 111)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow membership in only one User Class.,Neutral
2840,"(21, 112)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
2841,"(21, 113)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2842,"(21, 114)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall improve accessibility of online clinical information and results.,Neutral
2843,"(21, 115)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2844,"(21, 116)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
2845,"(21, 117)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
2846,"(21, 118)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
2847,"(21, 119)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall make the traditional order entry processes more practical.,Neutral
2848,"(21, 120)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
2849,"(21, 121)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
2850,"(21, 122)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
2851,"(21, 123)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
2852,"(21, 124)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2853,"(21, 125)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
2854,"(21, 126)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
2855,"(21, 127)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2856,"(21, 128)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
2857,"(21, 129)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2858,"(21, 130)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
2859,"(21, 131)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall delete history of received immunizations.,Neutral
2860,"(21, 132)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
2861,"(21, 133)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
2862,"(21, 134)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2863,"(21, 135)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system will provide the ability to register patients of all types.,Neutral
2864,"(21, 136)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
2865,"(21, 137)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
2866,"(21, 138)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
2867,"(21, 139)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
2868,"(21, 140)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
2869,"(21, 141)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
2870,"(21, 142)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
2871,"(21, 143)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
2872,"(21, 144)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
2873,"(21, 145)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2874,"(21, 146)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
2875,"(21, 147)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
2876,"(21, 148)",The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2877,"(22, 23)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2878,"(22, 24)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2879,"(22, 25)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2880,"(22, 26)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2881,"(22, 27)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
2882,"(22, 28)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2883,"(22, 29)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2884,"(22, 30)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
2885,"(22, 31)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
2886,"(22, 32)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2887,"(22, 33)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
2888,"(22, 34)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
2889,"(22, 35)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
2890,"(22, 36)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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).",Neutral
2891,"(22, 37)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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).",Neutral
2892,"(22, 38)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
2893,"(22, 39)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
2894,"(22, 40)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
2895,"(22, 41)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall improve efficiency of entering orders.,Neutral
2896,"(22, 42)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
2897,"(22, 43)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow complete order sets to be predefined and personalized.,Neutral
2898,"(22, 44)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow order checking.,Neutral
2899,"(22, 45)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2900,"(22, 46)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
2901,"(22, 47)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
2902,"(22, 48)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
2903,"(22, 49)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
2904,"(22, 50)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall support role-based access for security controls.,Neutral
2905,"(22, 51)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall support audit capability.,Neutral
2906,"(22, 52)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
2907,"(22, 53)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall support the requirements for all codified data ,Neutral
2908,"(22, 54)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
2909,"(22, 55)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
2910,"(22, 56)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall require the entry of an access code to gain access to the system.,Neutral
2911,"(22, 57)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
2912,"(22, 58)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
2913,"(22, 59)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2914,"(22, 60)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
2915,"(22, 61)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
2916,"(22, 62)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall have pre-defined progress note templates.,Neutral
2917,"(22, 63)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
2918,"(22, 64)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
2919,"(22, 65)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall require only a smart card to digitally sign an order.,Neutral
2920,"(22, 66)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
2921,"(22, 67)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow users to enter time in several different formats.,Neutral
2922,"(22, 68)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2923,"(22, 69)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
2924,"(22, 70)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2925,"(22, 71)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2926,"(22, 72)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
2927,"(22, 73)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2928,"(22, 74)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
2929,"(22, 75)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall have a option to release unsigned orders to services,Neutral
2930,"(22, 76)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2931,"(22, 77)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
2932,"(22, 78)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
2933,"(22, 79)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2934,"(22, 80)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
2935,"(22, 81)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
2936,"(22, 82)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2937,"(22, 83)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2938,"(22, 84)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2939,"(22, 85)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
2940,"(22, 86)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
2941,"(22, 87)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
2942,"(22, 88)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
2943,"(22, 89)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall not allow mandatory notifications to be disabled.,Neutral
2944,"(22, 90)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow users to disable unwanted notifications as desired.,Neutral
2945,"(22, 91)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
2946,"(22, 92)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2947,"(22, 93)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
2948,"(22, 94)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall use any protocol for transferring messages among packages.,Neutral
2949,"(22, 95)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
2950,"(22, 96)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
2951,"(22, 97)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
2952,"(22, 98)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
2953,"(22, 99)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
2954,"(22, 100)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
2955,"(22, 101)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
2956,"(22, 102)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
2957,"(22, 103)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
2958,"(22, 104)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow a user to foward notification to someone else at the site.,Neutral
2959,"(22, 105)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
2960,"(22, 106)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall define, populate, and retrieve information about user classes.",Neutral
2961,"(22, 107)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2962,"(22, 108)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
2963,"(22, 109)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
2964,"(22, 110)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow concurrent membership in more than one User Class.,Neutral
2965,"(22, 111)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow membership in only one User Class.,Neutral
2966,"(22, 112)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
2967,"(22, 113)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2968,"(22, 114)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall improve accessibility of online clinical information and results.,Neutral
2969,"(22, 115)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2970,"(22, 116)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
2971,"(22, 117)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
2972,"(22, 118)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
2973,"(22, 119)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall make the traditional order entry processes more practical.,Neutral
2974,"(22, 120)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
2975,"(22, 121)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
2976,"(22, 122)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
2977,"(22, 123)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
2978,"(22, 124)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2979,"(22, 125)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
2980,"(22, 126)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
2981,"(22, 127)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2982,"(22, 128)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
2983,"(22, 129)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
2984,"(22, 130)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
2985,"(22, 131)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall delete history of received immunizations.,Neutral
2986,"(22, 132)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
2987,"(22, 133)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
2988,"(22, 134)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
2989,"(22, 135)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system will provide the ability to register patients of all types.,Neutral
2990,"(22, 136)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
2991,"(22, 137)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
2992,"(22, 138)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
2993,"(22, 139)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
2994,"(22, 140)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
2995,"(22, 141)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
2996,"(22, 142)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
2997,"(22, 143)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
2998,"(22, 144)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
2999,"(22, 145)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,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.,Neutral
3000,"(22, 146)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
3001,"(22, 147)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
3002,"(22, 148)",The system shall ensure that some team members receive all information about a patient by using patient lists to tie notifications to teams.,"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.",Neutral
3003,"(23, 24)","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.","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.",Conflict
3004,"(23, 25)","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.",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.,Neutral
3005,"(23, 26)","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.",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
3006,"(23, 27)","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.",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
3007,"(23, 28)","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.","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.",Neutral
3008,"(23, 29)","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.","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.",Neutral
3009,"(23, 30)","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.",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
3010,"(23, 31)","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.",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
3011,"(23, 32)","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.",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.,Neutral
3012,"(23, 33)","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.",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
3013,"(23, 34)","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.",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
3014,"(23, 35)","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.","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
3015,"(23, 36)","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.","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).",Neutral
3016,"(23, 37)","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.","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).",Neutral
3017,"(23, 38)","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.","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
3018,"(23, 39)","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.",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
3019,"(23, 40)","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.",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
3020,"(23, 41)","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.",The system shall improve efficiency of entering orders.,Neutral
3021,"(23, 42)","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.",The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
3022,"(23, 43)","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.",The system shall allow complete order sets to be predefined and personalized.,Neutral
3023,"(23, 44)","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.",The system shall allow order checking.,Neutral
3024,"(23, 45)","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.","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3025,"(23, 46)","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.","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3026,"(23, 47)","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.",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
3027,"(23, 48)","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.",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
3028,"(23, 49)","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.",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
3029,"(23, 50)","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.",The system shall support role-based access for security controls.,Neutral
3030,"(23, 51)","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.",The system shall support audit capability.,Neutral
3031,"(23, 52)","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.",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
3032,"(23, 53)","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.",The system shall support the requirements for all codified data ,Neutral
3033,"(23, 54)","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.","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
3034,"(23, 55)","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.",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
3035,"(23, 56)","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.",The system shall require the entry of an access code to gain access to the system.,Neutral
3036,"(23, 57)","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.",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
3037,"(23, 58)","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.",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
3038,"(23, 59)","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.",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3039,"(23, 60)","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.",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3040,"(23, 61)","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.","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
3041,"(23, 62)","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.",The system shall have pre-defined progress note templates.,Neutral
3042,"(23, 63)","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.",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
3043,"(23, 64)","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.","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
3044,"(23, 65)","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.",The system shall require only a smart card to digitally sign an order.,Neutral
3045,"(23, 66)","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.",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
3046,"(23, 67)","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.",The system shall allow users to enter time in several different formats.,Neutral
3047,"(23, 68)","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.",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3048,"(23, 69)","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.",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3049,"(23, 70)","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.","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.",Neutral
3050,"(23, 71)","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.","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.",Neutral
3051,"(23, 72)","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.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
3052,"(23, 73)","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.","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.",Neutral
3053,"(23, 74)","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.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
3054,"(23, 75)","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.",The system shall have a option to release unsigned orders to services,Neutral
3055,"(23, 76)","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.","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.",Neutral
3056,"(23, 77)","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.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
3057,"(23, 78)","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.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
3058,"(23, 79)","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.","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.",Neutral
3059,"(23, 80)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
3060,"(23, 81)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
3061,"(23, 82)","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.",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.,Neutral
3062,"(23, 83)","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.",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.,Neutral
3063,"(23, 84)","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.",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.,Neutral
3064,"(23, 85)","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.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
3065,"(23, 86)","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.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
3066,"(23, 87)","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.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
3067,"(23, 88)","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.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
3068,"(23, 89)","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.",The system shall not allow mandatory notifications to be disabled.,Neutral
3069,"(23, 90)","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.",The system shall allow users to disable unwanted notifications as desired.,Neutral
3070,"(23, 91)","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.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
3071,"(23, 92)","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.",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.,Neutral
3072,"(23, 93)","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.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
3073,"(23, 94)","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.",The system shall use any protocol for transferring messages among packages.,Neutral
3074,"(23, 95)","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.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
3075,"(23, 96)","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.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
3076,"(23, 97)","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.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
3077,"(23, 98)","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.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
3078,"(23, 99)","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.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
3079,"(23, 100)","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.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
3080,"(23, 101)","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.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
3081,"(23, 102)","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.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
3082,"(23, 103)","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.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
3083,"(23, 104)","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.",The system shall allow a user to foward notification to someone else at the site.,Neutral
3084,"(23, 105)","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.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
3085,"(23, 106)","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.","The system shall define, populate, and retrieve information about user classes.",Neutral
3086,"(23, 107)","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.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3087,"(23, 108)","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.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3088,"(23, 109)","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.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
3089,"(23, 110)","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.",The system shall allow concurrent membership in more than one User Class.,Neutral
3090,"(23, 111)","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.",The system shall allow membership in only one User Class.,Neutral
3091,"(23, 112)","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.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
3092,"(23, 113)","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.","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.",Neutral
3093,"(23, 114)","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.",The system shall improve accessibility of online clinical information and results.,Neutral
3094,"(23, 115)","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.","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.",Neutral
3095,"(23, 116)","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.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
3096,"(23, 117)","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.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
3097,"(23, 118)","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.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
3098,"(23, 119)","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.",The system shall make the traditional order entry processes more practical.,Neutral
3099,"(23, 120)","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.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
3100,"(23, 121)","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.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
3101,"(23, 122)","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.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
3102,"(23, 123)","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.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
3103,"(23, 124)","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.","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.",Neutral
3104,"(23, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
3105,"(23, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
3106,"(23, 127)","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.","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.",Neutral
3107,"(23, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
3108,"(23, 129)","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.","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.",Neutral
3109,"(23, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
3110,"(23, 131)","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.",The system shall delete history of received immunizations.,Neutral
3111,"(23, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
3112,"(23, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
3113,"(23, 134)","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.",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.,Neutral
3114,"(23, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
3115,"(23, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
3116,"(23, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
3117,"(23, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
3118,"(23, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
3119,"(23, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
3120,"(23, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
3121,"(23, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
3122,"(23, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
3123,"(23, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
3124,"(23, 145)","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.",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.,Neutral
3125,"(23, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
3126,"(23, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
3127,"(23, 148)","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.","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.",Neutral
3128,"(24, 25)","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.",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.,Neutral
3129,"(24, 26)","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.",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
3130,"(24, 27)","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.",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
3131,"(24, 28)","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.","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.",Neutral
3132,"(24, 29)","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.","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.",Neutral
3133,"(24, 30)","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.",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
3134,"(24, 31)","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.",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
3135,"(24, 32)","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.",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.,Neutral
3136,"(24, 33)","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.",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
3137,"(24, 34)","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.",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
3138,"(24, 35)","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.","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
3139,"(24, 36)","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.","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).",Neutral
3140,"(24, 37)","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.","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).",Neutral
3141,"(24, 38)","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.","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
3142,"(24, 39)","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.",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
3143,"(24, 40)","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.",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
3144,"(24, 41)","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.",The system shall improve efficiency of entering orders.,Neutral
3145,"(24, 42)","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.",The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
3146,"(24, 43)","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.",The system shall allow complete order sets to be predefined and personalized.,Neutral
3147,"(24, 44)","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.",The system shall allow order checking.,Neutral
3148,"(24, 45)","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.","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3149,"(24, 46)","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.","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3150,"(24, 47)","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.",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
3151,"(24, 48)","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.",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
3152,"(24, 49)","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.",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
3153,"(24, 50)","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.",The system shall support role-based access for security controls.,Neutral
3154,"(24, 51)","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.",The system shall support audit capability.,Neutral
3155,"(24, 52)","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.",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
3156,"(24, 53)","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.",The system shall support the requirements for all codified data ,Neutral
3157,"(24, 54)","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.","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
3158,"(24, 55)","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.",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
3159,"(24, 56)","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.",The system shall require the entry of an access code to gain access to the system.,Neutral
3160,"(24, 57)","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.",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
3161,"(24, 58)","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.",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
3162,"(24, 59)","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.",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3163,"(24, 60)","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.",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3164,"(24, 61)","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.","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
3165,"(24, 62)","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.",The system shall have pre-defined progress note templates.,Neutral
3166,"(24, 63)","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.",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
3167,"(24, 64)","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.","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
3168,"(24, 65)","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.",The system shall require only a smart card to digitally sign an order.,Neutral
3169,"(24, 66)","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.",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
3170,"(24, 67)","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.",The system shall allow users to enter time in several different formats.,Neutral
3171,"(24, 68)","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.",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3172,"(24, 69)","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.",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3173,"(24, 70)","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.","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.",Neutral
3174,"(24, 71)","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.","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.",Neutral
3175,"(24, 72)","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.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
3176,"(24, 73)","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.","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.",Neutral
3177,"(24, 74)","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.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
3178,"(24, 75)","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.",The system shall have a option to release unsigned orders to services,Neutral
3179,"(24, 76)","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.","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.",Neutral
3180,"(24, 77)","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.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
3181,"(24, 78)","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.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
3182,"(24, 79)","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.","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.",Neutral
3183,"(24, 80)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
3184,"(24, 81)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
3185,"(24, 82)","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.",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.,Neutral
3186,"(24, 83)","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.",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.,Neutral
3187,"(24, 84)","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.",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.,Neutral
3188,"(24, 85)","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.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
3189,"(24, 86)","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.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
3190,"(24, 87)","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.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
3191,"(24, 88)","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.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
3192,"(24, 89)","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.",The system shall not allow mandatory notifications to be disabled.,Neutral
3193,"(24, 90)","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.",The system shall allow users to disable unwanted notifications as desired.,Neutral
3194,"(24, 91)","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.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
3195,"(24, 92)","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.",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.,Neutral
3196,"(24, 93)","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.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
3197,"(24, 94)","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.",The system shall use any protocol for transferring messages among packages.,Neutral
3198,"(24, 95)","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.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
3199,"(24, 96)","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.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
3200,"(24, 97)","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.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
3201,"(24, 98)","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.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
3202,"(24, 99)","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.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
3203,"(24, 100)","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.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
3204,"(24, 101)","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.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
3205,"(24, 102)","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.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
3206,"(24, 103)","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.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
3207,"(24, 104)","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.",The system shall allow a user to foward notification to someone else at the site.,Neutral
3208,"(24, 105)","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.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
3209,"(24, 106)","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.","The system shall define, populate, and retrieve information about user classes.",Neutral
3210,"(24, 107)","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.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3211,"(24, 108)","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.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3212,"(24, 109)","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.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
3213,"(24, 110)","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.",The system shall allow concurrent membership in more than one User Class.,Neutral
3214,"(24, 111)","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.",The system shall allow membership in only one User Class.,Neutral
3215,"(24, 112)","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.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
3216,"(24, 113)","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.","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.",Neutral
3217,"(24, 114)","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.",The system shall improve accessibility of online clinical information and results.,Neutral
3218,"(24, 115)","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.","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.",Neutral
3219,"(24, 116)","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.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
3220,"(24, 117)","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.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
3221,"(24, 118)","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.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
3222,"(24, 119)","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.",The system shall make the traditional order entry processes more practical.,Neutral
3223,"(24, 120)","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.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
3224,"(24, 121)","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.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
3225,"(24, 122)","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.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
3226,"(24, 123)","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.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
3227,"(24, 124)","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.","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.",Neutral
3228,"(24, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
3229,"(24, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
3230,"(24, 127)","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.","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.",Neutral
3231,"(24, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
3232,"(24, 129)","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.","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.",Neutral
3233,"(24, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
3234,"(24, 131)","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.",The system shall delete history of received immunizations.,Neutral
3235,"(24, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
3236,"(24, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
3237,"(24, 134)","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.",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.,Neutral
3238,"(24, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
3239,"(24, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
3240,"(24, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
3241,"(24, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
3242,"(24, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
3243,"(24, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
3244,"(24, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
3245,"(24, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
3246,"(24, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
3247,"(24, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
3248,"(24, 145)","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.",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.,Neutral
3249,"(24, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
3250,"(24, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
3251,"(24, 148)","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.","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.",Neutral
3252,"(25, 26)",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.,The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Neutral
3253,"(25, 27)",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.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Neutral
3254,"(25, 28)",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.,"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.",Neutral
3255,"(25, 29)",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.,"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.",Neutral
3256,"(25, 30)",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.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
3257,"(25, 31)",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.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
3258,"(25, 32)",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.,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.,Neutral
3259,"(25, 33)",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.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
3260,"(25, 34)",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.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
3261,"(25, 35)",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.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
3262,"(25, 36)",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.,"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).",Neutral
3263,"(25, 37)",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.,"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).",Neutral
3264,"(25, 38)",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.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
3265,"(25, 39)",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.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
3266,"(25, 40)",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.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
3267,"(25, 41)",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.,The system shall improve efficiency of entering orders.,Neutral
3268,"(25, 42)",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.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
3269,"(25, 43)",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.,The system shall allow complete order sets to be predefined and personalized.,Neutral
3270,"(25, 44)",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.,The system shall allow order checking.,Neutral
3271,"(25, 45)",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.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3272,"(25, 46)",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.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3273,"(25, 47)",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.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
3274,"(25, 48)",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.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
3275,"(25, 49)",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.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
3276,"(25, 50)",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.,The system shall support role-based access for security controls.,Neutral
3277,"(25, 51)",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.,The system shall support audit capability.,Neutral
3278,"(25, 52)",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.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
3279,"(25, 53)",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.,The system shall support the requirements for all codified data ,Neutral
3280,"(25, 54)",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.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
3281,"(25, 55)",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.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
3282,"(25, 56)",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.,The system shall require the entry of an access code to gain access to the system.,Neutral
3283,"(25, 57)",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.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
3284,"(25, 58)",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.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
3285,"(25, 59)",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.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3286,"(25, 60)",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.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3287,"(25, 61)",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.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
3288,"(25, 62)",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.,The system shall have pre-defined progress note templates.,Neutral
3289,"(25, 63)",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.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
3290,"(25, 64)",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.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
3291,"(25, 65)",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.,The system shall require only a smart card to digitally sign an order.,Neutral
3292,"(25, 66)",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.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
3293,"(25, 67)",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.,The system shall allow users to enter time in several different formats.,Neutral
3294,"(25, 68)",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.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3295,"(25, 69)",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.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3296,"(25, 70)",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.,"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.",Neutral
3297,"(25, 71)",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.,"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.",Neutral
3298,"(25, 72)",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.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
3299,"(25, 73)",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.,"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.",Neutral
3300,"(25, 74)",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.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
3301,"(25, 75)",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.,The system shall have a option to release unsigned orders to services,Neutral
3302,"(25, 76)",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.,"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.",Neutral
3303,"(25, 77)",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.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
3304,"(25, 78)",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.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
3305,"(25, 79)",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.,"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.",Neutral
3306,"(25, 80)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
3307,"(25, 81)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
3308,"(25, 82)",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.,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.,Neutral
3309,"(25, 83)",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.,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.,Neutral
3310,"(25, 84)",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.,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.,Neutral
3311,"(25, 85)",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.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
3312,"(25, 86)",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.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
3313,"(25, 87)",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.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
3314,"(25, 88)",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.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
3315,"(25, 89)",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.,The system shall not allow mandatory notifications to be disabled.,Neutral
3316,"(25, 90)",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.,The system shall allow users to disable unwanted notifications as desired.,Neutral
3317,"(25, 91)",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.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
3318,"(25, 92)",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.,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.,Neutral
3319,"(25, 93)",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.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
3320,"(25, 94)",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.,The system shall use any protocol for transferring messages among packages.,Neutral
3321,"(25, 95)",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.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
3322,"(25, 96)",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.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
3323,"(25, 97)",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.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
3324,"(25, 98)",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.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
3325,"(25, 99)",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.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
3326,"(25, 100)",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.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
3327,"(25, 101)",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.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
3328,"(25, 102)",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.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
3329,"(25, 103)",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.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
3330,"(25, 104)",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.,The system shall allow a user to foward notification to someone else at the site.,Neutral
3331,"(25, 105)",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.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
3332,"(25, 106)",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.,"The system shall define, populate, and retrieve information about user classes.",Neutral
3333,"(25, 107)",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.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3334,"(25, 108)",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.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3335,"(25, 109)",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.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
3336,"(25, 110)",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.,The system shall allow concurrent membership in more than one User Class.,Neutral
3337,"(25, 111)",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.,The system shall allow membership in only one User Class.,Neutral
3338,"(25, 112)",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.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
3339,"(25, 113)",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.,"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.",Neutral
3340,"(25, 114)",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.,The system shall improve accessibility of online clinical information and results.,Neutral
3341,"(25, 115)",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.,"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.",Neutral
3342,"(25, 116)",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.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
3343,"(25, 117)",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.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
3344,"(25, 118)",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.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
3345,"(25, 119)",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.,The system shall make the traditional order entry processes more practical.,Neutral
3346,"(25, 120)",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.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
3347,"(25, 121)",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.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
3348,"(25, 122)",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.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
3349,"(25, 123)",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.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
3350,"(25, 124)",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.,"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.",Neutral
3351,"(25, 125)",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.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
3352,"(25, 126)",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.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
3353,"(25, 127)",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.,"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.",Neutral
3354,"(25, 128)",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.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
3355,"(25, 129)",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.,"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.",Neutral
3356,"(25, 130)",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.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
3357,"(25, 131)",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.,The system shall delete history of received immunizations.,Neutral
3358,"(25, 132)",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.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
3359,"(25, 133)",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.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
3360,"(25, 134)",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.,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.,Neutral
3361,"(25, 135)",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.,The system will provide the ability to register patients of all types.,Neutral
3362,"(25, 136)",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.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
3363,"(25, 137)",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.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
3364,"(25, 138)",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.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
3365,"(25, 139)",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.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
3366,"(25, 140)",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.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
3367,"(25, 141)",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.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
3368,"(25, 142)",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.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
3369,"(25, 143)",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.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
3370,"(25, 144)",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.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
3371,"(25, 145)",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.,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.,Neutral
3372,"(25, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
3373,"(25, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
3374,"(25, 148)",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.,"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.",Neutral
3375,"(26, 27)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Conflict
3376,"(26, 28)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3377,"(26, 29)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3378,"(26, 30)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
3379,"(26, 31)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
3380,"(26, 32)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3381,"(26, 33)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
3382,"(26, 34)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
3383,"(26, 35)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
3384,"(26, 36)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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).",Neutral
3385,"(26, 37)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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).",Neutral
3386,"(26, 38)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
3387,"(26, 39)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
3388,"(26, 40)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
3389,"(26, 41)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall improve efficiency of entering orders.,Neutral
3390,"(26, 42)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
3391,"(26, 43)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow complete order sets to be predefined and personalized.,Neutral
3392,"(26, 44)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow order checking.,Neutral
3393,"(26, 45)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3394,"(26, 46)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3395,"(26, 47)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
3396,"(26, 48)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
3397,"(26, 49)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
3398,"(26, 50)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall support role-based access for security controls.,Neutral
3399,"(26, 51)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall support audit capability.,Neutral
3400,"(26, 52)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
3401,"(26, 53)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall support the requirements for all codified data ,Neutral
3402,"(26, 54)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
3403,"(26, 55)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
3404,"(26, 56)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall require the entry of an access code to gain access to the system.,Neutral
3405,"(26, 57)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
3406,"(26, 58)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
3407,"(26, 59)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3408,"(26, 60)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3409,"(26, 61)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
3410,"(26, 62)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall have pre-defined progress note templates.,Neutral
3411,"(26, 63)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
3412,"(26, 64)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
3413,"(26, 65)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall require only a smart card to digitally sign an order.,Neutral
3414,"(26, 66)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
3415,"(26, 67)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow users to enter time in several different formats.,Neutral
3416,"(26, 68)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3417,"(26, 69)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3418,"(26, 70)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3419,"(26, 71)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3420,"(26, 72)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
3421,"(26, 73)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3422,"(26, 74)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
3423,"(26, 75)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall have a option to release unsigned orders to services,Neutral
3424,"(26, 76)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3425,"(26, 77)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
3426,"(26, 78)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
3427,"(26, 79)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3428,"(26, 80)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
3429,"(26, 81)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
3430,"(26, 82)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3431,"(26, 83)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3432,"(26, 84)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3433,"(26, 85)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
3434,"(26, 86)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
3435,"(26, 87)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
3436,"(26, 88)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
3437,"(26, 89)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall not allow mandatory notifications to be disabled.,Neutral
3438,"(26, 90)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow users to disable unwanted notifications as desired.,Neutral
3439,"(26, 91)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
3440,"(26, 92)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3441,"(26, 93)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
3442,"(26, 94)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall use any protocol for transferring messages among packages.,Neutral
3443,"(26, 95)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
3444,"(26, 96)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
3445,"(26, 97)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
3446,"(26, 98)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
3447,"(26, 99)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
3448,"(26, 100)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
3449,"(26, 101)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
3450,"(26, 102)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
3451,"(26, 103)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
3452,"(26, 104)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow a user to foward notification to someone else at the site.,Neutral
3453,"(26, 105)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
3454,"(26, 106)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall define, populate, and retrieve information about user classes.",Neutral
3455,"(26, 107)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3456,"(26, 108)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3457,"(26, 109)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
3458,"(26, 110)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow concurrent membership in more than one User Class.,Neutral
3459,"(26, 111)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow membership in only one User Class.,Neutral
3460,"(26, 112)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
3461,"(26, 113)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3462,"(26, 114)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall improve accessibility of online clinical information and results.,Neutral
3463,"(26, 115)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3464,"(26, 116)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
3465,"(26, 117)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
3466,"(26, 118)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
3467,"(26, 119)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall make the traditional order entry processes more practical.,Neutral
3468,"(26, 120)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
3469,"(26, 121)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
3470,"(26, 122)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
3471,"(26, 123)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
3472,"(26, 124)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3473,"(26, 125)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
3474,"(26, 126)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
3475,"(26, 127)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3476,"(26, 128)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
3477,"(26, 129)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3478,"(26, 130)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
3479,"(26, 131)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall delete history of received immunizations.,Neutral
3480,"(26, 132)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
3481,"(26, 133)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
3482,"(26, 134)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3483,"(26, 135)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system will provide the ability to register patients of all types.,Neutral
3484,"(26, 136)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
3485,"(26, 137)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
3486,"(26, 138)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
3487,"(26, 139)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
3488,"(26, 140)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
3489,"(26, 141)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
3490,"(26, 142)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
3491,"(26, 143)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
3492,"(26, 144)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
3493,"(26, 145)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3494,"(26, 146)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
3495,"(26, 147)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
3496,"(26, 148)",The system shall update diagnostic and procedure codes used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3497,"(27, 28)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3498,"(27, 29)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3499,"(27, 30)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
3500,"(27, 31)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
3501,"(27, 32)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3502,"(27, 33)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
3503,"(27, 34)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
3504,"(27, 35)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
3505,"(27, 36)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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).",Neutral
3506,"(27, 37)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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).",Neutral
3507,"(27, 38)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
3508,"(27, 39)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
3509,"(27, 40)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
3510,"(27, 41)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall improve efficiency of entering orders.,Neutral
3511,"(27, 42)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
3512,"(27, 43)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow complete order sets to be predefined and personalized.,Neutral
3513,"(27, 44)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow order checking.,Neutral
3514,"(27, 45)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3515,"(27, 46)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3516,"(27, 47)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
3517,"(27, 48)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
3518,"(27, 49)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
3519,"(27, 50)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall support role-based access for security controls.,Neutral
3520,"(27, 51)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall support audit capability.,Neutral
3521,"(27, 52)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
3522,"(27, 53)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall support the requirements for all codified data ,Neutral
3523,"(27, 54)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
3524,"(27, 55)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
3525,"(27, 56)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall require the entry of an access code to gain access to the system.,Neutral
3526,"(27, 57)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
3527,"(27, 58)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
3528,"(27, 59)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3529,"(27, 60)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3530,"(27, 61)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
3531,"(27, 62)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall have pre-defined progress note templates.,Neutral
3532,"(27, 63)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
3533,"(27, 64)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
3534,"(27, 65)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall require only a smart card to digitally sign an order.,Neutral
3535,"(27, 66)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
3536,"(27, 67)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow users to enter time in several different formats.,Neutral
3537,"(27, 68)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3538,"(27, 69)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3539,"(27, 70)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3540,"(27, 71)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3541,"(27, 72)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
3542,"(27, 73)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3543,"(27, 74)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
3544,"(27, 75)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall have a option to release unsigned orders to services,Neutral
3545,"(27, 76)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3546,"(27, 77)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
3547,"(27, 78)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
3548,"(27, 79)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3549,"(27, 80)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
3550,"(27, 81)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
3551,"(27, 82)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3552,"(27, 83)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3553,"(27, 84)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3554,"(27, 85)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
3555,"(27, 86)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
3556,"(27, 87)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
3557,"(27, 88)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
3558,"(27, 89)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall not allow mandatory notifications to be disabled.,Neutral
3559,"(27, 90)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow users to disable unwanted notifications as desired.,Neutral
3560,"(27, 91)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
3561,"(27, 92)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3562,"(27, 93)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
3563,"(27, 94)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall use any protocol for transferring messages among packages.,Neutral
3564,"(27, 95)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
3565,"(27, 96)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
3566,"(27, 97)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
3567,"(27, 98)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
3568,"(27, 99)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
3569,"(27, 100)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
3570,"(27, 101)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
3571,"(27, 102)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
3572,"(27, 103)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
3573,"(27, 104)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow a user to foward notification to someone else at the site.,Neutral
3574,"(27, 105)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
3575,"(27, 106)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall define, populate, and retrieve information about user classes.",Neutral
3576,"(27, 107)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3577,"(27, 108)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3578,"(27, 109)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
3579,"(27, 110)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow concurrent membership in more than one User Class.,Neutral
3580,"(27, 111)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow membership in only one User Class.,Neutral
3581,"(27, 112)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
3582,"(27, 113)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3583,"(27, 114)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall improve accessibility of online clinical information and results.,Neutral
3584,"(27, 115)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3585,"(27, 116)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
3586,"(27, 117)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
3587,"(27, 118)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
3588,"(27, 119)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall make the traditional order entry processes more practical.,Neutral
3589,"(27, 120)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
3590,"(27, 121)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
3591,"(27, 122)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
3592,"(27, 123)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
3593,"(27, 124)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3594,"(27, 125)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
3595,"(27, 126)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
3596,"(27, 127)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3597,"(27, 128)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
3598,"(27, 129)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3599,"(27, 130)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
3600,"(27, 131)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall delete history of received immunizations.,Neutral
3601,"(27, 132)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
3602,"(27, 133)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
3603,"(27, 134)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3604,"(27, 135)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system will provide the ability to register patients of all types.,Neutral
3605,"(27, 136)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
3606,"(27, 137)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
3607,"(27, 138)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
3608,"(27, 139)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
3609,"(27, 140)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
3610,"(27, 141)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
3611,"(27, 142)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
3612,"(27, 143)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
3613,"(27, 144)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
3614,"(27, 145)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,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.,Neutral
3615,"(27, 146)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
3616,"(27, 147)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
3617,"(27, 148)",The system shall only update diagnostic used for billing purposes so codes are applicable at the time the service was provided.,"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.",Neutral
3618,"(28, 29)","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.","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.",Conflict
3619,"(28, 30)","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.",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
3620,"(28, 31)","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.",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
3621,"(28, 32)","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.",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.,Neutral
3622,"(28, 33)","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.",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
3623,"(28, 34)","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.",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
3624,"(28, 35)","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.","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
3625,"(28, 36)","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.","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).",Neutral
3626,"(28, 37)","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.","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).",Neutral
3627,"(28, 38)","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.","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
3628,"(28, 39)","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.",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
3629,"(28, 40)","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.",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
3630,"(28, 41)","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.",The system shall improve efficiency of entering orders.,Neutral
3631,"(28, 42)","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.",The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
3632,"(28, 43)","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.",The system shall allow complete order sets to be predefined and personalized.,Neutral
3633,"(28, 44)","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.",The system shall allow order checking.,Neutral
3634,"(28, 45)","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.","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3635,"(28, 46)","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.","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3636,"(28, 47)","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.",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
3637,"(28, 48)","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.",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
3638,"(28, 49)","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.",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
3639,"(28, 50)","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.",The system shall support role-based access for security controls.,Neutral
3640,"(28, 51)","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.",The system shall support audit capability.,Neutral
3641,"(28, 52)","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.",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
3642,"(28, 53)","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.",The system shall support the requirements for all codified data ,Neutral
3643,"(28, 54)","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.","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
3644,"(28, 55)","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.",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
3645,"(28, 56)","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.",The system shall require the entry of an access code to gain access to the system.,Neutral
3646,"(28, 57)","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.",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
3647,"(28, 58)","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.",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
3648,"(28, 59)","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.",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3649,"(28, 60)","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.",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3650,"(28, 61)","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.","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
3651,"(28, 62)","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.",The system shall have pre-defined progress note templates.,Neutral
3652,"(28, 63)","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.",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
3653,"(28, 64)","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.","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
3654,"(28, 65)","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.",The system shall require only a smart card to digitally sign an order.,Neutral
3655,"(28, 66)","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.",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
3656,"(28, 67)","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.",The system shall allow users to enter time in several different formats.,Neutral
3657,"(28, 68)","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.",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3658,"(28, 69)","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.",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3659,"(28, 70)","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.","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.",Neutral
3660,"(28, 71)","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.","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.",Neutral
3661,"(28, 72)","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.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
3662,"(28, 73)","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.","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.",Neutral
3663,"(28, 74)","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.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
3664,"(28, 75)","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.",The system shall have a option to release unsigned orders to services,Neutral
3665,"(28, 76)","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.","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.",Neutral
3666,"(28, 77)","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.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
3667,"(28, 78)","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.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
3668,"(28, 79)","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.","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.",Neutral
3669,"(28, 80)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
3670,"(28, 81)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
3671,"(28, 82)","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.",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.,Neutral
3672,"(28, 83)","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.",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.,Neutral
3673,"(28, 84)","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.",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.,Neutral
3674,"(28, 85)","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.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
3675,"(28, 86)","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.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
3676,"(28, 87)","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.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
3677,"(28, 88)","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.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
3678,"(28, 89)","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.",The system shall not allow mandatory notifications to be disabled.,Neutral
3679,"(28, 90)","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.",The system shall allow users to disable unwanted notifications as desired.,Neutral
3680,"(28, 91)","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.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
3681,"(28, 92)","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.",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.,Neutral
3682,"(28, 93)","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.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
3683,"(28, 94)","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.",The system shall use any protocol for transferring messages among packages.,Neutral
3684,"(28, 95)","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.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
3685,"(28, 96)","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.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
3686,"(28, 97)","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.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
3687,"(28, 98)","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.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
3688,"(28, 99)","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.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
3689,"(28, 100)","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.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
3690,"(28, 101)","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.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
3691,"(28, 102)","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.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
3692,"(28, 103)","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.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
3693,"(28, 104)","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.",The system shall allow a user to foward notification to someone else at the site.,Neutral
3694,"(28, 105)","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.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
3695,"(28, 106)","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.","The system shall define, populate, and retrieve information about user classes.",Neutral
3696,"(28, 107)","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.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3697,"(28, 108)","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.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3698,"(28, 109)","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.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
3699,"(28, 110)","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.",The system shall allow concurrent membership in more than one User Class.,Neutral
3700,"(28, 111)","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.",The system shall allow membership in only one User Class.,Neutral
3701,"(28, 112)","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.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
3702,"(28, 113)","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.","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.",Neutral
3703,"(28, 114)","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.",The system shall improve accessibility of online clinical information and results.,Neutral
3704,"(28, 115)","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.","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.",Neutral
3705,"(28, 116)","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.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
3706,"(28, 117)","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.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
3707,"(28, 118)","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.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
3708,"(28, 119)","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.",The system shall make the traditional order entry processes more practical.,Neutral
3709,"(28, 120)","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.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
3710,"(28, 121)","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.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
3711,"(28, 122)","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.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
3712,"(28, 123)","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.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
3713,"(28, 124)","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.","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.",Neutral
3714,"(28, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
3715,"(28, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
3716,"(28, 127)","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.","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.",Neutral
3717,"(28, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
3718,"(28, 129)","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.","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.",Neutral
3719,"(28, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
3720,"(28, 131)","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.",The system shall delete history of received immunizations.,Neutral
3721,"(28, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
3722,"(28, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
3723,"(28, 134)","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.",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.,Neutral
3724,"(28, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
3725,"(28, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
3726,"(28, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
3727,"(28, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
3728,"(28, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
3729,"(28, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
3730,"(28, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
3731,"(28, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
3732,"(28, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
3733,"(28, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
3734,"(28, 145)","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.",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.,Neutral
3735,"(28, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
3736,"(28, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
3737,"(28, 148)","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.","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.",Neutral
3738,"(29, 30)","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.",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Neutral
3739,"(29, 31)","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.",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Neutral
3740,"(29, 32)","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.",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.,Neutral
3741,"(29, 33)","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.",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
3742,"(29, 34)","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.",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
3743,"(29, 35)","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.","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
3744,"(29, 36)","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.","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).",Neutral
3745,"(29, 37)","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.","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).",Neutral
3746,"(29, 38)","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.","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
3747,"(29, 39)","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.",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
3748,"(29, 40)","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.",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
3749,"(29, 41)","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.",The system shall improve efficiency of entering orders.,Neutral
3750,"(29, 42)","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.",The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
3751,"(29, 43)","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.",The system shall allow complete order sets to be predefined and personalized.,Neutral
3752,"(29, 44)","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.",The system shall allow order checking.,Neutral
3753,"(29, 45)","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.","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3754,"(29, 46)","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.","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3755,"(29, 47)","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.",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
3756,"(29, 48)","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.",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
3757,"(29, 49)","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.",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
3758,"(29, 50)","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.",The system shall support role-based access for security controls.,Neutral
3759,"(29, 51)","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.",The system shall support audit capability.,Neutral
3760,"(29, 52)","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.",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
3761,"(29, 53)","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.",The system shall support the requirements for all codified data ,Neutral
3762,"(29, 54)","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.","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
3763,"(29, 55)","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.",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
3764,"(29, 56)","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.",The system shall require the entry of an access code to gain access to the system.,Neutral
3765,"(29, 57)","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.",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
3766,"(29, 58)","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.",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
3767,"(29, 59)","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.",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3768,"(29, 60)","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.",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3769,"(29, 61)","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.","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
3770,"(29, 62)","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.",The system shall have pre-defined progress note templates.,Neutral
3771,"(29, 63)","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.",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
3772,"(29, 64)","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.","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
3773,"(29, 65)","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.",The system shall require only a smart card to digitally sign an order.,Neutral
3774,"(29, 66)","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.",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
3775,"(29, 67)","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.",The system shall allow users to enter time in several different formats.,Neutral
3776,"(29, 68)","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.",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3777,"(29, 69)","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.",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3778,"(29, 70)","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.","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.",Neutral
3779,"(29, 71)","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.","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.",Neutral
3780,"(29, 72)","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.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
3781,"(29, 73)","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.","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.",Neutral
3782,"(29, 74)","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.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
3783,"(29, 75)","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.",The system shall have a option to release unsigned orders to services,Neutral
3784,"(29, 76)","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.","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.",Neutral
3785,"(29, 77)","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.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
3786,"(29, 78)","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.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
3787,"(29, 79)","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.","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.",Neutral
3788,"(29, 80)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
3789,"(29, 81)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
3790,"(29, 82)","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.",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.,Neutral
3791,"(29, 83)","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.",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.,Neutral
3792,"(29, 84)","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.",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.,Neutral
3793,"(29, 85)","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.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
3794,"(29, 86)","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.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
3795,"(29, 87)","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.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
3796,"(29, 88)","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.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
3797,"(29, 89)","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.",The system shall not allow mandatory notifications to be disabled.,Neutral
3798,"(29, 90)","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.",The system shall allow users to disable unwanted notifications as desired.,Neutral
3799,"(29, 91)","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.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
3800,"(29, 92)","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.",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.,Neutral
3801,"(29, 93)","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.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
3802,"(29, 94)","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.",The system shall use any protocol for transferring messages among packages.,Neutral
3803,"(29, 95)","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.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
3804,"(29, 96)","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.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
3805,"(29, 97)","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.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
3806,"(29, 98)","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.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
3807,"(29, 99)","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.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
3808,"(29, 100)","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.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
3809,"(29, 101)","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.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
3810,"(29, 102)","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.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
3811,"(29, 103)","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.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
3812,"(29, 104)","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.",The system shall allow a user to foward notification to someone else at the site.,Neutral
3813,"(29, 105)","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.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
3814,"(29, 106)","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.","The system shall define, populate, and retrieve information about user classes.",Neutral
3815,"(29, 107)","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.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3816,"(29, 108)","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.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3817,"(29, 109)","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.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
3818,"(29, 110)","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.",The system shall allow concurrent membership in more than one User Class.,Neutral
3819,"(29, 111)","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.",The system shall allow membership in only one User Class.,Neutral
3820,"(29, 112)","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.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
3821,"(29, 113)","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.","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.",Neutral
3822,"(29, 114)","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.",The system shall improve accessibility of online clinical information and results.,Neutral
3823,"(29, 115)","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.","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.",Neutral
3824,"(29, 116)","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.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
3825,"(29, 117)","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.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
3826,"(29, 118)","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.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
3827,"(29, 119)","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.",The system shall make the traditional order entry processes more practical.,Neutral
3828,"(29, 120)","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.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
3829,"(29, 121)","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.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
3830,"(29, 122)","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.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
3831,"(29, 123)","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.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
3832,"(29, 124)","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.","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.",Neutral
3833,"(29, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
3834,"(29, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
3835,"(29, 127)","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.","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.",Neutral
3836,"(29, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
3837,"(29, 129)","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.","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.",Neutral
3838,"(29, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
3839,"(29, 131)","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.",The system shall delete history of received immunizations.,Neutral
3840,"(29, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
3841,"(29, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
3842,"(29, 134)","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.",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.,Neutral
3843,"(29, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
3844,"(29, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
3845,"(29, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
3846,"(29, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
3847,"(29, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
3848,"(29, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
3849,"(29, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
3850,"(29, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
3851,"(29, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
3852,"(29, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
3853,"(29, 145)","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.",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.,Neutral
3854,"(29, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
3855,"(29, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
3856,"(29, 148)","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.","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.",Neutral
3857,"(30, 31)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Conflict
3858,"(30, 32)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,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.,Neutral
3859,"(30, 33)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
3860,"(30, 34)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
3861,"(30, 35)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
3862,"(30, 36)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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).",Neutral
3863,"(30, 37)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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).",Neutral
3864,"(30, 38)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
3865,"(30, 39)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
3866,"(30, 40)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
3867,"(30, 41)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall improve efficiency of entering orders.,Neutral
3868,"(30, 42)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
3869,"(30, 43)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow complete order sets to be predefined and personalized.,Neutral
3870,"(30, 44)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow order checking.,Neutral
3871,"(30, 45)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3872,"(30, 46)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3873,"(30, 47)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
3874,"(30, 48)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
3875,"(30, 49)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
3876,"(30, 50)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall support role-based access for security controls.,Neutral
3877,"(30, 51)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall support audit capability.,Neutral
3878,"(30, 52)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
3879,"(30, 53)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall support the requirements for all codified data ,Neutral
3880,"(30, 54)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
3881,"(30, 55)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
3882,"(30, 56)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall require the entry of an access code to gain access to the system.,Neutral
3883,"(30, 57)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
3884,"(30, 58)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
3885,"(30, 59)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3886,"(30, 60)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
3887,"(30, 61)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
3888,"(30, 62)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall have pre-defined progress note templates.,Neutral
3889,"(30, 63)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
3890,"(30, 64)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
3891,"(30, 65)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall require only a smart card to digitally sign an order.,Neutral
3892,"(30, 66)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
3893,"(30, 67)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow users to enter time in several different formats.,Neutral
3894,"(30, 68)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3895,"(30, 69)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
3896,"(30, 70)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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.",Neutral
3897,"(30, 71)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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.",Neutral
3898,"(30, 72)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
3899,"(30, 73)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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.",Neutral
3900,"(30, 74)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
3901,"(30, 75)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall have a option to release unsigned orders to services,Neutral
3902,"(30, 76)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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.",Neutral
3903,"(30, 77)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
3904,"(30, 78)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
3905,"(30, 79)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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.",Neutral
3906,"(30, 80)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
3907,"(30, 81)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
3908,"(30, 82)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,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.,Neutral
3909,"(30, 83)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,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.,Neutral
3910,"(30, 84)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,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.,Neutral
3911,"(30, 85)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
3912,"(30, 86)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
3913,"(30, 87)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
3914,"(30, 88)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
3915,"(30, 89)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall not allow mandatory notifications to be disabled.,Neutral
3916,"(30, 90)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow users to disable unwanted notifications as desired.,Neutral
3917,"(30, 91)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
3918,"(30, 92)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,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.,Neutral
3919,"(30, 93)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
3920,"(30, 94)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall use any protocol for transferring messages among packages.,Neutral
3921,"(30, 95)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
3922,"(30, 96)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
3923,"(30, 97)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
3924,"(30, 98)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
3925,"(30, 99)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
3926,"(30, 100)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
3927,"(30, 101)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
3928,"(30, 102)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
3929,"(30, 103)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
3930,"(30, 104)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow a user to foward notification to someone else at the site.,Neutral
3931,"(30, 105)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
3932,"(30, 106)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall define, populate, and retrieve information about user classes.",Neutral
3933,"(30, 107)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3934,"(30, 108)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
3935,"(30, 109)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
3936,"(30, 110)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow concurrent membership in more than one User Class.,Neutral
3937,"(30, 111)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow membership in only one User Class.,Neutral
3938,"(30, 112)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
3939,"(30, 113)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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.",Neutral
3940,"(30, 114)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall improve accessibility of online clinical information and results.,Neutral
3941,"(30, 115)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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.",Neutral
3942,"(30, 116)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
3943,"(30, 117)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
3944,"(30, 118)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
3945,"(30, 119)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall make the traditional order entry processes more practical.,Neutral
3946,"(30, 120)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
3947,"(30, 121)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
3948,"(30, 122)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
3949,"(30, 123)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
3950,"(30, 124)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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.",Neutral
3951,"(30, 125)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
3952,"(30, 126)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
3953,"(30, 127)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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.",Neutral
3954,"(30, 128)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
3955,"(30, 129)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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.",Neutral
3956,"(30, 130)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
3957,"(30, 131)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall delete history of received immunizations.,Neutral
3958,"(30, 132)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
3959,"(30, 133)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
3960,"(30, 134)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,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.,Neutral
3961,"(30, 135)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system will provide the ability to register patients of all types.,Neutral
3962,"(30, 136)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
3963,"(30, 137)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
3964,"(30, 138)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
3965,"(30, 139)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
3966,"(30, 140)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
3967,"(30, 141)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
3968,"(30, 142)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
3969,"(30, 143)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
3970,"(30, 144)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
3971,"(30, 145)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,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.,Neutral
3972,"(30, 146)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
3973,"(30, 147)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
3974,"(30, 148)",The system shall require the user to have access to the Clinical Coorindator menu in the List Manager Interface to assign CPRS tab access.,"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.",Neutral
3975,"(31, 32)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,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.,Neutral
3976,"(31, 33)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
3977,"(31, 34)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
3978,"(31, 35)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
3979,"(31, 36)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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).",Neutral
3980,"(31, 37)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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).",Neutral
3981,"(31, 38)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
3982,"(31, 39)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
3983,"(31, 40)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
3984,"(31, 41)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall improve efficiency of entering orders.,Neutral
3985,"(31, 42)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
3986,"(31, 43)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow complete order sets to be predefined and personalized.,Neutral
3987,"(31, 44)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow order checking.,Neutral
3988,"(31, 45)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3989,"(31, 46)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
3990,"(31, 47)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
3991,"(31, 48)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
3992,"(31, 49)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
3993,"(31, 50)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall support role-based access for security controls.,Neutral
3994,"(31, 51)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall support audit capability.,Neutral
3995,"(31, 52)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
3996,"(31, 53)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall support the requirements for all codified data ,Neutral
3997,"(31, 54)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
3998,"(31, 55)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
3999,"(31, 56)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall require the entry of an access code to gain access to the system.,Neutral
4000,"(31, 57)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
4001,"(31, 58)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
4002,"(31, 59)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4003,"(31, 60)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4004,"(31, 61)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
4005,"(31, 62)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall have pre-defined progress note templates.,Neutral
4006,"(31, 63)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
4007,"(31, 64)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
4008,"(31, 65)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall require only a smart card to digitally sign an order.,Neutral
4009,"(31, 66)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
4010,"(31, 67)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow users to enter time in several different formats.,Neutral
4011,"(31, 68)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4012,"(31, 69)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4013,"(31, 70)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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.",Neutral
4014,"(31, 71)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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.",Neutral
4015,"(31, 72)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
4016,"(31, 73)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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.",Neutral
4017,"(31, 74)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
4018,"(31, 75)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall have a option to release unsigned orders to services,Neutral
4019,"(31, 76)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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.",Neutral
4020,"(31, 77)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
4021,"(31, 78)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
4022,"(31, 79)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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.",Neutral
4023,"(31, 80)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
4024,"(31, 81)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
4025,"(31, 82)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,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.,Neutral
4026,"(31, 83)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,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.,Neutral
4027,"(31, 84)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,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.,Neutral
4028,"(31, 85)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
4029,"(31, 86)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
4030,"(31, 87)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
4031,"(31, 88)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
4032,"(31, 89)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall not allow mandatory notifications to be disabled.,Neutral
4033,"(31, 90)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow users to disable unwanted notifications as desired.,Neutral
4034,"(31, 91)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
4035,"(31, 92)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,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.,Neutral
4036,"(31, 93)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
4037,"(31, 94)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall use any protocol for transferring messages among packages.,Neutral
4038,"(31, 95)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
4039,"(31, 96)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
4040,"(31, 97)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
4041,"(31, 98)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
4042,"(31, 99)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
4043,"(31, 100)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
4044,"(31, 101)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
4045,"(31, 102)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
4046,"(31, 103)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
4047,"(31, 104)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow a user to foward notification to someone else at the site.,Neutral
4048,"(31, 105)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
4049,"(31, 106)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall define, populate, and retrieve information about user classes.",Neutral
4050,"(31, 107)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4051,"(31, 108)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4052,"(31, 109)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
4053,"(31, 110)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow concurrent membership in more than one User Class.,Neutral
4054,"(31, 111)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow membership in only one User Class.,Neutral
4055,"(31, 112)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
4056,"(31, 113)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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.",Neutral
4057,"(31, 114)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall improve accessibility of online clinical information and results.,Neutral
4058,"(31, 115)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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.",Neutral
4059,"(31, 116)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
4060,"(31, 117)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
4061,"(31, 118)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
4062,"(31, 119)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall make the traditional order entry processes more practical.,Neutral
4063,"(31, 120)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
4064,"(31, 121)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
4065,"(31, 122)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
4066,"(31, 123)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
4067,"(31, 124)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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.",Neutral
4068,"(31, 125)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
4069,"(31, 126)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
4070,"(31, 127)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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.",Neutral
4071,"(31, 128)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
4072,"(31, 129)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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.",Neutral
4073,"(31, 130)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
4074,"(31, 131)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall delete history of received immunizations.,Neutral
4075,"(31, 132)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
4076,"(31, 133)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
4077,"(31, 134)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,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.,Neutral
4078,"(31, 135)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system will provide the ability to register patients of all types.,Neutral
4079,"(31, 136)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
4080,"(31, 137)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
4081,"(31, 138)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
4082,"(31, 139)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
4083,"(31, 140)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
4084,"(31, 141)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
4085,"(31, 142)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
4086,"(31, 143)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
4087,"(31, 144)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
4088,"(31, 145)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,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.,Neutral
4089,"(31, 146)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
4090,"(31, 147)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
4091,"(31, 148)",The system shall require the user to have access to the List Manager Interface to assign CPRS tab access.,"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.",Neutral
4092,"(32, 33)",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.,The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Neutral
4093,"(32, 34)",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.,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
4094,"(32, 35)",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.,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
4095,"(32, 36)",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.,"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).",Neutral
4096,"(32, 37)",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.,"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).",Neutral
4097,"(32, 38)",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.,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
4098,"(32, 39)",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.,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
4099,"(32, 40)",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.,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
4100,"(32, 41)",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.,The system shall improve efficiency of entering orders.,Neutral
4101,"(32, 42)",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.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
4102,"(32, 43)",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.,The system shall allow complete order sets to be predefined and personalized.,Neutral
4103,"(32, 44)",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.,The system shall allow order checking.,Neutral
4104,"(32, 45)",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.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4105,"(32, 46)",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.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4106,"(32, 47)",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.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
4107,"(32, 48)",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.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
4108,"(32, 49)",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.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
4109,"(32, 50)",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.,The system shall support role-based access for security controls.,Neutral
4110,"(32, 51)",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.,The system shall support audit capability.,Neutral
4111,"(32, 52)",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.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
4112,"(32, 53)",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.,The system shall support the requirements for all codified data ,Neutral
4113,"(32, 54)",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.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
4114,"(32, 55)",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.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
4115,"(32, 56)",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.,The system shall require the entry of an access code to gain access to the system.,Neutral
4116,"(32, 57)",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.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
4117,"(32, 58)",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.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
4118,"(32, 59)",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.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4119,"(32, 60)",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.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4120,"(32, 61)",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.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
4121,"(32, 62)",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.,The system shall have pre-defined progress note templates.,Neutral
4122,"(32, 63)",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.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
4123,"(32, 64)",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.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
4124,"(32, 65)",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.,The system shall require only a smart card to digitally sign an order.,Neutral
4125,"(32, 66)",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.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
4126,"(32, 67)",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.,The system shall allow users to enter time in several different formats.,Neutral
4127,"(32, 68)",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.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4128,"(32, 69)",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.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4129,"(32, 70)",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.,"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.",Neutral
4130,"(32, 71)",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.,"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.",Neutral
4131,"(32, 72)",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.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
4132,"(32, 73)",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.,"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.",Neutral
4133,"(32, 74)",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.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
4134,"(32, 75)",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.,The system shall have a option to release unsigned orders to services,Neutral
4135,"(32, 76)",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.,"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.",Neutral
4136,"(32, 77)",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.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
4137,"(32, 78)",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.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
4138,"(32, 79)",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.,"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.",Neutral
4139,"(32, 80)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
4140,"(32, 81)",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.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
4141,"(32, 82)",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.,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.,Neutral
4142,"(32, 83)",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.,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.,Neutral
4143,"(32, 84)",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.,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.,Neutral
4144,"(32, 85)",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.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
4145,"(32, 86)",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.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
4146,"(32, 87)",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.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
4147,"(32, 88)",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.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
4148,"(32, 89)",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.,The system shall not allow mandatory notifications to be disabled.,Neutral
4149,"(32, 90)",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.,The system shall allow users to disable unwanted notifications as desired.,Neutral
4150,"(32, 91)",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.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
4151,"(32, 92)",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.,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.,Neutral
4152,"(32, 93)",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.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
4153,"(32, 94)",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.,The system shall use any protocol for transferring messages among packages.,Neutral
4154,"(32, 95)",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.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
4155,"(32, 96)",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.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
4156,"(32, 97)",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.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
4157,"(32, 98)",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.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
4158,"(32, 99)",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.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
4159,"(32, 100)",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.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
4160,"(32, 101)",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.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
4161,"(32, 102)",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.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
4162,"(32, 103)",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.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
4163,"(32, 104)",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.,The system shall allow a user to foward notification to someone else at the site.,Neutral
4164,"(32, 105)",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.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
4165,"(32, 106)",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.,"The system shall define, populate, and retrieve information about user classes.",Neutral
4166,"(32, 107)",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.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4167,"(32, 108)",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.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4168,"(32, 109)",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.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
4169,"(32, 110)",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.,The system shall allow concurrent membership in more than one User Class.,Neutral
4170,"(32, 111)",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.,The system shall allow membership in only one User Class.,Neutral
4171,"(32, 112)",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.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
4172,"(32, 113)",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.,"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.",Neutral
4173,"(32, 114)",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.,The system shall improve accessibility of online clinical information and results.,Neutral
4174,"(32, 115)",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.,"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.",Neutral
4175,"(32, 116)",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.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
4176,"(32, 117)",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.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
4177,"(32, 118)",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.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
4178,"(32, 119)",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.,The system shall make the traditional order entry processes more practical.,Neutral
4179,"(32, 120)",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.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
4180,"(32, 121)",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.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
4181,"(32, 122)",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.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
4182,"(32, 123)",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.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
4183,"(32, 124)",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.,"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.",Neutral
4184,"(32, 125)",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.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
4185,"(32, 126)",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.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
4186,"(32, 127)",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.,"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.",Neutral
4187,"(32, 128)",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.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
4188,"(32, 129)",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.,"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.",Neutral
4189,"(32, 130)",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.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
4190,"(32, 131)",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.,The system shall delete history of received immunizations.,Neutral
4191,"(32, 132)",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.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
4192,"(32, 133)",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.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
4193,"(32, 134)",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.,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.,Neutral
4194,"(32, 135)",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.,The system will provide the ability to register patients of all types.,Neutral
4195,"(32, 136)",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.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
4196,"(32, 137)",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.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
4197,"(32, 138)",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.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
4198,"(32, 139)",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.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
4199,"(32, 140)",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.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
4200,"(32, 141)",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.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
4201,"(32, 142)",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.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
4202,"(32, 143)",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.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
4203,"(32, 144)",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.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
4204,"(32, 145)",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.,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.,Neutral
4205,"(32, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
4206,"(32, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
4207,"(32, 148)",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.,"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.",Neutral
4208,"(33, 34)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Neutral
4209,"(33, 35)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
4210,"(33, 36)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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).",Neutral
4211,"(33, 37)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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).",Neutral
4212,"(33, 38)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
4213,"(33, 39)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
4214,"(33, 40)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
4215,"(33, 41)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall improve efficiency of entering orders.,Neutral
4216,"(33, 42)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
4217,"(33, 43)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow complete order sets to be predefined and personalized.,Neutral
4218,"(33, 44)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow order checking.,Neutral
4219,"(33, 45)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4220,"(33, 46)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4221,"(33, 47)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
4222,"(33, 48)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
4223,"(33, 49)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
4224,"(33, 50)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall support role-based access for security controls.,Neutral
4225,"(33, 51)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall support audit capability.,Neutral
4226,"(33, 52)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
4227,"(33, 53)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall support the requirements for all codified data ,Neutral
4228,"(33, 54)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
4229,"(33, 55)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
4230,"(33, 56)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall require the entry of an access code to gain access to the system.,Neutral
4231,"(33, 57)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
4232,"(33, 58)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
4233,"(33, 59)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4234,"(33, 60)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4235,"(33, 61)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
4236,"(33, 62)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall have pre-defined progress note templates.,Neutral
4237,"(33, 63)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
4238,"(33, 64)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
4239,"(33, 65)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall require only a smart card to digitally sign an order.,Neutral
4240,"(33, 66)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
4241,"(33, 67)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow users to enter time in several different formats.,Neutral
4242,"(33, 68)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4243,"(33, 69)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4244,"(33, 70)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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.",Neutral
4245,"(33, 71)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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.",Neutral
4246,"(33, 72)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
4247,"(33, 73)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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.",Neutral
4248,"(33, 74)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
4249,"(33, 75)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall have a option to release unsigned orders to services,Neutral
4250,"(33, 76)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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.",Neutral
4251,"(33, 77)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
4252,"(33, 78)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
4253,"(33, 79)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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.",Neutral
4254,"(33, 80)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
4255,"(33, 81)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
4256,"(33, 82)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,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.,Neutral
4257,"(33, 83)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,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.,Neutral
4258,"(33, 84)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,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.,Neutral
4259,"(33, 85)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
4260,"(33, 86)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
4261,"(33, 87)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall display a message telling the user that the selected patient is deceased.,Neutral
4262,"(33, 88)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
4263,"(33, 89)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall not allow mandatory notifications to be disabled.,Neutral
4264,"(33, 90)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow users to disable unwanted notifications as desired.,Neutral
4265,"(33, 91)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
4266,"(33, 92)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,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.,Neutral
4267,"(33, 93)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
4268,"(33, 94)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall use any protocol for transferring messages among packages.,Neutral
4269,"(33, 95)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
4270,"(33, 96)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
4271,"(33, 97)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
4272,"(33, 98)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
4273,"(33, 99)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
4274,"(33, 100)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
4275,"(33, 101)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
4276,"(33, 102)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
4277,"(33, 103)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
4278,"(33, 104)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow a user to foward notification to someone else at the site.,Neutral
4279,"(33, 105)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
4280,"(33, 106)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall define, populate, and retrieve information about user classes.",Neutral
4281,"(33, 107)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4282,"(33, 108)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4283,"(33, 109)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
4284,"(33, 110)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow concurrent membership in more than one User Class.,Neutral
4285,"(33, 111)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow membership in only one User Class.,Neutral
4286,"(33, 112)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
4287,"(33, 113)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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.",Neutral
4288,"(33, 114)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall improve accessibility of online clinical information and results.,Neutral
4289,"(33, 115)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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.",Neutral
4290,"(33, 116)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
4291,"(33, 117)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
4292,"(33, 118)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
4293,"(33, 119)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall make the traditional order entry processes more practical.,Neutral
4294,"(33, 120)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
4295,"(33, 121)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
4296,"(33, 122)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
4297,"(33, 123)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
4298,"(33, 124)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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.",Neutral
4299,"(33, 125)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
4300,"(33, 126)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
4301,"(33, 127)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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.",Neutral
4302,"(33, 128)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
4303,"(33, 129)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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.",Neutral
4304,"(33, 130)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
4305,"(33, 131)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall delete history of received immunizations.,Neutral
4306,"(33, 132)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall only delete history of recieved immunizations unless user specifies,Neutral
4307,"(33, 133)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
4308,"(33, 134)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,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.,Neutral
4309,"(33, 135)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system will provide the ability to register patients of all types.,Neutral
4310,"(33, 136)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
4311,"(33, 137)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall include Standard Laboratory and Medication orderable files.,Neutral
4312,"(33, 138)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
4313,"(33, 139)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
4314,"(33, 140)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
4315,"(33, 141)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
4316,"(33, 142)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
4317,"(33, 143)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
4318,"(33, 144)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
4319,"(33, 145)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,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.,Neutral
4320,"(33, 146)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
4321,"(33, 147)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
4322,"(33, 148)",The system shall sort notifications based on column heading: Info (information alerts are preceded with an “I”).,"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.",Neutral
4323,"(34, 35)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Neutral
4324,"(34, 36)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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).",Neutral
4325,"(34, 37)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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).",Neutral
4326,"(34, 38)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
4327,"(34, 39)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
4328,"(34, 40)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
4329,"(34, 41)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall improve efficiency of entering orders.,Neutral
4330,"(34, 42)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
4331,"(34, 43)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow complete order sets to be predefined and personalized.,Neutral
4332,"(34, 44)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow order checking.,Neutral
4333,"(34, 45)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4334,"(34, 46)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4335,"(34, 47)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
4336,"(34, 48)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
4337,"(34, 49)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
4338,"(34, 50)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall support role-based access for security controls.,Neutral
4339,"(34, 51)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall support audit capability.,Neutral
4340,"(34, 52)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
4341,"(34, 53)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall support the requirements for all codified data ,Neutral
4342,"(34, 54)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
4343,"(34, 55)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
4344,"(34, 56)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall require the entry of an access code to gain access to the system.,Neutral
4345,"(34, 57)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
4346,"(34, 58)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
4347,"(34, 59)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4348,"(34, 60)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4349,"(34, 61)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
4350,"(34, 62)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall have pre-defined progress note templates.,Neutral
4351,"(34, 63)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
4352,"(34, 64)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
4353,"(34, 65)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall require only a smart card to digitally sign an order.,Neutral
4354,"(34, 66)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
4355,"(34, 67)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow users to enter time in several different formats.,Neutral
4356,"(34, 68)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4357,"(34, 69)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4358,"(34, 70)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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.",Neutral
4359,"(34, 71)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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.",Neutral
4360,"(34, 72)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
4361,"(34, 73)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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.",Neutral
4362,"(34, 74)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
4363,"(34, 75)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall have a option to release unsigned orders to services,Neutral
4364,"(34, 76)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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.",Neutral
4365,"(34, 77)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
4366,"(34, 78)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
4367,"(34, 79)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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.",Neutral
4368,"(34, 80)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
4369,"(34, 81)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
4370,"(34, 82)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,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.,Neutral
4371,"(34, 83)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,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.,Neutral
4372,"(34, 84)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,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.,Neutral
4373,"(34, 85)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
4374,"(34, 86)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
4375,"(34, 87)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall display a message telling the user that the selected patient is deceased.,Neutral
4376,"(34, 88)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
4377,"(34, 89)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall not allow mandatory notifications to be disabled.,Neutral
4378,"(34, 90)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow users to disable unwanted notifications as desired.,Neutral
4379,"(34, 91)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
4380,"(34, 92)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,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.,Neutral
4381,"(34, 93)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
4382,"(34, 94)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall use any protocol for transferring messages among packages.,Neutral
4383,"(34, 95)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
4384,"(34, 96)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
4385,"(34, 97)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
4386,"(34, 98)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
4387,"(34, 99)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
4388,"(34, 100)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
4389,"(34, 101)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
4390,"(34, 102)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
4391,"(34, 103)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
4392,"(34, 104)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow a user to foward notification to someone else at the site.,Neutral
4393,"(34, 105)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
4394,"(34, 106)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall define, populate, and retrieve information about user classes.",Neutral
4395,"(34, 107)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4396,"(34, 108)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4397,"(34, 109)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
4398,"(34, 110)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow concurrent membership in more than one User Class.,Neutral
4399,"(34, 111)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow membership in only one User Class.,Neutral
4400,"(34, 112)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
4401,"(34, 113)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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.",Neutral
4402,"(34, 114)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall improve accessibility of online clinical information and results.,Neutral
4403,"(34, 115)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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.",Neutral
4404,"(34, 116)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
4405,"(34, 117)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
4406,"(34, 118)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
4407,"(34, 119)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall make the traditional order entry processes more practical.,Neutral
4408,"(34, 120)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
4409,"(34, 121)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
4410,"(34, 122)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
4411,"(34, 123)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
4412,"(34, 124)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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.",Neutral
4413,"(34, 125)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
4414,"(34, 126)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
4415,"(34, 127)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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.",Neutral
4416,"(34, 128)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
4417,"(34, 129)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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.",Neutral
4418,"(34, 130)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
4419,"(34, 131)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall delete history of received immunizations.,Neutral
4420,"(34, 132)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall only delete history of recieved immunizations unless user specifies,Neutral
4421,"(34, 133)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
4422,"(34, 134)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,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.,Neutral
4423,"(34, 135)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system will provide the ability to register patients of all types.,Neutral
4424,"(34, 136)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
4425,"(34, 137)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall include Standard Laboratory and Medication orderable files.,Neutral
4426,"(34, 138)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
4427,"(34, 139)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
4428,"(34, 140)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
4429,"(34, 141)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
4430,"(34, 142)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
4431,"(34, 143)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
4432,"(34, 144)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
4433,"(34, 145)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,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.,Neutral
4434,"(34, 146)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
4435,"(34, 147)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
4436,"(34, 148)",The system shall sort notifications based on column heading: Patient name (alphabetical or reverse alphabetical).,"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.",Neutral
4437,"(35, 36)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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).",Neutral
4438,"(35, 37)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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).",Neutral
4439,"(35, 38)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
4440,"(35, 39)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
4441,"(35, 40)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
4442,"(35, 41)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall improve efficiency of entering orders.,Neutral
4443,"(35, 42)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
4444,"(35, 43)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow complete order sets to be predefined and personalized.,Neutral
4445,"(35, 44)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow order checking.,Neutral
4446,"(35, 45)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4447,"(35, 46)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4448,"(35, 47)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
4449,"(35, 48)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
4450,"(35, 49)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
4451,"(35, 50)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall support role-based access for security controls.,Neutral
4452,"(35, 51)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall support audit capability.,Neutral
4453,"(35, 52)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
4454,"(35, 53)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall support the requirements for all codified data ,Neutral
4455,"(35, 54)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
4456,"(35, 55)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
4457,"(35, 56)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall require the entry of an access code to gain access to the system.,Neutral
4458,"(35, 57)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
4459,"(35, 58)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
4460,"(35, 59)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4461,"(35, 60)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4462,"(35, 61)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
4463,"(35, 62)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall have pre-defined progress note templates.,Neutral
4464,"(35, 63)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
4465,"(35, 64)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
4466,"(35, 65)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall require only a smart card to digitally sign an order.,Neutral
4467,"(35, 66)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
4468,"(35, 67)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow users to enter time in several different formats.,Neutral
4469,"(35, 68)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4470,"(35, 69)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4471,"(35, 70)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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.",Neutral
4472,"(35, 71)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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.",Neutral
4473,"(35, 72)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
4474,"(35, 73)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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.",Neutral
4475,"(35, 74)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
4476,"(35, 75)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall have a option to release unsigned orders to services,Neutral
4477,"(35, 76)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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.",Neutral
4478,"(35, 77)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
4479,"(35, 78)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
4480,"(35, 79)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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.",Neutral
4481,"(35, 80)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
4482,"(35, 81)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
4483,"(35, 82)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",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.,Neutral
4484,"(35, 83)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",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.,Neutral
4485,"(35, 84)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",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.,Neutral
4486,"(35, 85)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
4487,"(35, 86)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
4488,"(35, 87)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall display a message telling the user that the selected patient is deceased.,Neutral
4489,"(35, 88)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
4490,"(35, 89)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall not allow mandatory notifications to be disabled.,Neutral
4491,"(35, 90)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow users to disable unwanted notifications as desired.,Neutral
4492,"(35, 91)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
4493,"(35, 92)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",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.,Neutral
4494,"(35, 93)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
4495,"(35, 94)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall use any protocol for transferring messages among packages.,Neutral
4496,"(35, 95)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
4497,"(35, 96)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
4498,"(35, 97)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
4499,"(35, 98)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
4500,"(35, 99)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
4501,"(35, 100)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
4502,"(35, 101)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
4503,"(35, 102)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
4504,"(35, 103)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
4505,"(35, 104)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow a user to foward notification to someone else at the site.,Neutral
4506,"(35, 105)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
4507,"(35, 106)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall define, populate, and retrieve information about user classes.",Neutral
4508,"(35, 107)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4509,"(35, 108)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4510,"(35, 109)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
4511,"(35, 110)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow concurrent membership in more than one User Class.,Neutral
4512,"(35, 111)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow membership in only one User Class.,Neutral
4513,"(35, 112)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
4514,"(35, 113)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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.",Neutral
4515,"(35, 114)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall improve accessibility of online clinical information and results.,Neutral
4516,"(35, 115)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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.",Neutral
4517,"(35, 116)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
4518,"(35, 117)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
4519,"(35, 118)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
4520,"(35, 119)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall make the traditional order entry processes more practical.,Neutral
4521,"(35, 120)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
4522,"(35, 121)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
4523,"(35, 122)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
4524,"(35, 123)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
4525,"(35, 124)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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.",Neutral
4526,"(35, 125)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
4527,"(35, 126)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
4528,"(35, 127)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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.",Neutral
4529,"(35, 128)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
4530,"(35, 129)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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.",Neutral
4531,"(35, 130)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
4532,"(35, 131)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall delete history of received immunizations.,Neutral
4533,"(35, 132)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall only delete history of recieved immunizations unless user specifies,Neutral
4534,"(35, 133)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
4535,"(35, 134)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",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.,Neutral
4536,"(35, 135)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system will provide the ability to register patients of all types.,Neutral
4537,"(35, 136)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
4538,"(35, 137)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall include Standard Laboratory and Medication orderable files.,Neutral
4539,"(35, 138)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
4540,"(35, 139)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
4541,"(35, 140)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
4542,"(35, 141)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
4543,"(35, 142)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
4544,"(35, 143)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
4545,"(35, 144)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
4546,"(35, 145)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",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.,Neutral
4547,"(35, 146)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
4548,"(35, 147)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
4549,"(35, 148)","The system shall sort notifications based on column heading: Location (patient location, if known, alphabetical or reverse alphabetical).","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.",Neutral
4550,"(36, 37)","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).","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).",Neutral
4551,"(36, 38)","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).","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
4552,"(36, 39)","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).",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
4553,"(36, 40)","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).",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
4554,"(36, 41)","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).",The system shall improve efficiency of entering orders.,Neutral
4555,"(36, 42)","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).",The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
4556,"(36, 43)","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).",The system shall allow complete order sets to be predefined and personalized.,Neutral
4557,"(36, 44)","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).",The system shall allow order checking.,Neutral
4558,"(36, 45)","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).","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4559,"(36, 46)","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).","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4560,"(36, 47)","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).",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
4561,"(36, 48)","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).",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
4562,"(36, 49)","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).",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
4563,"(36, 50)","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).",The system shall support role-based access for security controls.,Neutral
4564,"(36, 51)","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).",The system shall support audit capability.,Neutral
4565,"(36, 52)","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).",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
4566,"(36, 53)","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).",The system shall support the requirements for all codified data ,Neutral
4567,"(36, 54)","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).","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
4568,"(36, 55)","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).",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
4569,"(36, 56)","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).",The system shall require the entry of an access code to gain access to the system.,Neutral
4570,"(36, 57)","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).",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
4571,"(36, 58)","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).",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
4572,"(36, 59)","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).",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4573,"(36, 60)","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).",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4574,"(36, 61)","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).","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
4575,"(36, 62)","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).",The system shall have pre-defined progress note templates.,Neutral
4576,"(36, 63)","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).",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
4577,"(36, 64)","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).","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
4578,"(36, 65)","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).",The system shall require only a smart card to digitally sign an order.,Neutral
4579,"(36, 66)","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).",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
4580,"(36, 67)","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).",The system shall allow users to enter time in several different formats.,Neutral
4581,"(36, 68)","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).",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4582,"(36, 69)","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).",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4583,"(36, 70)","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).","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.",Neutral
4584,"(36, 71)","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).","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.",Neutral
4585,"(36, 72)","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).",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
4586,"(36, 73)","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).","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.",Neutral
4587,"(36, 74)","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).",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
4588,"(36, 75)","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).",The system shall have a option to release unsigned orders to services,Neutral
4589,"(36, 76)","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).","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.",Neutral
4590,"(36, 77)","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).",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
4591,"(36, 78)","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).",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
4592,"(36, 79)","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).","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.",Neutral
4593,"(36, 80)","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).",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
4594,"(36, 81)","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).",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
4595,"(36, 82)","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).",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.,Neutral
4596,"(36, 83)","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).",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.,Neutral
4597,"(36, 84)","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).",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.,Neutral
4598,"(36, 85)","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).",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
4599,"(36, 86)","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).",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
4600,"(36, 87)","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).",The system shall display a message telling the user that the selected patient is deceased.,Neutral
4601,"(36, 88)","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).",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
4602,"(36, 89)","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).",The system shall not allow mandatory notifications to be disabled.,Neutral
4603,"(36, 90)","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).",The system shall allow users to disable unwanted notifications as desired.,Neutral
4604,"(36, 91)","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).",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
4605,"(36, 92)","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).",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.,Neutral
4606,"(36, 93)","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).",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
4607,"(36, 94)","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).",The system shall use any protocol for transferring messages among packages.,Neutral
4608,"(36, 95)","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).",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
4609,"(36, 96)","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).",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
4610,"(36, 97)","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).",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
4611,"(36, 98)","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).",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
4612,"(36, 99)","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).",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
4613,"(36, 100)","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).",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
4614,"(36, 101)","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).",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
4615,"(36, 102)","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).","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
4616,"(36, 103)","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).",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
4617,"(36, 104)","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).",The system shall allow a user to foward notification to someone else at the site.,Neutral
4618,"(36, 105)","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).",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
4619,"(36, 106)","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).","The system shall define, populate, and retrieve information about user classes.",Neutral
4620,"(36, 107)","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).",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4621,"(36, 108)","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).",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4622,"(36, 109)","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).",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
4623,"(36, 110)","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).",The system shall allow concurrent membership in more than one User Class.,Neutral
4624,"(36, 111)","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).",The system shall allow membership in only one User Class.,Neutral
4625,"(36, 112)","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).",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
4626,"(36, 113)","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).","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.",Neutral
4627,"(36, 114)","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).",The system shall improve accessibility of online clinical information and results.,Neutral
4628,"(36, 115)","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).","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.",Neutral
4629,"(36, 116)","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).","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
4630,"(36, 117)","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).","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
4631,"(36, 118)","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).",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
4632,"(36, 119)","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).",The system shall make the traditional order entry processes more practical.,Neutral
4633,"(36, 120)","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).",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
4634,"(36, 121)","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).",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
4635,"(36, 122)","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).",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
4636,"(36, 123)","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).","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
4637,"(36, 124)","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).","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.",Neutral
4638,"(36, 125)","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).","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
4639,"(36, 126)","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).",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
4640,"(36, 127)","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).","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.",Neutral
4641,"(36, 128)","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).","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
4642,"(36, 129)","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).","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.",Neutral
4643,"(36, 130)","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).","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
4644,"(36, 131)","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).",The system shall delete history of received immunizations.,Neutral
4645,"(36, 132)","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).",The system shall only delete history of recieved immunizations unless user specifies,Neutral
4646,"(36, 133)","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).",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
4647,"(36, 134)","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).",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.,Neutral
4648,"(36, 135)","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).",The system will provide the ability to register patients of all types.,Neutral
4649,"(36, 136)","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).","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
4650,"(36, 137)","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).",The system shall include Standard Laboratory and Medication orderable files.,Neutral
4651,"(36, 138)","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).",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
4652,"(36, 139)","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).",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
4653,"(36, 140)","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).",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
4654,"(36, 141)","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).",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
4655,"(36, 142)","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).",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
4656,"(36, 143)","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).",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
4657,"(36, 144)","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).","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
4658,"(36, 145)","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).",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.,Neutral
4659,"(36, 146)","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).",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
4660,"(36, 147)","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).","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
4661,"(36, 148)","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).","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.",Neutral
4662,"(37, 38)","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).","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Neutral
4663,"(37, 39)","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).",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
4664,"(37, 40)","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).",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
4665,"(37, 41)","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).",The system shall improve efficiency of entering orders.,Neutral
4666,"(37, 42)","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).",The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
4667,"(37, 43)","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).",The system shall allow complete order sets to be predefined and personalized.,Neutral
4668,"(37, 44)","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).",The system shall allow order checking.,Neutral
4669,"(37, 45)","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).","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4670,"(37, 46)","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).","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4671,"(37, 47)","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).",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
4672,"(37, 48)","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).",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
4673,"(37, 49)","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).",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
4674,"(37, 50)","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).",The system shall support role-based access for security controls.,Neutral
4675,"(37, 51)","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).",The system shall support audit capability.,Neutral
4676,"(37, 52)","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).",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
4677,"(37, 53)","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).",The system shall support the requirements for all codified data ,Neutral
4678,"(37, 54)","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).","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
4679,"(37, 55)","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).",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
4680,"(37, 56)","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).",The system shall require the entry of an access code to gain access to the system.,Neutral
4681,"(37, 57)","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).",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
4682,"(37, 58)","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).",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
4683,"(37, 59)","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).",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4684,"(37, 60)","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).",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4685,"(37, 61)","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).","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
4686,"(37, 62)","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).",The system shall have pre-defined progress note templates.,Neutral
4687,"(37, 63)","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).",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
4688,"(37, 64)","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).","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
4689,"(37, 65)","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).",The system shall require only a smart card to digitally sign an order.,Neutral
4690,"(37, 66)","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).",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
4691,"(37, 67)","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).",The system shall allow users to enter time in several different formats.,Neutral
4692,"(37, 68)","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).",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4693,"(37, 69)","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).",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4694,"(37, 70)","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).","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.",Neutral
4695,"(37, 71)","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).","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.",Neutral
4696,"(37, 72)","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).",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
4697,"(37, 73)","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).","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.",Neutral
4698,"(37, 74)","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).",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
4699,"(37, 75)","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).",The system shall have a option to release unsigned orders to services,Neutral
4700,"(37, 76)","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).","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.",Neutral
4701,"(37, 77)","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).",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
4702,"(37, 78)","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).",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
4703,"(37, 79)","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).","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.",Neutral
4704,"(37, 80)","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).",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
4705,"(37, 81)","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).",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
4706,"(37, 82)","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).",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.,Neutral
4707,"(37, 83)","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).",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.,Neutral
4708,"(37, 84)","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).",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.,Neutral
4709,"(37, 85)","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).",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
4710,"(37, 86)","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).",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
4711,"(37, 87)","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).",The system shall display a message telling the user that the selected patient is deceased.,Neutral
4712,"(37, 88)","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).",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
4713,"(37, 89)","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).",The system shall not allow mandatory notifications to be disabled.,Neutral
4714,"(37, 90)","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).",The system shall allow users to disable unwanted notifications as desired.,Neutral
4715,"(37, 91)","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).",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
4716,"(37, 92)","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).",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.,Neutral
4717,"(37, 93)","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).",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
4718,"(37, 94)","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).",The system shall use any protocol for transferring messages among packages.,Neutral
4719,"(37, 95)","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).",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
4720,"(37, 96)","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).",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
4721,"(37, 97)","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).",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
4722,"(37, 98)","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).",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
4723,"(37, 99)","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).",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
4724,"(37, 100)","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).",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
4725,"(37, 101)","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).",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
4726,"(37, 102)","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).","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
4727,"(37, 103)","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).",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
4728,"(37, 104)","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).",The system shall allow a user to foward notification to someone else at the site.,Neutral
4729,"(37, 105)","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).",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
4730,"(37, 106)","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).","The system shall define, populate, and retrieve information about user classes.",Neutral
4731,"(37, 107)","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).",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4732,"(37, 108)","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).",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4733,"(37, 109)","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).",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
4734,"(37, 110)","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).",The system shall allow concurrent membership in more than one User Class.,Neutral
4735,"(37, 111)","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).",The system shall allow membership in only one User Class.,Neutral
4736,"(37, 112)","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).",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
4737,"(37, 113)","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).","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.",Neutral
4738,"(37, 114)","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).",The system shall improve accessibility of online clinical information and results.,Neutral
4739,"(37, 115)","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).","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.",Neutral
4740,"(37, 116)","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).","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
4741,"(37, 117)","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).","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
4742,"(37, 118)","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).",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
4743,"(37, 119)","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).",The system shall make the traditional order entry processes more practical.,Neutral
4744,"(37, 120)","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).",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
4745,"(37, 121)","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).",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
4746,"(37, 122)","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).",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
4747,"(37, 123)","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).","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
4748,"(37, 124)","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).","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.",Neutral
4749,"(37, 125)","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).","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
4750,"(37, 126)","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).",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
4751,"(37, 127)","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).","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.",Neutral
4752,"(37, 128)","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).","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
4753,"(37, 129)","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).","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.",Neutral
4754,"(37, 130)","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).","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
4755,"(37, 131)","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).",The system shall delete history of received immunizations.,Neutral
4756,"(37, 132)","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).",The system shall only delete history of recieved immunizations unless user specifies,Neutral
4757,"(37, 133)","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).",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
4758,"(37, 134)","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).",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.,Neutral
4759,"(37, 135)","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).",The system will provide the ability to register patients of all types.,Neutral
4760,"(37, 136)","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).","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
4761,"(37, 137)","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).",The system shall include Standard Laboratory and Medication orderable files.,Neutral
4762,"(37, 138)","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).",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
4763,"(37, 139)","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).",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
4764,"(37, 140)","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).",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
4765,"(37, 141)","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).",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
4766,"(37, 142)","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).",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
4767,"(37, 143)","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).",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
4768,"(37, 144)","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).","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
4769,"(37, 145)","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).",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.,Neutral
4770,"(37, 146)","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).",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
4771,"(37, 147)","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).","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
4772,"(37, 148)","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).","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.",Neutral
4773,"(38, 39)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Neutral
4774,"(38, 40)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
4775,"(38, 41)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall improve efficiency of entering orders.,Neutral
4776,"(38, 42)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
4777,"(38, 43)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow complete order sets to be predefined and personalized.,Neutral
4778,"(38, 44)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow order checking.,Neutral
4779,"(38, 45)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4780,"(38, 46)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4781,"(38, 47)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
4782,"(38, 48)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
4783,"(38, 49)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
4784,"(38, 50)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall support role-based access for security controls.,Neutral
4785,"(38, 51)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall support audit capability.,Neutral
4786,"(38, 52)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
4787,"(38, 53)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall support the requirements for all codified data ,Neutral
4788,"(38, 54)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
4789,"(38, 55)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
4790,"(38, 56)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall require the entry of an access code to gain access to the system.,Neutral
4791,"(38, 57)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
4792,"(38, 58)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
4793,"(38, 59)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4794,"(38, 60)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4795,"(38, 61)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
4796,"(38, 62)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall have pre-defined progress note templates.,Neutral
4797,"(38, 63)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
4798,"(38, 64)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
4799,"(38, 65)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall require only a smart card to digitally sign an order.,Neutral
4800,"(38, 66)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
4801,"(38, 67)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow users to enter time in several different formats.,Neutral
4802,"(38, 68)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4803,"(38, 69)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4804,"(38, 70)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","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.",Neutral
4805,"(38, 71)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","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.",Neutral
4806,"(38, 72)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
4807,"(38, 73)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","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.",Neutral
4808,"(38, 74)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
4809,"(38, 75)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall have a option to release unsigned orders to services,Neutral
4810,"(38, 76)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","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.",Neutral
4811,"(38, 77)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
4812,"(38, 78)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
4813,"(38, 79)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","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.",Neutral
4814,"(38, 80)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
4815,"(38, 81)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
4816,"(38, 82)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",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.,Neutral
4817,"(38, 83)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",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.,Neutral
4818,"(38, 84)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",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.,Neutral
4819,"(38, 85)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
4820,"(38, 86)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
4821,"(38, 87)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall display a message telling the user that the selected patient is deceased.,Neutral
4822,"(38, 88)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
4823,"(38, 89)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall not allow mandatory notifications to be disabled.,Neutral
4824,"(38, 90)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow users to disable unwanted notifications as desired.,Neutral
4825,"(38, 91)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
4826,"(38, 92)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",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.,Neutral
4827,"(38, 93)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
4828,"(38, 94)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall use any protocol for transferring messages among packages.,Neutral
4829,"(38, 95)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
4830,"(38, 96)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
4831,"(38, 97)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
4832,"(38, 98)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
4833,"(38, 99)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
4834,"(38, 100)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
4835,"(38, 101)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
4836,"(38, 102)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
4837,"(38, 103)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
4838,"(38, 104)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow a user to foward notification to someone else at the site.,Neutral
4839,"(38, 105)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
4840,"(38, 106)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall define, populate, and retrieve information about user classes.",Neutral
4841,"(38, 107)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4842,"(38, 108)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4843,"(38, 109)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
4844,"(38, 110)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow concurrent membership in more than one User Class.,Neutral
4845,"(38, 111)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow membership in only one User Class.,Neutral
4846,"(38, 112)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
4847,"(38, 113)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","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.",Neutral
4848,"(38, 114)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall improve accessibility of online clinical information and results.,Neutral
4849,"(38, 115)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","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.",Neutral
4850,"(38, 116)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
4851,"(38, 117)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
4852,"(38, 118)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
4853,"(38, 119)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall make the traditional order entry processes more practical.,Neutral
4854,"(38, 120)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
4855,"(38, 121)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
4856,"(38, 122)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
4857,"(38, 123)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
4858,"(38, 124)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","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.",Neutral
4859,"(38, 125)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
4860,"(38, 126)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
4861,"(38, 127)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","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.",Neutral
4862,"(38, 128)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
4863,"(38, 129)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","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.",Neutral
4864,"(38, 130)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
4865,"(38, 131)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall delete history of received immunizations.,Neutral
4866,"(38, 132)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall only delete history of recieved immunizations unless user specifies,Neutral
4867,"(38, 133)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
4868,"(38, 134)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",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.,Neutral
4869,"(38, 135)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system will provide the ability to register patients of all types.,Neutral
4870,"(38, 136)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
4871,"(38, 137)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall include Standard Laboratory and Medication orderable files.,Neutral
4872,"(38, 138)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
4873,"(38, 139)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
4874,"(38, 140)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
4875,"(38, 141)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
4876,"(38, 142)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
4877,"(38, 143)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
4878,"(38, 144)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
4879,"(38, 145)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",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.,Neutral
4880,"(38, 146)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
4881,"(38, 147)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
4882,"(38, 148)","The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical).","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.",Neutral
4883,"(39, 40)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Neutral
4884,"(39, 41)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall improve efficiency of entering orders.,Neutral
4885,"(39, 42)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
4886,"(39, 43)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow complete order sets to be predefined and personalized.,Neutral
4887,"(39, 44)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow order checking.,Neutral
4888,"(39, 45)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4889,"(39, 46)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4890,"(39, 47)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
4891,"(39, 48)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
4892,"(39, 49)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
4893,"(39, 50)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall support role-based access for security controls.,Neutral
4894,"(39, 51)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall support audit capability.,Neutral
4895,"(39, 52)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
4896,"(39, 53)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall support the requirements for all codified data ,Neutral
4897,"(39, 54)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
4898,"(39, 55)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
4899,"(39, 56)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall require the entry of an access code to gain access to the system.,Neutral
4900,"(39, 57)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
4901,"(39, 58)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
4902,"(39, 59)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4903,"(39, 60)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
4904,"(39, 61)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
4905,"(39, 62)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall have pre-defined progress note templates.,Neutral
4906,"(39, 63)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
4907,"(39, 64)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
4908,"(39, 65)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall require only a smart card to digitally sign an order.,Neutral
4909,"(39, 66)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
4910,"(39, 67)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow users to enter time in several different formats.,Neutral
4911,"(39, 68)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4912,"(39, 69)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
4913,"(39, 70)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"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.",Neutral
4914,"(39, 71)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"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.",Neutral
4915,"(39, 72)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
4916,"(39, 73)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"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.",Neutral
4917,"(39, 74)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
4918,"(39, 75)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall have a option to release unsigned orders to services,Neutral
4919,"(39, 76)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"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.",Neutral
4920,"(39, 77)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
4921,"(39, 78)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
4922,"(39, 79)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"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.",Neutral
4923,"(39, 80)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
4924,"(39, 81)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
4925,"(39, 82)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,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.,Neutral
4926,"(39, 83)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,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.,Neutral
4927,"(39, 84)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,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.,Neutral
4928,"(39, 85)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
4929,"(39, 86)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
4930,"(39, 87)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall display a message telling the user that the selected patient is deceased.,Neutral
4931,"(39, 88)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
4932,"(39, 89)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall not allow mandatory notifications to be disabled.,Neutral
4933,"(39, 90)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow users to disable unwanted notifications as desired.,Neutral
4934,"(39, 91)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
4935,"(39, 92)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,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.,Neutral
4936,"(39, 93)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
4937,"(39, 94)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall use any protocol for transferring messages among packages.,Neutral
4938,"(39, 95)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
4939,"(39, 96)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
4940,"(39, 97)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
4941,"(39, 98)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
4942,"(39, 99)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
4943,"(39, 100)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
4944,"(39, 101)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
4945,"(39, 102)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
4946,"(39, 103)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
4947,"(39, 104)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow a user to foward notification to someone else at the site.,Neutral
4948,"(39, 105)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
4949,"(39, 106)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall define, populate, and retrieve information about user classes.",Neutral
4950,"(39, 107)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4951,"(39, 108)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
4952,"(39, 109)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
4953,"(39, 110)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow concurrent membership in more than one User Class.,Neutral
4954,"(39, 111)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow membership in only one User Class.,Neutral
4955,"(39, 112)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
4956,"(39, 113)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"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.",Neutral
4957,"(39, 114)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall improve accessibility of online clinical information and results.,Neutral
4958,"(39, 115)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"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.",Neutral
4959,"(39, 116)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
4960,"(39, 117)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
4961,"(39, 118)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
4962,"(39, 119)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall make the traditional order entry processes more practical.,Neutral
4963,"(39, 120)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
4964,"(39, 121)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
4965,"(39, 122)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
4966,"(39, 123)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
4967,"(39, 124)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"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.",Neutral
4968,"(39, 125)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
4969,"(39, 126)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
4970,"(39, 127)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"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.",Neutral
4971,"(39, 128)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
4972,"(39, 129)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"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.",Neutral
4973,"(39, 130)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
4974,"(39, 131)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall delete history of received immunizations.,Neutral
4975,"(39, 132)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall only delete history of recieved immunizations unless user specifies,Neutral
4976,"(39, 133)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
4977,"(39, 134)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,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.,Neutral
4978,"(39, 135)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system will provide the ability to register patients of all types.,Neutral
4979,"(39, 136)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
4980,"(39, 137)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall include Standard Laboratory and Medication orderable files.,Neutral
4981,"(39, 138)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
4982,"(39, 139)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
4983,"(39, 140)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
4984,"(39, 141)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
4985,"(39, 142)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
4986,"(39, 143)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
4987,"(39, 144)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
4988,"(39, 145)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,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.,Neutral
4989,"(39, 146)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
4990,"(39, 147)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
4991,"(39, 148)",The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person).,"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.",Neutral
4992,"(40, 41)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall improve efficiency of entering orders.,Neutral
4993,"(40, 42)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall improve efficiency of entering orders by atleast 20 percent.,Neutral
4994,"(40, 43)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow complete order sets to be predefined and personalized.,Neutral
4995,"(40, 44)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow order checking.,Neutral
4996,"(40, 45)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4997,"(40, 46)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
4998,"(40, 47)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
4999,"(40, 48)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
5000,"(40, 49)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
5001,"(40, 50)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall support role-based access for security controls.,Neutral
5002,"(40, 51)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall support audit capability.,Neutral
5003,"(40, 52)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
5004,"(40, 53)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall support the requirements for all codified data ,Neutral
5005,"(40, 54)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
5006,"(40, 55)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
5007,"(40, 56)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall require the entry of an access code to gain access to the system.,Neutral
5008,"(40, 57)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
5009,"(40, 58)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
5010,"(40, 59)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5011,"(40, 60)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5012,"(40, 61)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
5013,"(40, 62)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall have pre-defined progress note templates.,Neutral
5014,"(40, 63)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
5015,"(40, 64)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
5016,"(40, 65)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall require only a smart card to digitally sign an order.,Neutral
5017,"(40, 66)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
5018,"(40, 67)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow users to enter time in several different formats.,Neutral
5019,"(40, 68)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5020,"(40, 69)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5021,"(40, 70)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"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.",Neutral
5022,"(40, 71)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"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.",Neutral
5023,"(40, 72)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
5024,"(40, 73)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"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.",Neutral
5025,"(40, 74)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
5026,"(40, 75)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall have a option to release unsigned orders to services,Neutral
5027,"(40, 76)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"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.",Neutral
5028,"(40, 77)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
5029,"(40, 78)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
5030,"(40, 79)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"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.",Neutral
5031,"(40, 80)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
5032,"(40, 81)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
5033,"(40, 82)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,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.,Neutral
5034,"(40, 83)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,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.,Neutral
5035,"(40, 84)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,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.,Neutral
5036,"(40, 85)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
5037,"(40, 86)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
5038,"(40, 87)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
5039,"(40, 88)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
5040,"(40, 89)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall not allow mandatory notifications to be disabled.,Neutral
5041,"(40, 90)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow users to disable unwanted notifications as desired.,Neutral
5042,"(40, 91)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
5043,"(40, 92)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,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.,Neutral
5044,"(40, 93)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
5045,"(40, 94)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall use any protocol for transferring messages among packages.,Neutral
5046,"(40, 95)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
5047,"(40, 96)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
5048,"(40, 97)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
5049,"(40, 98)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
5050,"(40, 99)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
5051,"(40, 100)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
5052,"(40, 101)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
5053,"(40, 102)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
5054,"(40, 103)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
5055,"(40, 104)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow a user to foward notification to someone else at the site.,Neutral
5056,"(40, 105)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
5057,"(40, 106)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall define, populate, and retrieve information about user classes.",Neutral
5058,"(40, 107)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5059,"(40, 108)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5060,"(40, 109)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
5061,"(40, 110)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow concurrent membership in more than one User Class.,Neutral
5062,"(40, 111)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow membership in only one User Class.,Neutral
5063,"(40, 112)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
5064,"(40, 113)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"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.",Neutral
5065,"(40, 114)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall improve accessibility of online clinical information and results.,Neutral
5066,"(40, 115)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"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.",Neutral
5067,"(40, 116)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
5068,"(40, 117)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
5069,"(40, 118)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
5070,"(40, 119)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall make the traditional order entry processes more practical.,Neutral
5071,"(40, 120)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
5072,"(40, 121)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
5073,"(40, 122)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
5074,"(40, 123)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
5075,"(40, 124)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"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.",Neutral
5076,"(40, 125)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
5077,"(40, 126)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
5078,"(40, 127)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"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.",Neutral
5079,"(40, 128)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
5080,"(40, 129)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"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.",Neutral
5081,"(40, 130)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
5082,"(40, 131)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall delete history of received immunizations.,Neutral
5083,"(40, 132)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
5084,"(40, 133)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
5085,"(40, 134)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,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.,Neutral
5086,"(40, 135)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system will provide the ability to register patients of all types.,Neutral
5087,"(40, 136)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
5088,"(40, 137)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
5089,"(40, 138)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
5090,"(40, 139)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
5091,"(40, 140)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
5092,"(40, 141)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
5093,"(40, 142)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
5094,"(40, 143)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
5095,"(40, 144)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
5096,"(40, 145)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,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.,Neutral
5097,"(40, 146)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
5098,"(40, 147)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
5099,"(40, 148)",The system shall indicate problems with inactive codes have the “#” symbol in the status column.,"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.",Neutral
5100,"(41, 42)",The system shall improve efficiency of entering orders.,The system shall improve efficiency of entering orders by atleast 20 percent.,Conflict
5101,"(41, 43)",The system shall improve efficiency of entering orders.,The system shall allow complete order sets to be predefined and personalized.,Neutral
5102,"(41, 44)",The system shall improve efficiency of entering orders.,The system shall allow order checking.,Neutral
5103,"(41, 45)",The system shall improve efficiency of entering orders.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
5104,"(41, 46)",The system shall improve efficiency of entering orders.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
5105,"(41, 47)",The system shall improve efficiency of entering orders.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
5106,"(41, 48)",The system shall improve efficiency of entering orders.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
5107,"(41, 49)",The system shall improve efficiency of entering orders.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
5108,"(41, 50)",The system shall improve efficiency of entering orders.,The system shall support role-based access for security controls.,Neutral
5109,"(41, 51)",The system shall improve efficiency of entering orders.,The system shall support audit capability.,Neutral
5110,"(41, 52)",The system shall improve efficiency of entering orders.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
5111,"(41, 53)",The system shall improve efficiency of entering orders.,The system shall support the requirements for all codified data ,Neutral
5112,"(41, 54)",The system shall improve efficiency of entering orders.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
5113,"(41, 55)",The system shall improve efficiency of entering orders.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
5114,"(41, 56)",The system shall improve efficiency of entering orders.,The system shall require the entry of an access code to gain access to the system.,Neutral
5115,"(41, 57)",The system shall improve efficiency of entering orders.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
5116,"(41, 58)",The system shall improve efficiency of entering orders.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
5117,"(41, 59)",The system shall improve efficiency of entering orders.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5118,"(41, 60)",The system shall improve efficiency of entering orders.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5119,"(41, 61)",The system shall improve efficiency of entering orders.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
5120,"(41, 62)",The system shall improve efficiency of entering orders.,The system shall have pre-defined progress note templates.,Neutral
5121,"(41, 63)",The system shall improve efficiency of entering orders.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
5122,"(41, 64)",The system shall improve efficiency of entering orders.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
5123,"(41, 65)",The system shall improve efficiency of entering orders.,The system shall require only a smart card to digitally sign an order.,Neutral
5124,"(41, 66)",The system shall improve efficiency of entering orders.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
5125,"(41, 67)",The system shall improve efficiency of entering orders.,The system shall allow users to enter time in several different formats.,Neutral
5126,"(41, 68)",The system shall improve efficiency of entering orders.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5127,"(41, 69)",The system shall improve efficiency of entering orders.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5128,"(41, 70)",The system shall improve efficiency of entering orders.,"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.",Neutral
5129,"(41, 71)",The system shall improve efficiency of entering orders.,"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.",Neutral
5130,"(41, 72)",The system shall improve efficiency of entering orders.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
5131,"(41, 73)",The system shall improve efficiency of entering orders.,"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.",Neutral
5132,"(41, 74)",The system shall improve efficiency of entering orders.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
5133,"(41, 75)",The system shall improve efficiency of entering orders.,The system shall have a option to release unsigned orders to services,Neutral
5134,"(41, 76)",The system shall improve efficiency of entering orders.,"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.",Neutral
5135,"(41, 77)",The system shall improve efficiency of entering orders.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
5136,"(41, 78)",The system shall improve efficiency of entering orders.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
5137,"(41, 79)",The system shall improve efficiency of entering orders.,"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.",Neutral
5138,"(41, 80)",The system shall improve efficiency of entering orders.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
5139,"(41, 81)",The system shall improve efficiency of entering orders.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
5140,"(41, 82)",The system shall improve efficiency of entering orders.,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.,Neutral
5141,"(41, 83)",The system shall improve efficiency of entering orders.,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.,Neutral
5142,"(41, 84)",The system shall improve efficiency of entering orders.,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.,Neutral
5143,"(41, 85)",The system shall improve efficiency of entering orders.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
5144,"(41, 86)",The system shall improve efficiency of entering orders.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
5145,"(41, 87)",The system shall improve efficiency of entering orders.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
5146,"(41, 88)",The system shall improve efficiency of entering orders.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
5147,"(41, 89)",The system shall improve efficiency of entering orders.,The system shall not allow mandatory notifications to be disabled.,Neutral
5148,"(41, 90)",The system shall improve efficiency of entering orders.,The system shall allow users to disable unwanted notifications as desired.,Neutral
5149,"(41, 91)",The system shall improve efficiency of entering orders.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
5150,"(41, 92)",The system shall improve efficiency of entering orders.,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.,Neutral
5151,"(41, 93)",The system shall improve efficiency of entering orders.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
5152,"(41, 94)",The system shall improve efficiency of entering orders.,The system shall use any protocol for transferring messages among packages.,Neutral
5153,"(41, 95)",The system shall improve efficiency of entering orders.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
5154,"(41, 96)",The system shall improve efficiency of entering orders.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
5155,"(41, 97)",The system shall improve efficiency of entering orders.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
5156,"(41, 98)",The system shall improve efficiency of entering orders.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
5157,"(41, 99)",The system shall improve efficiency of entering orders.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
5158,"(41, 100)",The system shall improve efficiency of entering orders.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
5159,"(41, 101)",The system shall improve efficiency of entering orders.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
5160,"(41, 102)",The system shall improve efficiency of entering orders.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
5161,"(41, 103)",The system shall improve efficiency of entering orders.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
5162,"(41, 104)",The system shall improve efficiency of entering orders.,The system shall allow a user to foward notification to someone else at the site.,Neutral
5163,"(41, 105)",The system shall improve efficiency of entering orders.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
5164,"(41, 106)",The system shall improve efficiency of entering orders.,"The system shall define, populate, and retrieve information about user classes.",Neutral
5165,"(41, 107)",The system shall improve efficiency of entering orders.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5166,"(41, 108)",The system shall improve efficiency of entering orders.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5167,"(41, 109)",The system shall improve efficiency of entering orders.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
5168,"(41, 110)",The system shall improve efficiency of entering orders.,The system shall allow concurrent membership in more than one User Class.,Neutral
5169,"(41, 111)",The system shall improve efficiency of entering orders.,The system shall allow membership in only one User Class.,Neutral
5170,"(41, 112)",The system shall improve efficiency of entering orders.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
5171,"(41, 113)",The system shall improve efficiency of entering orders.,"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.",Neutral
5172,"(41, 114)",The system shall improve efficiency of entering orders.,The system shall improve accessibility of online clinical information and results.,Neutral
5173,"(41, 115)",The system shall improve efficiency of entering orders.,"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.",Neutral
5174,"(41, 116)",The system shall improve efficiency of entering orders.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
5175,"(41, 117)",The system shall improve efficiency of entering orders.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
5176,"(41, 118)",The system shall improve efficiency of entering orders.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
5177,"(41, 119)",The system shall improve efficiency of entering orders.,The system shall make the traditional order entry processes more practical.,Neutral
5178,"(41, 120)",The system shall improve efficiency of entering orders.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
5179,"(41, 121)",The system shall improve efficiency of entering orders.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
5180,"(41, 122)",The system shall improve efficiency of entering orders.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
5181,"(41, 123)",The system shall improve efficiency of entering orders.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
5182,"(41, 124)",The system shall improve efficiency of entering orders.,"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.",Neutral
5183,"(41, 125)",The system shall improve efficiency of entering orders.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
5184,"(41, 126)",The system shall improve efficiency of entering orders.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
5185,"(41, 127)",The system shall improve efficiency of entering orders.,"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.",Neutral
5186,"(41, 128)",The system shall improve efficiency of entering orders.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
5187,"(41, 129)",The system shall improve efficiency of entering orders.,"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.",Neutral
5188,"(41, 130)",The system shall improve efficiency of entering orders.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
5189,"(41, 131)",The system shall improve efficiency of entering orders.,The system shall delete history of received immunizations.,Neutral
5190,"(41, 132)",The system shall improve efficiency of entering orders.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
5191,"(41, 133)",The system shall improve efficiency of entering orders.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
5192,"(41, 134)",The system shall improve efficiency of entering orders.,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.,Neutral
5193,"(41, 135)",The system shall improve efficiency of entering orders.,The system will provide the ability to register patients of all types.,Neutral
5194,"(41, 136)",The system shall improve efficiency of entering orders.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
5195,"(41, 137)",The system shall improve efficiency of entering orders.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
5196,"(41, 138)",The system shall improve efficiency of entering orders.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
5197,"(41, 139)",The system shall improve efficiency of entering orders.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
5198,"(41, 140)",The system shall improve efficiency of entering orders.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
5199,"(41, 141)",The system shall improve efficiency of entering orders.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
5200,"(41, 142)",The system shall improve efficiency of entering orders.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
5201,"(41, 143)",The system shall improve efficiency of entering orders.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
5202,"(41, 144)",The system shall improve efficiency of entering orders.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
5203,"(41, 145)",The system shall improve efficiency of entering orders.,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.,Neutral
5204,"(41, 146)",The system shall improve efficiency of entering orders.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
5205,"(41, 147)",The system shall improve efficiency of entering orders.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
5206,"(41, 148)",The system shall improve efficiency of entering orders.,"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.",Neutral
5207,"(42, 43)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow complete order sets to be predefined and personalized.,Neutral
5208,"(42, 44)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow order checking.,Neutral
5209,"(42, 45)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
5210,"(42, 46)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
5211,"(42, 47)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
5212,"(42, 48)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
5213,"(42, 49)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
5214,"(42, 50)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall support role-based access for security controls.,Neutral
5215,"(42, 51)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall support audit capability.,Neutral
5216,"(42, 52)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
5217,"(42, 53)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall support the requirements for all codified data ,Neutral
5218,"(42, 54)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
5219,"(42, 55)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
5220,"(42, 56)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall require the entry of an access code to gain access to the system.,Neutral
5221,"(42, 57)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
5222,"(42, 58)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
5223,"(42, 59)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5224,"(42, 60)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5225,"(42, 61)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
5226,"(42, 62)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall have pre-defined progress note templates.,Neutral
5227,"(42, 63)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
5228,"(42, 64)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
5229,"(42, 65)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall require only a smart card to digitally sign an order.,Neutral
5230,"(42, 66)",The system shall improve efficiency of entering orders by atleast 20 percent.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
5231,"(42, 67)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow users to enter time in several different formats.,Neutral
5232,"(42, 68)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5233,"(42, 69)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5234,"(42, 70)",The system shall improve efficiency of entering orders by atleast 20 percent.,"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.",Neutral
5235,"(42, 71)",The system shall improve efficiency of entering orders by atleast 20 percent.,"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.",Neutral
5236,"(42, 72)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
5237,"(42, 73)",The system shall improve efficiency of entering orders by atleast 20 percent.,"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.",Neutral
5238,"(42, 74)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
5239,"(42, 75)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall have a option to release unsigned orders to services,Neutral
5240,"(42, 76)",The system shall improve efficiency of entering orders by atleast 20 percent.,"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.",Neutral
5241,"(42, 77)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
5242,"(42, 78)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
5243,"(42, 79)",The system shall improve efficiency of entering orders by atleast 20 percent.,"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.",Neutral
5244,"(42, 80)",The system shall improve efficiency of entering orders by atleast 20 percent.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
5245,"(42, 81)",The system shall improve efficiency of entering orders by atleast 20 percent.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
5246,"(42, 82)",The system shall improve efficiency of entering orders by atleast 20 percent.,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.,Neutral
5247,"(42, 83)",The system shall improve efficiency of entering orders by atleast 20 percent.,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.,Neutral
5248,"(42, 84)",The system shall improve efficiency of entering orders by atleast 20 percent.,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.,Neutral
5249,"(42, 85)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
5250,"(42, 86)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
5251,"(42, 87)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
5252,"(42, 88)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
5253,"(42, 89)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall not allow mandatory notifications to be disabled.,Neutral
5254,"(42, 90)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow users to disable unwanted notifications as desired.,Neutral
5255,"(42, 91)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
5256,"(42, 92)",The system shall improve efficiency of entering orders by atleast 20 percent.,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.,Neutral
5257,"(42, 93)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
5258,"(42, 94)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall use any protocol for transferring messages among packages.,Neutral
5259,"(42, 95)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
5260,"(42, 96)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
5261,"(42, 97)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
5262,"(42, 98)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
5263,"(42, 99)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
5264,"(42, 100)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
5265,"(42, 101)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
5266,"(42, 102)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
5267,"(42, 103)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
5268,"(42, 104)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow a user to foward notification to someone else at the site.,Neutral
5269,"(42, 105)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
5270,"(42, 106)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall define, populate, and retrieve information about user classes.",Neutral
5271,"(42, 107)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5272,"(42, 108)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5273,"(42, 109)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
5274,"(42, 110)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow concurrent membership in more than one User Class.,Neutral
5275,"(42, 111)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow membership in only one User Class.,Neutral
5276,"(42, 112)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
5277,"(42, 113)",The system shall improve efficiency of entering orders by atleast 20 percent.,"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.",Neutral
5278,"(42, 114)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall improve accessibility of online clinical information and results.,Neutral
5279,"(42, 115)",The system shall improve efficiency of entering orders by atleast 20 percent.,"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.",Neutral
5280,"(42, 116)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
5281,"(42, 117)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
5282,"(42, 118)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
5283,"(42, 119)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall make the traditional order entry processes more practical.,Neutral
5284,"(42, 120)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
5285,"(42, 121)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
5286,"(42, 122)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
5287,"(42, 123)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
5288,"(42, 124)",The system shall improve efficiency of entering orders by atleast 20 percent.,"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.",Neutral
5289,"(42, 125)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
5290,"(42, 126)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
5291,"(42, 127)",The system shall improve efficiency of entering orders by atleast 20 percent.,"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.",Neutral
5292,"(42, 128)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
5293,"(42, 129)",The system shall improve efficiency of entering orders by atleast 20 percent.,"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.",Neutral
5294,"(42, 130)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
5295,"(42, 131)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall delete history of received immunizations.,Neutral
5296,"(42, 132)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
5297,"(42, 133)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
5298,"(42, 134)",The system shall improve efficiency of entering orders by atleast 20 percent.,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.,Neutral
5299,"(42, 135)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system will provide the ability to register patients of all types.,Neutral
5300,"(42, 136)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
5301,"(42, 137)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
5302,"(42, 138)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
5303,"(42, 139)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
5304,"(42, 140)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
5305,"(42, 141)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
5306,"(42, 142)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
5307,"(42, 143)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
5308,"(42, 144)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
5309,"(42, 145)",The system shall improve efficiency of entering orders by atleast 20 percent.,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.,Neutral
5310,"(42, 146)",The system shall improve efficiency of entering orders by atleast 20 percent.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
5311,"(42, 147)",The system shall improve efficiency of entering orders by atleast 20 percent.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
5312,"(42, 148)",The system shall improve efficiency of entering orders by atleast 20 percent.,"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.",Neutral
5313,"(43, 44)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow order checking.,Neutral
5314,"(43, 45)",The system shall allow complete order sets to be predefined and personalized.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
5315,"(43, 46)",The system shall allow complete order sets to be predefined and personalized.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
5316,"(43, 47)",The system shall allow complete order sets to be predefined and personalized.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
5317,"(43, 48)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
5318,"(43, 49)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
5319,"(43, 50)",The system shall allow complete order sets to be predefined and personalized.,The system shall support role-based access for security controls.,Neutral
5320,"(43, 51)",The system shall allow complete order sets to be predefined and personalized.,The system shall support audit capability.,Neutral
5321,"(43, 52)",The system shall allow complete order sets to be predefined and personalized.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
5322,"(43, 53)",The system shall allow complete order sets to be predefined and personalized.,The system shall support the requirements for all codified data ,Neutral
5323,"(43, 54)",The system shall allow complete order sets to be predefined and personalized.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
5324,"(43, 55)",The system shall allow complete order sets to be predefined and personalized.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
5325,"(43, 56)",The system shall allow complete order sets to be predefined and personalized.,The system shall require the entry of an access code to gain access to the system.,Neutral
5326,"(43, 57)",The system shall allow complete order sets to be predefined and personalized.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
5327,"(43, 58)",The system shall allow complete order sets to be predefined and personalized.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
5328,"(43, 59)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5329,"(43, 60)",The system shall allow complete order sets to be predefined and personalized.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5330,"(43, 61)",The system shall allow complete order sets to be predefined and personalized.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
5331,"(43, 62)",The system shall allow complete order sets to be predefined and personalized.,The system shall have pre-defined progress note templates.,Neutral
5332,"(43, 63)",The system shall allow complete order sets to be predefined and personalized.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
5333,"(43, 64)",The system shall allow complete order sets to be predefined and personalized.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
5334,"(43, 65)",The system shall allow complete order sets to be predefined and personalized.,The system shall require only a smart card to digitally sign an order.,Neutral
5335,"(43, 66)",The system shall allow complete order sets to be predefined and personalized.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
5336,"(43, 67)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow users to enter time in several different formats.,Neutral
5337,"(43, 68)",The system shall allow complete order sets to be predefined and personalized.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5338,"(43, 69)",The system shall allow complete order sets to be predefined and personalized.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5339,"(43, 70)",The system shall allow complete order sets to be predefined and personalized.,"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.",Neutral
5340,"(43, 71)",The system shall allow complete order sets to be predefined and personalized.,"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.",Neutral
5341,"(43, 72)",The system shall allow complete order sets to be predefined and personalized.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
5342,"(43, 73)",The system shall allow complete order sets to be predefined and personalized.,"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.",Neutral
5343,"(43, 74)",The system shall allow complete order sets to be predefined and personalized.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
5344,"(43, 75)",The system shall allow complete order sets to be predefined and personalized.,The system shall have a option to release unsigned orders to services,Neutral
5345,"(43, 76)",The system shall allow complete order sets to be predefined and personalized.,"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.",Neutral
5346,"(43, 77)",The system shall allow complete order sets to be predefined and personalized.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
5347,"(43, 78)",The system shall allow complete order sets to be predefined and personalized.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
5348,"(43, 79)",The system shall allow complete order sets to be predefined and personalized.,"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.",Neutral
5349,"(43, 80)",The system shall allow complete order sets to be predefined and personalized.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
5350,"(43, 81)",The system shall allow complete order sets to be predefined and personalized.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
5351,"(43, 82)",The system shall allow complete order sets to be predefined and personalized.,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.,Neutral
5352,"(43, 83)",The system shall allow complete order sets to be predefined and personalized.,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.,Neutral
5353,"(43, 84)",The system shall allow complete order sets to be predefined and personalized.,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.,Neutral
5354,"(43, 85)",The system shall allow complete order sets to be predefined and personalized.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
5355,"(43, 86)",The system shall allow complete order sets to be predefined and personalized.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
5356,"(43, 87)",The system shall allow complete order sets to be predefined and personalized.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
5357,"(43, 88)",The system shall allow complete order sets to be predefined and personalized.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
5358,"(43, 89)",The system shall allow complete order sets to be predefined and personalized.,The system shall not allow mandatory notifications to be disabled.,Neutral
5359,"(43, 90)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow users to disable unwanted notifications as desired.,Neutral
5360,"(43, 91)",The system shall allow complete order sets to be predefined and personalized.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
5361,"(43, 92)",The system shall allow complete order sets to be predefined and personalized.,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.,Neutral
5362,"(43, 93)",The system shall allow complete order sets to be predefined and personalized.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
5363,"(43, 94)",The system shall allow complete order sets to be predefined and personalized.,The system shall use any protocol for transferring messages among packages.,Neutral
5364,"(43, 95)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
5365,"(43, 96)",The system shall allow complete order sets to be predefined and personalized.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
5366,"(43, 97)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
5367,"(43, 98)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
5368,"(43, 99)",The system shall allow complete order sets to be predefined and personalized.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
5369,"(43, 100)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
5370,"(43, 101)",The system shall allow complete order sets to be predefined and personalized.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
5371,"(43, 102)",The system shall allow complete order sets to be predefined and personalized.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
5372,"(43, 103)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
5373,"(43, 104)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow a user to foward notification to someone else at the site.,Neutral
5374,"(43, 105)",The system shall allow complete order sets to be predefined and personalized.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
5375,"(43, 106)",The system shall allow complete order sets to be predefined and personalized.,"The system shall define, populate, and retrieve information about user classes.",Neutral
5376,"(43, 107)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5377,"(43, 108)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5378,"(43, 109)",The system shall allow complete order sets to be predefined and personalized.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
5379,"(43, 110)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow concurrent membership in more than one User Class.,Neutral
5380,"(43, 111)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow membership in only one User Class.,Neutral
5381,"(43, 112)",The system shall allow complete order sets to be predefined and personalized.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
5382,"(43, 113)",The system shall allow complete order sets to be predefined and personalized.,"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.",Neutral
5383,"(43, 114)",The system shall allow complete order sets to be predefined and personalized.,The system shall improve accessibility of online clinical information and results.,Neutral
5384,"(43, 115)",The system shall allow complete order sets to be predefined and personalized.,"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.",Neutral
5385,"(43, 116)",The system shall allow complete order sets to be predefined and personalized.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
5386,"(43, 117)",The system shall allow complete order sets to be predefined and personalized.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
5387,"(43, 118)",The system shall allow complete order sets to be predefined and personalized.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
5388,"(43, 119)",The system shall allow complete order sets to be predefined and personalized.,The system shall make the traditional order entry processes more practical.,Neutral
5389,"(43, 120)",The system shall allow complete order sets to be predefined and personalized.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
5390,"(43, 121)",The system shall allow complete order sets to be predefined and personalized.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
5391,"(43, 122)",The system shall allow complete order sets to be predefined and personalized.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
5392,"(43, 123)",The system shall allow complete order sets to be predefined and personalized.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
5393,"(43, 124)",The system shall allow complete order sets to be predefined and personalized.,"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.",Neutral
5394,"(43, 125)",The system shall allow complete order sets to be predefined and personalized.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
5395,"(43, 126)",The system shall allow complete order sets to be predefined and personalized.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
5396,"(43, 127)",The system shall allow complete order sets to be predefined and personalized.,"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.",Neutral
5397,"(43, 128)",The system shall allow complete order sets to be predefined and personalized.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
5398,"(43, 129)",The system shall allow complete order sets to be predefined and personalized.,"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.",Neutral
5399,"(43, 130)",The system shall allow complete order sets to be predefined and personalized.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
5400,"(43, 131)",The system shall allow complete order sets to be predefined and personalized.,The system shall delete history of received immunizations.,Neutral
5401,"(43, 132)",The system shall allow complete order sets to be predefined and personalized.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
5402,"(43, 133)",The system shall allow complete order sets to be predefined and personalized.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
5403,"(43, 134)",The system shall allow complete order sets to be predefined and personalized.,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.,Neutral
5404,"(43, 135)",The system shall allow complete order sets to be predefined and personalized.,The system will provide the ability to register patients of all types.,Neutral
5405,"(43, 136)",The system shall allow complete order sets to be predefined and personalized.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
5406,"(43, 137)",The system shall allow complete order sets to be predefined and personalized.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
5407,"(43, 138)",The system shall allow complete order sets to be predefined and personalized.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
5408,"(43, 139)",The system shall allow complete order sets to be predefined and personalized.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
5409,"(43, 140)",The system shall allow complete order sets to be predefined and personalized.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
5410,"(43, 141)",The system shall allow complete order sets to be predefined and personalized.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
5411,"(43, 142)",The system shall allow complete order sets to be predefined and personalized.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
5412,"(43, 143)",The system shall allow complete order sets to be predefined and personalized.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
5413,"(43, 144)",The system shall allow complete order sets to be predefined and personalized.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
5414,"(43, 145)",The system shall allow complete order sets to be predefined and personalized.,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.,Neutral
5415,"(43, 146)",The system shall allow complete order sets to be predefined and personalized.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
5416,"(43, 147)",The system shall allow complete order sets to be predefined and personalized.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
5417,"(43, 148)",The system shall allow complete order sets to be predefined and personalized.,"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.",Neutral
5418,"(44, 45)",The system shall allow order checking.,"The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
5419,"(44, 46)",The system shall allow order checking.,"The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Neutral
5420,"(44, 47)",The system shall allow order checking.,The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
5421,"(44, 48)",The system shall allow order checking.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
5422,"(44, 49)",The system shall allow order checking.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
5423,"(44, 50)",The system shall allow order checking.,The system shall support role-based access for security controls.,Neutral
5424,"(44, 51)",The system shall allow order checking.,The system shall support audit capability.,Neutral
5425,"(44, 52)",The system shall allow order checking.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
5426,"(44, 53)",The system shall allow order checking.,The system shall support the requirements for all codified data ,Neutral
5427,"(44, 54)",The system shall allow order checking.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
5428,"(44, 55)",The system shall allow order checking.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
5429,"(44, 56)",The system shall allow order checking.,The system shall require the entry of an access code to gain access to the system.,Neutral
5430,"(44, 57)",The system shall allow order checking.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
5431,"(44, 58)",The system shall allow order checking.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
5432,"(44, 59)",The system shall allow order checking.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5433,"(44, 60)",The system shall allow order checking.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5434,"(44, 61)",The system shall allow order checking.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
5435,"(44, 62)",The system shall allow order checking.,The system shall have pre-defined progress note templates.,Neutral
5436,"(44, 63)",The system shall allow order checking.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
5437,"(44, 64)",The system shall allow order checking.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
5438,"(44, 65)",The system shall allow order checking.,The system shall require only a smart card to digitally sign an order.,Neutral
5439,"(44, 66)",The system shall allow order checking.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
5440,"(44, 67)",The system shall allow order checking.,The system shall allow users to enter time in several different formats.,Neutral
5441,"(44, 68)",The system shall allow order checking.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5442,"(44, 69)",The system shall allow order checking.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5443,"(44, 70)",The system shall allow order checking.,"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.",Neutral
5444,"(44, 71)",The system shall allow order checking.,"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.",Neutral
5445,"(44, 72)",The system shall allow order checking.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
5446,"(44, 73)",The system shall allow order checking.,"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.",Neutral
5447,"(44, 74)",The system shall allow order checking.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
5448,"(44, 75)",The system shall allow order checking.,The system shall have a option to release unsigned orders to services,Neutral
5449,"(44, 76)",The system shall allow order checking.,"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.",Neutral
5450,"(44, 77)",The system shall allow order checking.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
5451,"(44, 78)",The system shall allow order checking.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
5452,"(44, 79)",The system shall allow order checking.,"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.",Neutral
5453,"(44, 80)",The system shall allow order checking.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
5454,"(44, 81)",The system shall allow order checking.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
5455,"(44, 82)",The system shall allow order checking.,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.,Neutral
5456,"(44, 83)",The system shall allow order checking.,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.,Neutral
5457,"(44, 84)",The system shall allow order checking.,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.,Neutral
5458,"(44, 85)",The system shall allow order checking.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
5459,"(44, 86)",The system shall allow order checking.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
5460,"(44, 87)",The system shall allow order checking.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
5461,"(44, 88)",The system shall allow order checking.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
5462,"(44, 89)",The system shall allow order checking.,The system shall not allow mandatory notifications to be disabled.,Neutral
5463,"(44, 90)",The system shall allow order checking.,The system shall allow users to disable unwanted notifications as desired.,Neutral
5464,"(44, 91)",The system shall allow order checking.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
5465,"(44, 92)",The system shall allow order checking.,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.,Neutral
5466,"(44, 93)",The system shall allow order checking.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
5467,"(44, 94)",The system shall allow order checking.,The system shall use any protocol for transferring messages among packages.,Neutral
5468,"(44, 95)",The system shall allow order checking.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
5469,"(44, 96)",The system shall allow order checking.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
5470,"(44, 97)",The system shall allow order checking.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
5471,"(44, 98)",The system shall allow order checking.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
5472,"(44, 99)",The system shall allow order checking.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
5473,"(44, 100)",The system shall allow order checking.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
5474,"(44, 101)",The system shall allow order checking.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
5475,"(44, 102)",The system shall allow order checking.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
5476,"(44, 103)",The system shall allow order checking.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
5477,"(44, 104)",The system shall allow order checking.,The system shall allow a user to foward notification to someone else at the site.,Neutral
5478,"(44, 105)",The system shall allow order checking.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
5479,"(44, 106)",The system shall allow order checking.,"The system shall define, populate, and retrieve information about user classes.",Neutral
5480,"(44, 107)",The system shall allow order checking.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5481,"(44, 108)",The system shall allow order checking.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5482,"(44, 109)",The system shall allow order checking.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
5483,"(44, 110)",The system shall allow order checking.,The system shall allow concurrent membership in more than one User Class.,Neutral
5484,"(44, 111)",The system shall allow order checking.,The system shall allow membership in only one User Class.,Neutral
5485,"(44, 112)",The system shall allow order checking.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
5486,"(44, 113)",The system shall allow order checking.,"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.",Neutral
5487,"(44, 114)",The system shall allow order checking.,The system shall improve accessibility of online clinical information and results.,Neutral
5488,"(44, 115)",The system shall allow order checking.,"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.",Neutral
5489,"(44, 116)",The system shall allow order checking.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
5490,"(44, 117)",The system shall allow order checking.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
5491,"(44, 118)",The system shall allow order checking.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
5492,"(44, 119)",The system shall allow order checking.,The system shall make the traditional order entry processes more practical.,Neutral
5493,"(44, 120)",The system shall allow order checking.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
5494,"(44, 121)",The system shall allow order checking.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
5495,"(44, 122)",The system shall allow order checking.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
5496,"(44, 123)",The system shall allow order checking.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
5497,"(44, 124)",The system shall allow order checking.,"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.",Neutral
5498,"(44, 125)",The system shall allow order checking.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
5499,"(44, 126)",The system shall allow order checking.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
5500,"(44, 127)",The system shall allow order checking.,"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.",Neutral
5501,"(44, 128)",The system shall allow order checking.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
5502,"(44, 129)",The system shall allow order checking.,"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.",Neutral
5503,"(44, 130)",The system shall allow order checking.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
5504,"(44, 131)",The system shall allow order checking.,The system shall delete history of received immunizations.,Neutral
5505,"(44, 132)",The system shall allow order checking.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
5506,"(44, 133)",The system shall allow order checking.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
5507,"(44, 134)",The system shall allow order checking.,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.,Neutral
5508,"(44, 135)",The system shall allow order checking.,The system will provide the ability to register patients of all types.,Neutral
5509,"(44, 136)",The system shall allow order checking.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
5510,"(44, 137)",The system shall allow order checking.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
5511,"(44, 138)",The system shall allow order checking.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
5512,"(44, 139)",The system shall allow order checking.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
5513,"(44, 140)",The system shall allow order checking.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
5514,"(44, 141)",The system shall allow order checking.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
5515,"(44, 142)",The system shall allow order checking.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
5516,"(44, 143)",The system shall allow order checking.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
5517,"(44, 144)",The system shall allow order checking.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
5518,"(44, 145)",The system shall allow order checking.,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.,Neutral
5519,"(44, 146)",The system shall allow order checking.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
5520,"(44, 147)",The system shall allow order checking.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
5521,"(44, 148)",The system shall allow order checking.,"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.",Neutral
5522,"(45, 46)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Conflict
5523,"(45, 47)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
5524,"(45, 48)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
5525,"(45, 49)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
5526,"(45, 50)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall support role-based access for security controls.,Neutral
5527,"(45, 51)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall support audit capability.,Neutral
5528,"(45, 52)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
5529,"(45, 53)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall support the requirements for all codified data ,Neutral
5530,"(45, 54)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
5531,"(45, 55)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
5532,"(45, 56)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall require the entry of an access code to gain access to the system.,Neutral
5533,"(45, 57)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
5534,"(45, 58)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
5535,"(45, 59)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5536,"(45, 60)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5537,"(45, 61)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
5538,"(45, 62)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall have pre-defined progress note templates.,Neutral
5539,"(45, 63)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
5540,"(45, 64)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
5541,"(45, 65)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall require only a smart card to digitally sign an order.,Neutral
5542,"(45, 66)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
5543,"(45, 67)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow users to enter time in several different formats.,Neutral
5544,"(45, 68)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5545,"(45, 69)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5546,"(45, 70)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5547,"(45, 71)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5548,"(45, 72)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
5549,"(45, 73)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5550,"(45, 74)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
5551,"(45, 75)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall have a option to release unsigned orders to services,Neutral
5552,"(45, 76)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5553,"(45, 77)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
5554,"(45, 78)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
5555,"(45, 79)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5556,"(45, 80)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
5557,"(45, 81)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
5558,"(45, 82)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",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.,Neutral
5559,"(45, 83)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",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.,Neutral
5560,"(45, 84)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",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.,Neutral
5561,"(45, 85)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
5562,"(45, 86)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
5563,"(45, 87)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
5564,"(45, 88)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
5565,"(45, 89)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall not allow mandatory notifications to be disabled.,Neutral
5566,"(45, 90)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow users to disable unwanted notifications as desired.,Neutral
5567,"(45, 91)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
5568,"(45, 92)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",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.,Neutral
5569,"(45, 93)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
5570,"(45, 94)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall use any protocol for transferring messages among packages.,Neutral
5571,"(45, 95)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
5572,"(45, 96)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
5573,"(45, 97)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
5574,"(45, 98)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
5575,"(45, 99)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
5576,"(45, 100)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
5577,"(45, 101)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
5578,"(45, 102)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
5579,"(45, 103)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
5580,"(45, 104)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow a user to foward notification to someone else at the site.,Neutral
5581,"(45, 105)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
5582,"(45, 106)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall define, populate, and retrieve information about user classes.",Neutral
5583,"(45, 107)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5584,"(45, 108)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5585,"(45, 109)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
5586,"(45, 110)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow concurrent membership in more than one User Class.,Neutral
5587,"(45, 111)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow membership in only one User Class.,Neutral
5588,"(45, 112)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
5589,"(45, 113)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5590,"(45, 114)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall improve accessibility of online clinical information and results.,Neutral
5591,"(45, 115)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5592,"(45, 116)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
5593,"(45, 117)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
5594,"(45, 118)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
5595,"(45, 119)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall make the traditional order entry processes more practical.,Neutral
5596,"(45, 120)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
5597,"(45, 121)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
5598,"(45, 122)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
5599,"(45, 123)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
5600,"(45, 124)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5601,"(45, 125)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
5602,"(45, 126)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
5603,"(45, 127)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5604,"(45, 128)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
5605,"(45, 129)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5606,"(45, 130)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
5607,"(45, 131)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall delete history of received immunizations.,Neutral
5608,"(45, 132)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
5609,"(45, 133)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
5610,"(45, 134)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",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.,Neutral
5611,"(45, 135)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system will provide the ability to register patients of all types.,Neutral
5612,"(45, 136)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
5613,"(45, 137)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
5614,"(45, 138)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
5615,"(45, 139)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
5616,"(45, 140)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
5617,"(45, 141)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
5618,"(45, 142)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
5619,"(45, 143)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
5620,"(45, 144)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
5621,"(45, 145)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",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.,Neutral
5622,"(45, 146)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
5623,"(45, 147)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
5624,"(45, 148)","The system shall provide real-time order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5625,"(46, 47)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Neutral
5626,"(46, 48)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
5627,"(46, 49)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
5628,"(46, 50)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall support role-based access for security controls.,Neutral
5629,"(46, 51)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall support audit capability.,Neutral
5630,"(46, 52)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
5631,"(46, 53)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall support the requirements for all codified data ,Neutral
5632,"(46, 54)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
5633,"(46, 55)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
5634,"(46, 56)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall require the entry of an access code to gain access to the system.,Neutral
5635,"(46, 57)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
5636,"(46, 58)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
5637,"(46, 59)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5638,"(46, 60)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5639,"(46, 61)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
5640,"(46, 62)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall have pre-defined progress note templates.,Neutral
5641,"(46, 63)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
5642,"(46, 64)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
5643,"(46, 65)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall require only a smart card to digitally sign an order.,Neutral
5644,"(46, 66)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
5645,"(46, 67)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow users to enter time in several different formats.,Neutral
5646,"(46, 68)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5647,"(46, 69)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5648,"(46, 70)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5649,"(46, 71)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5650,"(46, 72)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
5651,"(46, 73)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5652,"(46, 74)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
5653,"(46, 75)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall have a option to release unsigned orders to services,Neutral
5654,"(46, 76)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5655,"(46, 77)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
5656,"(46, 78)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
5657,"(46, 79)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5658,"(46, 80)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
5659,"(46, 81)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
5660,"(46, 82)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",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.,Neutral
5661,"(46, 83)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",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.,Neutral
5662,"(46, 84)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",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.,Neutral
5663,"(46, 85)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
5664,"(46, 86)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
5665,"(46, 87)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
5666,"(46, 88)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
5667,"(46, 89)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall not allow mandatory notifications to be disabled.,Neutral
5668,"(46, 90)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow users to disable unwanted notifications as desired.,Neutral
5669,"(46, 91)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
5670,"(46, 92)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",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.,Neutral
5671,"(46, 93)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
5672,"(46, 94)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall use any protocol for transferring messages among packages.,Neutral
5673,"(46, 95)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
5674,"(46, 96)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
5675,"(46, 97)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
5676,"(46, 98)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
5677,"(46, 99)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
5678,"(46, 100)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
5679,"(46, 101)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
5680,"(46, 102)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
5681,"(46, 103)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
5682,"(46, 104)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow a user to foward notification to someone else at the site.,Neutral
5683,"(46, 105)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
5684,"(46, 106)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall define, populate, and retrieve information about user classes.",Neutral
5685,"(46, 107)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5686,"(46, 108)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5687,"(46, 109)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
5688,"(46, 110)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow concurrent membership in more than one User Class.,Neutral
5689,"(46, 111)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow membership in only one User Class.,Neutral
5690,"(46, 112)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
5691,"(46, 113)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5692,"(46, 114)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall improve accessibility of online clinical information and results.,Neutral
5693,"(46, 115)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5694,"(46, 116)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
5695,"(46, 117)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
5696,"(46, 118)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
5697,"(46, 119)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall make the traditional order entry processes more practical.,Neutral
5698,"(46, 120)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
5699,"(46, 121)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
5700,"(46, 122)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
5701,"(46, 123)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
5702,"(46, 124)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5703,"(46, 125)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
5704,"(46, 126)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
5705,"(46, 127)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5706,"(46, 128)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
5707,"(46, 129)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5708,"(46, 130)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
5709,"(46, 131)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall delete history of received immunizations.,Neutral
5710,"(46, 132)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
5711,"(46, 133)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
5712,"(46, 134)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",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.,Neutral
5713,"(46, 135)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system will provide the ability to register patients of all types.,Neutral
5714,"(46, 136)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
5715,"(46, 137)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
5716,"(46, 138)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
5717,"(46, 139)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
5718,"(46, 140)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
5719,"(46, 141)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
5720,"(46, 142)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
5721,"(46, 143)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
5722,"(46, 144)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
5723,"(46, 145)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",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.,Neutral
5724,"(46, 146)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
5725,"(46, 147)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
5726,"(46, 148)","The system shall provide order checking, as well as extended expert system/decision support capabilities that enhance the order entry process.","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.",Neutral
5727,"(47, 48)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Neutral
5728,"(47, 49)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Neutral
5729,"(47, 50)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall support role-based access for security controls.,Neutral
5730,"(47, 51)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall support audit capability.,Neutral
5731,"(47, 52)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
5732,"(47, 53)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall support the requirements for all codified data ,Neutral
5733,"(47, 54)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
5734,"(47, 55)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
5735,"(47, 56)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall require the entry of an access code to gain access to the system.,Neutral
5736,"(47, 57)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
5737,"(47, 58)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
5738,"(47, 59)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5739,"(47, 60)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5740,"(47, 61)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
5741,"(47, 62)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall have pre-defined progress note templates.,Neutral
5742,"(47, 63)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
5743,"(47, 64)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
5744,"(47, 65)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall require only a smart card to digitally sign an order.,Neutral
5745,"(47, 66)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
5746,"(47, 67)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow users to enter time in several different formats.,Neutral
5747,"(47, 68)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5748,"(47, 69)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5749,"(47, 70)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"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.",Neutral
5750,"(47, 71)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"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.",Neutral
5751,"(47, 72)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
5752,"(47, 73)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"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.",Neutral
5753,"(47, 74)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
5754,"(47, 75)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall have a option to release unsigned orders to services,Neutral
5755,"(47, 76)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"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.",Neutral
5756,"(47, 77)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
5757,"(47, 78)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
5758,"(47, 79)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"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.",Neutral
5759,"(47, 80)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
5760,"(47, 81)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
5761,"(47, 82)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,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.,Neutral
5762,"(47, 83)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,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.,Neutral
5763,"(47, 84)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,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.,Neutral
5764,"(47, 85)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
5765,"(47, 86)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
5766,"(47, 87)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
5767,"(47, 88)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
5768,"(47, 89)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall not allow mandatory notifications to be disabled.,Neutral
5769,"(47, 90)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow users to disable unwanted notifications as desired.,Neutral
5770,"(47, 91)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
5771,"(47, 92)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,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.,Neutral
5772,"(47, 93)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
5773,"(47, 94)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall use any protocol for transferring messages among packages.,Neutral
5774,"(47, 95)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
5775,"(47, 96)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
5776,"(47, 97)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
5777,"(47, 98)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
5778,"(47, 99)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
5779,"(47, 100)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
5780,"(47, 101)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
5781,"(47, 102)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
5782,"(47, 103)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
5783,"(47, 104)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow a user to foward notification to someone else at the site.,Neutral
5784,"(47, 105)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
5785,"(47, 106)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall define, populate, and retrieve information about user classes.",Neutral
5786,"(47, 107)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5787,"(47, 108)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5788,"(47, 109)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
5789,"(47, 110)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow concurrent membership in more than one User Class.,Neutral
5790,"(47, 111)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow membership in only one User Class.,Neutral
5791,"(47, 112)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
5792,"(47, 113)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"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.",Neutral
5793,"(47, 114)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall improve accessibility of online clinical information and results.,Neutral
5794,"(47, 115)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"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.",Neutral
5795,"(47, 116)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
5796,"(47, 117)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
5797,"(47, 118)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
5798,"(47, 119)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall make the traditional order entry processes more practical.,Neutral
5799,"(47, 120)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
5800,"(47, 121)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
5801,"(47, 122)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
5802,"(47, 123)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
5803,"(47, 124)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"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.",Neutral
5804,"(47, 125)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
5805,"(47, 126)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
5806,"(47, 127)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"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.",Neutral
5807,"(47, 128)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
5808,"(47, 129)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"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.",Neutral
5809,"(47, 130)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
5810,"(47, 131)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall delete history of received immunizations.,Neutral
5811,"(47, 132)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
5812,"(47, 133)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
5813,"(47, 134)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,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.,Neutral
5814,"(47, 135)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system will provide the ability to register patients of all types.,Neutral
5815,"(47, 136)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
5816,"(47, 137)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
5817,"(47, 138)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
5818,"(47, 139)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
5819,"(47, 140)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
5820,"(47, 141)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
5821,"(47, 142)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
5822,"(47, 143)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
5823,"(47, 144)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
5824,"(47, 145)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,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.,Neutral
5825,"(47, 146)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
5826,"(47, 147)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
5827,"(47, 148)",The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design.,"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.",Neutral
5828,"(48, 49)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Conflict
5829,"(48, 50)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall support role-based access for security controls.,Neutral
5830,"(48, 51)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall support audit capability.,Neutral
5831,"(48, 52)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
5832,"(48, 53)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall support the requirements for all codified data ,Neutral
5833,"(48, 54)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
5834,"(48, 55)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
5835,"(48, 56)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall require the entry of an access code to gain access to the system.,Neutral
5836,"(48, 57)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
5837,"(48, 58)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
5838,"(48, 59)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5839,"(48, 60)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5840,"(48, 61)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
5841,"(48, 62)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall have pre-defined progress note templates.,Neutral
5842,"(48, 63)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
5843,"(48, 64)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
5844,"(48, 65)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall require only a smart card to digitally sign an order.,Neutral
5845,"(48, 66)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
5846,"(48, 67)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow users to enter time in several different formats.,Neutral
5847,"(48, 68)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5848,"(48, 69)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5849,"(48, 70)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5850,"(48, 71)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5851,"(48, 72)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
5852,"(48, 73)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5853,"(48, 74)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
5854,"(48, 75)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall have a option to release unsigned orders to services,Neutral
5855,"(48, 76)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5856,"(48, 77)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
5857,"(48, 78)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
5858,"(48, 79)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5859,"(48, 80)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
5860,"(48, 81)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
5861,"(48, 82)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,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.,Neutral
5862,"(48, 83)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,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.,Neutral
5863,"(48, 84)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,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.,Neutral
5864,"(48, 85)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
5865,"(48, 86)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
5866,"(48, 87)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
5867,"(48, 88)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
5868,"(48, 89)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall not allow mandatory notifications to be disabled.,Neutral
5869,"(48, 90)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow users to disable unwanted notifications as desired.,Neutral
5870,"(48, 91)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
5871,"(48, 92)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,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.,Neutral
5872,"(48, 93)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
5873,"(48, 94)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall use any protocol for transferring messages among packages.,Neutral
5874,"(48, 95)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
5875,"(48, 96)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
5876,"(48, 97)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
5877,"(48, 98)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
5878,"(48, 99)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
5879,"(48, 100)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
5880,"(48, 101)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
5881,"(48, 102)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
5882,"(48, 103)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
5883,"(48, 104)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow a user to foward notification to someone else at the site.,Neutral
5884,"(48, 105)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
5885,"(48, 106)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall define, populate, and retrieve information about user classes.",Neutral
5886,"(48, 107)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5887,"(48, 108)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5888,"(48, 109)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
5889,"(48, 110)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow concurrent membership in more than one User Class.,Neutral
5890,"(48, 111)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow membership in only one User Class.,Neutral
5891,"(48, 112)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
5892,"(48, 113)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5893,"(48, 114)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall improve accessibility of online clinical information and results.,Neutral
5894,"(48, 115)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5895,"(48, 116)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
5896,"(48, 117)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
5897,"(48, 118)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
5898,"(48, 119)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall make the traditional order entry processes more practical.,Neutral
5899,"(48, 120)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
5900,"(48, 121)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
5901,"(48, 122)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
5902,"(48, 123)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
5903,"(48, 124)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5904,"(48, 125)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
5905,"(48, 126)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
5906,"(48, 127)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5907,"(48, 128)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
5908,"(48, 129)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5909,"(48, 130)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
5910,"(48, 131)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall delete history of received immunizations.,Neutral
5911,"(48, 132)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
5912,"(48, 133)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
5913,"(48, 134)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,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.,Neutral
5914,"(48, 135)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system will provide the ability to register patients of all types.,Neutral
5915,"(48, 136)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
5916,"(48, 137)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
5917,"(48, 138)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
5918,"(48, 139)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
5919,"(48, 140)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
5920,"(48, 141)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
5921,"(48, 142)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
5922,"(48, 143)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
5923,"(48, 144)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
5924,"(48, 145)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,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.,Neutral
5925,"(48, 146)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
5926,"(48, 147)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
5927,"(48, 148)",The system shall allow creation of personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5928,"(49, 50)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall support role-based access for security controls.,Neutral
5929,"(49, 51)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall support audit capability.,Neutral
5930,"(49, 52)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
5931,"(49, 53)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall support the requirements for all codified data ,Neutral
5932,"(49, 54)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
5933,"(49, 55)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
5934,"(49, 56)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall require the entry of an access code to gain access to the system.,Neutral
5935,"(49, 57)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
5936,"(49, 58)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
5937,"(49, 59)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5938,"(49, 60)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
5939,"(49, 61)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
5940,"(49, 62)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall have pre-defined progress note templates.,Neutral
5941,"(49, 63)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
5942,"(49, 64)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
5943,"(49, 65)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall require only a smart card to digitally sign an order.,Neutral
5944,"(49, 66)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
5945,"(49, 67)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow users to enter time in several different formats.,Neutral
5946,"(49, 68)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5947,"(49, 69)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
5948,"(49, 70)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5949,"(49, 71)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5950,"(49, 72)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
5951,"(49, 73)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5952,"(49, 74)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
5953,"(49, 75)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall have a option to release unsigned orders to services,Neutral
5954,"(49, 76)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5955,"(49, 77)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
5956,"(49, 78)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
5957,"(49, 79)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5958,"(49, 80)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
5959,"(49, 81)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
5960,"(49, 82)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,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.,Neutral
5961,"(49, 83)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,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.,Neutral
5962,"(49, 84)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,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.,Neutral
5963,"(49, 85)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
5964,"(49, 86)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
5965,"(49, 87)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
5966,"(49, 88)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
5967,"(49, 89)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall not allow mandatory notifications to be disabled.,Neutral
5968,"(49, 90)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow users to disable unwanted notifications as desired.,Neutral
5969,"(49, 91)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
5970,"(49, 92)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,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.,Neutral
5971,"(49, 93)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
5972,"(49, 94)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall use any protocol for transferring messages among packages.,Neutral
5973,"(49, 95)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
5974,"(49, 96)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
5975,"(49, 97)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
5976,"(49, 98)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
5977,"(49, 99)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
5978,"(49, 100)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
5979,"(49, 101)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
5980,"(49, 102)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
5981,"(49, 103)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
5982,"(49, 104)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow a user to foward notification to someone else at the site.,Neutral
5983,"(49, 105)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
5984,"(49, 106)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall define, populate, and retrieve information about user classes.",Neutral
5985,"(49, 107)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5986,"(49, 108)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
5987,"(49, 109)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
5988,"(49, 110)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow concurrent membership in more than one User Class.,Neutral
5989,"(49, 111)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow membership in only one User Class.,Neutral
5990,"(49, 112)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
5991,"(49, 113)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5992,"(49, 114)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall improve accessibility of online clinical information and results.,Neutral
5993,"(49, 115)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"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.",Neutral
5994,"(49, 116)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
5995,"(49, 117)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
5996,"(49, 118)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
5997,"(49, 119)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall make the traditional order entry processes more practical.,Neutral
5998,"(49, 120)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
5999,"(49, 121)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
6000,"(49, 122)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
6001,"(49, 123)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
6002,"(49, 124)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"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.",Neutral
6003,"(49, 125)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
6004,"(49, 126)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
6005,"(49, 127)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"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.",Neutral
6006,"(49, 128)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
6007,"(49, 129)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"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.",Neutral
6008,"(49, 130)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
6009,"(49, 131)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall delete history of received immunizations.,Neutral
6010,"(49, 132)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
6011,"(49, 133)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
6012,"(49, 134)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,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.,Neutral
6013,"(49, 135)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system will provide the ability to register patients of all types.,Neutral
6014,"(49, 136)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
6015,"(49, 137)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
6016,"(49, 138)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
6017,"(49, 139)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
6018,"(49, 140)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
6019,"(49, 141)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
6020,"(49, 142)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
6021,"(49, 143)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
6022,"(49, 144)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
6023,"(49, 145)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,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.,Neutral
6024,"(49, 146)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
6025,"(49, 147)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
6026,"(49, 148)",The system shall allow creation of semi-personalized templates to fit the specific needs of individual practices.,"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.",Neutral
6027,"(50, 51)",The system shall support role-based access for security controls.,The system shall support audit capability.,Neutral
6028,"(50, 52)",The system shall support role-based access for security controls.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
6029,"(50, 53)",The system shall support role-based access for security controls.,The system shall support the requirements for all codified data ,Neutral
6030,"(50, 54)",The system shall support role-based access for security controls.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
6031,"(50, 55)",The system shall support role-based access for security controls.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
6032,"(50, 56)",The system shall support role-based access for security controls.,The system shall require the entry of an access code to gain access to the system.,Neutral
6033,"(50, 57)",The system shall support role-based access for security controls.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
6034,"(50, 58)",The system shall support role-based access for security controls.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
6035,"(50, 59)",The system shall support role-based access for security controls.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6036,"(50, 60)",The system shall support role-based access for security controls.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6037,"(50, 61)",The system shall support role-based access for security controls.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
6038,"(50, 62)",The system shall support role-based access for security controls.,The system shall have pre-defined progress note templates.,Neutral
6039,"(50, 63)",The system shall support role-based access for security controls.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
6040,"(50, 64)",The system shall support role-based access for security controls.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
6041,"(50, 65)",The system shall support role-based access for security controls.,The system shall require only a smart card to digitally sign an order.,Neutral
6042,"(50, 66)",The system shall support role-based access for security controls.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
6043,"(50, 67)",The system shall support role-based access for security controls.,The system shall allow users to enter time in several different formats.,Neutral
6044,"(50, 68)",The system shall support role-based access for security controls.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6045,"(50, 69)",The system shall support role-based access for security controls.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6046,"(50, 70)",The system shall support role-based access for security controls.,"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.",Neutral
6047,"(50, 71)",The system shall support role-based access for security controls.,"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.",Neutral
6048,"(50, 72)",The system shall support role-based access for security controls.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
6049,"(50, 73)",The system shall support role-based access for security controls.,"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.",Neutral
6050,"(50, 74)",The system shall support role-based access for security controls.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
6051,"(50, 75)",The system shall support role-based access for security controls.,The system shall have a option to release unsigned orders to services,Neutral
6052,"(50, 76)",The system shall support role-based access for security controls.,"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.",Neutral
6053,"(50, 77)",The system shall support role-based access for security controls.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
6054,"(50, 78)",The system shall support role-based access for security controls.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
6055,"(50, 79)",The system shall support role-based access for security controls.,"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.",Neutral
6056,"(50, 80)",The system shall support role-based access for security controls.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
6057,"(50, 81)",The system shall support role-based access for security controls.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
6058,"(50, 82)",The system shall support role-based access for security controls.,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.,Neutral
6059,"(50, 83)",The system shall support role-based access for security controls.,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.,Neutral
6060,"(50, 84)",The system shall support role-based access for security controls.,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.,Neutral
6061,"(50, 85)",The system shall support role-based access for security controls.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
6062,"(50, 86)",The system shall support role-based access for security controls.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
6063,"(50, 87)",The system shall support role-based access for security controls.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
6064,"(50, 88)",The system shall support role-based access for security controls.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
6065,"(50, 89)",The system shall support role-based access for security controls.,The system shall not allow mandatory notifications to be disabled.,Neutral
6066,"(50, 90)",The system shall support role-based access for security controls.,The system shall allow users to disable unwanted notifications as desired.,Neutral
6067,"(50, 91)",The system shall support role-based access for security controls.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
6068,"(50, 92)",The system shall support role-based access for security controls.,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.,Neutral
6069,"(50, 93)",The system shall support role-based access for security controls.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
6070,"(50, 94)",The system shall support role-based access for security controls.,The system shall use any protocol for transferring messages among packages.,Neutral
6071,"(50, 95)",The system shall support role-based access for security controls.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
6072,"(50, 96)",The system shall support role-based access for security controls.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
6073,"(50, 97)",The system shall support role-based access for security controls.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
6074,"(50, 98)",The system shall support role-based access for security controls.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
6075,"(50, 99)",The system shall support role-based access for security controls.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
6076,"(50, 100)",The system shall support role-based access for security controls.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
6077,"(50, 101)",The system shall support role-based access for security controls.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
6078,"(50, 102)",The system shall support role-based access for security controls.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
6079,"(50, 103)",The system shall support role-based access for security controls.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
6080,"(50, 104)",The system shall support role-based access for security controls.,The system shall allow a user to foward notification to someone else at the site.,Neutral
6081,"(50, 105)",The system shall support role-based access for security controls.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
6082,"(50, 106)",The system shall support role-based access for security controls.,"The system shall define, populate, and retrieve information about user classes.",Neutral
6083,"(50, 107)",The system shall support role-based access for security controls.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6084,"(50, 108)",The system shall support role-based access for security controls.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6085,"(50, 109)",The system shall support role-based access for security controls.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
6086,"(50, 110)",The system shall support role-based access for security controls.,The system shall allow concurrent membership in more than one User Class.,Neutral
6087,"(50, 111)",The system shall support role-based access for security controls.,The system shall allow membership in only one User Class.,Neutral
6088,"(50, 112)",The system shall support role-based access for security controls.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
6089,"(50, 113)",The system shall support role-based access for security controls.,"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.",Neutral
6090,"(50, 114)",The system shall support role-based access for security controls.,The system shall improve accessibility of online clinical information and results.,Neutral
6091,"(50, 115)",The system shall support role-based access for security controls.,"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.",Neutral
6092,"(50, 116)",The system shall support role-based access for security controls.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
6093,"(50, 117)",The system shall support role-based access for security controls.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
6094,"(50, 118)",The system shall support role-based access for security controls.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
6095,"(50, 119)",The system shall support role-based access for security controls.,The system shall make the traditional order entry processes more practical.,Neutral
6096,"(50, 120)",The system shall support role-based access for security controls.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
6097,"(50, 121)",The system shall support role-based access for security controls.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
6098,"(50, 122)",The system shall support role-based access for security controls.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
6099,"(50, 123)",The system shall support role-based access for security controls.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
6100,"(50, 124)",The system shall support role-based access for security controls.,"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.",Neutral
6101,"(50, 125)",The system shall support role-based access for security controls.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
6102,"(50, 126)",The system shall support role-based access for security controls.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
6103,"(50, 127)",The system shall support role-based access for security controls.,"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.",Neutral
6104,"(50, 128)",The system shall support role-based access for security controls.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
6105,"(50, 129)",The system shall support role-based access for security controls.,"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.",Neutral
6106,"(50, 130)",The system shall support role-based access for security controls.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
6107,"(50, 131)",The system shall support role-based access for security controls.,The system shall delete history of received immunizations.,Neutral
6108,"(50, 132)",The system shall support role-based access for security controls.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
6109,"(50, 133)",The system shall support role-based access for security controls.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
6110,"(50, 134)",The system shall support role-based access for security controls.,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.,Neutral
6111,"(50, 135)",The system shall support role-based access for security controls.,The system will provide the ability to register patients of all types.,Neutral
6112,"(50, 136)",The system shall support role-based access for security controls.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
6113,"(50, 137)",The system shall support role-based access for security controls.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
6114,"(50, 138)",The system shall support role-based access for security controls.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
6115,"(50, 139)",The system shall support role-based access for security controls.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
6116,"(50, 140)",The system shall support role-based access for security controls.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
6117,"(50, 141)",The system shall support role-based access for security controls.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
6118,"(50, 142)",The system shall support role-based access for security controls.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
6119,"(50, 143)",The system shall support role-based access for security controls.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
6120,"(50, 144)",The system shall support role-based access for security controls.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
6121,"(50, 145)",The system shall support role-based access for security controls.,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.,Neutral
6122,"(50, 146)",The system shall support role-based access for security controls.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
6123,"(50, 147)",The system shall support role-based access for security controls.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
6124,"(50, 148)",The system shall support role-based access for security controls.,"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.",Neutral
6125,"(51, 52)",The system shall support audit capability.,The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Neutral
6126,"(51, 53)",The system shall support audit capability.,The system shall support the requirements for all codified data ,Neutral
6127,"(51, 54)",The system shall support audit capability.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
6128,"(51, 55)",The system shall support audit capability.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
6129,"(51, 56)",The system shall support audit capability.,The system shall require the entry of an access code to gain access to the system.,Neutral
6130,"(51, 57)",The system shall support audit capability.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
6131,"(51, 58)",The system shall support audit capability.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
6132,"(51, 59)",The system shall support audit capability.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6133,"(51, 60)",The system shall support audit capability.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6134,"(51, 61)",The system shall support audit capability.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
6135,"(51, 62)",The system shall support audit capability.,The system shall have pre-defined progress note templates.,Neutral
6136,"(51, 63)",The system shall support audit capability.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
6137,"(51, 64)",The system shall support audit capability.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
6138,"(51, 65)",The system shall support audit capability.,The system shall require only a smart card to digitally sign an order.,Neutral
6139,"(51, 66)",The system shall support audit capability.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
6140,"(51, 67)",The system shall support audit capability.,The system shall allow users to enter time in several different formats.,Neutral
6141,"(51, 68)",The system shall support audit capability.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6142,"(51, 69)",The system shall support audit capability.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6143,"(51, 70)",The system shall support audit capability.,"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.",Neutral
6144,"(51, 71)",The system shall support audit capability.,"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.",Neutral
6145,"(51, 72)",The system shall support audit capability.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
6146,"(51, 73)",The system shall support audit capability.,"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.",Neutral
6147,"(51, 74)",The system shall support audit capability.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
6148,"(51, 75)",The system shall support audit capability.,The system shall have a option to release unsigned orders to services,Neutral
6149,"(51, 76)",The system shall support audit capability.,"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.",Neutral
6150,"(51, 77)",The system shall support audit capability.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
6151,"(51, 78)",The system shall support audit capability.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
6152,"(51, 79)",The system shall support audit capability.,"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.",Neutral
6153,"(51, 80)",The system shall support audit capability.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
6154,"(51, 81)",The system shall support audit capability.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
6155,"(51, 82)",The system shall support audit capability.,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.,Neutral
6156,"(51, 83)",The system shall support audit capability.,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.,Neutral
6157,"(51, 84)",The system shall support audit capability.,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.,Neutral
6158,"(51, 85)",The system shall support audit capability.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
6159,"(51, 86)",The system shall support audit capability.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
6160,"(51, 87)",The system shall support audit capability.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
6161,"(51, 88)",The system shall support audit capability.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
6162,"(51, 89)",The system shall support audit capability.,The system shall not allow mandatory notifications to be disabled.,Neutral
6163,"(51, 90)",The system shall support audit capability.,The system shall allow users to disable unwanted notifications as desired.,Neutral
6164,"(51, 91)",The system shall support audit capability.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
6165,"(51, 92)",The system shall support audit capability.,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.,Neutral
6166,"(51, 93)",The system shall support audit capability.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
6167,"(51, 94)",The system shall support audit capability.,The system shall use any protocol for transferring messages among packages.,Neutral
6168,"(51, 95)",The system shall support audit capability.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
6169,"(51, 96)",The system shall support audit capability.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
6170,"(51, 97)",The system shall support audit capability.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
6171,"(51, 98)",The system shall support audit capability.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
6172,"(51, 99)",The system shall support audit capability.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
6173,"(51, 100)",The system shall support audit capability.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
6174,"(51, 101)",The system shall support audit capability.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
6175,"(51, 102)",The system shall support audit capability.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
6176,"(51, 103)",The system shall support audit capability.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
6177,"(51, 104)",The system shall support audit capability.,The system shall allow a user to foward notification to someone else at the site.,Neutral
6178,"(51, 105)",The system shall support audit capability.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
6179,"(51, 106)",The system shall support audit capability.,"The system shall define, populate, and retrieve information about user classes.",Neutral
6180,"(51, 107)",The system shall support audit capability.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6181,"(51, 108)",The system shall support audit capability.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6182,"(51, 109)",The system shall support audit capability.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
6183,"(51, 110)",The system shall support audit capability.,The system shall allow concurrent membership in more than one User Class.,Neutral
6184,"(51, 111)",The system shall support audit capability.,The system shall allow membership in only one User Class.,Neutral
6185,"(51, 112)",The system shall support audit capability.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
6186,"(51, 113)",The system shall support audit capability.,"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.",Neutral
6187,"(51, 114)",The system shall support audit capability.,The system shall improve accessibility of online clinical information and results.,Neutral
6188,"(51, 115)",The system shall support audit capability.,"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.",Neutral
6189,"(51, 116)",The system shall support audit capability.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
6190,"(51, 117)",The system shall support audit capability.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
6191,"(51, 118)",The system shall support audit capability.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
6192,"(51, 119)",The system shall support audit capability.,The system shall make the traditional order entry processes more practical.,Neutral
6193,"(51, 120)",The system shall support audit capability.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
6194,"(51, 121)",The system shall support audit capability.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
6195,"(51, 122)",The system shall support audit capability.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
6196,"(51, 123)",The system shall support audit capability.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
6197,"(51, 124)",The system shall support audit capability.,"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.",Neutral
6198,"(51, 125)",The system shall support audit capability.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
6199,"(51, 126)",The system shall support audit capability.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
6200,"(51, 127)",The system shall support audit capability.,"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.",Neutral
6201,"(51, 128)",The system shall support audit capability.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
6202,"(51, 129)",The system shall support audit capability.,"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.",Neutral
6203,"(51, 130)",The system shall support audit capability.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
6204,"(51, 131)",The system shall support audit capability.,The system shall delete history of received immunizations.,Neutral
6205,"(51, 132)",The system shall support audit capability.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
6206,"(51, 133)",The system shall support audit capability.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
6207,"(51, 134)",The system shall support audit capability.,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.,Neutral
6208,"(51, 135)",The system shall support audit capability.,The system will provide the ability to register patients of all types.,Neutral
6209,"(51, 136)",The system shall support audit capability.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
6210,"(51, 137)",The system shall support audit capability.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
6211,"(51, 138)",The system shall support audit capability.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
6212,"(51, 139)",The system shall support audit capability.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
6213,"(51, 140)",The system shall support audit capability.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
6214,"(51, 141)",The system shall support audit capability.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
6215,"(51, 142)",The system shall support audit capability.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
6216,"(51, 143)",The system shall support audit capability.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
6217,"(51, 144)",The system shall support audit capability.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
6218,"(51, 145)",The system shall support audit capability.,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.,Neutral
6219,"(51, 146)",The system shall support audit capability.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
6220,"(51, 147)",The system shall support audit capability.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
6221,"(51, 148)",The system shall support audit capability.,"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.",Neutral
6222,"(52, 53)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall support the requirements for all codified data ,Conflict
6223,"(52, 54)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
6224,"(52, 55)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
6225,"(52, 56)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall require the entry of an access code to gain access to the system.,Neutral
6226,"(52, 57)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
6227,"(52, 58)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
6228,"(52, 59)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6229,"(52, 60)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6230,"(52, 61)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
6231,"(52, 62)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall have pre-defined progress note templates.,Neutral
6232,"(52, 63)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
6233,"(52, 64)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
6234,"(52, 65)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall require only a smart card to digitally sign an order.,Neutral
6235,"(52, 66)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
6236,"(52, 67)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow users to enter time in several different formats.,Neutral
6237,"(52, 68)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6238,"(52, 69)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6239,"(52, 70)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"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.",Neutral
6240,"(52, 71)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"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.",Neutral
6241,"(52, 72)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
6242,"(52, 73)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"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.",Neutral
6243,"(52, 74)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
6244,"(52, 75)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall have a option to release unsigned orders to services,Neutral
6245,"(52, 76)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"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.",Neutral
6246,"(52, 77)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
6247,"(52, 78)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
6248,"(52, 79)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"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.",Neutral
6249,"(52, 80)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
6250,"(52, 81)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
6251,"(52, 82)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,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.,Neutral
6252,"(52, 83)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,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.,Neutral
6253,"(52, 84)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,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.,Neutral
6254,"(52, 85)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
6255,"(52, 86)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
6256,"(52, 87)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
6257,"(52, 88)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
6258,"(52, 89)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall not allow mandatory notifications to be disabled.,Neutral
6259,"(52, 90)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow users to disable unwanted notifications as desired.,Neutral
6260,"(52, 91)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
6261,"(52, 92)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,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.,Neutral
6262,"(52, 93)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
6263,"(52, 94)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall use any protocol for transferring messages among packages.,Neutral
6264,"(52, 95)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
6265,"(52, 96)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
6266,"(52, 97)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
6267,"(52, 98)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
6268,"(52, 99)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
6269,"(52, 100)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
6270,"(52, 101)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
6271,"(52, 102)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
6272,"(52, 103)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
6273,"(52, 104)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow a user to foward notification to someone else at the site.,Neutral
6274,"(52, 105)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
6275,"(52, 106)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall define, populate, and retrieve information about user classes.",Neutral
6276,"(52, 107)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6277,"(52, 108)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6278,"(52, 109)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
6279,"(52, 110)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow concurrent membership in more than one User Class.,Neutral
6280,"(52, 111)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow membership in only one User Class.,Neutral
6281,"(52, 112)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
6282,"(52, 113)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"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.",Neutral
6283,"(52, 114)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall improve accessibility of online clinical information and results.,Neutral
6284,"(52, 115)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"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.",Neutral
6285,"(52, 116)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
6286,"(52, 117)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
6287,"(52, 118)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
6288,"(52, 119)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall make the traditional order entry processes more practical.,Neutral
6289,"(52, 120)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
6290,"(52, 121)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
6291,"(52, 122)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
6292,"(52, 123)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
6293,"(52, 124)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"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.",Neutral
6294,"(52, 125)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
6295,"(52, 126)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
6296,"(52, 127)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"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.",Neutral
6297,"(52, 128)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
6298,"(52, 129)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"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.",Neutral
6299,"(52, 130)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
6300,"(52, 131)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall delete history of received immunizations.,Neutral
6301,"(52, 132)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
6302,"(52, 133)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
6303,"(52, 134)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,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.,Neutral
6304,"(52, 135)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system will provide the ability to register patients of all types.,Neutral
6305,"(52, 136)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
6306,"(52, 137)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
6307,"(52, 138)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
6308,"(52, 139)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
6309,"(52, 140)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
6310,"(52, 141)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
6311,"(52, 142)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
6312,"(52, 143)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
6313,"(52, 144)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
6314,"(52, 145)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,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.,Neutral
6315,"(52, 146)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
6316,"(52, 147)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
6317,"(52, 148)",The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures.,"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.",Neutral
6318,"(53, 54)",The system shall support the requirements for all codified data ,"The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Neutral
6319,"(53, 55)",The system shall support the requirements for all codified data ,The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
6320,"(53, 56)",The system shall support the requirements for all codified data ,The system shall require the entry of an access code to gain access to the system.,Neutral
6321,"(53, 57)",The system shall support the requirements for all codified data ,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
6322,"(53, 58)",The system shall support the requirements for all codified data ,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
6323,"(53, 59)",The system shall support the requirements for all codified data ,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6324,"(53, 60)",The system shall support the requirements for all codified data ,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6325,"(53, 61)",The system shall support the requirements for all codified data ,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
6326,"(53, 62)",The system shall support the requirements for all codified data ,The system shall have pre-defined progress note templates.,Neutral
6327,"(53, 63)",The system shall support the requirements for all codified data ,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
6328,"(53, 64)",The system shall support the requirements for all codified data ,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
6329,"(53, 65)",The system shall support the requirements for all codified data ,The system shall require only a smart card to digitally sign an order.,Neutral
6330,"(53, 66)",The system shall support the requirements for all codified data ,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
6331,"(53, 67)",The system shall support the requirements for all codified data ,The system shall allow users to enter time in several different formats.,Neutral
6332,"(53, 68)",The system shall support the requirements for all codified data ,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6333,"(53, 69)",The system shall support the requirements for all codified data ,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6334,"(53, 70)",The system shall support the requirements for all codified data ,"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.",Neutral
6335,"(53, 71)",The system shall support the requirements for all codified data ,"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.",Neutral
6336,"(53, 72)",The system shall support the requirements for all codified data ,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
6337,"(53, 73)",The system shall support the requirements for all codified data ,"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.",Neutral
6338,"(53, 74)",The system shall support the requirements for all codified data ,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
6339,"(53, 75)",The system shall support the requirements for all codified data ,The system shall have a option to release unsigned orders to services,Neutral
6340,"(53, 76)",The system shall support the requirements for all codified data ,"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.",Neutral
6341,"(53, 77)",The system shall support the requirements for all codified data ,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
6342,"(53, 78)",The system shall support the requirements for all codified data ,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
6343,"(53, 79)",The system shall support the requirements for all codified data ,"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.",Neutral
6344,"(53, 80)",The system shall support the requirements for all codified data ,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
6345,"(53, 81)",The system shall support the requirements for all codified data ,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
6346,"(53, 82)",The system shall support the requirements for all codified data ,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.,Neutral
6347,"(53, 83)",The system shall support the requirements for all codified data ,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.,Neutral
6348,"(53, 84)",The system shall support the requirements for all codified data ,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.,Neutral
6349,"(53, 85)",The system shall support the requirements for all codified data ,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
6350,"(53, 86)",The system shall support the requirements for all codified data ,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
6351,"(53, 87)",The system shall support the requirements for all codified data ,The system shall display a message telling the user that the selected patient is deceased.,Neutral
6352,"(53, 88)",The system shall support the requirements for all codified data ,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
6353,"(53, 89)",The system shall support the requirements for all codified data ,The system shall not allow mandatory notifications to be disabled.,Neutral
6354,"(53, 90)",The system shall support the requirements for all codified data ,The system shall allow users to disable unwanted notifications as desired.,Neutral
6355,"(53, 91)",The system shall support the requirements for all codified data ,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
6356,"(53, 92)",The system shall support the requirements for all codified data ,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.,Neutral
6357,"(53, 93)",The system shall support the requirements for all codified data ,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
6358,"(53, 94)",The system shall support the requirements for all codified data ,The system shall use any protocol for transferring messages among packages.,Neutral
6359,"(53, 95)",The system shall support the requirements for all codified data ,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
6360,"(53, 96)",The system shall support the requirements for all codified data ,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
6361,"(53, 97)",The system shall support the requirements for all codified data ,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
6362,"(53, 98)",The system shall support the requirements for all codified data ,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
6363,"(53, 99)",The system shall support the requirements for all codified data ,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
6364,"(53, 100)",The system shall support the requirements for all codified data ,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
6365,"(53, 101)",The system shall support the requirements for all codified data ,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
6366,"(53, 102)",The system shall support the requirements for all codified data ,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
6367,"(53, 103)",The system shall support the requirements for all codified data ,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
6368,"(53, 104)",The system shall support the requirements for all codified data ,The system shall allow a user to foward notification to someone else at the site.,Neutral
6369,"(53, 105)",The system shall support the requirements for all codified data ,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
6370,"(53, 106)",The system shall support the requirements for all codified data ,"The system shall define, populate, and retrieve information about user classes.",Neutral
6371,"(53, 107)",The system shall support the requirements for all codified data ,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6372,"(53, 108)",The system shall support the requirements for all codified data ,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6373,"(53, 109)",The system shall support the requirements for all codified data ,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
6374,"(53, 110)",The system shall support the requirements for all codified data ,The system shall allow concurrent membership in more than one User Class.,Neutral
6375,"(53, 111)",The system shall support the requirements for all codified data ,The system shall allow membership in only one User Class.,Neutral
6376,"(53, 112)",The system shall support the requirements for all codified data ,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
6377,"(53, 113)",The system shall support the requirements for all codified data ,"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.",Neutral
6378,"(53, 114)",The system shall support the requirements for all codified data ,The system shall improve accessibility of online clinical information and results.,Neutral
6379,"(53, 115)",The system shall support the requirements for all codified data ,"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.",Neutral
6380,"(53, 116)",The system shall support the requirements for all codified data ,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
6381,"(53, 117)",The system shall support the requirements for all codified data ,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
6382,"(53, 118)",The system shall support the requirements for all codified data ,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
6383,"(53, 119)",The system shall support the requirements for all codified data ,The system shall make the traditional order entry processes more practical.,Neutral
6384,"(53, 120)",The system shall support the requirements for all codified data ,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
6385,"(53, 121)",The system shall support the requirements for all codified data ,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
6386,"(53, 122)",The system shall support the requirements for all codified data ,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
6387,"(53, 123)",The system shall support the requirements for all codified data ,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
6388,"(53, 124)",The system shall support the requirements for all codified data ,"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.",Neutral
6389,"(53, 125)",The system shall support the requirements for all codified data ,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
6390,"(53, 126)",The system shall support the requirements for all codified data ,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
6391,"(53, 127)",The system shall support the requirements for all codified data ,"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.",Neutral
6392,"(53, 128)",The system shall support the requirements for all codified data ,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
6393,"(53, 129)",The system shall support the requirements for all codified data ,"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.",Neutral
6394,"(53, 130)",The system shall support the requirements for all codified data ,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
6395,"(53, 131)",The system shall support the requirements for all codified data ,The system shall delete history of received immunizations.,Neutral
6396,"(53, 132)",The system shall support the requirements for all codified data ,The system shall only delete history of recieved immunizations unless user specifies,Neutral
6397,"(53, 133)",The system shall support the requirements for all codified data ,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
6398,"(53, 134)",The system shall support the requirements for all codified data ,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.,Neutral
6399,"(53, 135)",The system shall support the requirements for all codified data ,The system will provide the ability to register patients of all types.,Neutral
6400,"(53, 136)",The system shall support the requirements for all codified data ,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
6401,"(53, 137)",The system shall support the requirements for all codified data ,The system shall include Standard Laboratory and Medication orderable files.,Neutral
6402,"(53, 138)",The system shall support the requirements for all codified data ,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
6403,"(53, 139)",The system shall support the requirements for all codified data ,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
6404,"(53, 140)",The system shall support the requirements for all codified data ,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
6405,"(53, 141)",The system shall support the requirements for all codified data ,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
6406,"(53, 142)",The system shall support the requirements for all codified data ,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
6407,"(53, 143)",The system shall support the requirements for all codified data ,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
6408,"(53, 144)",The system shall support the requirements for all codified data ,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
6409,"(53, 145)",The system shall support the requirements for all codified data ,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.,Neutral
6410,"(53, 146)",The system shall support the requirements for all codified data ,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
6411,"(53, 147)",The system shall support the requirements for all codified data ,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
6412,"(53, 148)",The system shall support the requirements for all codified data ,"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.",Neutral
6413,"(54, 55)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall require the entry of an access code and a verify code to gain access to the system.,Neutral
6414,"(54, 56)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall require the entry of an access code to gain access to the system.,Neutral
6415,"(54, 57)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
6416,"(54, 58)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
6417,"(54, 59)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6418,"(54, 60)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6419,"(54, 61)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
6420,"(54, 62)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall have pre-defined progress note templates.,Neutral
6421,"(54, 63)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
6422,"(54, 64)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
6423,"(54, 65)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall require only a smart card to digitally sign an order.,Neutral
6424,"(54, 66)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
6425,"(54, 67)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow users to enter time in several different formats.,Neutral
6426,"(54, 68)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6427,"(54, 69)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6428,"(54, 70)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","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.",Neutral
6429,"(54, 71)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","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.",Neutral
6430,"(54, 72)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
6431,"(54, 73)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","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.",Neutral
6432,"(54, 74)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
6433,"(54, 75)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall have a option to release unsigned orders to services,Neutral
6434,"(54, 76)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","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.",Neutral
6435,"(54, 77)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
6436,"(54, 78)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
6437,"(54, 79)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","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.",Neutral
6438,"(54, 80)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
6439,"(54, 81)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
6440,"(54, 82)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",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.,Neutral
6441,"(54, 83)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",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.,Neutral
6442,"(54, 84)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",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.,Neutral
6443,"(54, 85)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
6444,"(54, 86)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
6445,"(54, 87)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall display a message telling the user that the selected patient is deceased.,Neutral
6446,"(54, 88)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
6447,"(54, 89)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall not allow mandatory notifications to be disabled.,Neutral
6448,"(54, 90)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow users to disable unwanted notifications as desired.,Neutral
6449,"(54, 91)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
6450,"(54, 92)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",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.,Neutral
6451,"(54, 93)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
6452,"(54, 94)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall use any protocol for transferring messages among packages.,Neutral
6453,"(54, 95)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
6454,"(54, 96)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
6455,"(54, 97)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
6456,"(54, 98)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
6457,"(54, 99)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
6458,"(54, 100)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
6459,"(54, 101)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
6460,"(54, 102)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
6461,"(54, 103)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
6462,"(54, 104)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow a user to foward notification to someone else at the site.,Neutral
6463,"(54, 105)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
6464,"(54, 106)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The system shall define, populate, and retrieve information about user classes.",Neutral
6465,"(54, 107)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6466,"(54, 108)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6467,"(54, 109)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
6468,"(54, 110)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow concurrent membership in more than one User Class.,Neutral
6469,"(54, 111)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow membership in only one User Class.,Neutral
6470,"(54, 112)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
6471,"(54, 113)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","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.",Neutral
6472,"(54, 114)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall improve accessibility of online clinical information and results.,Neutral
6473,"(54, 115)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","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.",Neutral
6474,"(54, 116)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
6475,"(54, 117)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
6476,"(54, 118)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
6477,"(54, 119)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall make the traditional order entry processes more practical.,Neutral
6478,"(54, 120)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
6479,"(54, 121)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
6480,"(54, 122)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
6481,"(54, 123)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
6482,"(54, 124)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","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.",Neutral
6483,"(54, 125)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
6484,"(54, 126)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
6485,"(54, 127)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","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.",Neutral
6486,"(54, 128)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
6487,"(54, 129)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","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.",Neutral
6488,"(54, 130)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
6489,"(54, 131)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall delete history of received immunizations.,Neutral
6490,"(54, 132)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall only delete history of recieved immunizations unless user specifies,Neutral
6491,"(54, 133)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
6492,"(54, 134)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",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.,Neutral
6493,"(54, 135)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system will provide the ability to register patients of all types.,Neutral
6494,"(54, 136)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
6495,"(54, 137)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall include Standard Laboratory and Medication orderable files.,Neutral
6496,"(54, 138)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
6497,"(54, 139)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
6498,"(54, 140)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
6499,"(54, 141)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
6500,"(54, 142)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
6501,"(54, 143)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
6502,"(54, 144)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
6503,"(54, 145)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",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.,Neutral
6504,"(54, 146)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
6505,"(54, 147)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
6506,"(54, 148)","The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order).","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.",Neutral
6507,"(55, 56)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall require the entry of an access code to gain access to the system.,Conflict
6508,"(55, 57)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
6509,"(55, 58)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
6510,"(55, 59)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6511,"(55, 60)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6512,"(55, 61)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
6513,"(55, 62)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall have pre-defined progress note templates.,Neutral
6514,"(55, 63)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
6515,"(55, 64)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
6516,"(55, 65)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall require only a smart card to digitally sign an order.,Neutral
6517,"(55, 66)",The system shall require the entry of an access code and a verify code to gain access to the system.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
6518,"(55, 67)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow users to enter time in several different formats.,Neutral
6519,"(55, 68)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6520,"(55, 69)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6521,"(55, 70)",The system shall require the entry of an access code and a verify code to gain access to the system.,"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.",Neutral
6522,"(55, 71)",The system shall require the entry of an access code and a verify code to gain access to the system.,"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.",Neutral
6523,"(55, 72)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
6524,"(55, 73)",The system shall require the entry of an access code and a verify code to gain access to the system.,"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.",Neutral
6525,"(55, 74)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
6526,"(55, 75)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall have a option to release unsigned orders to services,Neutral
6527,"(55, 76)",The system shall require the entry of an access code and a verify code to gain access to the system.,"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.",Neutral
6528,"(55, 77)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
6529,"(55, 78)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
6530,"(55, 79)",The system shall require the entry of an access code and a verify code to gain access to the system.,"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.",Neutral
6531,"(55, 80)",The system shall require the entry of an access code and a verify code to gain access to the system.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
6532,"(55, 81)",The system shall require the entry of an access code and a verify code to gain access to the system.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
6533,"(55, 82)",The system shall require the entry of an access code and a verify code to gain access to the system.,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.,Neutral
6534,"(55, 83)",The system shall require the entry of an access code and a verify code to gain access to the system.,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.,Neutral
6535,"(55, 84)",The system shall require the entry of an access code and a verify code to gain access to the system.,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.,Neutral
6536,"(55, 85)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
6537,"(55, 86)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
6538,"(55, 87)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
6539,"(55, 88)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
6540,"(55, 89)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall not allow mandatory notifications to be disabled.,Neutral
6541,"(55, 90)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow users to disable unwanted notifications as desired.,Neutral
6542,"(55, 91)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
6543,"(55, 92)",The system shall require the entry of an access code and a verify code to gain access to the system.,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.,Neutral
6544,"(55, 93)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
6545,"(55, 94)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall use any protocol for transferring messages among packages.,Neutral
6546,"(55, 95)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
6547,"(55, 96)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
6548,"(55, 97)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
6549,"(55, 98)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
6550,"(55, 99)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
6551,"(55, 100)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
6552,"(55, 101)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
6553,"(55, 102)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
6554,"(55, 103)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
6555,"(55, 104)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow a user to foward notification to someone else at the site.,Neutral
6556,"(55, 105)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
6557,"(55, 106)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The system shall define, populate, and retrieve information about user classes.",Neutral
6558,"(55, 107)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6559,"(55, 108)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6560,"(55, 109)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
6561,"(55, 110)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow concurrent membership in more than one User Class.,Neutral
6562,"(55, 111)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow membership in only one User Class.,Neutral
6563,"(55, 112)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
6564,"(55, 113)",The system shall require the entry of an access code and a verify code to gain access to the system.,"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.",Neutral
6565,"(55, 114)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall improve accessibility of online clinical information and results.,Neutral
6566,"(55, 115)",The system shall require the entry of an access code and a verify code to gain access to the system.,"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.",Neutral
6567,"(55, 116)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
6568,"(55, 117)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
6569,"(55, 118)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
6570,"(55, 119)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall make the traditional order entry processes more practical.,Neutral
6571,"(55, 120)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
6572,"(55, 121)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
6573,"(55, 122)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
6574,"(55, 123)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
6575,"(55, 124)",The system shall require the entry of an access code and a verify code to gain access to the system.,"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.",Neutral
6576,"(55, 125)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
6577,"(55, 126)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
6578,"(55, 127)",The system shall require the entry of an access code and a verify code to gain access to the system.,"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.",Neutral
6579,"(55, 128)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
6580,"(55, 129)",The system shall require the entry of an access code and a verify code to gain access to the system.,"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.",Neutral
6581,"(55, 130)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
6582,"(55, 131)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall delete history of received immunizations.,Neutral
6583,"(55, 132)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
6584,"(55, 133)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
6585,"(55, 134)",The system shall require the entry of an access code and a verify code to gain access to the system.,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.,Neutral
6586,"(55, 135)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system will provide the ability to register patients of all types.,Neutral
6587,"(55, 136)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
6588,"(55, 137)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
6589,"(55, 138)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
6590,"(55, 139)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
6591,"(55, 140)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
6592,"(55, 141)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
6593,"(55, 142)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
6594,"(55, 143)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
6595,"(55, 144)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
6596,"(55, 145)",The system shall require the entry of an access code and a verify code to gain access to the system.,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.,Neutral
6597,"(55, 146)",The system shall require the entry of an access code and a verify code to gain access to the system.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
6598,"(55, 147)",The system shall require the entry of an access code and a verify code to gain access to the system.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
6599,"(55, 148)",The system shall require the entry of an access code and a verify code to gain access to the system.,"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.",Neutral
6600,"(56, 57)",The system shall require the entry of an access code to gain access to the system.,The system shall enforce these access levels when problems are entered via the encounter form.,Neutral
6601,"(56, 58)",The system shall require the entry of an access code to gain access to the system.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
6602,"(56, 59)",The system shall require the entry of an access code to gain access to the system.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6603,"(56, 60)",The system shall require the entry of an access code to gain access to the system.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6604,"(56, 61)",The system shall require the entry of an access code to gain access to the system.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
6605,"(56, 62)",The system shall require the entry of an access code to gain access to the system.,The system shall have pre-defined progress note templates.,Neutral
6606,"(56, 63)",The system shall require the entry of an access code to gain access to the system.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
6607,"(56, 64)",The system shall require the entry of an access code to gain access to the system.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
6608,"(56, 65)",The system shall require the entry of an access code to gain access to the system.,The system shall require only a smart card to digitally sign an order.,Neutral
6609,"(56, 66)",The system shall require the entry of an access code to gain access to the system.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
6610,"(56, 67)",The system shall require the entry of an access code to gain access to the system.,The system shall allow users to enter time in several different formats.,Neutral
6611,"(56, 68)",The system shall require the entry of an access code to gain access to the system.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6612,"(56, 69)",The system shall require the entry of an access code to gain access to the system.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6613,"(56, 70)",The system shall require the entry of an access code to gain access to the system.,"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.",Neutral
6614,"(56, 71)",The system shall require the entry of an access code to gain access to the system.,"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.",Neutral
6615,"(56, 72)",The system shall require the entry of an access code to gain access to the system.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
6616,"(56, 73)",The system shall require the entry of an access code to gain access to the system.,"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.",Neutral
6617,"(56, 74)",The system shall require the entry of an access code to gain access to the system.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
6618,"(56, 75)",The system shall require the entry of an access code to gain access to the system.,The system shall have a option to release unsigned orders to services,Neutral
6619,"(56, 76)",The system shall require the entry of an access code to gain access to the system.,"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.",Neutral
6620,"(56, 77)",The system shall require the entry of an access code to gain access to the system.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
6621,"(56, 78)",The system shall require the entry of an access code to gain access to the system.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
6622,"(56, 79)",The system shall require the entry of an access code to gain access to the system.,"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.",Neutral
6623,"(56, 80)",The system shall require the entry of an access code to gain access to the system.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
6624,"(56, 81)",The system shall require the entry of an access code to gain access to the system.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
6625,"(56, 82)",The system shall require the entry of an access code to gain access to the system.,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.,Neutral
6626,"(56, 83)",The system shall require the entry of an access code to gain access to the system.,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.,Neutral
6627,"(56, 84)",The system shall require the entry of an access code to gain access to the system.,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.,Neutral
6628,"(56, 85)",The system shall require the entry of an access code to gain access to the system.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
6629,"(56, 86)",The system shall require the entry of an access code to gain access to the system.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
6630,"(56, 87)",The system shall require the entry of an access code to gain access to the system.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
6631,"(56, 88)",The system shall require the entry of an access code to gain access to the system.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
6632,"(56, 89)",The system shall require the entry of an access code to gain access to the system.,The system shall not allow mandatory notifications to be disabled.,Neutral
6633,"(56, 90)",The system shall require the entry of an access code to gain access to the system.,The system shall allow users to disable unwanted notifications as desired.,Neutral
6634,"(56, 91)",The system shall require the entry of an access code to gain access to the system.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
6635,"(56, 92)",The system shall require the entry of an access code to gain access to the system.,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.,Neutral
6636,"(56, 93)",The system shall require the entry of an access code to gain access to the system.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
6637,"(56, 94)",The system shall require the entry of an access code to gain access to the system.,The system shall use any protocol for transferring messages among packages.,Neutral
6638,"(56, 95)",The system shall require the entry of an access code to gain access to the system.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
6639,"(56, 96)",The system shall require the entry of an access code to gain access to the system.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
6640,"(56, 97)",The system shall require the entry of an access code to gain access to the system.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
6641,"(56, 98)",The system shall require the entry of an access code to gain access to the system.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
6642,"(56, 99)",The system shall require the entry of an access code to gain access to the system.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
6643,"(56, 100)",The system shall require the entry of an access code to gain access to the system.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
6644,"(56, 101)",The system shall require the entry of an access code to gain access to the system.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
6645,"(56, 102)",The system shall require the entry of an access code to gain access to the system.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
6646,"(56, 103)",The system shall require the entry of an access code to gain access to the system.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
6647,"(56, 104)",The system shall require the entry of an access code to gain access to the system.,The system shall allow a user to foward notification to someone else at the site.,Neutral
6648,"(56, 105)",The system shall require the entry of an access code to gain access to the system.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
6649,"(56, 106)",The system shall require the entry of an access code to gain access to the system.,"The system shall define, populate, and retrieve information about user classes.",Neutral
6650,"(56, 107)",The system shall require the entry of an access code to gain access to the system.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6651,"(56, 108)",The system shall require the entry of an access code to gain access to the system.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6652,"(56, 109)",The system shall require the entry of an access code to gain access to the system.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
6653,"(56, 110)",The system shall require the entry of an access code to gain access to the system.,The system shall allow concurrent membership in more than one User Class.,Neutral
6654,"(56, 111)",The system shall require the entry of an access code to gain access to the system.,The system shall allow membership in only one User Class.,Neutral
6655,"(56, 112)",The system shall require the entry of an access code to gain access to the system.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
6656,"(56, 113)",The system shall require the entry of an access code to gain access to the system.,"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.",Neutral
6657,"(56, 114)",The system shall require the entry of an access code to gain access to the system.,The system shall improve accessibility of online clinical information and results.,Neutral
6658,"(56, 115)",The system shall require the entry of an access code to gain access to the system.,"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.",Neutral
6659,"(56, 116)",The system shall require the entry of an access code to gain access to the system.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
6660,"(56, 117)",The system shall require the entry of an access code to gain access to the system.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
6661,"(56, 118)",The system shall require the entry of an access code to gain access to the system.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
6662,"(56, 119)",The system shall require the entry of an access code to gain access to the system.,The system shall make the traditional order entry processes more practical.,Neutral
6663,"(56, 120)",The system shall require the entry of an access code to gain access to the system.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
6664,"(56, 121)",The system shall require the entry of an access code to gain access to the system.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
6665,"(56, 122)",The system shall require the entry of an access code to gain access to the system.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
6666,"(56, 123)",The system shall require the entry of an access code to gain access to the system.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
6667,"(56, 124)",The system shall require the entry of an access code to gain access to the system.,"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.",Neutral
6668,"(56, 125)",The system shall require the entry of an access code to gain access to the system.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
6669,"(56, 126)",The system shall require the entry of an access code to gain access to the system.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
6670,"(56, 127)",The system shall require the entry of an access code to gain access to the system.,"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.",Neutral
6671,"(56, 128)",The system shall require the entry of an access code to gain access to the system.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
6672,"(56, 129)",The system shall require the entry of an access code to gain access to the system.,"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.",Neutral
6673,"(56, 130)",The system shall require the entry of an access code to gain access to the system.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
6674,"(56, 131)",The system shall require the entry of an access code to gain access to the system.,The system shall delete history of received immunizations.,Neutral
6675,"(56, 132)",The system shall require the entry of an access code to gain access to the system.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
6676,"(56, 133)",The system shall require the entry of an access code to gain access to the system.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
6677,"(56, 134)",The system shall require the entry of an access code to gain access to the system.,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.,Neutral
6678,"(56, 135)",The system shall require the entry of an access code to gain access to the system.,The system will provide the ability to register patients of all types.,Neutral
6679,"(56, 136)",The system shall require the entry of an access code to gain access to the system.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
6680,"(56, 137)",The system shall require the entry of an access code to gain access to the system.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
6681,"(56, 138)",The system shall require the entry of an access code to gain access to the system.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
6682,"(56, 139)",The system shall require the entry of an access code to gain access to the system.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
6683,"(56, 140)",The system shall require the entry of an access code to gain access to the system.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
6684,"(56, 141)",The system shall require the entry of an access code to gain access to the system.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
6685,"(56, 142)",The system shall require the entry of an access code to gain access to the system.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
6686,"(56, 143)",The system shall require the entry of an access code to gain access to the system.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
6687,"(56, 144)",The system shall require the entry of an access code to gain access to the system.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
6688,"(56, 145)",The system shall require the entry of an access code to gain access to the system.,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.,Neutral
6689,"(56, 146)",The system shall require the entry of an access code to gain access to the system.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
6690,"(56, 147)",The system shall require the entry of an access code to gain access to the system.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
6691,"(56, 148)",The system shall require the entry of an access code to gain access to the system.,"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.",Neutral
6692,"(57, 58)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Neutral
6693,"(57, 59)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6694,"(57, 60)",The system shall enforce these access levels when problems are entered via the encounter form.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6695,"(57, 61)",The system shall enforce these access levels when problems are entered via the encounter form.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
6696,"(57, 62)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall have pre-defined progress note templates.,Neutral
6697,"(57, 63)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
6698,"(57, 64)",The system shall enforce these access levels when problems are entered via the encounter form.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
6699,"(57, 65)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall require only a smart card to digitally sign an order.,Neutral
6700,"(57, 66)",The system shall enforce these access levels when problems are entered via the encounter form.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
6701,"(57, 67)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow users to enter time in several different formats.,Neutral
6702,"(57, 68)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6703,"(57, 69)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6704,"(57, 70)",The system shall enforce these access levels when problems are entered via the encounter form.,"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.",Neutral
6705,"(57, 71)",The system shall enforce these access levels when problems are entered via the encounter form.,"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.",Neutral
6706,"(57, 72)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
6707,"(57, 73)",The system shall enforce these access levels when problems are entered via the encounter form.,"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.",Neutral
6708,"(57, 74)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
6709,"(57, 75)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall have a option to release unsigned orders to services,Neutral
6710,"(57, 76)",The system shall enforce these access levels when problems are entered via the encounter form.,"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.",Neutral
6711,"(57, 77)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
6712,"(57, 78)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
6713,"(57, 79)",The system shall enforce these access levels when problems are entered via the encounter form.,"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.",Neutral
6714,"(57, 80)",The system shall enforce these access levels when problems are entered via the encounter form.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
6715,"(57, 81)",The system shall enforce these access levels when problems are entered via the encounter form.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
6716,"(57, 82)",The system shall enforce these access levels when problems are entered via the encounter form.,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.,Neutral
6717,"(57, 83)",The system shall enforce these access levels when problems are entered via the encounter form.,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.,Neutral
6718,"(57, 84)",The system shall enforce these access levels when problems are entered via the encounter form.,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.,Neutral
6719,"(57, 85)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
6720,"(57, 86)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
6721,"(57, 87)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
6722,"(57, 88)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
6723,"(57, 89)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall not allow mandatory notifications to be disabled.,Neutral
6724,"(57, 90)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow users to disable unwanted notifications as desired.,Neutral
6725,"(57, 91)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
6726,"(57, 92)",The system shall enforce these access levels when problems are entered via the encounter form.,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.,Neutral
6727,"(57, 93)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
6728,"(57, 94)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall use any protocol for transferring messages among packages.,Neutral
6729,"(57, 95)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
6730,"(57, 96)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
6731,"(57, 97)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
6732,"(57, 98)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
6733,"(57, 99)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
6734,"(57, 100)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
6735,"(57, 101)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
6736,"(57, 102)",The system shall enforce these access levels when problems are entered via the encounter form.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
6737,"(57, 103)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
6738,"(57, 104)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow a user to foward notification to someone else at the site.,Neutral
6739,"(57, 105)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
6740,"(57, 106)",The system shall enforce these access levels when problems are entered via the encounter form.,"The system shall define, populate, and retrieve information about user classes.",Neutral
6741,"(57, 107)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6742,"(57, 108)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6743,"(57, 109)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
6744,"(57, 110)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow concurrent membership in more than one User Class.,Neutral
6745,"(57, 111)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow membership in only one User Class.,Neutral
6746,"(57, 112)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
6747,"(57, 113)",The system shall enforce these access levels when problems are entered via the encounter form.,"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.",Neutral
6748,"(57, 114)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall improve accessibility of online clinical information and results.,Neutral
6749,"(57, 115)",The system shall enforce these access levels when problems are entered via the encounter form.,"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.",Neutral
6750,"(57, 116)",The system shall enforce these access levels when problems are entered via the encounter form.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
6751,"(57, 117)",The system shall enforce these access levels when problems are entered via the encounter form.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
6752,"(57, 118)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
6753,"(57, 119)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall make the traditional order entry processes more practical.,Neutral
6754,"(57, 120)",The system shall enforce these access levels when problems are entered via the encounter form.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
6755,"(57, 121)",The system shall enforce these access levels when problems are entered via the encounter form.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
6756,"(57, 122)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
6757,"(57, 123)",The system shall enforce these access levels when problems are entered via the encounter form.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
6758,"(57, 124)",The system shall enforce these access levels when problems are entered via the encounter form.,"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.",Neutral
6759,"(57, 125)",The system shall enforce these access levels when problems are entered via the encounter form.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
6760,"(57, 126)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
6761,"(57, 127)",The system shall enforce these access levels when problems are entered via the encounter form.,"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.",Neutral
6762,"(57, 128)",The system shall enforce these access levels when problems are entered via the encounter form.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
6763,"(57, 129)",The system shall enforce these access levels when problems are entered via the encounter form.,"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.",Neutral
6764,"(57, 130)",The system shall enforce these access levels when problems are entered via the encounter form.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
6765,"(57, 131)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall delete history of received immunizations.,Neutral
6766,"(57, 132)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
6767,"(57, 133)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
6768,"(57, 134)",The system shall enforce these access levels when problems are entered via the encounter form.,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.,Neutral
6769,"(57, 135)",The system shall enforce these access levels when problems are entered via the encounter form.,The system will provide the ability to register patients of all types.,Neutral
6770,"(57, 136)",The system shall enforce these access levels when problems are entered via the encounter form.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
6771,"(57, 137)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
6772,"(57, 138)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
6773,"(57, 139)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
6774,"(57, 140)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
6775,"(57, 141)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
6776,"(57, 142)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
6777,"(57, 143)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
6778,"(57, 144)",The system shall enforce these access levels when problems are entered via the encounter form.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
6779,"(57, 145)",The system shall enforce these access levels when problems are entered via the encounter form.,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.,Neutral
6780,"(57, 146)",The system shall enforce these access levels when problems are entered via the encounter form.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
6781,"(57, 147)",The system shall enforce these access levels when problems are entered via the encounter form.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
6782,"(57, 148)",The system shall enforce these access levels when problems are entered via the encounter form.,"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.",Neutral
6783,"(58, 59)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6784,"(58, 60)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Neutral
6785,"(58, 61)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
6786,"(58, 62)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall have pre-defined progress note templates.,Neutral
6787,"(58, 63)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
6788,"(58, 64)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
6789,"(58, 65)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall require only a smart card to digitally sign an order.,Neutral
6790,"(58, 66)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
6791,"(58, 67)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow users to enter time in several different formats.,Neutral
6792,"(58, 68)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6793,"(58, 69)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6794,"(58, 70)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"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.",Neutral
6795,"(58, 71)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"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.",Neutral
6796,"(58, 72)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
6797,"(58, 73)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"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.",Neutral
6798,"(58, 74)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
6799,"(58, 75)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall have a option to release unsigned orders to services,Neutral
6800,"(58, 76)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"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.",Neutral
6801,"(58, 77)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
6802,"(58, 78)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
6803,"(58, 79)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"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.",Neutral
6804,"(58, 80)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
6805,"(58, 81)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
6806,"(58, 82)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,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.,Neutral
6807,"(58, 83)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,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.,Neutral
6808,"(58, 84)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,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.,Neutral
6809,"(58, 85)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
6810,"(58, 86)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
6811,"(58, 87)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
6812,"(58, 88)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
6813,"(58, 89)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall not allow mandatory notifications to be disabled.,Neutral
6814,"(58, 90)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow users to disable unwanted notifications as desired.,Neutral
6815,"(58, 91)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
6816,"(58, 92)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,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.,Neutral
6817,"(58, 93)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
6818,"(58, 94)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall use any protocol for transferring messages among packages.,Neutral
6819,"(58, 95)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
6820,"(58, 96)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
6821,"(58, 97)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
6822,"(58, 98)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
6823,"(58, 99)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
6824,"(58, 100)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
6825,"(58, 101)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
6826,"(58, 102)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
6827,"(58, 103)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
6828,"(58, 104)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow a user to foward notification to someone else at the site.,Neutral
6829,"(58, 105)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
6830,"(58, 106)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The system shall define, populate, and retrieve information about user classes.",Neutral
6831,"(58, 107)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6832,"(58, 108)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6833,"(58, 109)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
6834,"(58, 110)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow concurrent membership in more than one User Class.,Neutral
6835,"(58, 111)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow membership in only one User Class.,Neutral
6836,"(58, 112)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
6837,"(58, 113)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"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.",Neutral
6838,"(58, 114)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall improve accessibility of online clinical information and results.,Neutral
6839,"(58, 115)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"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.",Neutral
6840,"(58, 116)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
6841,"(58, 117)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
6842,"(58, 118)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
6843,"(58, 119)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall make the traditional order entry processes more practical.,Neutral
6844,"(58, 120)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
6845,"(58, 121)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
6846,"(58, 122)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
6847,"(58, 123)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
6848,"(58, 124)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"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.",Neutral
6849,"(58, 125)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
6850,"(58, 126)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
6851,"(58, 127)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"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.",Neutral
6852,"(58, 128)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
6853,"(58, 129)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"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.",Neutral
6854,"(58, 130)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
6855,"(58, 131)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall delete history of received immunizations.,Neutral
6856,"(58, 132)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
6857,"(58, 133)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
6858,"(58, 134)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,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.,Neutral
6859,"(58, 135)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system will provide the ability to register patients of all types.,Neutral
6860,"(58, 136)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
6861,"(58, 137)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
6862,"(58, 138)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
6863,"(58, 139)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
6864,"(58, 140)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
6865,"(58, 141)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
6866,"(58, 142)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
6867,"(58, 143)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
6868,"(58, 144)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
6869,"(58, 145)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,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.,Neutral
6870,"(58, 146)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
6871,"(58, 147)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
6872,"(58, 148)",The system shall provide an option to so a user can quickly set up orders for frequently placed orders.,"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.",Neutral
6873,"(59, 60)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Conflict
6874,"(59, 61)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
6875,"(59, 62)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall have pre-defined progress note templates.,Neutral
6876,"(59, 63)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
6877,"(59, 64)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
6878,"(59, 65)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall require only a smart card to digitally sign an order.,Neutral
6879,"(59, 66)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
6880,"(59, 67)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow users to enter time in several different formats.,Neutral
6881,"(59, 68)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6882,"(59, 69)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6883,"(59, 70)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6884,"(59, 71)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6885,"(59, 72)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
6886,"(59, 73)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6887,"(59, 74)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
6888,"(59, 75)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall have a option to release unsigned orders to services,Neutral
6889,"(59, 76)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6890,"(59, 77)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
6891,"(59, 78)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
6892,"(59, 79)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6893,"(59, 80)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
6894,"(59, 81)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
6895,"(59, 82)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,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.,Neutral
6896,"(59, 83)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,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.,Neutral
6897,"(59, 84)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,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.,Neutral
6898,"(59, 85)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
6899,"(59, 86)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
6900,"(59, 87)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
6901,"(59, 88)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
6902,"(59, 89)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall not allow mandatory notifications to be disabled.,Neutral
6903,"(59, 90)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow users to disable unwanted notifications as desired.,Neutral
6904,"(59, 91)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
6905,"(59, 92)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,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.,Neutral
6906,"(59, 93)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
6907,"(59, 94)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall use any protocol for transferring messages among packages.,Neutral
6908,"(59, 95)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
6909,"(59, 96)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
6910,"(59, 97)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
6911,"(59, 98)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
6912,"(59, 99)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
6913,"(59, 100)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
6914,"(59, 101)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
6915,"(59, 102)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
6916,"(59, 103)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
6917,"(59, 104)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow a user to foward notification to someone else at the site.,Neutral
6918,"(59, 105)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
6919,"(59, 106)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall define, populate, and retrieve information about user classes.",Neutral
6920,"(59, 107)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6921,"(59, 108)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
6922,"(59, 109)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
6923,"(59, 110)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow concurrent membership in more than one User Class.,Neutral
6924,"(59, 111)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow membership in only one User Class.,Neutral
6925,"(59, 112)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
6926,"(59, 113)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6927,"(59, 114)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall improve accessibility of online clinical information and results.,Neutral
6928,"(59, 115)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6929,"(59, 116)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
6930,"(59, 117)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
6931,"(59, 118)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
6932,"(59, 119)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall make the traditional order entry processes more practical.,Neutral
6933,"(59, 120)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
6934,"(59, 121)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
6935,"(59, 122)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
6936,"(59, 123)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
6937,"(59, 124)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6938,"(59, 125)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
6939,"(59, 126)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
6940,"(59, 127)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6941,"(59, 128)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
6942,"(59, 129)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6943,"(59, 130)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
6944,"(59, 131)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall delete history of received immunizations.,Neutral
6945,"(59, 132)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
6946,"(59, 133)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
6947,"(59, 134)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,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.,Neutral
6948,"(59, 135)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system will provide the ability to register patients of all types.,Neutral
6949,"(59, 136)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
6950,"(59, 137)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
6951,"(59, 138)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
6952,"(59, 139)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
6953,"(59, 140)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
6954,"(59, 141)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
6955,"(59, 142)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
6956,"(59, 143)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
6957,"(59, 144)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
6958,"(59, 145)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,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.,Neutral
6959,"(59, 146)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
6960,"(59, 147)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
6961,"(59, 148)",The system shall allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6962,"(60, 61)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Neutral
6963,"(60, 62)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall have pre-defined progress note templates.,Neutral
6964,"(60, 63)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
6965,"(60, 64)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
6966,"(60, 65)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall require only a smart card to digitally sign an order.,Neutral
6967,"(60, 66)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
6968,"(60, 67)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow users to enter time in several different formats.,Neutral
6969,"(60, 68)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6970,"(60, 69)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
6971,"(60, 70)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6972,"(60, 71)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6973,"(60, 72)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
6974,"(60, 73)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6975,"(60, 74)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
6976,"(60, 75)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall have a option to release unsigned orders to services,Neutral
6977,"(60, 76)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6978,"(60, 77)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
6979,"(60, 78)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
6980,"(60, 79)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
6981,"(60, 80)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
6982,"(60, 81)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
6983,"(60, 82)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,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.,Neutral
6984,"(60, 83)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,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.,Neutral
6985,"(60, 84)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,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.,Neutral
6986,"(60, 85)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
6987,"(60, 86)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
6988,"(60, 87)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
6989,"(60, 88)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
6990,"(60, 89)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall not allow mandatory notifications to be disabled.,Neutral
6991,"(60, 90)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow users to disable unwanted notifications as desired.,Neutral
6992,"(60, 91)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
6993,"(60, 92)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,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.,Neutral
6994,"(60, 93)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
6995,"(60, 94)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall use any protocol for transferring messages among packages.,Neutral
6996,"(60, 95)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
6997,"(60, 96)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
6998,"(60, 97)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
6999,"(60, 98)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7000,"(60, 99)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7001,"(60, 100)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7002,"(60, 101)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7003,"(60, 102)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7004,"(60, 103)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7005,"(60, 104)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow a user to foward notification to someone else at the site.,Neutral
7006,"(60, 105)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7007,"(60, 106)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall define, populate, and retrieve information about user classes.",Neutral
7008,"(60, 107)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7009,"(60, 108)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7010,"(60, 109)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7011,"(60, 110)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow concurrent membership in more than one User Class.,Neutral
7012,"(60, 111)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow membership in only one User Class.,Neutral
7013,"(60, 112)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7014,"(60, 113)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
7015,"(60, 114)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall improve accessibility of online clinical information and results.,Neutral
7016,"(60, 115)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
7017,"(60, 116)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7018,"(60, 117)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7019,"(60, 118)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7020,"(60, 119)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall make the traditional order entry processes more practical.,Neutral
7021,"(60, 120)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
7022,"(60, 121)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
7023,"(60, 122)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
7024,"(60, 123)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
7025,"(60, 124)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
7026,"(60, 125)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
7027,"(60, 126)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
7028,"(60, 127)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
7029,"(60, 128)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
7030,"(60, 129)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
7031,"(60, 130)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
7032,"(60, 131)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall delete history of received immunizations.,Neutral
7033,"(60, 132)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
7034,"(60, 133)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
7035,"(60, 134)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,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.,Neutral
7036,"(60, 135)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system will provide the ability to register patients of all types.,Neutral
7037,"(60, 136)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
7038,"(60, 137)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
7039,"(60, 138)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
7040,"(60, 139)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
7041,"(60, 140)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
7042,"(60, 141)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
7043,"(60, 142)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
7044,"(60, 143)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
7045,"(60, 144)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
7046,"(60, 145)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,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.,Neutral
7047,"(60, 146)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
7048,"(60, 147)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
7049,"(60, 148)",The system must allow several orders to be placed with the ability for a user to sign for them all at once.,"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.",Neutral
7050,"(61, 62)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall have pre-defined progress note templates.,Neutral
7051,"(61, 63)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
7052,"(61, 64)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
7053,"(61, 65)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall require only a smart card to digitally sign an order.,Neutral
7054,"(61, 66)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
7055,"(61, 67)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow users to enter time in several different formats.,Neutral
7056,"(61, 68)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7057,"(61, 69)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7058,"(61, 70)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","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.",Neutral
7059,"(61, 71)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","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.",Neutral
7060,"(61, 72)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
7061,"(61, 73)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","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.",Neutral
7062,"(61, 74)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
7063,"(61, 75)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall have a option to release unsigned orders to services,Neutral
7064,"(61, 76)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","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.",Neutral
7065,"(61, 77)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
7066,"(61, 78)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
7067,"(61, 79)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","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.",Neutral
7068,"(61, 80)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
7069,"(61, 81)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
7070,"(61, 82)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",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.,Neutral
7071,"(61, 83)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",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.,Neutral
7072,"(61, 84)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",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.,Neutral
7073,"(61, 85)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
7074,"(61, 86)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
7075,"(61, 87)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
7076,"(61, 88)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
7077,"(61, 89)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall not allow mandatory notifications to be disabled.,Neutral
7078,"(61, 90)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow users to disable unwanted notifications as desired.,Neutral
7079,"(61, 91)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
7080,"(61, 92)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",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.,Neutral
7081,"(61, 93)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
7082,"(61, 94)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall use any protocol for transferring messages among packages.,Neutral
7083,"(61, 95)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
7084,"(61, 96)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
7085,"(61, 97)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
7086,"(61, 98)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7087,"(61, 99)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7088,"(61, 100)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7089,"(61, 101)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7090,"(61, 102)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7091,"(61, 103)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7092,"(61, 104)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow a user to foward notification to someone else at the site.,Neutral
7093,"(61, 105)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7094,"(61, 106)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","The system shall define, populate, and retrieve information about user classes.",Neutral
7095,"(61, 107)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7096,"(61, 108)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7097,"(61, 109)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7098,"(61, 110)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow concurrent membership in more than one User Class.,Neutral
7099,"(61, 111)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow membership in only one User Class.,Neutral
7100,"(61, 112)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7101,"(61, 113)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","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.",Neutral
7102,"(61, 114)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall improve accessibility of online clinical information and results.,Neutral
7103,"(61, 115)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","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.",Neutral
7104,"(61, 116)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7105,"(61, 117)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7106,"(61, 118)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7107,"(61, 119)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall make the traditional order entry processes more practical.,Neutral
7108,"(61, 120)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
7109,"(61, 121)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
7110,"(61, 122)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
7111,"(61, 123)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
7112,"(61, 124)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","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.",Neutral
7113,"(61, 125)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
7114,"(61, 126)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
7115,"(61, 127)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","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.",Neutral
7116,"(61, 128)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
7117,"(61, 129)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","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.",Neutral
7118,"(61, 130)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
7119,"(61, 131)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall delete history of received immunizations.,Neutral
7120,"(61, 132)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
7121,"(61, 133)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
7122,"(61, 134)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",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.,Neutral
7123,"(61, 135)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system will provide the ability to register patients of all types.,Neutral
7124,"(61, 136)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
7125,"(61, 137)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
7126,"(61, 138)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
7127,"(61, 139)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
7128,"(61, 140)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
7129,"(61, 141)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
7130,"(61, 142)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
7131,"(61, 143)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
7132,"(61, 144)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
7133,"(61, 145)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",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.,Neutral
7134,"(61, 146)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
7135,"(61, 147)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
7136,"(61, 148)","The system shall allow event-delay capability for pre-admission, discharge, and transfer orders.","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.",Neutral
7137,"(62, 63)",The system shall have pre-defined progress note templates.,The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Neutral
7138,"(62, 64)",The system shall have pre-defined progress note templates.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
7139,"(62, 65)",The system shall have pre-defined progress note templates.,The system shall require only a smart card to digitally sign an order.,Neutral
7140,"(62, 66)",The system shall have pre-defined progress note templates.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
7141,"(62, 67)",The system shall have pre-defined progress note templates.,The system shall allow users to enter time in several different formats.,Neutral
7142,"(62, 68)",The system shall have pre-defined progress note templates.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7143,"(62, 69)",The system shall have pre-defined progress note templates.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7144,"(62, 70)",The system shall have pre-defined progress note templates.,"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.",Neutral
7145,"(62, 71)",The system shall have pre-defined progress note templates.,"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.",Neutral
7146,"(62, 72)",The system shall have pre-defined progress note templates.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
7147,"(62, 73)",The system shall have pre-defined progress note templates.,"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.",Neutral
7148,"(62, 74)",The system shall have pre-defined progress note templates.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
7149,"(62, 75)",The system shall have pre-defined progress note templates.,The system shall have a option to release unsigned orders to services,Neutral
7150,"(62, 76)",The system shall have pre-defined progress note templates.,"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.",Neutral
7151,"(62, 77)",The system shall have pre-defined progress note templates.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
7152,"(62, 78)",The system shall have pre-defined progress note templates.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
7153,"(62, 79)",The system shall have pre-defined progress note templates.,"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.",Neutral
7154,"(62, 80)",The system shall have pre-defined progress note templates.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
7155,"(62, 81)",The system shall have pre-defined progress note templates.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
7156,"(62, 82)",The system shall have pre-defined progress note templates.,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.,Neutral
7157,"(62, 83)",The system shall have pre-defined progress note templates.,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.,Neutral
7158,"(62, 84)",The system shall have pre-defined progress note templates.,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.,Neutral
7159,"(62, 85)",The system shall have pre-defined progress note templates.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
7160,"(62, 86)",The system shall have pre-defined progress note templates.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
7161,"(62, 87)",The system shall have pre-defined progress note templates.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
7162,"(62, 88)",The system shall have pre-defined progress note templates.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
7163,"(62, 89)",The system shall have pre-defined progress note templates.,The system shall not allow mandatory notifications to be disabled.,Neutral
7164,"(62, 90)",The system shall have pre-defined progress note templates.,The system shall allow users to disable unwanted notifications as desired.,Neutral
7165,"(62, 91)",The system shall have pre-defined progress note templates.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
7166,"(62, 92)",The system shall have pre-defined progress note templates.,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.,Neutral
7167,"(62, 93)",The system shall have pre-defined progress note templates.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
7168,"(62, 94)",The system shall have pre-defined progress note templates.,The system shall use any protocol for transferring messages among packages.,Neutral
7169,"(62, 95)",The system shall have pre-defined progress note templates.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
7170,"(62, 96)",The system shall have pre-defined progress note templates.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
7171,"(62, 97)",The system shall have pre-defined progress note templates.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
7172,"(62, 98)",The system shall have pre-defined progress note templates.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7173,"(62, 99)",The system shall have pre-defined progress note templates.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7174,"(62, 100)",The system shall have pre-defined progress note templates.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7175,"(62, 101)",The system shall have pre-defined progress note templates.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7176,"(62, 102)",The system shall have pre-defined progress note templates.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7177,"(62, 103)",The system shall have pre-defined progress note templates.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7178,"(62, 104)",The system shall have pre-defined progress note templates.,The system shall allow a user to foward notification to someone else at the site.,Neutral
7179,"(62, 105)",The system shall have pre-defined progress note templates.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7180,"(62, 106)",The system shall have pre-defined progress note templates.,"The system shall define, populate, and retrieve information about user classes.",Neutral
7181,"(62, 107)",The system shall have pre-defined progress note templates.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7182,"(62, 108)",The system shall have pre-defined progress note templates.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7183,"(62, 109)",The system shall have pre-defined progress note templates.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7184,"(62, 110)",The system shall have pre-defined progress note templates.,The system shall allow concurrent membership in more than one User Class.,Neutral
7185,"(62, 111)",The system shall have pre-defined progress note templates.,The system shall allow membership in only one User Class.,Neutral
7186,"(62, 112)",The system shall have pre-defined progress note templates.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7187,"(62, 113)",The system shall have pre-defined progress note templates.,"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.",Neutral
7188,"(62, 114)",The system shall have pre-defined progress note templates.,The system shall improve accessibility of online clinical information and results.,Neutral
7189,"(62, 115)",The system shall have pre-defined progress note templates.,"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.",Neutral
7190,"(62, 116)",The system shall have pre-defined progress note templates.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7191,"(62, 117)",The system shall have pre-defined progress note templates.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7192,"(62, 118)",The system shall have pre-defined progress note templates.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7193,"(62, 119)",The system shall have pre-defined progress note templates.,The system shall make the traditional order entry processes more practical.,Neutral
7194,"(62, 120)",The system shall have pre-defined progress note templates.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
7195,"(62, 121)",The system shall have pre-defined progress note templates.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
7196,"(62, 122)",The system shall have pre-defined progress note templates.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
7197,"(62, 123)",The system shall have pre-defined progress note templates.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
7198,"(62, 124)",The system shall have pre-defined progress note templates.,"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.",Neutral
7199,"(62, 125)",The system shall have pre-defined progress note templates.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
7200,"(62, 126)",The system shall have pre-defined progress note templates.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
7201,"(62, 127)",The system shall have pre-defined progress note templates.,"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.",Neutral
7202,"(62, 128)",The system shall have pre-defined progress note templates.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
7203,"(62, 129)",The system shall have pre-defined progress note templates.,"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.",Neutral
7204,"(62, 130)",The system shall have pre-defined progress note templates.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
7205,"(62, 131)",The system shall have pre-defined progress note templates.,The system shall delete history of received immunizations.,Neutral
7206,"(62, 132)",The system shall have pre-defined progress note templates.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
7207,"(62, 133)",The system shall have pre-defined progress note templates.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
7208,"(62, 134)",The system shall have pre-defined progress note templates.,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.,Neutral
7209,"(62, 135)",The system shall have pre-defined progress note templates.,The system will provide the ability to register patients of all types.,Neutral
7210,"(62, 136)",The system shall have pre-defined progress note templates.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
7211,"(62, 137)",The system shall have pre-defined progress note templates.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
7212,"(62, 138)",The system shall have pre-defined progress note templates.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
7213,"(62, 139)",The system shall have pre-defined progress note templates.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
7214,"(62, 140)",The system shall have pre-defined progress note templates.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
7215,"(62, 141)",The system shall have pre-defined progress note templates.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
7216,"(62, 142)",The system shall have pre-defined progress note templates.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
7217,"(62, 143)",The system shall have pre-defined progress note templates.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
7218,"(62, 144)",The system shall have pre-defined progress note templates.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
7219,"(62, 145)",The system shall have pre-defined progress note templates.,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.,Neutral
7220,"(62, 146)",The system shall have pre-defined progress note templates.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
7221,"(62, 147)",The system shall have pre-defined progress note templates.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
7222,"(62, 148)",The system shall have pre-defined progress note templates.,"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.",Neutral
7223,"(63, 64)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Neutral
7224,"(63, 65)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall require only a smart card to digitally sign an order.,Neutral
7225,"(63, 66)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
7226,"(63, 67)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow users to enter time in several different formats.,Neutral
7227,"(63, 68)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7228,"(63, 69)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7229,"(63, 70)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"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.",Neutral
7230,"(63, 71)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"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.",Neutral
7231,"(63, 72)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
7232,"(63, 73)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"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.",Neutral
7233,"(63, 74)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
7234,"(63, 75)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall have a option to release unsigned orders to services,Neutral
7235,"(63, 76)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"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.",Neutral
7236,"(63, 77)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
7237,"(63, 78)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
7238,"(63, 79)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"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.",Neutral
7239,"(63, 80)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
7240,"(63, 81)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
7241,"(63, 82)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,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.,Neutral
7242,"(63, 83)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,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.,Neutral
7243,"(63, 84)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,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.,Neutral
7244,"(63, 85)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
7245,"(63, 86)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
7246,"(63, 87)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
7247,"(63, 88)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
7248,"(63, 89)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall not allow mandatory notifications to be disabled.,Neutral
7249,"(63, 90)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow users to disable unwanted notifications as desired.,Neutral
7250,"(63, 91)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
7251,"(63, 92)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,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.,Neutral
7252,"(63, 93)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
7253,"(63, 94)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall use any protocol for transferring messages among packages.,Neutral
7254,"(63, 95)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
7255,"(63, 96)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
7256,"(63, 97)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
7257,"(63, 98)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7258,"(63, 99)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7259,"(63, 100)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7260,"(63, 101)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7261,"(63, 102)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7262,"(63, 103)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7263,"(63, 104)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow a user to foward notification to someone else at the site.,Neutral
7264,"(63, 105)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7265,"(63, 106)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"The system shall define, populate, and retrieve information about user classes.",Neutral
7266,"(63, 107)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7267,"(63, 108)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7268,"(63, 109)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7269,"(63, 110)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow concurrent membership in more than one User Class.,Neutral
7270,"(63, 111)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow membership in only one User Class.,Neutral
7271,"(63, 112)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7272,"(63, 113)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"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.",Neutral
7273,"(63, 114)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall improve accessibility of online clinical information and results.,Neutral
7274,"(63, 115)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"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.",Neutral
7275,"(63, 116)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7276,"(63, 117)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7277,"(63, 118)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7278,"(63, 119)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall make the traditional order entry processes more practical.,Neutral
7279,"(63, 120)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
7280,"(63, 121)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
7281,"(63, 122)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
7282,"(63, 123)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
7283,"(63, 124)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"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.",Neutral
7284,"(63, 125)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
7285,"(63, 126)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
7286,"(63, 127)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"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.",Neutral
7287,"(63, 128)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
7288,"(63, 129)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"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.",Neutral
7289,"(63, 130)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
7290,"(63, 131)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall delete history of received immunizations.,Neutral
7291,"(63, 132)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
7292,"(63, 133)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
7293,"(63, 134)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,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.,Neutral
7294,"(63, 135)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system will provide the ability to register patients of all types.,Neutral
7295,"(63, 136)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
7296,"(63, 137)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
7297,"(63, 138)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
7298,"(63, 139)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
7299,"(63, 140)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
7300,"(63, 141)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
7301,"(63, 142)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
7302,"(63, 143)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
7303,"(63, 144)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
7304,"(63, 145)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,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.,Neutral
7305,"(63, 146)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
7306,"(63, 147)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
7307,"(63, 148)",The system shall provide OB/GYN progress note templates based on the IHS progress note templates.,"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.",Neutral
7308,"(64, 65)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall require only a smart card to digitally sign an order.,Conflict
7309,"(64, 66)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
7310,"(64, 67)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow users to enter time in several different formats.,Neutral
7311,"(64, 68)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7312,"(64, 69)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7313,"(64, 70)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","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.",Neutral
7314,"(64, 71)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","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.",Neutral
7315,"(64, 72)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
7316,"(64, 73)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","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.",Neutral
7317,"(64, 74)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
7318,"(64, 75)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall have a option to release unsigned orders to services,Neutral
7319,"(64, 76)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","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.",Neutral
7320,"(64, 77)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
7321,"(64, 78)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
7322,"(64, 79)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","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.",Neutral
7323,"(64, 80)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
7324,"(64, 81)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
7325,"(64, 82)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",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.,Neutral
7326,"(64, 83)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",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.,Neutral
7327,"(64, 84)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",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.,Neutral
7328,"(64, 85)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
7329,"(64, 86)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
7330,"(64, 87)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
7331,"(64, 88)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
7332,"(64, 89)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall not allow mandatory notifications to be disabled.,Neutral
7333,"(64, 90)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow users to disable unwanted notifications as desired.,Neutral
7334,"(64, 91)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
7335,"(64, 92)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",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.,Neutral
7336,"(64, 93)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
7337,"(64, 94)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall use any protocol for transferring messages among packages.,Neutral
7338,"(64, 95)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
7339,"(64, 96)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
7340,"(64, 97)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
7341,"(64, 98)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7342,"(64, 99)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7343,"(64, 100)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7344,"(64, 101)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7345,"(64, 102)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7346,"(64, 103)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7347,"(64, 104)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow a user to foward notification to someone else at the site.,Neutral
7348,"(64, 105)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7349,"(64, 106)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","The system shall define, populate, and retrieve information about user classes.",Neutral
7350,"(64, 107)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7351,"(64, 108)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7352,"(64, 109)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7353,"(64, 110)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow concurrent membership in more than one User Class.,Neutral
7354,"(64, 111)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow membership in only one User Class.,Neutral
7355,"(64, 112)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7356,"(64, 113)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","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.",Neutral
7357,"(64, 114)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall improve accessibility of online clinical information and results.,Neutral
7358,"(64, 115)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","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.",Neutral
7359,"(64, 116)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7360,"(64, 117)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7361,"(64, 118)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7362,"(64, 119)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall make the traditional order entry processes more practical.,Neutral
7363,"(64, 120)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
7364,"(64, 121)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
7365,"(64, 122)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
7366,"(64, 123)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
7367,"(64, 124)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","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.",Neutral
7368,"(64, 125)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
7369,"(64, 126)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
7370,"(64, 127)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","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.",Neutral
7371,"(64, 128)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
7372,"(64, 129)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","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.",Neutral
7373,"(64, 130)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
7374,"(64, 131)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall delete history of received immunizations.,Neutral
7375,"(64, 132)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
7376,"(64, 133)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
7377,"(64, 134)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",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.,Neutral
7378,"(64, 135)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system will provide the ability to register patients of all types.,Neutral
7379,"(64, 136)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
7380,"(64, 137)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
7381,"(64, 138)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
7382,"(64, 139)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
7383,"(64, 140)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
7384,"(64, 141)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
7385,"(64, 142)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
7386,"(64, 143)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
7387,"(64, 144)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
7388,"(64, 145)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",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.,Neutral
7389,"(64, 146)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
7390,"(64, 147)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
7391,"(64, 148)","The system shall require a smart card reader, smart card, and a PIN to digitally sign an order.","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.",Neutral
7392,"(65, 66)",The system shall require only a smart card to digitally sign an order.,The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Neutral
7393,"(65, 67)",The system shall require only a smart card to digitally sign an order.,The system shall allow users to enter time in several different formats.,Neutral
7394,"(65, 68)",The system shall require only a smart card to digitally sign an order.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7395,"(65, 69)",The system shall require only a smart card to digitally sign an order.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7396,"(65, 70)",The system shall require only a smart card to digitally sign an order.,"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.",Neutral
7397,"(65, 71)",The system shall require only a smart card to digitally sign an order.,"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.",Neutral
7398,"(65, 72)",The system shall require only a smart card to digitally sign an order.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
7399,"(65, 73)",The system shall require only a smart card to digitally sign an order.,"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.",Neutral
7400,"(65, 74)",The system shall require only a smart card to digitally sign an order.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
7401,"(65, 75)",The system shall require only a smart card to digitally sign an order.,The system shall have a option to release unsigned orders to services,Neutral
7402,"(65, 76)",The system shall require only a smart card to digitally sign an order.,"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.",Neutral
7403,"(65, 77)",The system shall require only a smart card to digitally sign an order.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
7404,"(65, 78)",The system shall require only a smart card to digitally sign an order.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
7405,"(65, 79)",The system shall require only a smart card to digitally sign an order.,"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.",Neutral
7406,"(65, 80)",The system shall require only a smart card to digitally sign an order.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
7407,"(65, 81)",The system shall require only a smart card to digitally sign an order.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
7408,"(65, 82)",The system shall require only a smart card to digitally sign an order.,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.,Neutral
7409,"(65, 83)",The system shall require only a smart card to digitally sign an order.,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.,Neutral
7410,"(65, 84)",The system shall require only a smart card to digitally sign an order.,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.,Neutral
7411,"(65, 85)",The system shall require only a smart card to digitally sign an order.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
7412,"(65, 86)",The system shall require only a smart card to digitally sign an order.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
7413,"(65, 87)",The system shall require only a smart card to digitally sign an order.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
7414,"(65, 88)",The system shall require only a smart card to digitally sign an order.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
7415,"(65, 89)",The system shall require only a smart card to digitally sign an order.,The system shall not allow mandatory notifications to be disabled.,Neutral
7416,"(65, 90)",The system shall require only a smart card to digitally sign an order.,The system shall allow users to disable unwanted notifications as desired.,Neutral
7417,"(65, 91)",The system shall require only a smart card to digitally sign an order.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
7418,"(65, 92)",The system shall require only a smart card to digitally sign an order.,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.,Neutral
7419,"(65, 93)",The system shall require only a smart card to digitally sign an order.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
7420,"(65, 94)",The system shall require only a smart card to digitally sign an order.,The system shall use any protocol for transferring messages among packages.,Neutral
7421,"(65, 95)",The system shall require only a smart card to digitally sign an order.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
7422,"(65, 96)",The system shall require only a smart card to digitally sign an order.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
7423,"(65, 97)",The system shall require only a smart card to digitally sign an order.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
7424,"(65, 98)",The system shall require only a smart card to digitally sign an order.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7425,"(65, 99)",The system shall require only a smart card to digitally sign an order.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7426,"(65, 100)",The system shall require only a smart card to digitally sign an order.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7427,"(65, 101)",The system shall require only a smart card to digitally sign an order.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7428,"(65, 102)",The system shall require only a smart card to digitally sign an order.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7429,"(65, 103)",The system shall require only a smart card to digitally sign an order.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7430,"(65, 104)",The system shall require only a smart card to digitally sign an order.,The system shall allow a user to foward notification to someone else at the site.,Neutral
7431,"(65, 105)",The system shall require only a smart card to digitally sign an order.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7432,"(65, 106)",The system shall require only a smart card to digitally sign an order.,"The system shall define, populate, and retrieve information about user classes.",Neutral
7433,"(65, 107)",The system shall require only a smart card to digitally sign an order.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7434,"(65, 108)",The system shall require only a smart card to digitally sign an order.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7435,"(65, 109)",The system shall require only a smart card to digitally sign an order.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7436,"(65, 110)",The system shall require only a smart card to digitally sign an order.,The system shall allow concurrent membership in more than one User Class.,Neutral
7437,"(65, 111)",The system shall require only a smart card to digitally sign an order.,The system shall allow membership in only one User Class.,Neutral
7438,"(65, 112)",The system shall require only a smart card to digitally sign an order.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7439,"(65, 113)",The system shall require only a smart card to digitally sign an order.,"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.",Neutral
7440,"(65, 114)",The system shall require only a smart card to digitally sign an order.,The system shall improve accessibility of online clinical information and results.,Neutral
7441,"(65, 115)",The system shall require only a smart card to digitally sign an order.,"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.",Neutral
7442,"(65, 116)",The system shall require only a smart card to digitally sign an order.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7443,"(65, 117)",The system shall require only a smart card to digitally sign an order.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7444,"(65, 118)",The system shall require only a smart card to digitally sign an order.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7445,"(65, 119)",The system shall require only a smart card to digitally sign an order.,The system shall make the traditional order entry processes more practical.,Neutral
7446,"(65, 120)",The system shall require only a smart card to digitally sign an order.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
7447,"(65, 121)",The system shall require only a smart card to digitally sign an order.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
7448,"(65, 122)",The system shall require only a smart card to digitally sign an order.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
7449,"(65, 123)",The system shall require only a smart card to digitally sign an order.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
7450,"(65, 124)",The system shall require only a smart card to digitally sign an order.,"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.",Neutral
7451,"(65, 125)",The system shall require only a smart card to digitally sign an order.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
7452,"(65, 126)",The system shall require only a smart card to digitally sign an order.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
7453,"(65, 127)",The system shall require only a smart card to digitally sign an order.,"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.",Neutral
7454,"(65, 128)",The system shall require only a smart card to digitally sign an order.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
7455,"(65, 129)",The system shall require only a smart card to digitally sign an order.,"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.",Neutral
7456,"(65, 130)",The system shall require only a smart card to digitally sign an order.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
7457,"(65, 131)",The system shall require only a smart card to digitally sign an order.,The system shall delete history of received immunizations.,Neutral
7458,"(65, 132)",The system shall require only a smart card to digitally sign an order.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
7459,"(65, 133)",The system shall require only a smart card to digitally sign an order.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
7460,"(65, 134)",The system shall require only a smart card to digitally sign an order.,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.,Neutral
7461,"(65, 135)",The system shall require only a smart card to digitally sign an order.,The system will provide the ability to register patients of all types.,Neutral
7462,"(65, 136)",The system shall require only a smart card to digitally sign an order.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
7463,"(65, 137)",The system shall require only a smart card to digitally sign an order.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
7464,"(65, 138)",The system shall require only a smart card to digitally sign an order.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
7465,"(65, 139)",The system shall require only a smart card to digitally sign an order.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
7466,"(65, 140)",The system shall require only a smart card to digitally sign an order.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
7467,"(65, 141)",The system shall require only a smart card to digitally sign an order.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
7468,"(65, 142)",The system shall require only a smart card to digitally sign an order.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
7469,"(65, 143)",The system shall require only a smart card to digitally sign an order.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
7470,"(65, 144)",The system shall require only a smart card to digitally sign an order.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
7471,"(65, 145)",The system shall require only a smart card to digitally sign an order.,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.,Neutral
7472,"(65, 146)",The system shall require only a smart card to digitally sign an order.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
7473,"(65, 147)",The system shall require only a smart card to digitally sign an order.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
7474,"(65, 148)",The system shall require only a smart card to digitally sign an order.,"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.",Neutral
7475,"(66, 67)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow users to enter time in several different formats.,Neutral
7476,"(66, 68)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7477,"(66, 69)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7478,"(66, 70)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"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.",Neutral
7479,"(66, 71)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"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.",Neutral
7480,"(66, 72)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
7481,"(66, 73)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"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.",Neutral
7482,"(66, 74)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
7483,"(66, 75)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall have a option to release unsigned orders to services,Neutral
7484,"(66, 76)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"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.",Neutral
7485,"(66, 77)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
7486,"(66, 78)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
7487,"(66, 79)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"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.",Neutral
7488,"(66, 80)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
7489,"(66, 81)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
7490,"(66, 82)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,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.,Neutral
7491,"(66, 83)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,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.,Neutral
7492,"(66, 84)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,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.,Neutral
7493,"(66, 85)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
7494,"(66, 86)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
7495,"(66, 87)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
7496,"(66, 88)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
7497,"(66, 89)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall not allow mandatory notifications to be disabled.,Neutral
7498,"(66, 90)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow users to disable unwanted notifications as desired.,Neutral
7499,"(66, 91)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
7500,"(66, 92)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,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.,Neutral
7501,"(66, 93)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
7502,"(66, 94)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall use any protocol for transferring messages among packages.,Neutral
7503,"(66, 95)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
7504,"(66, 96)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
7505,"(66, 97)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
7506,"(66, 98)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7507,"(66, 99)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7508,"(66, 100)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7509,"(66, 101)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7510,"(66, 102)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7511,"(66, 103)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7512,"(66, 104)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow a user to foward notification to someone else at the site.,Neutral
7513,"(66, 105)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7514,"(66, 106)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"The system shall define, populate, and retrieve information about user classes.",Neutral
7515,"(66, 107)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7516,"(66, 108)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7517,"(66, 109)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7518,"(66, 110)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow concurrent membership in more than one User Class.,Neutral
7519,"(66, 111)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow membership in only one User Class.,Neutral
7520,"(66, 112)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7521,"(66, 113)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"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.",Neutral
7522,"(66, 114)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall improve accessibility of online clinical information and results.,Neutral
7523,"(66, 115)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"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.",Neutral
7524,"(66, 116)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7525,"(66, 117)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7526,"(66, 118)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7527,"(66, 119)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall make the traditional order entry processes more practical.,Neutral
7528,"(66, 120)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
7529,"(66, 121)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
7530,"(66, 122)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
7531,"(66, 123)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
7532,"(66, 124)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"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.",Neutral
7533,"(66, 125)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
7534,"(66, 126)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
7535,"(66, 127)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"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.",Neutral
7536,"(66, 128)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
7537,"(66, 129)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"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.",Neutral
7538,"(66, 130)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
7539,"(66, 131)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall delete history of received immunizations.,Neutral
7540,"(66, 132)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
7541,"(66, 133)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
7542,"(66, 134)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,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.,Neutral
7543,"(66, 135)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system will provide the ability to register patients of all types.,Neutral
7544,"(66, 136)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
7545,"(66, 137)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
7546,"(66, 138)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
7547,"(66, 139)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
7548,"(66, 140)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
7549,"(66, 141)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
7550,"(66, 142)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
7551,"(66, 143)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
7552,"(66, 144)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
7553,"(66, 145)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,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.,Neutral
7554,"(66, 146)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
7555,"(66, 147)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
7556,"(66, 148)",The document-handling system (TIU) shall have boilerplate and cut and paste capabilities.,"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.",Neutral
7557,"(67, 68)",The system shall allow users to enter time in several different formats.,The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7558,"(67, 69)",The system shall allow users to enter time in several different formats.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Neutral
7559,"(67, 70)",The system shall allow users to enter time in several different formats.,"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.",Conflict
7560,"(67, 71)",The system shall allow users to enter time in several different formats.,"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.",Neutral
7561,"(67, 72)",The system shall allow users to enter time in several different formats.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
7562,"(67, 73)",The system shall allow users to enter time in several different formats.,"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.",Neutral
7563,"(67, 74)",The system shall allow users to enter time in several different formats.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
7564,"(67, 75)",The system shall allow users to enter time in several different formats.,The system shall have a option to release unsigned orders to services,Neutral
7565,"(67, 76)",The system shall allow users to enter time in several different formats.,"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.",Neutral
7566,"(67, 77)",The system shall allow users to enter time in several different formats.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
7567,"(67, 78)",The system shall allow users to enter time in several different formats.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
7568,"(67, 79)",The system shall allow users to enter time in several different formats.,"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.",Neutral
7569,"(67, 80)",The system shall allow users to enter time in several different formats.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
7570,"(67, 81)",The system shall allow users to enter time in several different formats.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
7571,"(67, 82)",The system shall allow users to enter time in several different formats.,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.,Neutral
7572,"(67, 83)",The system shall allow users to enter time in several different formats.,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.,Neutral
7573,"(67, 84)",The system shall allow users to enter time in several different formats.,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.,Neutral
7574,"(67, 85)",The system shall allow users to enter time in several different formats.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
7575,"(67, 86)",The system shall allow users to enter time in several different formats.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
7576,"(67, 87)",The system shall allow users to enter time in several different formats.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
7577,"(67, 88)",The system shall allow users to enter time in several different formats.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
7578,"(67, 89)",The system shall allow users to enter time in several different formats.,The system shall not allow mandatory notifications to be disabled.,Neutral
7579,"(67, 90)",The system shall allow users to enter time in several different formats.,The system shall allow users to disable unwanted notifications as desired.,Neutral
7580,"(67, 91)",The system shall allow users to enter time in several different formats.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
7581,"(67, 92)",The system shall allow users to enter time in several different formats.,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.,Neutral
7582,"(67, 93)",The system shall allow users to enter time in several different formats.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
7583,"(67, 94)",The system shall allow users to enter time in several different formats.,The system shall use any protocol for transferring messages among packages.,Neutral
7584,"(67, 95)",The system shall allow users to enter time in several different formats.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
7585,"(67, 96)",The system shall allow users to enter time in several different formats.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
7586,"(67, 97)",The system shall allow users to enter time in several different formats.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
7587,"(67, 98)",The system shall allow users to enter time in several different formats.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7588,"(67, 99)",The system shall allow users to enter time in several different formats.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7589,"(67, 100)",The system shall allow users to enter time in several different formats.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7590,"(67, 101)",The system shall allow users to enter time in several different formats.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7591,"(67, 102)",The system shall allow users to enter time in several different formats.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7592,"(67, 103)",The system shall allow users to enter time in several different formats.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7593,"(67, 104)",The system shall allow users to enter time in several different formats.,The system shall allow a user to foward notification to someone else at the site.,Neutral
7594,"(67, 105)",The system shall allow users to enter time in several different formats.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7595,"(67, 106)",The system shall allow users to enter time in several different formats.,"The system shall define, populate, and retrieve information about user classes.",Neutral
7596,"(67, 107)",The system shall allow users to enter time in several different formats.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7597,"(67, 108)",The system shall allow users to enter time in several different formats.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7598,"(67, 109)",The system shall allow users to enter time in several different formats.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7599,"(67, 110)",The system shall allow users to enter time in several different formats.,The system shall allow concurrent membership in more than one User Class.,Neutral
7600,"(67, 111)",The system shall allow users to enter time in several different formats.,The system shall allow membership in only one User Class.,Neutral
7601,"(67, 112)",The system shall allow users to enter time in several different formats.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7602,"(67, 113)",The system shall allow users to enter time in several different formats.,"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.",Neutral
7603,"(67, 114)",The system shall allow users to enter time in several different formats.,The system shall improve accessibility of online clinical information and results.,Neutral
7604,"(67, 115)",The system shall allow users to enter time in several different formats.,"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.",Neutral
7605,"(67, 116)",The system shall allow users to enter time in several different formats.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7606,"(67, 117)",The system shall allow users to enter time in several different formats.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7607,"(67, 118)",The system shall allow users to enter time in several different formats.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7608,"(67, 119)",The system shall allow users to enter time in several different formats.,The system shall make the traditional order entry processes more practical.,Neutral
7609,"(67, 120)",The system shall allow users to enter time in several different formats.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
7610,"(67, 121)",The system shall allow users to enter time in several different formats.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
7611,"(67, 122)",The system shall allow users to enter time in several different formats.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
7612,"(67, 123)",The system shall allow users to enter time in several different formats.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
7613,"(67, 124)",The system shall allow users to enter time in several different formats.,"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.",Neutral
7614,"(67, 125)",The system shall allow users to enter time in several different formats.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
7615,"(67, 126)",The system shall allow users to enter time in several different formats.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
7616,"(67, 127)",The system shall allow users to enter time in several different formats.,"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.",Neutral
7617,"(67, 128)",The system shall allow users to enter time in several different formats.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
7618,"(67, 129)",The system shall allow users to enter time in several different formats.,"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.",Neutral
7619,"(67, 130)",The system shall allow users to enter time in several different formats.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
7620,"(67, 131)",The system shall allow users to enter time in several different formats.,The system shall delete history of received immunizations.,Neutral
7621,"(67, 132)",The system shall allow users to enter time in several different formats.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
7622,"(67, 133)",The system shall allow users to enter time in several different formats.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
7623,"(67, 134)",The system shall allow users to enter time in several different formats.,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.,Neutral
7624,"(67, 135)",The system shall allow users to enter time in several different formats.,The system will provide the ability to register patients of all types.,Neutral
7625,"(67, 136)",The system shall allow users to enter time in several different formats.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
7626,"(67, 137)",The system shall allow users to enter time in several different formats.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
7627,"(67, 138)",The system shall allow users to enter time in several different formats.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
7628,"(67, 139)",The system shall allow users to enter time in several different formats.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
7629,"(67, 140)",The system shall allow users to enter time in several different formats.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
7630,"(67, 141)",The system shall allow users to enter time in several different formats.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
7631,"(67, 142)",The system shall allow users to enter time in several different formats.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
7632,"(67, 143)",The system shall allow users to enter time in several different formats.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
7633,"(67, 144)",The system shall allow users to enter time in several different formats.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
7634,"(67, 145)",The system shall allow users to enter time in several different formats.,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.,Neutral
7635,"(67, 146)",The system shall allow users to enter time in several different formats.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
7636,"(67, 147)",The system shall allow users to enter time in several different formats.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
7637,"(67, 148)",The system shall allow users to enter time in several different formats.,"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.",Neutral
7638,"(68, 69)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Conflict
7639,"(68, 70)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7640,"(68, 71)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7641,"(68, 72)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
7642,"(68, 73)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7643,"(68, 74)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
7644,"(68, 75)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall have a option to release unsigned orders to services,Neutral
7645,"(68, 76)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7646,"(68, 77)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
7647,"(68, 78)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
7648,"(68, 79)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7649,"(68, 80)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
7650,"(68, 81)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
7651,"(68, 82)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,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.,Neutral
7652,"(68, 83)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,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.,Neutral
7653,"(68, 84)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,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.,Neutral
7654,"(68, 85)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
7655,"(68, 86)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
7656,"(68, 87)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
7657,"(68, 88)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
7658,"(68, 89)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall not allow mandatory notifications to be disabled.,Neutral
7659,"(68, 90)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow users to disable unwanted notifications as desired.,Neutral
7660,"(68, 91)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
7661,"(68, 92)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,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.,Neutral
7662,"(68, 93)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
7663,"(68, 94)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall use any protocol for transferring messages among packages.,Neutral
7664,"(68, 95)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
7665,"(68, 96)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
7666,"(68, 97)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
7667,"(68, 98)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7668,"(68, 99)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7669,"(68, 100)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7670,"(68, 101)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7671,"(68, 102)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7672,"(68, 103)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7673,"(68, 104)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow a user to foward notification to someone else at the site.,Neutral
7674,"(68, 105)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7675,"(68, 106)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall define, populate, and retrieve information about user classes.",Neutral
7676,"(68, 107)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7677,"(68, 108)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7678,"(68, 109)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7679,"(68, 110)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow concurrent membership in more than one User Class.,Neutral
7680,"(68, 111)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow membership in only one User Class.,Neutral
7681,"(68, 112)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7682,"(68, 113)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7683,"(68, 114)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall improve accessibility of online clinical information and results.,Neutral
7684,"(68, 115)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7685,"(68, 116)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7686,"(68, 117)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7687,"(68, 118)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7688,"(68, 119)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall make the traditional order entry processes more practical.,Neutral
7689,"(68, 120)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
7690,"(68, 121)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
7691,"(68, 122)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
7692,"(68, 123)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
7693,"(68, 124)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7694,"(68, 125)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
7695,"(68, 126)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
7696,"(68, 127)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7697,"(68, 128)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
7698,"(68, 129)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7699,"(68, 130)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
7700,"(68, 131)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall delete history of received immunizations.,Neutral
7701,"(68, 132)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
7702,"(68, 133)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
7703,"(68, 134)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,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.,Neutral
7704,"(68, 135)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system will provide the ability to register patients of all types.,Neutral
7705,"(68, 136)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
7706,"(68, 137)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
7707,"(68, 138)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
7708,"(68, 139)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
7709,"(68, 140)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
7710,"(68, 141)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
7711,"(68, 142)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
7712,"(68, 143)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
7713,"(68, 144)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
7714,"(68, 145)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,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.,Neutral
7715,"(68, 146)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
7716,"(68, 147)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
7717,"(68, 148)",The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7718,"(69, 70)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7719,"(69, 71)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7720,"(69, 72)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
7721,"(69, 73)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7722,"(69, 74)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
7723,"(69, 75)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall have a option to release unsigned orders to services,Neutral
7724,"(69, 76)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7725,"(69, 77)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
7726,"(69, 78)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
7727,"(69, 79)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7728,"(69, 80)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
7729,"(69, 81)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
7730,"(69, 82)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,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.,Neutral
7731,"(69, 83)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,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.,Neutral
7732,"(69, 84)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,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.,Neutral
7733,"(69, 85)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
7734,"(69, 86)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
7735,"(69, 87)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
7736,"(69, 88)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
7737,"(69, 89)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall not allow mandatory notifications to be disabled.,Neutral
7738,"(69, 90)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow users to disable unwanted notifications as desired.,Neutral
7739,"(69, 91)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
7740,"(69, 92)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,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.,Neutral
7741,"(69, 93)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
7742,"(69, 94)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall use any protocol for transferring messages among packages.,Neutral
7743,"(69, 95)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
7744,"(69, 96)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
7745,"(69, 97)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
7746,"(69, 98)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7747,"(69, 99)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7748,"(69, 100)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7749,"(69, 101)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7750,"(69, 102)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7751,"(69, 103)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7752,"(69, 104)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow a user to foward notification to someone else at the site.,Neutral
7753,"(69, 105)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7754,"(69, 106)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall define, populate, and retrieve information about user classes.",Neutral
7755,"(69, 107)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7756,"(69, 108)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7757,"(69, 109)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7758,"(69, 110)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow concurrent membership in more than one User Class.,Neutral
7759,"(69, 111)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow membership in only one User Class.,Neutral
7760,"(69, 112)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7761,"(69, 113)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7762,"(69, 114)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall improve accessibility of online clinical information and results.,Neutral
7763,"(69, 115)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7764,"(69, 116)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7765,"(69, 117)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7766,"(69, 118)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7767,"(69, 119)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall make the traditional order entry processes more practical.,Neutral
7768,"(69, 120)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
7769,"(69, 121)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
7770,"(69, 122)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
7771,"(69, 123)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
7772,"(69, 124)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7773,"(69, 125)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
7774,"(69, 126)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
7775,"(69, 127)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7776,"(69, 128)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
7777,"(69, 129)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7778,"(69, 130)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
7779,"(69, 131)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall delete history of received immunizations.,Neutral
7780,"(69, 132)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
7781,"(69, 133)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
7782,"(69, 134)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,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.,Neutral
7783,"(69, 135)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system will provide the ability to register patients of all types.,Neutral
7784,"(69, 136)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
7785,"(69, 137)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
7786,"(69, 138)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
7787,"(69, 139)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
7788,"(69, 140)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
7789,"(69, 141)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
7790,"(69, 142)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
7791,"(69, 143)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
7792,"(69, 144)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
7793,"(69, 145)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,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.,Neutral
7794,"(69, 146)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
7795,"(69, 147)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
7796,"(69, 148)",The system shall only require a user to review and sign changed if a user has just entered orders or documents that are unsigned.,"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.",Neutral
7797,"(70, 71)","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.","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.",Neutral
7798,"(70, 72)","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.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
7799,"(70, 73)","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.","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.",Neutral
7800,"(70, 74)","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.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
7801,"(70, 75)","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.",The system shall have a option to release unsigned orders to services,Neutral
7802,"(70, 76)","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.","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.",Neutral
7803,"(70, 77)","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.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
7804,"(70, 78)","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.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
7805,"(70, 79)","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.","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.",Neutral
7806,"(70, 80)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
7807,"(70, 81)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
7808,"(70, 82)","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.",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.,Neutral
7809,"(70, 83)","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.",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.,Neutral
7810,"(70, 84)","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.",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.,Neutral
7811,"(70, 85)","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.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
7812,"(70, 86)","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.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
7813,"(70, 87)","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.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
7814,"(70, 88)","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.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
7815,"(70, 89)","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.",The system shall not allow mandatory notifications to be disabled.,Neutral
7816,"(70, 90)","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.",The system shall allow users to disable unwanted notifications as desired.,Neutral
7817,"(70, 91)","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.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
7818,"(70, 92)","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.",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.,Neutral
7819,"(70, 93)","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.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
7820,"(70, 94)","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.",The system shall use any protocol for transferring messages among packages.,Neutral
7821,"(70, 95)","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.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
7822,"(70, 96)","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.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
7823,"(70, 97)","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.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
7824,"(70, 98)","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.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7825,"(70, 99)","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.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7826,"(70, 100)","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.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7827,"(70, 101)","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.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7828,"(70, 102)","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.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7829,"(70, 103)","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.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7830,"(70, 104)","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.",The system shall allow a user to foward notification to someone else at the site.,Neutral
7831,"(70, 105)","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.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7832,"(70, 106)","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.","The system shall define, populate, and retrieve information about user classes.",Neutral
7833,"(70, 107)","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.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7834,"(70, 108)","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.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7835,"(70, 109)","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.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7836,"(70, 110)","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.",The system shall allow concurrent membership in more than one User Class.,Neutral
7837,"(70, 111)","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.",The system shall allow membership in only one User Class.,Neutral
7838,"(70, 112)","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.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7839,"(70, 113)","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.","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.",Neutral
7840,"(70, 114)","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.",The system shall improve accessibility of online clinical information and results.,Neutral
7841,"(70, 115)","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.","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.",Neutral
7842,"(70, 116)","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.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7843,"(70, 117)","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.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7844,"(70, 118)","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.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7845,"(70, 119)","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.",The system shall make the traditional order entry processes more practical.,Neutral
7846,"(70, 120)","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.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
7847,"(70, 121)","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.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
7848,"(70, 122)","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.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
7849,"(70, 123)","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.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
7850,"(70, 124)","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.","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.",Neutral
7851,"(70, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
7852,"(70, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
7853,"(70, 127)","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.","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.",Neutral
7854,"(70, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
7855,"(70, 129)","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.","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.",Neutral
7856,"(70, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
7857,"(70, 131)","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.",The system shall delete history of received immunizations.,Neutral
7858,"(70, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
7859,"(70, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
7860,"(70, 134)","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.",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.,Neutral
7861,"(70, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
7862,"(70, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
7863,"(70, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
7864,"(70, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
7865,"(70, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
7866,"(70, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
7867,"(70, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
7868,"(70, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
7869,"(70, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
7870,"(70, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
7871,"(70, 145)","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.",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.,Neutral
7872,"(70, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
7873,"(70, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
7874,"(70, 148)","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.","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.",Neutral
7875,"(71, 72)","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.",The system shall sort characters based on their numeric values in the character set that VistA uses.,Neutral
7876,"(71, 73)","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.","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.",Neutral
7877,"(71, 74)","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.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
7878,"(71, 75)","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.",The system shall have a option to release unsigned orders to services,Neutral
7879,"(71, 76)","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.","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.",Neutral
7880,"(71, 77)","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.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
7881,"(71, 78)","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.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
7882,"(71, 79)","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.","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.",Neutral
7883,"(71, 80)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
7884,"(71, 81)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
7885,"(71, 82)","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.",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.,Neutral
7886,"(71, 83)","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.",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.,Neutral
7887,"(71, 84)","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.",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.,Neutral
7888,"(71, 85)","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.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
7889,"(71, 86)","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.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
7890,"(71, 87)","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.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
7891,"(71, 88)","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.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
7892,"(71, 89)","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.",The system shall not allow mandatory notifications to be disabled.,Neutral
7893,"(71, 90)","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.",The system shall allow users to disable unwanted notifications as desired.,Neutral
7894,"(71, 91)","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.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
7895,"(71, 92)","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.",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.,Neutral
7896,"(71, 93)","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.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
7897,"(71, 94)","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.",The system shall use any protocol for transferring messages among packages.,Neutral
7898,"(71, 95)","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.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
7899,"(71, 96)","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.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
7900,"(71, 97)","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.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
7901,"(71, 98)","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.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7902,"(71, 99)","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.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7903,"(71, 100)","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.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7904,"(71, 101)","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.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7905,"(71, 102)","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.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7906,"(71, 103)","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.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7907,"(71, 104)","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.",The system shall allow a user to foward notification to someone else at the site.,Neutral
7908,"(71, 105)","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.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7909,"(71, 106)","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.","The system shall define, populate, and retrieve information about user classes.",Neutral
7910,"(71, 107)","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.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7911,"(71, 108)","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.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7912,"(71, 109)","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.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7913,"(71, 110)","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.",The system shall allow concurrent membership in more than one User Class.,Neutral
7914,"(71, 111)","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.",The system shall allow membership in only one User Class.,Neutral
7915,"(71, 112)","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.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7916,"(71, 113)","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.","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.",Neutral
7917,"(71, 114)","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.",The system shall improve accessibility of online clinical information and results.,Neutral
7918,"(71, 115)","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.","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.",Neutral
7919,"(71, 116)","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.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7920,"(71, 117)","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.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7921,"(71, 118)","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.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7922,"(71, 119)","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.",The system shall make the traditional order entry processes more practical.,Neutral
7923,"(71, 120)","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.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
7924,"(71, 121)","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.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
7925,"(71, 122)","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.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
7926,"(71, 123)","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.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
7927,"(71, 124)","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.","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.",Neutral
7928,"(71, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
7929,"(71, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
7930,"(71, 127)","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.","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.",Neutral
7931,"(71, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
7932,"(71, 129)","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.","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.",Neutral
7933,"(71, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
7934,"(71, 131)","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.",The system shall delete history of received immunizations.,Neutral
7935,"(71, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
7936,"(71, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
7937,"(71, 134)","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.",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.,Neutral
7938,"(71, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
7939,"(71, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
7940,"(71, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
7941,"(71, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
7942,"(71, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
7943,"(71, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
7944,"(71, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
7945,"(71, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
7946,"(71, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
7947,"(71, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
7948,"(71, 145)","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.",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.,Neutral
7949,"(71, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
7950,"(71, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
7951,"(71, 148)","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.","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.",Neutral
7952,"(72, 73)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"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.",Neutral
7953,"(72, 74)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
7954,"(72, 75)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall have a option to release unsigned orders to services,Neutral
7955,"(72, 76)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"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.",Neutral
7956,"(72, 77)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
7957,"(72, 78)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
7958,"(72, 79)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"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.",Neutral
7959,"(72, 80)",The system shall sort characters based on their numeric values in the character set that VistA uses.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
7960,"(72, 81)",The system shall sort characters based on their numeric values in the character set that VistA uses.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
7961,"(72, 82)",The system shall sort characters based on their numeric values in the character set that VistA uses.,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.,Neutral
7962,"(72, 83)",The system shall sort characters based on their numeric values in the character set that VistA uses.,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.,Neutral
7963,"(72, 84)",The system shall sort characters based on their numeric values in the character set that VistA uses.,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.,Neutral
7964,"(72, 85)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
7965,"(72, 86)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
7966,"(72, 87)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
7967,"(72, 88)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
7968,"(72, 89)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall not allow mandatory notifications to be disabled.,Neutral
7969,"(72, 90)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall allow users to disable unwanted notifications as desired.,Neutral
7970,"(72, 91)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
7971,"(72, 92)",The system shall sort characters based on their numeric values in the character set that VistA uses.,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.,Neutral
7972,"(72, 93)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
7973,"(72, 94)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall use any protocol for transferring messages among packages.,Neutral
7974,"(72, 95)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
7975,"(72, 96)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
7976,"(72, 97)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
7977,"(72, 98)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
7978,"(72, 99)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
7979,"(72, 100)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
7980,"(72, 101)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
7981,"(72, 102)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
7982,"(72, 103)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
7983,"(72, 104)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall allow a user to foward notification to someone else at the site.,Neutral
7984,"(72, 105)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
7985,"(72, 106)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"The system shall define, populate, and retrieve information about user classes.",Neutral
7986,"(72, 107)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7987,"(72, 108)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
7988,"(72, 109)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
7989,"(72, 110)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall allow concurrent membership in more than one User Class.,Neutral
7990,"(72, 111)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall allow membership in only one User Class.,Neutral
7991,"(72, 112)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
7992,"(72, 113)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"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.",Neutral
7993,"(72, 114)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall improve accessibility of online clinical information and results.,Neutral
7994,"(72, 115)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"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.",Neutral
7995,"(72, 116)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
7996,"(72, 117)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
7997,"(72, 118)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
7998,"(72, 119)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall make the traditional order entry processes more practical.,Neutral
7999,"(72, 120)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8000,"(72, 121)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8001,"(72, 122)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8002,"(72, 123)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8003,"(72, 124)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"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.",Neutral
8004,"(72, 125)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8005,"(72, 126)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8006,"(72, 127)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"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.",Neutral
8007,"(72, 128)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8008,"(72, 129)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"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.",Neutral
8009,"(72, 130)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8010,"(72, 131)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall delete history of received immunizations.,Neutral
8011,"(72, 132)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
8012,"(72, 133)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8013,"(72, 134)",The system shall sort characters based on their numeric values in the character set that VistA uses.,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.,Neutral
8014,"(72, 135)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system will provide the ability to register patients of all types.,Neutral
8015,"(72, 136)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8016,"(72, 137)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
8017,"(72, 138)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8018,"(72, 139)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8019,"(72, 140)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8020,"(72, 141)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8021,"(72, 142)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8022,"(72, 143)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8023,"(72, 144)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8024,"(72, 145)",The system shall sort characters based on their numeric values in the character set that VistA uses.,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.,Neutral
8025,"(72, 146)",The system shall sort characters based on their numeric values in the character set that VistA uses.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8026,"(72, 147)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8027,"(72, 148)",The system shall sort characters based on their numeric values in the character set that VistA uses.,"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.",Neutral
8028,"(73, 74)","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.",The system shall not release orders to services or activated until they are signed if they require a signature.,Neutral
8029,"(73, 75)","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.",The system shall have a option to release unsigned orders to services,Neutral
8030,"(73, 76)","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.","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.",Neutral
8031,"(73, 77)","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.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
8032,"(73, 78)","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.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
8033,"(73, 79)","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.","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.",Neutral
8034,"(73, 80)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
8035,"(73, 81)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
8036,"(73, 82)","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.",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.,Neutral
8037,"(73, 83)","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.",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.,Neutral
8038,"(73, 84)","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.",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.,Neutral
8039,"(73, 85)","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.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
8040,"(73, 86)","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.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
8041,"(73, 87)","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.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
8042,"(73, 88)","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.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8043,"(73, 89)","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.",The system shall not allow mandatory notifications to be disabled.,Neutral
8044,"(73, 90)","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.",The system shall allow users to disable unwanted notifications as desired.,Neutral
8045,"(73, 91)","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.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8046,"(73, 92)","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.",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.,Neutral
8047,"(73, 93)","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.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8048,"(73, 94)","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.",The system shall use any protocol for transferring messages among packages.,Neutral
8049,"(73, 95)","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.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8050,"(73, 96)","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.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8051,"(73, 97)","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.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8052,"(73, 98)","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.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8053,"(73, 99)","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.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8054,"(73, 100)","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.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8055,"(73, 101)","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.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8056,"(73, 102)","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.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8057,"(73, 103)","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.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8058,"(73, 104)","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.",The system shall allow a user to foward notification to someone else at the site.,Neutral
8059,"(73, 105)","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.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8060,"(73, 106)","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.","The system shall define, populate, and retrieve information about user classes.",Neutral
8061,"(73, 107)","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.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8062,"(73, 108)","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.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8063,"(73, 109)","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.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8064,"(73, 110)","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.",The system shall allow concurrent membership in more than one User Class.,Neutral
8065,"(73, 111)","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.",The system shall allow membership in only one User Class.,Neutral
8066,"(73, 112)","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.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8067,"(73, 113)","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.","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.",Neutral
8068,"(73, 114)","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.",The system shall improve accessibility of online clinical information and results.,Neutral
8069,"(73, 115)","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.","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.",Neutral
8070,"(73, 116)","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.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8071,"(73, 117)","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.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8072,"(73, 118)","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.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8073,"(73, 119)","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.",The system shall make the traditional order entry processes more practical.,Neutral
8074,"(73, 120)","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.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8075,"(73, 121)","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.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8076,"(73, 122)","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.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8077,"(73, 123)","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.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8078,"(73, 124)","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.","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.",Neutral
8079,"(73, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8080,"(73, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8081,"(73, 127)","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.","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.",Neutral
8082,"(73, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8083,"(73, 129)","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.","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.",Neutral
8084,"(73, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8085,"(73, 131)","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.",The system shall delete history of received immunizations.,Neutral
8086,"(73, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
8087,"(73, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8088,"(73, 134)","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.",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.,Neutral
8089,"(73, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
8090,"(73, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8091,"(73, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
8092,"(73, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8093,"(73, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8094,"(73, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8095,"(73, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8096,"(73, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8097,"(73, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8098,"(73, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8099,"(73, 145)","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.",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.,Neutral
8100,"(73, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8101,"(73, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8102,"(73, 148)","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.","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.",Neutral
8103,"(74, 75)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall have a option to release unsigned orders to services,Conflict
8104,"(74, 76)",The system shall not release orders to services or activated until they are signed if they require a signature.,"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.",Neutral
8105,"(74, 77)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
8106,"(74, 78)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
8107,"(74, 79)",The system shall not release orders to services or activated until they are signed if they require a signature.,"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.",Neutral
8108,"(74, 80)",The system shall not release orders to services or activated until they are signed if they require a signature.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
8109,"(74, 81)",The system shall not release orders to services or activated until they are signed if they require a signature.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
8110,"(74, 82)",The system shall not release orders to services or activated until they are signed if they require a signature.,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.,Neutral
8111,"(74, 83)",The system shall not release orders to services or activated until they are signed if they require a signature.,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.,Neutral
8112,"(74, 84)",The system shall not release orders to services or activated until they are signed if they require a signature.,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.,Neutral
8113,"(74, 85)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
8114,"(74, 86)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
8115,"(74, 87)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
8116,"(74, 88)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8117,"(74, 89)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall not allow mandatory notifications to be disabled.,Neutral
8118,"(74, 90)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall allow users to disable unwanted notifications as desired.,Neutral
8119,"(74, 91)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8120,"(74, 92)",The system shall not release orders to services or activated until they are signed if they require a signature.,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.,Neutral
8121,"(74, 93)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8122,"(74, 94)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall use any protocol for transferring messages among packages.,Neutral
8123,"(74, 95)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8124,"(74, 96)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8125,"(74, 97)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8126,"(74, 98)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8127,"(74, 99)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8128,"(74, 100)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8129,"(74, 101)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8130,"(74, 102)",The system shall not release orders to services or activated until they are signed if they require a signature.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8131,"(74, 103)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8132,"(74, 104)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall allow a user to foward notification to someone else at the site.,Neutral
8133,"(74, 105)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8134,"(74, 106)",The system shall not release orders to services or activated until they are signed if they require a signature.,"The system shall define, populate, and retrieve information about user classes.",Neutral
8135,"(74, 107)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8136,"(74, 108)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8137,"(74, 109)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8138,"(74, 110)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall allow concurrent membership in more than one User Class.,Neutral
8139,"(74, 111)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall allow membership in only one User Class.,Neutral
8140,"(74, 112)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8141,"(74, 113)",The system shall not release orders to services or activated until they are signed if they require a signature.,"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.",Neutral
8142,"(74, 114)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall improve accessibility of online clinical information and results.,Neutral
8143,"(74, 115)",The system shall not release orders to services or activated until they are signed if they require a signature.,"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.",Neutral
8144,"(74, 116)",The system shall not release orders to services or activated until they are signed if they require a signature.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8145,"(74, 117)",The system shall not release orders to services or activated until they are signed if they require a signature.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8146,"(74, 118)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8147,"(74, 119)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall make the traditional order entry processes more practical.,Neutral
8148,"(74, 120)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8149,"(74, 121)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8150,"(74, 122)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8151,"(74, 123)",The system shall not release orders to services or activated until they are signed if they require a signature.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8152,"(74, 124)",The system shall not release orders to services or activated until they are signed if they require a signature.,"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.",Neutral
8153,"(74, 125)",The system shall not release orders to services or activated until they are signed if they require a signature.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8154,"(74, 126)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8155,"(74, 127)",The system shall not release orders to services or activated until they are signed if they require a signature.,"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.",Neutral
8156,"(74, 128)",The system shall not release orders to services or activated until they are signed if they require a signature.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8157,"(74, 129)",The system shall not release orders to services or activated until they are signed if they require a signature.,"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.",Neutral
8158,"(74, 130)",The system shall not release orders to services or activated until they are signed if they require a signature.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8159,"(74, 131)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall delete history of received immunizations.,Neutral
8160,"(74, 132)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
8161,"(74, 133)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8162,"(74, 134)",The system shall not release orders to services or activated until they are signed if they require a signature.,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.,Neutral
8163,"(74, 135)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system will provide the ability to register patients of all types.,Neutral
8164,"(74, 136)",The system shall not release orders to services or activated until they are signed if they require a signature.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8165,"(74, 137)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
8166,"(74, 138)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8167,"(74, 139)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8168,"(74, 140)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8169,"(74, 141)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8170,"(74, 142)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8171,"(74, 143)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8172,"(74, 144)",The system shall not release orders to services or activated until they are signed if they require a signature.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8173,"(74, 145)",The system shall not release orders to services or activated until they are signed if they require a signature.,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.,Neutral
8174,"(74, 146)",The system shall not release orders to services or activated until they are signed if they require a signature.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8175,"(74, 147)",The system shall not release orders to services or activated until they are signed if they require a signature.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8176,"(74, 148)",The system shall not release orders to services or activated until they are signed if they require a signature.,"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.",Neutral
8177,"(75, 76)",The system shall have a option to release unsigned orders to services,"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.",Neutral
8178,"(75, 77)",The system shall have a option to release unsigned orders to services,The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
8179,"(75, 78)",The system shall have a option to release unsigned orders to services,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
8180,"(75, 79)",The system shall have a option to release unsigned orders to services,"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.",Neutral
8181,"(75, 80)",The system shall have a option to release unsigned orders to services,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
8182,"(75, 81)",The system shall have a option to release unsigned orders to services,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
8183,"(75, 82)",The system shall have a option to release unsigned orders to services,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.,Neutral
8184,"(75, 83)",The system shall have a option to release unsigned orders to services,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.,Neutral
8185,"(75, 84)",The system shall have a option to release unsigned orders to services,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.,Neutral
8186,"(75, 85)",The system shall have a option to release unsigned orders to services,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
8187,"(75, 86)",The system shall have a option to release unsigned orders to services,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
8188,"(75, 87)",The system shall have a option to release unsigned orders to services,The system shall display a message telling the user that the selected patient is deceased.,Neutral
8189,"(75, 88)",The system shall have a option to release unsigned orders to services,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8190,"(75, 89)",The system shall have a option to release unsigned orders to services,The system shall not allow mandatory notifications to be disabled.,Neutral
8191,"(75, 90)",The system shall have a option to release unsigned orders to services,The system shall allow users to disable unwanted notifications as desired.,Neutral
8192,"(75, 91)",The system shall have a option to release unsigned orders to services,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8193,"(75, 92)",The system shall have a option to release unsigned orders to services,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.,Neutral
8194,"(75, 93)",The system shall have a option to release unsigned orders to services,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8195,"(75, 94)",The system shall have a option to release unsigned orders to services,The system shall use any protocol for transferring messages among packages.,Neutral
8196,"(75, 95)",The system shall have a option to release unsigned orders to services,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8197,"(75, 96)",The system shall have a option to release unsigned orders to services,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8198,"(75, 97)",The system shall have a option to release unsigned orders to services,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8199,"(75, 98)",The system shall have a option to release unsigned orders to services,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8200,"(75, 99)",The system shall have a option to release unsigned orders to services,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8201,"(75, 100)",The system shall have a option to release unsigned orders to services,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8202,"(75, 101)",The system shall have a option to release unsigned orders to services,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8203,"(75, 102)",The system shall have a option to release unsigned orders to services,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8204,"(75, 103)",The system shall have a option to release unsigned orders to services,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8205,"(75, 104)",The system shall have a option to release unsigned orders to services,The system shall allow a user to foward notification to someone else at the site.,Neutral
8206,"(75, 105)",The system shall have a option to release unsigned orders to services,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8207,"(75, 106)",The system shall have a option to release unsigned orders to services,"The system shall define, populate, and retrieve information about user classes.",Neutral
8208,"(75, 107)",The system shall have a option to release unsigned orders to services,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8209,"(75, 108)",The system shall have a option to release unsigned orders to services,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8210,"(75, 109)",The system shall have a option to release unsigned orders to services,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8211,"(75, 110)",The system shall have a option to release unsigned orders to services,The system shall allow concurrent membership in more than one User Class.,Neutral
8212,"(75, 111)",The system shall have a option to release unsigned orders to services,The system shall allow membership in only one User Class.,Neutral
8213,"(75, 112)",The system shall have a option to release unsigned orders to services,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8214,"(75, 113)",The system shall have a option to release unsigned orders to services,"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.",Neutral
8215,"(75, 114)",The system shall have a option to release unsigned orders to services,The system shall improve accessibility of online clinical information and results.,Neutral
8216,"(75, 115)",The system shall have a option to release unsigned orders to services,"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.",Neutral
8217,"(75, 116)",The system shall have a option to release unsigned orders to services,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8218,"(75, 117)",The system shall have a option to release unsigned orders to services,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8219,"(75, 118)",The system shall have a option to release unsigned orders to services,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8220,"(75, 119)",The system shall have a option to release unsigned orders to services,The system shall make the traditional order entry processes more practical.,Neutral
8221,"(75, 120)",The system shall have a option to release unsigned orders to services,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8222,"(75, 121)",The system shall have a option to release unsigned orders to services,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8223,"(75, 122)",The system shall have a option to release unsigned orders to services,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8224,"(75, 123)",The system shall have a option to release unsigned orders to services,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8225,"(75, 124)",The system shall have a option to release unsigned orders to services,"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.",Neutral
8226,"(75, 125)",The system shall have a option to release unsigned orders to services,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8227,"(75, 126)",The system shall have a option to release unsigned orders to services,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8228,"(75, 127)",The system shall have a option to release unsigned orders to services,"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.",Neutral
8229,"(75, 128)",The system shall have a option to release unsigned orders to services,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8230,"(75, 129)",The system shall have a option to release unsigned orders to services,"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.",Neutral
8231,"(75, 130)",The system shall have a option to release unsigned orders to services,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8232,"(75, 131)",The system shall have a option to release unsigned orders to services,The system shall delete history of received immunizations.,Neutral
8233,"(75, 132)",The system shall have a option to release unsigned orders to services,The system shall only delete history of recieved immunizations unless user specifies,Neutral
8234,"(75, 133)",The system shall have a option to release unsigned orders to services,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8235,"(75, 134)",The system shall have a option to release unsigned orders to services,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.,Neutral
8236,"(75, 135)",The system shall have a option to release unsigned orders to services,The system will provide the ability to register patients of all types.,Neutral
8237,"(75, 136)",The system shall have a option to release unsigned orders to services,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8238,"(75, 137)",The system shall have a option to release unsigned orders to services,The system shall include Standard Laboratory and Medication orderable files.,Neutral
8239,"(75, 138)",The system shall have a option to release unsigned orders to services,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8240,"(75, 139)",The system shall have a option to release unsigned orders to services,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8241,"(75, 140)",The system shall have a option to release unsigned orders to services,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8242,"(75, 141)",The system shall have a option to release unsigned orders to services,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8243,"(75, 142)",The system shall have a option to release unsigned orders to services,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8244,"(75, 143)",The system shall have a option to release unsigned orders to services,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8245,"(75, 144)",The system shall have a option to release unsigned orders to services,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8246,"(75, 145)",The system shall have a option to release unsigned orders to services,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.,Neutral
8247,"(75, 146)",The system shall have a option to release unsigned orders to services,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8248,"(75, 147)",The system shall have a option to release unsigned orders to services,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8249,"(75, 148)",The system shall have a option to release unsigned orders to services,"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.",Neutral
8250,"(76, 77)","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.",The system shall ask the user if the user wants to continue using the system before timing out.,Neutral
8251,"(76, 78)","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.",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
8252,"(76, 79)","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.","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.",Neutral
8253,"(76, 80)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
8254,"(76, 81)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
8255,"(76, 82)","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.",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.,Neutral
8256,"(76, 83)","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.",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.,Neutral
8257,"(76, 84)","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.",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.,Neutral
8258,"(76, 85)","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.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
8259,"(76, 86)","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.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
8260,"(76, 87)","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.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
8261,"(76, 88)","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.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8262,"(76, 89)","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.",The system shall not allow mandatory notifications to be disabled.,Neutral
8263,"(76, 90)","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.",The system shall allow users to disable unwanted notifications as desired.,Neutral
8264,"(76, 91)","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.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8265,"(76, 92)","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.",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.,Neutral
8266,"(76, 93)","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.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8267,"(76, 94)","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.",The system shall use any protocol for transferring messages among packages.,Neutral
8268,"(76, 95)","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.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8269,"(76, 96)","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.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8270,"(76, 97)","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.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8271,"(76, 98)","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.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8272,"(76, 99)","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.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8273,"(76, 100)","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.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8274,"(76, 101)","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.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8275,"(76, 102)","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.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8276,"(76, 103)","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.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8277,"(76, 104)","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.",The system shall allow a user to foward notification to someone else at the site.,Neutral
8278,"(76, 105)","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.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8279,"(76, 106)","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.","The system shall define, populate, and retrieve information about user classes.",Neutral
8280,"(76, 107)","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.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8281,"(76, 108)","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.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8282,"(76, 109)","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.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8283,"(76, 110)","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.",The system shall allow concurrent membership in more than one User Class.,Neutral
8284,"(76, 111)","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.",The system shall allow membership in only one User Class.,Neutral
8285,"(76, 112)","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.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8286,"(76, 113)","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.","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.",Neutral
8287,"(76, 114)","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.",The system shall improve accessibility of online clinical information and results.,Neutral
8288,"(76, 115)","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.","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.",Neutral
8289,"(76, 116)","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.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8290,"(76, 117)","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.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8291,"(76, 118)","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.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8292,"(76, 119)","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.",The system shall make the traditional order entry processes more practical.,Neutral
8293,"(76, 120)","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.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8294,"(76, 121)","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.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8295,"(76, 122)","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.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8296,"(76, 123)","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.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8297,"(76, 124)","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.","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.",Neutral
8298,"(76, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8299,"(76, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8300,"(76, 127)","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.","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.",Neutral
8301,"(76, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8302,"(76, 129)","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.","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.",Neutral
8303,"(76, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8304,"(76, 131)","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.",The system shall delete history of received immunizations.,Neutral
8305,"(76, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
8306,"(76, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8307,"(76, 134)","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.",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.,Neutral
8308,"(76, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
8309,"(76, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8310,"(76, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
8311,"(76, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8312,"(76, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8313,"(76, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8314,"(76, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8315,"(76, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8316,"(76, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8317,"(76, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8318,"(76, 145)","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.",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.,Neutral
8319,"(76, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8320,"(76, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8321,"(76, 148)","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.","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.",Neutral
8322,"(77, 78)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Neutral
8323,"(77, 79)",The system shall ask the user if the user wants to continue using the system before timing out.,"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.",Neutral
8324,"(77, 80)",The system shall ask the user if the user wants to continue using the system before timing out.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
8325,"(77, 81)",The system shall ask the user if the user wants to continue using the system before timing out.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
8326,"(77, 82)",The system shall ask the user if the user wants to continue using the system before timing out.,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.,Neutral
8327,"(77, 83)",The system shall ask the user if the user wants to continue using the system before timing out.,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.,Neutral
8328,"(77, 84)",The system shall ask the user if the user wants to continue using the system before timing out.,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.,Neutral
8329,"(77, 85)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
8330,"(77, 86)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
8331,"(77, 87)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
8332,"(77, 88)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8333,"(77, 89)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall not allow mandatory notifications to be disabled.,Neutral
8334,"(77, 90)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall allow users to disable unwanted notifications as desired.,Neutral
8335,"(77, 91)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8336,"(77, 92)",The system shall ask the user if the user wants to continue using the system before timing out.,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.,Neutral
8337,"(77, 93)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8338,"(77, 94)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall use any protocol for transferring messages among packages.,Neutral
8339,"(77, 95)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8340,"(77, 96)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8341,"(77, 97)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8342,"(77, 98)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8343,"(77, 99)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8344,"(77, 100)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8345,"(77, 101)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8346,"(77, 102)",The system shall ask the user if the user wants to continue using the system before timing out.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8347,"(77, 103)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8348,"(77, 104)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall allow a user to foward notification to someone else at the site.,Neutral
8349,"(77, 105)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8350,"(77, 106)",The system shall ask the user if the user wants to continue using the system before timing out.,"The system shall define, populate, and retrieve information about user classes.",Neutral
8351,"(77, 107)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8352,"(77, 108)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8353,"(77, 109)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8354,"(77, 110)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall allow concurrent membership in more than one User Class.,Neutral
8355,"(77, 111)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall allow membership in only one User Class.,Neutral
8356,"(77, 112)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8357,"(77, 113)",The system shall ask the user if the user wants to continue using the system before timing out.,"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.",Neutral
8358,"(77, 114)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall improve accessibility of online clinical information and results.,Neutral
8359,"(77, 115)",The system shall ask the user if the user wants to continue using the system before timing out.,"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.",Neutral
8360,"(77, 116)",The system shall ask the user if the user wants to continue using the system before timing out.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8361,"(77, 117)",The system shall ask the user if the user wants to continue using the system before timing out.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8362,"(77, 118)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8363,"(77, 119)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall make the traditional order entry processes more practical.,Neutral
8364,"(77, 120)",The system shall ask the user if the user wants to continue using the system before timing out.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8365,"(77, 121)",The system shall ask the user if the user wants to continue using the system before timing out.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8366,"(77, 122)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8367,"(77, 123)",The system shall ask the user if the user wants to continue using the system before timing out.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8368,"(77, 124)",The system shall ask the user if the user wants to continue using the system before timing out.,"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.",Neutral
8369,"(77, 125)",The system shall ask the user if the user wants to continue using the system before timing out.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8370,"(77, 126)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8371,"(77, 127)",The system shall ask the user if the user wants to continue using the system before timing out.,"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.",Neutral
8372,"(77, 128)",The system shall ask the user if the user wants to continue using the system before timing out.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8373,"(77, 129)",The system shall ask the user if the user wants to continue using the system before timing out.,"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.",Neutral
8374,"(77, 130)",The system shall ask the user if the user wants to continue using the system before timing out.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8375,"(77, 131)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall delete history of received immunizations.,Neutral
8376,"(77, 132)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
8377,"(77, 133)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8378,"(77, 134)",The system shall ask the user if the user wants to continue using the system before timing out.,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.,Neutral
8379,"(77, 135)",The system shall ask the user if the user wants to continue using the system before timing out.,The system will provide the ability to register patients of all types.,Neutral
8380,"(77, 136)",The system shall ask the user if the user wants to continue using the system before timing out.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8381,"(77, 137)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
8382,"(77, 138)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8383,"(77, 139)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8384,"(77, 140)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8385,"(77, 141)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8386,"(77, 142)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8387,"(77, 143)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8388,"(77, 144)",The system shall ask the user if the user wants to continue using the system before timing out.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8389,"(77, 145)",The system shall ask the user if the user wants to continue using the system before timing out.,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.,Neutral
8390,"(77, 146)",The system shall ask the user if the user wants to continue using the system before timing out.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8391,"(77, 147)",The system shall ask the user if the user wants to continue using the system before timing out.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8392,"(77, 148)",The system shall ask the user if the user wants to continue using the system before timing out.,"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.",Neutral
8393,"(78, 79)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"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.",Neutral
8394,"(78, 80)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
8395,"(78, 81)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
8396,"(78, 82)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,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.,Neutral
8397,"(78, 83)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,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.,Neutral
8398,"(78, 84)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,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.,Neutral
8399,"(78, 85)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
8400,"(78, 86)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
8401,"(78, 87)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
8402,"(78, 88)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8403,"(78, 89)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall not allow mandatory notifications to be disabled.,Neutral
8404,"(78, 90)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall allow users to disable unwanted notifications as desired.,Neutral
8405,"(78, 91)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8406,"(78, 92)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,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.,Neutral
8407,"(78, 93)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8408,"(78, 94)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall use any protocol for transferring messages among packages.,Neutral
8409,"(78, 95)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8410,"(78, 96)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8411,"(78, 97)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8412,"(78, 98)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8413,"(78, 99)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8414,"(78, 100)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8415,"(78, 101)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8416,"(78, 102)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8417,"(78, 103)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8418,"(78, 104)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall allow a user to foward notification to someone else at the site.,Neutral
8419,"(78, 105)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8420,"(78, 106)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"The system shall define, populate, and retrieve information about user classes.",Neutral
8421,"(78, 107)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8422,"(78, 108)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8423,"(78, 109)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8424,"(78, 110)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall allow concurrent membership in more than one User Class.,Neutral
8425,"(78, 111)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall allow membership in only one User Class.,Neutral
8426,"(78, 112)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8427,"(78, 113)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"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.",Neutral
8428,"(78, 114)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall improve accessibility of online clinical information and results.,Neutral
8429,"(78, 115)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"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.",Neutral
8430,"(78, 116)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8431,"(78, 117)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8432,"(78, 118)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8433,"(78, 119)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall make the traditional order entry processes more practical.,Neutral
8434,"(78, 120)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8435,"(78, 121)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8436,"(78, 122)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8437,"(78, 123)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8438,"(78, 124)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"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.",Neutral
8439,"(78, 125)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8440,"(78, 126)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8441,"(78, 127)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"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.",Neutral
8442,"(78, 128)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8443,"(78, 129)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"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.",Neutral
8444,"(78, 130)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8445,"(78, 131)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall delete history of received immunizations.,Neutral
8446,"(78, 132)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
8447,"(78, 133)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8448,"(78, 134)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,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.,Neutral
8449,"(78, 135)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system will provide the ability to register patients of all types.,Neutral
8450,"(78, 136)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8451,"(78, 137)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
8452,"(78, 138)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8453,"(78, 139)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8454,"(78, 140)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8455,"(78, 141)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8456,"(78, 142)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8457,"(78, 143)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8458,"(78, 144)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8459,"(78, 145)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,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.,Neutral
8460,"(78, 146)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8461,"(78, 147)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8462,"(78, 148)",The system shall provide a way to limit the users or sites that have access to remote retrievable data.,"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.",Neutral
8463,"(79, 80)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Neutral
8464,"(79, 81)","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.",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Neutral
8465,"(79, 82)","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.",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.,Neutral
8466,"(79, 83)","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.",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.,Neutral
8467,"(79, 84)","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.",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.,Neutral
8468,"(79, 85)","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.",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
8469,"(79, 86)","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.",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
8470,"(79, 87)","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.",The system shall display a message telling the user that the selected patient is deceased.,Neutral
8471,"(79, 88)","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.",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8472,"(79, 89)","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.",The system shall not allow mandatory notifications to be disabled.,Neutral
8473,"(79, 90)","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.",The system shall allow users to disable unwanted notifications as desired.,Neutral
8474,"(79, 91)","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.",The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8475,"(79, 92)","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.",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.,Neutral
8476,"(79, 93)","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.",The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8477,"(79, 94)","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.",The system shall use any protocol for transferring messages among packages.,Neutral
8478,"(79, 95)","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.",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8479,"(79, 96)","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.",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8480,"(79, 97)","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.",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8481,"(79, 98)","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.",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8482,"(79, 99)","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.",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8483,"(79, 100)","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.",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8484,"(79, 101)","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.",The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8485,"(79, 102)","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.","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8486,"(79, 103)","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.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8487,"(79, 104)","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.",The system shall allow a user to foward notification to someone else at the site.,Neutral
8488,"(79, 105)","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.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8489,"(79, 106)","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.","The system shall define, populate, and retrieve information about user classes.",Neutral
8490,"(79, 107)","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.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8491,"(79, 108)","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.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8492,"(79, 109)","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.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8493,"(79, 110)","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.",The system shall allow concurrent membership in more than one User Class.,Neutral
8494,"(79, 111)","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.",The system shall allow membership in only one User Class.,Neutral
8495,"(79, 112)","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.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8496,"(79, 113)","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.","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.",Neutral
8497,"(79, 114)","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.",The system shall improve accessibility of online clinical information and results.,Neutral
8498,"(79, 115)","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.","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.",Neutral
8499,"(79, 116)","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.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8500,"(79, 117)","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.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8501,"(79, 118)","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.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8502,"(79, 119)","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.",The system shall make the traditional order entry processes more practical.,Neutral
8503,"(79, 120)","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.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8504,"(79, 121)","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.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8505,"(79, 122)","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.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8506,"(79, 123)","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.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8507,"(79, 124)","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.","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.",Neutral
8508,"(79, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8509,"(79, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8510,"(79, 127)","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.","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.",Neutral
8511,"(79, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8512,"(79, 129)","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.","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.",Neutral
8513,"(79, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8514,"(79, 131)","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.",The system shall delete history of received immunizations.,Neutral
8515,"(79, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
8516,"(79, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8517,"(79, 134)","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.",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.,Neutral
8518,"(79, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
8519,"(79, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8520,"(79, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
8521,"(79, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8522,"(79, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8523,"(79, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8524,"(79, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8525,"(79, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8526,"(79, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8527,"(79, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8528,"(79, 145)","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.",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.,Neutral
8529,"(79, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8530,"(79, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8531,"(79, 148)","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.","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.",Neutral
8532,"(80, 81)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,Conflict
8533,"(80, 82)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,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.,Neutral
8534,"(80, 83)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,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.,Neutral
8535,"(80, 84)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,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.,Neutral
8536,"(80, 85)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
8537,"(80, 86)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
8538,"(80, 87)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
8539,"(80, 88)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8540,"(80, 89)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall not allow mandatory notifications to be disabled.,Neutral
8541,"(80, 90)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall allow users to disable unwanted notifications as desired.,Neutral
8542,"(80, 91)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8543,"(80, 92)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,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.,Neutral
8544,"(80, 93)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8545,"(80, 94)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall use any protocol for transferring messages among packages.,Neutral
8546,"(80, 95)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8547,"(80, 96)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8548,"(80, 97)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8549,"(80, 98)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8550,"(80, 99)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8551,"(80, 100)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8552,"(80, 101)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8553,"(80, 102)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8554,"(80, 103)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8555,"(80, 104)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall allow a user to foward notification to someone else at the site.,Neutral
8556,"(80, 105)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8557,"(80, 106)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"The system shall define, populate, and retrieve information about user classes.",Neutral
8558,"(80, 107)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8559,"(80, 108)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8560,"(80, 109)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8561,"(80, 110)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall allow concurrent membership in more than one User Class.,Neutral
8562,"(80, 111)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall allow membership in only one User Class.,Neutral
8563,"(80, 112)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8564,"(80, 113)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"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.",Neutral
8565,"(80, 114)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall improve accessibility of online clinical information and results.,Neutral
8566,"(80, 115)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"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.",Neutral
8567,"(80, 116)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8568,"(80, 117)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8569,"(80, 118)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8570,"(80, 119)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall make the traditional order entry processes more practical.,Neutral
8571,"(80, 120)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8572,"(80, 121)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8573,"(80, 122)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8574,"(80, 123)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8575,"(80, 124)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"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.",Neutral
8576,"(80, 125)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8577,"(80, 126)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8578,"(80, 127)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"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.",Neutral
8579,"(80, 128)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8580,"(80, 129)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"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.",Neutral
8581,"(80, 130)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8582,"(80, 131)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall delete history of received immunizations.,Neutral
8583,"(80, 132)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
8584,"(80, 133)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8585,"(80, 134)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,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.,Neutral
8586,"(80, 135)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system will provide the ability to register patients of all types.,Neutral
8587,"(80, 136)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8588,"(80, 137)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
8589,"(80, 138)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8590,"(80, 139)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8591,"(80, 140)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8592,"(80, 141)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8593,"(80, 142)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8594,"(80, 143)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8595,"(80, 144)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8596,"(80, 145)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,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.,Neutral
8597,"(80, 146)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8598,"(80, 147)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8599,"(80, 148)",Problems entered on the encounter form by clerical personnel shall be left as UNVERIFIED.,"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.",Neutral
8600,"(81, 82)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,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.,Neutral
8601,"(81, 83)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,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.,Neutral
8602,"(81, 84)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,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.,Neutral
8603,"(81, 85)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
8604,"(81, 86)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
8605,"(81, 87)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
8606,"(81, 88)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8607,"(81, 89)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall not allow mandatory notifications to be disabled.,Neutral
8608,"(81, 90)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall allow users to disable unwanted notifications as desired.,Neutral
8609,"(81, 91)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8610,"(81, 92)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,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.,Neutral
8611,"(81, 93)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8612,"(81, 94)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall use any protocol for transferring messages among packages.,Neutral
8613,"(81, 95)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8614,"(81, 96)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8615,"(81, 97)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8616,"(81, 98)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8617,"(81, 99)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8618,"(81, 100)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8619,"(81, 101)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8620,"(81, 102)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8621,"(81, 103)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8622,"(81, 104)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall allow a user to foward notification to someone else at the site.,Neutral
8623,"(81, 105)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8624,"(81, 106)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"The system shall define, populate, and retrieve information about user classes.",Neutral
8625,"(81, 107)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8626,"(81, 108)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8627,"(81, 109)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8628,"(81, 110)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall allow concurrent membership in more than one User Class.,Neutral
8629,"(81, 111)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall allow membership in only one User Class.,Neutral
8630,"(81, 112)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8631,"(81, 113)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"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.",Neutral
8632,"(81, 114)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall improve accessibility of online clinical information and results.,Neutral
8633,"(81, 115)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"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.",Neutral
8634,"(81, 116)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8635,"(81, 117)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8636,"(81, 118)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8637,"(81, 119)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall make the traditional order entry processes more practical.,Neutral
8638,"(81, 120)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8639,"(81, 121)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8640,"(81, 122)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8641,"(81, 123)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8642,"(81, 124)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"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.",Neutral
8643,"(81, 125)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8644,"(81, 126)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8645,"(81, 127)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"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.",Neutral
8646,"(81, 128)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8647,"(81, 129)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"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.",Neutral
8648,"(81, 130)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8649,"(81, 131)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall delete history of received immunizations.,Neutral
8650,"(81, 132)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
8651,"(81, 133)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8652,"(81, 134)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,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.,Neutral
8653,"(81, 135)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system will provide the ability to register patients of all types.,Neutral
8654,"(81, 136)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8655,"(81, 137)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
8656,"(81, 138)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8657,"(81, 139)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8658,"(81, 140)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8659,"(81, 141)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8660,"(81, 142)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8661,"(81, 143)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8662,"(81, 144)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8663,"(81, 145)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,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.,Neutral
8664,"(81, 146)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8665,"(81, 147)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8666,"(81, 148)",Problems entered on the encounter form by clerical personnel shall be left as UNSIGNED.,"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.",Neutral
8667,"(82, 83)",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.,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.,Conflict
8668,"(82, 84)",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.,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.,Neutral
8669,"(82, 85)",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.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
8670,"(82, 86)",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.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
8671,"(82, 87)",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.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
8672,"(82, 88)",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.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8673,"(82, 89)",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.,The system shall not allow mandatory notifications to be disabled.,Neutral
8674,"(82, 90)",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.,The system shall allow users to disable unwanted notifications as desired.,Neutral
8675,"(82, 91)",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.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8676,"(82, 92)",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.,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.,Neutral
8677,"(82, 93)",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.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8678,"(82, 94)",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.,The system shall use any protocol for transferring messages among packages.,Neutral
8679,"(82, 95)",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.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8680,"(82, 96)",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.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8681,"(82, 97)",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.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8682,"(82, 98)",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.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8683,"(82, 99)",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.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8684,"(82, 100)",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.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8685,"(82, 101)",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.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8686,"(82, 102)",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.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8687,"(82, 103)",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.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8688,"(82, 104)",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.,The system shall allow a user to foward notification to someone else at the site.,Neutral
8689,"(82, 105)",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.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8690,"(82, 106)",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.,"The system shall define, populate, and retrieve information about user classes.",Neutral
8691,"(82, 107)",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.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8692,"(82, 108)",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.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8693,"(82, 109)",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.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8694,"(82, 110)",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.,The system shall allow concurrent membership in more than one User Class.,Neutral
8695,"(82, 111)",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.,The system shall allow membership in only one User Class.,Neutral
8696,"(82, 112)",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.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8697,"(82, 113)",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.,"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.",Neutral
8698,"(82, 114)",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.,The system shall improve accessibility of online clinical information and results.,Neutral
8699,"(82, 115)",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.,"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.",Neutral
8700,"(82, 116)",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.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8701,"(82, 117)",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.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8702,"(82, 118)",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.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8703,"(82, 119)",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.,The system shall make the traditional order entry processes more practical.,Neutral
8704,"(82, 120)",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.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8705,"(82, 121)",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.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8706,"(82, 122)",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.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8707,"(82, 123)",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.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8708,"(82, 124)",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.,"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.",Neutral
8709,"(82, 125)",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.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8710,"(82, 126)",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.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8711,"(82, 127)",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.,"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.",Neutral
8712,"(82, 128)",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.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8713,"(82, 129)",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.,"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.",Neutral
8714,"(82, 130)",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.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8715,"(82, 131)",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.,The system shall delete history of received immunizations.,Neutral
8716,"(82, 132)",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.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
8717,"(82, 133)",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.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8718,"(82, 134)",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.,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.,Neutral
8719,"(82, 135)",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.,The system will provide the ability to register patients of all types.,Neutral
8720,"(82, 136)",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.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8721,"(82, 137)",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.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
8722,"(82, 138)",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.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8723,"(82, 139)",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.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8724,"(82, 140)",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.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8725,"(82, 141)",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.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8726,"(82, 142)",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.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8727,"(82, 143)",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.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8728,"(82, 144)",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.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8729,"(82, 145)",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.,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.,Neutral
8730,"(82, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8731,"(82, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8732,"(82, 148)",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.,"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.",Neutral
8733,"(83, 84)",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.,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.,Neutral
8734,"(83, 85)",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.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
8735,"(83, 86)",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.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
8736,"(83, 87)",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.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
8737,"(83, 88)",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.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8738,"(83, 89)",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.,The system shall not allow mandatory notifications to be disabled.,Neutral
8739,"(83, 90)",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.,The system shall allow users to disable unwanted notifications as desired.,Neutral
8740,"(83, 91)",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.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8741,"(83, 92)",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.,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.,Neutral
8742,"(83, 93)",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.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8743,"(83, 94)",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.,The system shall use any protocol for transferring messages among packages.,Neutral
8744,"(83, 95)",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.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8745,"(83, 96)",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.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8746,"(83, 97)",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.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8747,"(83, 98)",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.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8748,"(83, 99)",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.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8749,"(83, 100)",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.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8750,"(83, 101)",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.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8751,"(83, 102)",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.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8752,"(83, 103)",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.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8753,"(83, 104)",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.,The system shall allow a user to foward notification to someone else at the site.,Neutral
8754,"(83, 105)",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.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8755,"(83, 106)",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.,"The system shall define, populate, and retrieve information about user classes.",Neutral
8756,"(83, 107)",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.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8757,"(83, 108)",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.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8758,"(83, 109)",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.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8759,"(83, 110)",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.,The system shall allow concurrent membership in more than one User Class.,Neutral
8760,"(83, 111)",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.,The system shall allow membership in only one User Class.,Neutral
8761,"(83, 112)",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.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8762,"(83, 113)",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.,"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.",Neutral
8763,"(83, 114)",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.,The system shall improve accessibility of online clinical information and results.,Neutral
8764,"(83, 115)",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.,"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.",Neutral
8765,"(83, 116)",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.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8766,"(83, 117)",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.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8767,"(83, 118)",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.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8768,"(83, 119)",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.,The system shall make the traditional order entry processes more practical.,Neutral
8769,"(83, 120)",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.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8770,"(83, 121)",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.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8771,"(83, 122)",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.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8772,"(83, 123)",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.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8773,"(83, 124)",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.,"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.",Neutral
8774,"(83, 125)",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.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8775,"(83, 126)",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.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8776,"(83, 127)",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.,"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.",Neutral
8777,"(83, 128)",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.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8778,"(83, 129)",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.,"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.",Neutral
8779,"(83, 130)",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.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8780,"(83, 131)",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.,The system shall delete history of received immunizations.,Neutral
8781,"(83, 132)",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.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
8782,"(83, 133)",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.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8783,"(83, 134)",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.,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.,Neutral
8784,"(83, 135)",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.,The system will provide the ability to register patients of all types.,Neutral
8785,"(83, 136)",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.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8786,"(83, 137)",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.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
8787,"(83, 138)",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.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8788,"(83, 139)",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.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8789,"(83, 140)",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.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8790,"(83, 141)",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.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8791,"(83, 142)",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.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8792,"(83, 143)",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.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8793,"(83, 144)",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.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8794,"(83, 145)",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.,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.,Neutral
8795,"(83, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8796,"(83, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8797,"(83, 148)",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.,"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.",Neutral
8798,"(84, 85)",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.,The system shall indicate that the record is sensitive and may only be viewed by authorized users.,Neutral
8799,"(84, 86)",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.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Neutral
8800,"(84, 87)",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.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
8801,"(84, 88)",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.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8802,"(84, 89)",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.,The system shall not allow mandatory notifications to be disabled.,Neutral
8803,"(84, 90)",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.,The system shall allow users to disable unwanted notifications as desired.,Neutral
8804,"(84, 91)",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.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8805,"(84, 92)",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.,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.,Neutral
8806,"(84, 93)",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.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8807,"(84, 94)",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.,The system shall use any protocol for transferring messages among packages.,Neutral
8808,"(84, 95)",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.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8809,"(84, 96)",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.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8810,"(84, 97)",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.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8811,"(84, 98)",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.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8812,"(84, 99)",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.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8813,"(84, 100)",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.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8814,"(84, 101)",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.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8815,"(84, 102)",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.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8816,"(84, 103)",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.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8817,"(84, 104)",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.,The system shall allow a user to foward notification to someone else at the site.,Neutral
8818,"(84, 105)",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.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8819,"(84, 106)",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.,"The system shall define, populate, and retrieve information about user classes.",Neutral
8820,"(84, 107)",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.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8821,"(84, 108)",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.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8822,"(84, 109)",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.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8823,"(84, 110)",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.,The system shall allow concurrent membership in more than one User Class.,Neutral
8824,"(84, 111)",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.,The system shall allow membership in only one User Class.,Neutral
8825,"(84, 112)",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.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8826,"(84, 113)",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.,"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.",Neutral
8827,"(84, 114)",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.,The system shall improve accessibility of online clinical information and results.,Neutral
8828,"(84, 115)",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.,"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.",Neutral
8829,"(84, 116)",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.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8830,"(84, 117)",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.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8831,"(84, 118)",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.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8832,"(84, 119)",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.,The system shall make the traditional order entry processes more practical.,Neutral
8833,"(84, 120)",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.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8834,"(84, 121)",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.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8835,"(84, 122)",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.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8836,"(84, 123)",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.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8837,"(84, 124)",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.,"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.",Neutral
8838,"(84, 125)",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.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8839,"(84, 126)",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.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8840,"(84, 127)",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.,"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.",Neutral
8841,"(84, 128)",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.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8842,"(84, 129)",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.,"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.",Neutral
8843,"(84, 130)",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.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8844,"(84, 131)",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.,The system shall delete history of received immunizations.,Neutral
8845,"(84, 132)",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.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
8846,"(84, 133)",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.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8847,"(84, 134)",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.,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.,Neutral
8848,"(84, 135)",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.,The system will provide the ability to register patients of all types.,Neutral
8849,"(84, 136)",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.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8850,"(84, 137)",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.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
8851,"(84, 138)",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.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8852,"(84, 139)",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.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8853,"(84, 140)",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.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8854,"(84, 141)",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.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8855,"(84, 142)",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.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8856,"(84, 143)",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.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8857,"(84, 144)",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.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8858,"(84, 145)",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.,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.,Neutral
8859,"(84, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8860,"(84, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8861,"(84, 148)",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.,"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.",Neutral
8862,"(85, 86)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,Conflict
8863,"(85, 87)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
8864,"(85, 88)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8865,"(85, 89)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall not allow mandatory notifications to be disabled.,Neutral
8866,"(85, 90)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall allow users to disable unwanted notifications as desired.,Neutral
8867,"(85, 91)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8868,"(85, 92)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,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.,Neutral
8869,"(85, 93)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8870,"(85, 94)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall use any protocol for transferring messages among packages.,Neutral
8871,"(85, 95)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8872,"(85, 96)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8873,"(85, 97)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8874,"(85, 98)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8875,"(85, 99)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8876,"(85, 100)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8877,"(85, 101)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8878,"(85, 102)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8879,"(85, 103)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8880,"(85, 104)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall allow a user to foward notification to someone else at the site.,Neutral
8881,"(85, 105)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8882,"(85, 106)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"The system shall define, populate, and retrieve information about user classes.",Neutral
8883,"(85, 107)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8884,"(85, 108)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8885,"(85, 109)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8886,"(85, 110)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall allow concurrent membership in more than one User Class.,Neutral
8887,"(85, 111)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall allow membership in only one User Class.,Neutral
8888,"(85, 112)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8889,"(85, 113)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"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.",Neutral
8890,"(85, 114)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall improve accessibility of online clinical information and results.,Neutral
8891,"(85, 115)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"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.",Neutral
8892,"(85, 116)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8893,"(85, 117)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8894,"(85, 118)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8895,"(85, 119)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall make the traditional order entry processes more practical.,Neutral
8896,"(85, 120)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8897,"(85, 121)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8898,"(85, 122)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8899,"(85, 123)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8900,"(85, 124)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"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.",Neutral
8901,"(85, 125)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8902,"(85, 126)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8903,"(85, 127)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"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.",Neutral
8904,"(85, 128)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8905,"(85, 129)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"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.",Neutral
8906,"(85, 130)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8907,"(85, 131)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall delete history of received immunizations.,Neutral
8908,"(85, 132)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
8909,"(85, 133)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8910,"(85, 134)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,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.,Neutral
8911,"(85, 135)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system will provide the ability to register patients of all types.,Neutral
8912,"(85, 136)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8913,"(85, 137)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
8914,"(85, 138)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8915,"(85, 139)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8916,"(85, 140)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8917,"(85, 141)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8918,"(85, 142)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8919,"(85, 143)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8920,"(85, 144)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8921,"(85, 145)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,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.,Neutral
8922,"(85, 146)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8923,"(85, 147)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8924,"(85, 148)",The system shall indicate that the record is sensitive and may only be viewed by authorized users.,"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.",Neutral
8925,"(86, 87)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall display a message telling the user that the selected patient is deceased.,Neutral
8926,"(86, 88)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8927,"(86, 89)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall not allow mandatory notifications to be disabled.,Neutral
8928,"(86, 90)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall allow users to disable unwanted notifications as desired.,Neutral
8929,"(86, 91)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8930,"(86, 92)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,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.,Neutral
8931,"(86, 93)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8932,"(86, 94)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall use any protocol for transferring messages among packages.,Neutral
8933,"(86, 95)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8934,"(86, 96)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8935,"(86, 97)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8936,"(86, 98)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8937,"(86, 99)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8938,"(86, 100)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
8939,"(86, 101)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
8940,"(86, 102)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
8941,"(86, 103)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
8942,"(86, 104)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall allow a user to foward notification to someone else at the site.,Neutral
8943,"(86, 105)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
8944,"(86, 106)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"The system shall define, populate, and retrieve information about user classes.",Neutral
8945,"(86, 107)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8946,"(86, 108)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
8947,"(86, 109)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
8948,"(86, 110)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall allow concurrent membership in more than one User Class.,Neutral
8949,"(86, 111)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall allow membership in only one User Class.,Neutral
8950,"(86, 112)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
8951,"(86, 113)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"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.",Neutral
8952,"(86, 114)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall improve accessibility of online clinical information and results.,Neutral
8953,"(86, 115)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"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.",Neutral
8954,"(86, 116)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
8955,"(86, 117)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
8956,"(86, 118)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
8957,"(86, 119)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall make the traditional order entry processes more practical.,Neutral
8958,"(86, 120)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
8959,"(86, 121)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
8960,"(86, 122)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
8961,"(86, 123)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
8962,"(86, 124)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"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.",Neutral
8963,"(86, 125)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
8964,"(86, 126)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
8965,"(86, 127)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"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.",Neutral
8966,"(86, 128)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
8967,"(86, 129)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"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.",Neutral
8968,"(86, 130)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
8969,"(86, 131)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall delete history of received immunizations.,Neutral
8970,"(86, 132)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
8971,"(86, 133)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
8972,"(86, 134)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,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.,Neutral
8973,"(86, 135)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system will provide the ability to register patients of all types.,Neutral
8974,"(86, 136)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
8975,"(86, 137)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
8976,"(86, 138)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
8977,"(86, 139)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
8978,"(86, 140)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
8979,"(86, 141)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
8980,"(86, 142)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
8981,"(86, 143)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
8982,"(86, 144)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
8983,"(86, 145)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,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.,Neutral
8984,"(86, 146)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
8985,"(86, 147)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
8986,"(86, 148)",The system shall indicate that a record is sensitive and may only be viewed by authorized users only if the user is not authorized.,"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.",Neutral
8987,"(87, 88)",The system shall display a message telling the user that the selected patient is deceased.,The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,Neutral
8988,"(87, 89)",The system shall display a message telling the user that the selected patient is deceased.,The system shall not allow mandatory notifications to be disabled.,Neutral
8989,"(87, 90)",The system shall display a message telling the user that the selected patient is deceased.,The system shall allow users to disable unwanted notifications as desired.,Neutral
8990,"(87, 91)",The system shall display a message telling the user that the selected patient is deceased.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
8991,"(87, 92)",The system shall display a message telling the user that the selected patient is deceased.,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.,Neutral
8992,"(87, 93)",The system shall display a message telling the user that the selected patient is deceased.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
8993,"(87, 94)",The system shall display a message telling the user that the selected patient is deceased.,The system shall use any protocol for transferring messages among packages.,Neutral
8994,"(87, 95)",The system shall display a message telling the user that the selected patient is deceased.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
8995,"(87, 96)",The system shall display a message telling the user that the selected patient is deceased.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
8996,"(87, 97)",The system shall display a message telling the user that the selected patient is deceased.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
8997,"(87, 98)",The system shall display a message telling the user that the selected patient is deceased.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
8998,"(87, 99)",The system shall display a message telling the user that the selected patient is deceased.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
8999,"(87, 100)",The system shall display a message telling the user that the selected patient is deceased.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9000,"(87, 101)",The system shall display a message telling the user that the selected patient is deceased.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9001,"(87, 102)",The system shall display a message telling the user that the selected patient is deceased.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9002,"(87, 103)",The system shall display a message telling the user that the selected patient is deceased.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9003,"(87, 104)",The system shall display a message telling the user that the selected patient is deceased.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9004,"(87, 105)",The system shall display a message telling the user that the selected patient is deceased.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9005,"(87, 106)",The system shall display a message telling the user that the selected patient is deceased.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9006,"(87, 107)",The system shall display a message telling the user that the selected patient is deceased.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9007,"(87, 108)",The system shall display a message telling the user that the selected patient is deceased.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9008,"(87, 109)",The system shall display a message telling the user that the selected patient is deceased.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9009,"(87, 110)",The system shall display a message telling the user that the selected patient is deceased.,The system shall allow concurrent membership in more than one User Class.,Neutral
9010,"(87, 111)",The system shall display a message telling the user that the selected patient is deceased.,The system shall allow membership in only one User Class.,Neutral
9011,"(87, 112)",The system shall display a message telling the user that the selected patient is deceased.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9012,"(87, 113)",The system shall display a message telling the user that the selected patient is deceased.,"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.",Neutral
9013,"(87, 114)",The system shall display a message telling the user that the selected patient is deceased.,The system shall improve accessibility of online clinical information and results.,Neutral
9014,"(87, 115)",The system shall display a message telling the user that the selected patient is deceased.,"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.",Neutral
9015,"(87, 116)",The system shall display a message telling the user that the selected patient is deceased.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9016,"(87, 117)",The system shall display a message telling the user that the selected patient is deceased.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9017,"(87, 118)",The system shall display a message telling the user that the selected patient is deceased.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9018,"(87, 119)",The system shall display a message telling the user that the selected patient is deceased.,The system shall make the traditional order entry processes more practical.,Neutral
9019,"(87, 120)",The system shall display a message telling the user that the selected patient is deceased.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9020,"(87, 121)",The system shall display a message telling the user that the selected patient is deceased.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9021,"(87, 122)",The system shall display a message telling the user that the selected patient is deceased.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9022,"(87, 123)",The system shall display a message telling the user that the selected patient is deceased.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9023,"(87, 124)",The system shall display a message telling the user that the selected patient is deceased.,"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.",Neutral
9024,"(87, 125)",The system shall display a message telling the user that the selected patient is deceased.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9025,"(87, 126)",The system shall display a message telling the user that the selected patient is deceased.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9026,"(87, 127)",The system shall display a message telling the user that the selected patient is deceased.,"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.",Neutral
9027,"(87, 128)",The system shall display a message telling the user that the selected patient is deceased.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9028,"(87, 129)",The system shall display a message telling the user that the selected patient is deceased.,"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.",Neutral
9029,"(87, 130)",The system shall display a message telling the user that the selected patient is deceased.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9030,"(87, 131)",The system shall display a message telling the user that the selected patient is deceased.,The system shall delete history of received immunizations.,Neutral
9031,"(87, 132)",The system shall display a message telling the user that the selected patient is deceased.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9032,"(87, 133)",The system shall display a message telling the user that the selected patient is deceased.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9033,"(87, 134)",The system shall display a message telling the user that the selected patient is deceased.,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.,Neutral
9034,"(87, 135)",The system shall display a message telling the user that the selected patient is deceased.,The system will provide the ability to register patients of all types.,Neutral
9035,"(87, 136)",The system shall display a message telling the user that the selected patient is deceased.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9036,"(87, 137)",The system shall display a message telling the user that the selected patient is deceased.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9037,"(87, 138)",The system shall display a message telling the user that the selected patient is deceased.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9038,"(87, 139)",The system shall display a message telling the user that the selected patient is deceased.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9039,"(87, 140)",The system shall display a message telling the user that the selected patient is deceased.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9040,"(87, 141)",The system shall display a message telling the user that the selected patient is deceased.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9041,"(87, 142)",The system shall display a message telling the user that the selected patient is deceased.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9042,"(87, 143)",The system shall display a message telling the user that the selected patient is deceased.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9043,"(87, 144)",The system shall display a message telling the user that the selected patient is deceased.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9044,"(87, 145)",The system shall display a message telling the user that the selected patient is deceased.,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.,Neutral
9045,"(87, 146)",The system shall display a message telling the user that the selected patient is deceased.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9046,"(87, 147)",The system shall display a message telling the user that the selected patient is deceased.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9047,"(87, 148)",The system shall display a message telling the user that the selected patient is deceased.,"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.",Neutral
9048,"(88, 89)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall not allow mandatory notifications to be disabled.,Neutral
9049,"(88, 90)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall allow users to disable unwanted notifications as desired.,Neutral
9050,"(88, 91)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
9051,"(88, 92)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,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.,Neutral
9052,"(88, 93)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
9053,"(88, 94)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall use any protocol for transferring messages among packages.,Neutral
9054,"(88, 95)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
9055,"(88, 96)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
9056,"(88, 97)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
9057,"(88, 98)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
9058,"(88, 99)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
9059,"(88, 100)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9060,"(88, 101)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9061,"(88, 102)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9062,"(88, 103)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9063,"(88, 104)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9064,"(88, 105)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9065,"(88, 106)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9066,"(88, 107)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9067,"(88, 108)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9068,"(88, 109)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9069,"(88, 110)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall allow concurrent membership in more than one User Class.,Neutral
9070,"(88, 111)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall allow membership in only one User Class.,Neutral
9071,"(88, 112)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9072,"(88, 113)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"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.",Neutral
9073,"(88, 114)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall improve accessibility of online clinical information and results.,Neutral
9074,"(88, 115)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"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.",Neutral
9075,"(88, 116)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9076,"(88, 117)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9077,"(88, 118)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9078,"(88, 119)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall make the traditional order entry processes more practical.,Neutral
9079,"(88, 120)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9080,"(88, 121)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9081,"(88, 122)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9082,"(88, 123)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9083,"(88, 124)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"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.",Neutral
9084,"(88, 125)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9085,"(88, 126)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9086,"(88, 127)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"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.",Neutral
9087,"(88, 128)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9088,"(88, 129)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"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.",Neutral
9089,"(88, 130)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9090,"(88, 131)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall delete history of received immunizations.,Neutral
9091,"(88, 132)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9092,"(88, 133)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9093,"(88, 134)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,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.,Neutral
9094,"(88, 135)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system will provide the ability to register patients of all types.,Neutral
9095,"(88, 136)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9096,"(88, 137)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9097,"(88, 138)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9098,"(88, 139)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9099,"(88, 140)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9100,"(88, 141)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9101,"(88, 142)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9102,"(88, 143)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9103,"(88, 144)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9104,"(88, 145)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,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.,Neutral
9105,"(88, 146)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9106,"(88, 147)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9107,"(88, 148)",The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list.,"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.",Neutral
9108,"(89, 90)",The system shall not allow mandatory notifications to be disabled.,The system shall allow users to disable unwanted notifications as desired.,Conflict
9109,"(89, 91)",The system shall not allow mandatory notifications to be disabled.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
9110,"(89, 92)",The system shall not allow mandatory notifications to be disabled.,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.,Neutral
9111,"(89, 93)",The system shall not allow mandatory notifications to be disabled.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
9112,"(89, 94)",The system shall not allow mandatory notifications to be disabled.,The system shall use any protocol for transferring messages among packages.,Neutral
9113,"(89, 95)",The system shall not allow mandatory notifications to be disabled.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
9114,"(89, 96)",The system shall not allow mandatory notifications to be disabled.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
9115,"(89, 97)",The system shall not allow mandatory notifications to be disabled.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
9116,"(89, 98)",The system shall not allow mandatory notifications to be disabled.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
9117,"(89, 99)",The system shall not allow mandatory notifications to be disabled.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
9118,"(89, 100)",The system shall not allow mandatory notifications to be disabled.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9119,"(89, 101)",The system shall not allow mandatory notifications to be disabled.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9120,"(89, 102)",The system shall not allow mandatory notifications to be disabled.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9121,"(89, 103)",The system shall not allow mandatory notifications to be disabled.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9122,"(89, 104)",The system shall not allow mandatory notifications to be disabled.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9123,"(89, 105)",The system shall not allow mandatory notifications to be disabled.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9124,"(89, 106)",The system shall not allow mandatory notifications to be disabled.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9125,"(89, 107)",The system shall not allow mandatory notifications to be disabled.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9126,"(89, 108)",The system shall not allow mandatory notifications to be disabled.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9127,"(89, 109)",The system shall not allow mandatory notifications to be disabled.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9128,"(89, 110)",The system shall not allow mandatory notifications to be disabled.,The system shall allow concurrent membership in more than one User Class.,Neutral
9129,"(89, 111)",The system shall not allow mandatory notifications to be disabled.,The system shall allow membership in only one User Class.,Neutral
9130,"(89, 112)",The system shall not allow mandatory notifications to be disabled.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9131,"(89, 113)",The system shall not allow mandatory notifications to be disabled.,"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.",Neutral
9132,"(89, 114)",The system shall not allow mandatory notifications to be disabled.,The system shall improve accessibility of online clinical information and results.,Neutral
9133,"(89, 115)",The system shall not allow mandatory notifications to be disabled.,"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.",Neutral
9134,"(89, 116)",The system shall not allow mandatory notifications to be disabled.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9135,"(89, 117)",The system shall not allow mandatory notifications to be disabled.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9136,"(89, 118)",The system shall not allow mandatory notifications to be disabled.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9137,"(89, 119)",The system shall not allow mandatory notifications to be disabled.,The system shall make the traditional order entry processes more practical.,Neutral
9138,"(89, 120)",The system shall not allow mandatory notifications to be disabled.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9139,"(89, 121)",The system shall not allow mandatory notifications to be disabled.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9140,"(89, 122)",The system shall not allow mandatory notifications to be disabled.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9141,"(89, 123)",The system shall not allow mandatory notifications to be disabled.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9142,"(89, 124)",The system shall not allow mandatory notifications to be disabled.,"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.",Neutral
9143,"(89, 125)",The system shall not allow mandatory notifications to be disabled.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9144,"(89, 126)",The system shall not allow mandatory notifications to be disabled.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9145,"(89, 127)",The system shall not allow mandatory notifications to be disabled.,"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.",Neutral
9146,"(89, 128)",The system shall not allow mandatory notifications to be disabled.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9147,"(89, 129)",The system shall not allow mandatory notifications to be disabled.,"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.",Neutral
9148,"(89, 130)",The system shall not allow mandatory notifications to be disabled.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9149,"(89, 131)",The system shall not allow mandatory notifications to be disabled.,The system shall delete history of received immunizations.,Neutral
9150,"(89, 132)",The system shall not allow mandatory notifications to be disabled.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9151,"(89, 133)",The system shall not allow mandatory notifications to be disabled.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9152,"(89, 134)",The system shall not allow mandatory notifications to be disabled.,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.,Neutral
9153,"(89, 135)",The system shall not allow mandatory notifications to be disabled.,The system will provide the ability to register patients of all types.,Neutral
9154,"(89, 136)",The system shall not allow mandatory notifications to be disabled.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9155,"(89, 137)",The system shall not allow mandatory notifications to be disabled.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9156,"(89, 138)",The system shall not allow mandatory notifications to be disabled.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9157,"(89, 139)",The system shall not allow mandatory notifications to be disabled.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9158,"(89, 140)",The system shall not allow mandatory notifications to be disabled.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9159,"(89, 141)",The system shall not allow mandatory notifications to be disabled.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9160,"(89, 142)",The system shall not allow mandatory notifications to be disabled.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9161,"(89, 143)",The system shall not allow mandatory notifications to be disabled.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9162,"(89, 144)",The system shall not allow mandatory notifications to be disabled.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9163,"(89, 145)",The system shall not allow mandatory notifications to be disabled.,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.,Neutral
9164,"(89, 146)",The system shall not allow mandatory notifications to be disabled.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9165,"(89, 147)",The system shall not allow mandatory notifications to be disabled.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9166,"(89, 148)",The system shall not allow mandatory notifications to be disabled.,"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.",Neutral
9167,"(90, 91)",The system shall allow users to disable unwanted notifications as desired.,The system shall only display notifications for a user's patients or notifications that have been forwarded.,Neutral
9168,"(90, 92)",The system shall allow users to disable unwanted notifications as desired.,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.,Neutral
9169,"(90, 93)",The system shall allow users to disable unwanted notifications as desired.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
9170,"(90, 94)",The system shall allow users to disable unwanted notifications as desired.,The system shall use any protocol for transferring messages among packages.,Neutral
9171,"(90, 95)",The system shall allow users to disable unwanted notifications as desired.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
9172,"(90, 96)",The system shall allow users to disable unwanted notifications as desired.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
9173,"(90, 97)",The system shall allow users to disable unwanted notifications as desired.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
9174,"(90, 98)",The system shall allow users to disable unwanted notifications as desired.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
9175,"(90, 99)",The system shall allow users to disable unwanted notifications as desired.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
9176,"(90, 100)",The system shall allow users to disable unwanted notifications as desired.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9177,"(90, 101)",The system shall allow users to disable unwanted notifications as desired.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9178,"(90, 102)",The system shall allow users to disable unwanted notifications as desired.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9179,"(90, 103)",The system shall allow users to disable unwanted notifications as desired.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9180,"(90, 104)",The system shall allow users to disable unwanted notifications as desired.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9181,"(90, 105)",The system shall allow users to disable unwanted notifications as desired.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9182,"(90, 106)",The system shall allow users to disable unwanted notifications as desired.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9183,"(90, 107)",The system shall allow users to disable unwanted notifications as desired.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9184,"(90, 108)",The system shall allow users to disable unwanted notifications as desired.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9185,"(90, 109)",The system shall allow users to disable unwanted notifications as desired.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9186,"(90, 110)",The system shall allow users to disable unwanted notifications as desired.,The system shall allow concurrent membership in more than one User Class.,Neutral
9187,"(90, 111)",The system shall allow users to disable unwanted notifications as desired.,The system shall allow membership in only one User Class.,Neutral
9188,"(90, 112)",The system shall allow users to disable unwanted notifications as desired.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9189,"(90, 113)",The system shall allow users to disable unwanted notifications as desired.,"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.",Neutral
9190,"(90, 114)",The system shall allow users to disable unwanted notifications as desired.,The system shall improve accessibility of online clinical information and results.,Neutral
9191,"(90, 115)",The system shall allow users to disable unwanted notifications as desired.,"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.",Neutral
9192,"(90, 116)",The system shall allow users to disable unwanted notifications as desired.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9193,"(90, 117)",The system shall allow users to disable unwanted notifications as desired.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9194,"(90, 118)",The system shall allow users to disable unwanted notifications as desired.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9195,"(90, 119)",The system shall allow users to disable unwanted notifications as desired.,The system shall make the traditional order entry processes more practical.,Neutral
9196,"(90, 120)",The system shall allow users to disable unwanted notifications as desired.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9197,"(90, 121)",The system shall allow users to disable unwanted notifications as desired.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9198,"(90, 122)",The system shall allow users to disable unwanted notifications as desired.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9199,"(90, 123)",The system shall allow users to disable unwanted notifications as desired.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9200,"(90, 124)",The system shall allow users to disable unwanted notifications as desired.,"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.",Neutral
9201,"(90, 125)",The system shall allow users to disable unwanted notifications as desired.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9202,"(90, 126)",The system shall allow users to disable unwanted notifications as desired.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9203,"(90, 127)",The system shall allow users to disable unwanted notifications as desired.,"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.",Neutral
9204,"(90, 128)",The system shall allow users to disable unwanted notifications as desired.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9205,"(90, 129)",The system shall allow users to disable unwanted notifications as desired.,"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.",Neutral
9206,"(90, 130)",The system shall allow users to disable unwanted notifications as desired.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9207,"(90, 131)",The system shall allow users to disable unwanted notifications as desired.,The system shall delete history of received immunizations.,Neutral
9208,"(90, 132)",The system shall allow users to disable unwanted notifications as desired.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9209,"(90, 133)",The system shall allow users to disable unwanted notifications as desired.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9210,"(90, 134)",The system shall allow users to disable unwanted notifications as desired.,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.,Neutral
9211,"(90, 135)",The system shall allow users to disable unwanted notifications as desired.,The system will provide the ability to register patients of all types.,Neutral
9212,"(90, 136)",The system shall allow users to disable unwanted notifications as desired.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9213,"(90, 137)",The system shall allow users to disable unwanted notifications as desired.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9214,"(90, 138)",The system shall allow users to disable unwanted notifications as desired.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9215,"(90, 139)",The system shall allow users to disable unwanted notifications as desired.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9216,"(90, 140)",The system shall allow users to disable unwanted notifications as desired.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9217,"(90, 141)",The system shall allow users to disable unwanted notifications as desired.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9218,"(90, 142)",The system shall allow users to disable unwanted notifications as desired.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9219,"(90, 143)",The system shall allow users to disable unwanted notifications as desired.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9220,"(90, 144)",The system shall allow users to disable unwanted notifications as desired.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9221,"(90, 145)",The system shall allow users to disable unwanted notifications as desired.,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.,Neutral
9222,"(90, 146)",The system shall allow users to disable unwanted notifications as desired.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9223,"(90, 147)",The system shall allow users to disable unwanted notifications as desired.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9224,"(90, 148)",The system shall allow users to disable unwanted notifications as desired.,"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.",Neutral
9225,"(91, 92)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,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.,Neutral
9226,"(91, 93)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
9227,"(91, 94)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall use any protocol for transferring messages among packages.,Neutral
9228,"(91, 95)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
9229,"(91, 96)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
9230,"(91, 97)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
9231,"(91, 98)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
9232,"(91, 99)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
9233,"(91, 100)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9234,"(91, 101)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9235,"(91, 102)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9236,"(91, 103)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9237,"(91, 104)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9238,"(91, 105)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9239,"(91, 106)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9240,"(91, 107)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9241,"(91, 108)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9242,"(91, 109)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9243,"(91, 110)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall allow concurrent membership in more than one User Class.,Neutral
9244,"(91, 111)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall allow membership in only one User Class.,Neutral
9245,"(91, 112)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9246,"(91, 113)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"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.",Neutral
9247,"(91, 114)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall improve accessibility of online clinical information and results.,Neutral
9248,"(91, 115)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"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.",Neutral
9249,"(91, 116)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9250,"(91, 117)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9251,"(91, 118)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9252,"(91, 119)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall make the traditional order entry processes more practical.,Neutral
9253,"(91, 120)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9254,"(91, 121)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9255,"(91, 122)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9256,"(91, 123)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9257,"(91, 124)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"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.",Neutral
9258,"(91, 125)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9259,"(91, 126)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9260,"(91, 127)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"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.",Neutral
9261,"(91, 128)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9262,"(91, 129)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"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.",Neutral
9263,"(91, 130)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9264,"(91, 131)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall delete history of received immunizations.,Neutral
9265,"(91, 132)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9266,"(91, 133)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9267,"(91, 134)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,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.,Neutral
9268,"(91, 135)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system will provide the ability to register patients of all types.,Neutral
9269,"(91, 136)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9270,"(91, 137)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9271,"(91, 138)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9272,"(91, 139)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9273,"(91, 140)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9274,"(91, 141)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9275,"(91, 142)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9276,"(91, 143)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9277,"(91, 144)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9278,"(91, 145)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,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.,Neutral
9279,"(91, 146)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9280,"(91, 147)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9281,"(91, 148)",The system shall only display notifications for a user's patients or notifications that have been forwarded.,"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.",Neutral
9282,"(92, 93)",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.,The system shall use HL-7 communications protocol for transferring messages among packages.,Neutral
9283,"(92, 94)",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.,The system shall use any protocol for transferring messages among packages.,Neutral
9284,"(92, 95)",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.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
9285,"(92, 96)",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.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
9286,"(92, 97)",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.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
9287,"(92, 98)",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.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
9288,"(92, 99)",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.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
9289,"(92, 100)",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.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9290,"(92, 101)",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.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9291,"(92, 102)",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.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9292,"(92, 103)",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.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9293,"(92, 104)",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.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9294,"(92, 105)",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.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9295,"(92, 106)",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.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9296,"(92, 107)",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.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9297,"(92, 108)",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.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9298,"(92, 109)",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.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9299,"(92, 110)",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.,The system shall allow concurrent membership in more than one User Class.,Neutral
9300,"(92, 111)",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.,The system shall allow membership in only one User Class.,Neutral
9301,"(92, 112)",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.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9302,"(92, 113)",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.,"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.",Neutral
9303,"(92, 114)",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.,The system shall improve accessibility of online clinical information and results.,Neutral
9304,"(92, 115)",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.,"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.",Neutral
9305,"(92, 116)",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.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9306,"(92, 117)",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.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9307,"(92, 118)",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.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9308,"(92, 119)",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.,The system shall make the traditional order entry processes more practical.,Neutral
9309,"(92, 120)",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.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9310,"(92, 121)",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.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9311,"(92, 122)",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.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9312,"(92, 123)",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.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9313,"(92, 124)",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.,"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.",Neutral
9314,"(92, 125)",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.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9315,"(92, 126)",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.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9316,"(92, 127)",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.,"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.",Neutral
9317,"(92, 128)",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.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9318,"(92, 129)",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.,"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.",Neutral
9319,"(92, 130)",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.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9320,"(92, 131)",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.,The system shall delete history of received immunizations.,Neutral
9321,"(92, 132)",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.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9322,"(92, 133)",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.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9323,"(92, 134)",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.,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.,Neutral
9324,"(92, 135)",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.,The system will provide the ability to register patients of all types.,Neutral
9325,"(92, 136)",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.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9326,"(92, 137)",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.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9327,"(92, 138)",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.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9328,"(92, 139)",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.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9329,"(92, 140)",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.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9330,"(92, 141)",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.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9331,"(92, 142)",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.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9332,"(92, 143)",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.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9333,"(92, 144)",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.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9334,"(92, 145)",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.,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.,Neutral
9335,"(92, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9336,"(92, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9337,"(92, 148)",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.,"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.",Neutral
9338,"(93, 94)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall use any protocol for transferring messages among packages.,Conflict
9339,"(93, 95)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
9340,"(93, 96)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
9341,"(93, 97)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
9342,"(93, 98)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
9343,"(93, 99)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
9344,"(93, 100)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9345,"(93, 101)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9346,"(93, 102)",The system shall use HL-7 communications protocol for transferring messages among packages.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9347,"(93, 103)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9348,"(93, 104)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9349,"(93, 105)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9350,"(93, 106)",The system shall use HL-7 communications protocol for transferring messages among packages.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9351,"(93, 107)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9352,"(93, 108)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9353,"(93, 109)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9354,"(93, 110)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall allow concurrent membership in more than one User Class.,Neutral
9355,"(93, 111)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall allow membership in only one User Class.,Neutral
9356,"(93, 112)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9357,"(93, 113)",The system shall use HL-7 communications protocol for transferring messages among packages.,"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.",Neutral
9358,"(93, 114)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall improve accessibility of online clinical information and results.,Neutral
9359,"(93, 115)",The system shall use HL-7 communications protocol for transferring messages among packages.,"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.",Neutral
9360,"(93, 116)",The system shall use HL-7 communications protocol for transferring messages among packages.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9361,"(93, 117)",The system shall use HL-7 communications protocol for transferring messages among packages.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9362,"(93, 118)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9363,"(93, 119)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall make the traditional order entry processes more practical.,Neutral
9364,"(93, 120)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9365,"(93, 121)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9366,"(93, 122)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9367,"(93, 123)",The system shall use HL-7 communications protocol for transferring messages among packages.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9368,"(93, 124)",The system shall use HL-7 communications protocol for transferring messages among packages.,"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.",Neutral
9369,"(93, 125)",The system shall use HL-7 communications protocol for transferring messages among packages.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9370,"(93, 126)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9371,"(93, 127)",The system shall use HL-7 communications protocol for transferring messages among packages.,"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.",Neutral
9372,"(93, 128)",The system shall use HL-7 communications protocol for transferring messages among packages.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9373,"(93, 129)",The system shall use HL-7 communications protocol for transferring messages among packages.,"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.",Neutral
9374,"(93, 130)",The system shall use HL-7 communications protocol for transferring messages among packages.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9375,"(93, 131)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall delete history of received immunizations.,Neutral
9376,"(93, 132)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9377,"(93, 133)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9378,"(93, 134)",The system shall use HL-7 communications protocol for transferring messages among packages.,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.,Neutral
9379,"(93, 135)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system will provide the ability to register patients of all types.,Neutral
9380,"(93, 136)",The system shall use HL-7 communications protocol for transferring messages among packages.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9381,"(93, 137)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9382,"(93, 138)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9383,"(93, 139)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9384,"(93, 140)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9385,"(93, 141)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9386,"(93, 142)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9387,"(93, 143)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9388,"(93, 144)",The system shall use HL-7 communications protocol for transferring messages among packages.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9389,"(93, 145)",The system shall use HL-7 communications protocol for transferring messages among packages.,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.,Neutral
9390,"(93, 146)",The system shall use HL-7 communications protocol for transferring messages among packages.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9391,"(93, 147)",The system shall use HL-7 communications protocol for transferring messages among packages.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9392,"(93, 148)",The system shall use HL-7 communications protocol for transferring messages among packages.,"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.",Neutral
9393,"(94, 95)",The system shall use any protocol for transferring messages among packages.,The system shall allow user classes to be used across VistA to replace and/or complement security keys.,Neutral
9394,"(94, 96)",The system shall use any protocol for transferring messages among packages.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Neutral
9395,"(94, 97)",The system shall use any protocol for transferring messages among packages.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
9396,"(94, 98)",The system shall use any protocol for transferring messages among packages.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
9397,"(94, 99)",The system shall use any protocol for transferring messages among packages.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
9398,"(94, 100)",The system shall use any protocol for transferring messages among packages.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9399,"(94, 101)",The system shall use any protocol for transferring messages among packages.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9400,"(94, 102)",The system shall use any protocol for transferring messages among packages.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9401,"(94, 103)",The system shall use any protocol for transferring messages among packages.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9402,"(94, 104)",The system shall use any protocol for transferring messages among packages.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9403,"(94, 105)",The system shall use any protocol for transferring messages among packages.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9404,"(94, 106)",The system shall use any protocol for transferring messages among packages.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9405,"(94, 107)",The system shall use any protocol for transferring messages among packages.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9406,"(94, 108)",The system shall use any protocol for transferring messages among packages.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9407,"(94, 109)",The system shall use any protocol for transferring messages among packages.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9408,"(94, 110)",The system shall use any protocol for transferring messages among packages.,The system shall allow concurrent membership in more than one User Class.,Neutral
9409,"(94, 111)",The system shall use any protocol for transferring messages among packages.,The system shall allow membership in only one User Class.,Neutral
9410,"(94, 112)",The system shall use any protocol for transferring messages among packages.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9411,"(94, 113)",The system shall use any protocol for transferring messages among packages.,"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.",Neutral
9412,"(94, 114)",The system shall use any protocol for transferring messages among packages.,The system shall improve accessibility of online clinical information and results.,Neutral
9413,"(94, 115)",The system shall use any protocol for transferring messages among packages.,"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.",Neutral
9414,"(94, 116)",The system shall use any protocol for transferring messages among packages.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9415,"(94, 117)",The system shall use any protocol for transferring messages among packages.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9416,"(94, 118)",The system shall use any protocol for transferring messages among packages.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9417,"(94, 119)",The system shall use any protocol for transferring messages among packages.,The system shall make the traditional order entry processes more practical.,Neutral
9418,"(94, 120)",The system shall use any protocol for transferring messages among packages.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9419,"(94, 121)",The system shall use any protocol for transferring messages among packages.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9420,"(94, 122)",The system shall use any protocol for transferring messages among packages.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9421,"(94, 123)",The system shall use any protocol for transferring messages among packages.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9422,"(94, 124)",The system shall use any protocol for transferring messages among packages.,"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.",Neutral
9423,"(94, 125)",The system shall use any protocol for transferring messages among packages.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9424,"(94, 126)",The system shall use any protocol for transferring messages among packages.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9425,"(94, 127)",The system shall use any protocol for transferring messages among packages.,"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.",Neutral
9426,"(94, 128)",The system shall use any protocol for transferring messages among packages.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9427,"(94, 129)",The system shall use any protocol for transferring messages among packages.,"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.",Neutral
9428,"(94, 130)",The system shall use any protocol for transferring messages among packages.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9429,"(94, 131)",The system shall use any protocol for transferring messages among packages.,The system shall delete history of received immunizations.,Neutral
9430,"(94, 132)",The system shall use any protocol for transferring messages among packages.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9431,"(94, 133)",The system shall use any protocol for transferring messages among packages.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9432,"(94, 134)",The system shall use any protocol for transferring messages among packages.,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.,Neutral
9433,"(94, 135)",The system shall use any protocol for transferring messages among packages.,The system will provide the ability to register patients of all types.,Neutral
9434,"(94, 136)",The system shall use any protocol for transferring messages among packages.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9435,"(94, 137)",The system shall use any protocol for transferring messages among packages.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9436,"(94, 138)",The system shall use any protocol for transferring messages among packages.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9437,"(94, 139)",The system shall use any protocol for transferring messages among packages.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9438,"(94, 140)",The system shall use any protocol for transferring messages among packages.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9439,"(94, 141)",The system shall use any protocol for transferring messages among packages.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9440,"(94, 142)",The system shall use any protocol for transferring messages among packages.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9441,"(94, 143)",The system shall use any protocol for transferring messages among packages.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9442,"(94, 144)",The system shall use any protocol for transferring messages among packages.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9443,"(94, 145)",The system shall use any protocol for transferring messages among packages.,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.,Neutral
9444,"(94, 146)",The system shall use any protocol for transferring messages among packages.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9445,"(94, 147)",The system shall use any protocol for transferring messages among packages.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9446,"(94, 148)",The system shall use any protocol for transferring messages among packages.,"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.",Neutral
9447,"(95, 96)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,Conflict
9448,"(95, 97)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
9449,"(95, 98)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
9450,"(95, 99)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
9451,"(95, 100)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9452,"(95, 101)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9453,"(95, 102)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9454,"(95, 103)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9455,"(95, 104)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9456,"(95, 105)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9457,"(95, 106)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9458,"(95, 107)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9459,"(95, 108)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9460,"(95, 109)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9461,"(95, 110)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall allow concurrent membership in more than one User Class.,Neutral
9462,"(95, 111)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall allow membership in only one User Class.,Neutral
9463,"(95, 112)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9464,"(95, 113)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"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.",Neutral
9465,"(95, 114)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall improve accessibility of online clinical information and results.,Neutral
9466,"(95, 115)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"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.",Neutral
9467,"(95, 116)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9468,"(95, 117)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9469,"(95, 118)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9470,"(95, 119)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall make the traditional order entry processes more practical.,Neutral
9471,"(95, 120)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9472,"(95, 121)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9473,"(95, 122)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9474,"(95, 123)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9475,"(95, 124)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"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.",Neutral
9476,"(95, 125)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9477,"(95, 126)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9478,"(95, 127)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"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.",Neutral
9479,"(95, 128)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9480,"(95, 129)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"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.",Neutral
9481,"(95, 130)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9482,"(95, 131)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall delete history of received immunizations.,Neutral
9483,"(95, 132)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9484,"(95, 133)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9485,"(95, 134)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,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.,Neutral
9486,"(95, 135)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system will provide the ability to register patients of all types.,Neutral
9487,"(95, 136)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9488,"(95, 137)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9489,"(95, 138)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9490,"(95, 139)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9491,"(95, 140)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9492,"(95, 141)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9493,"(95, 142)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9494,"(95, 143)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9495,"(95, 144)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9496,"(95, 145)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,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.,Neutral
9497,"(95, 146)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9498,"(95, 147)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9499,"(95, 148)",The system shall allow user classes to be used across VistA to replace and/or complement security keys.,"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.",Neutral
9500,"(96, 97)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,Neutral
9501,"(96, 98)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Neutral
9502,"(96, 99)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
9503,"(96, 100)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9504,"(96, 101)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9505,"(96, 102)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9506,"(96, 103)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9507,"(96, 104)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9508,"(96, 105)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9509,"(96, 106)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9510,"(96, 107)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9511,"(96, 108)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9512,"(96, 109)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9513,"(96, 110)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall allow concurrent membership in more than one User Class.,Neutral
9514,"(96, 111)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall allow membership in only one User Class.,Neutral
9515,"(96, 112)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9516,"(96, 113)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"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.",Neutral
9517,"(96, 114)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall improve accessibility of online clinical information and results.,Neutral
9518,"(96, 115)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"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.",Neutral
9519,"(96, 116)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9520,"(96, 117)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9521,"(96, 118)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9522,"(96, 119)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall make the traditional order entry processes more practical.,Neutral
9523,"(96, 120)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9524,"(96, 121)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9525,"(96, 122)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9526,"(96, 123)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9527,"(96, 124)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"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.",Neutral
9528,"(96, 125)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9529,"(96, 126)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9530,"(96, 127)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"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.",Neutral
9531,"(96, 128)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9532,"(96, 129)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"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.",Neutral
9533,"(96, 130)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9534,"(96, 131)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall delete history of received immunizations.,Neutral
9535,"(96, 132)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9536,"(96, 133)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9537,"(96, 134)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,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.,Neutral
9538,"(96, 135)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system will provide the ability to register patients of all types.,Neutral
9539,"(96, 136)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9540,"(96, 137)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9541,"(96, 138)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9542,"(96, 139)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9543,"(96, 140)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9544,"(96, 141)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9545,"(96, 142)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9546,"(96, 143)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9547,"(96, 144)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9548,"(96, 145)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,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.,Neutral
9549,"(96, 146)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9550,"(96, 147)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9551,"(96, 148)",The system shall not allow user classes to be used across VistaA to replace and/or complement security keys.,"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.",Neutral
9552,"(97, 98)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,Conflict
9553,"(97, 99)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
9554,"(97, 100)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9555,"(97, 101)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9556,"(97, 102)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9557,"(97, 103)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9558,"(97, 104)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9559,"(97, 105)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9560,"(97, 106)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9561,"(97, 107)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9562,"(97, 108)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9563,"(97, 109)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9564,"(97, 110)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall allow concurrent membership in more than one User Class.,Neutral
9565,"(97, 111)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall allow membership in only one User Class.,Neutral
9566,"(97, 112)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9567,"(97, 113)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"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.",Neutral
9568,"(97, 114)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall improve accessibility of online clinical information and results.,Neutral
9569,"(97, 115)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"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.",Neutral
9570,"(97, 116)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9571,"(97, 117)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9572,"(97, 118)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9573,"(97, 119)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall make the traditional order entry processes more practical.,Neutral
9574,"(97, 120)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9575,"(97, 121)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9576,"(97, 122)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9577,"(97, 123)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9578,"(97, 124)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"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.",Neutral
9579,"(97, 125)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9580,"(97, 126)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9581,"(97, 127)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"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.",Neutral
9582,"(97, 128)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9583,"(97, 129)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"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.",Neutral
9584,"(97, 130)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9585,"(97, 131)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall delete history of received immunizations.,Neutral
9586,"(97, 132)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9587,"(97, 133)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9588,"(97, 134)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,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.,Neutral
9589,"(97, 135)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system will provide the ability to register patients of all types.,Neutral
9590,"(97, 136)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9591,"(97, 137)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9592,"(97, 138)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9593,"(97, 139)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9594,"(97, 140)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9595,"(97, 141)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9596,"(97, 142)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9597,"(97, 143)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9598,"(97, 144)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9599,"(97, 145)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,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.,Neutral
9600,"(97, 146)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9601,"(97, 147)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9602,"(97, 148)",The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles.,"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.",Neutral
9603,"(98, 99)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,Neutral
9604,"(98, 100)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9605,"(98, 101)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9606,"(98, 102)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9607,"(98, 103)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9608,"(98, 104)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9609,"(98, 105)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9610,"(98, 106)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9611,"(98, 107)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9612,"(98, 108)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9613,"(98, 109)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9614,"(98, 110)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall allow concurrent membership in more than one User Class.,Neutral
9615,"(98, 111)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall allow membership in only one User Class.,Neutral
9616,"(98, 112)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9617,"(98, 113)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"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.",Neutral
9618,"(98, 114)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall improve accessibility of online clinical information and results.,Neutral
9619,"(98, 115)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"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.",Neutral
9620,"(98, 116)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9621,"(98, 117)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9622,"(98, 118)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9623,"(98, 119)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall make the traditional order entry processes more practical.,Neutral
9624,"(98, 120)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9625,"(98, 121)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9626,"(98, 122)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9627,"(98, 123)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9628,"(98, 124)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"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.",Neutral
9629,"(98, 125)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9630,"(98, 126)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9631,"(98, 127)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"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.",Neutral
9632,"(98, 128)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9633,"(98, 129)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"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.",Neutral
9634,"(98, 130)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9635,"(98, 131)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall delete history of received immunizations.,Neutral
9636,"(98, 132)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9637,"(98, 133)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9638,"(98, 134)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,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.,Neutral
9639,"(98, 135)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system will provide the ability to register patients of all types.,Neutral
9640,"(98, 136)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9641,"(98, 137)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9642,"(98, 138)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9643,"(98, 139)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9644,"(98, 140)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9645,"(98, 141)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9646,"(98, 142)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9647,"(98, 143)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9648,"(98, 144)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9649,"(98, 145)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,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.,Neutral
9650,"(98, 146)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9651,"(98, 147)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9652,"(98, 148)",The system shall allow document types to inherit authorizations from other levels when using classes to assign roles.,"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.",Neutral
9653,"(99, 100)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall allow other VistA applications to access the user class file to determine the role of an employee.,Neutral
9654,"(99, 101)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9655,"(99, 102)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9656,"(99, 103)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9657,"(99, 104)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9658,"(99, 105)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9659,"(99, 106)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9660,"(99, 107)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9661,"(99, 108)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9662,"(99, 109)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9663,"(99, 110)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall allow concurrent membership in more than one User Class.,Neutral
9664,"(99, 111)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall allow membership in only one User Class.,Neutral
9665,"(99, 112)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9666,"(99, 113)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"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.",Neutral
9667,"(99, 114)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall improve accessibility of online clinical information and results.,Neutral
9668,"(99, 115)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"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.",Neutral
9669,"(99, 116)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9670,"(99, 117)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9671,"(99, 118)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9672,"(99, 119)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall make the traditional order entry processes more practical.,Neutral
9673,"(99, 120)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9674,"(99, 121)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9675,"(99, 122)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9676,"(99, 123)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9677,"(99, 124)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"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.",Neutral
9678,"(99, 125)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9679,"(99, 126)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9680,"(99, 127)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"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.",Neutral
9681,"(99, 128)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9682,"(99, 129)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"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.",Neutral
9683,"(99, 130)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9684,"(99, 131)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall delete history of received immunizations.,Neutral
9685,"(99, 132)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9686,"(99, 133)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9687,"(99, 134)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,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.,Neutral
9688,"(99, 135)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system will provide the ability to register patients of all types.,Neutral
9689,"(99, 136)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9690,"(99, 137)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9691,"(99, 138)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9692,"(99, 139)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9693,"(99, 140)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9694,"(99, 141)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9695,"(99, 142)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9696,"(99, 143)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9697,"(99, 144)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9698,"(99, 145)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,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.,Neutral
9699,"(99, 146)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9700,"(99, 147)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9701,"(99, 148)",The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations.,"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.",Neutral
9702,"(100, 101)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall stored the names of users who view remote data in the remote site's database.,Neutral
9703,"(100, 102)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9704,"(100, 103)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9705,"(100, 104)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9706,"(100, 105)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9707,"(100, 106)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9708,"(100, 107)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9709,"(100, 108)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9710,"(100, 109)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9711,"(100, 110)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall allow concurrent membership in more than one User Class.,Neutral
9712,"(100, 111)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall allow membership in only one User Class.,Neutral
9713,"(100, 112)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9714,"(100, 113)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"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.",Neutral
9715,"(100, 114)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall improve accessibility of online clinical information and results.,Neutral
9716,"(100, 115)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"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.",Neutral
9717,"(100, 116)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9718,"(100, 117)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9719,"(100, 118)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9720,"(100, 119)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall make the traditional order entry processes more practical.,Neutral
9721,"(100, 120)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9722,"(100, 121)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9723,"(100, 122)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9724,"(100, 123)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9725,"(100, 124)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"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.",Neutral
9726,"(100, 125)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9727,"(100, 126)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9728,"(100, 127)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"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.",Neutral
9729,"(100, 128)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9730,"(100, 129)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"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.",Neutral
9731,"(100, 130)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9732,"(100, 131)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall delete history of received immunizations.,Neutral
9733,"(100, 132)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9734,"(100, 133)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9735,"(100, 134)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,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.,Neutral
9736,"(100, 135)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system will provide the ability to register patients of all types.,Neutral
9737,"(100, 136)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9738,"(100, 137)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9739,"(100, 138)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9740,"(100, 139)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9741,"(100, 140)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9742,"(100, 141)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9743,"(100, 142)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9744,"(100, 143)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9745,"(100, 144)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9746,"(100, 145)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,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.,Neutral
9747,"(100, 146)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9748,"(100, 147)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9749,"(100, 148)",The system shall allow other VistA applications to access the user class file to determine the role of an employee.,"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.",Neutral
9750,"(101, 102)",The system shall stored the names of users who view remote data in the remote site's database.,"The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",Neutral
9751,"(101, 103)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9752,"(101, 104)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9753,"(101, 105)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9754,"(101, 106)",The system shall stored the names of users who view remote data in the remote site's database.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9755,"(101, 107)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9756,"(101, 108)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9757,"(101, 109)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9758,"(101, 110)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall allow concurrent membership in more than one User Class.,Neutral
9759,"(101, 111)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall allow membership in only one User Class.,Neutral
9760,"(101, 112)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9761,"(101, 113)",The system shall stored the names of users who view remote data in the remote site's database.,"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.",Neutral
9762,"(101, 114)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall improve accessibility of online clinical information and results.,Neutral
9763,"(101, 115)",The system shall stored the names of users who view remote data in the remote site's database.,"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.",Neutral
9764,"(101, 116)",The system shall stored the names of users who view remote data in the remote site's database.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9765,"(101, 117)",The system shall stored the names of users who view remote data in the remote site's database.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9766,"(101, 118)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9767,"(101, 119)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall make the traditional order entry processes more practical.,Neutral
9768,"(101, 120)",The system shall stored the names of users who view remote data in the remote site's database.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9769,"(101, 121)",The system shall stored the names of users who view remote data in the remote site's database.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9770,"(101, 122)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9771,"(101, 123)",The system shall stored the names of users who view remote data in the remote site's database.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9772,"(101, 124)",The system shall stored the names of users who view remote data in the remote site's database.,"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.",Neutral
9773,"(101, 125)",The system shall stored the names of users who view remote data in the remote site's database.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9774,"(101, 126)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9775,"(101, 127)",The system shall stored the names of users who view remote data in the remote site's database.,"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.",Neutral
9776,"(101, 128)",The system shall stored the names of users who view remote data in the remote site's database.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9777,"(101, 129)",The system shall stored the names of users who view remote data in the remote site's database.,"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.",Neutral
9778,"(101, 130)",The system shall stored the names of users who view remote data in the remote site's database.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9779,"(101, 131)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall delete history of received immunizations.,Neutral
9780,"(101, 132)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9781,"(101, 133)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9782,"(101, 134)",The system shall stored the names of users who view remote data in the remote site's database.,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.,Neutral
9783,"(101, 135)",The system shall stored the names of users who view remote data in the remote site's database.,The system will provide the ability to register patients of all types.,Neutral
9784,"(101, 136)",The system shall stored the names of users who view remote data in the remote site's database.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9785,"(101, 137)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9786,"(101, 138)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9787,"(101, 139)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9788,"(101, 140)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9789,"(101, 141)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9790,"(101, 142)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9791,"(101, 143)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9792,"(101, 144)",The system shall stored the names of users who view remote data in the remote site's database.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9793,"(101, 145)",The system shall stored the names of users who view remote data in the remote site's database.,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.,Neutral
9794,"(101, 146)",The system shall stored the names of users who view remote data in the remote site's database.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9795,"(101, 147)",The system shall stored the names of users who view remote data in the remote site's database.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9796,"(101, 148)",The system shall stored the names of users who view remote data in the remote site's database.,"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.",Neutral
9797,"(102, 103)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,Neutral
9798,"(102, 104)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall allow a user to foward notification to someone else at the site.,Neutral
9799,"(102, 105)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9800,"(102, 106)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","The system shall define, populate, and retrieve information about user classes.",Neutral
9801,"(102, 107)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9802,"(102, 108)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9803,"(102, 109)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9804,"(102, 110)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall allow concurrent membership in more than one User Class.,Neutral
9805,"(102, 111)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall allow membership in only one User Class.,Neutral
9806,"(102, 112)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9807,"(102, 113)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","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.",Neutral
9808,"(102, 114)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall improve accessibility of online clinical information and results.,Neutral
9809,"(102, 115)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","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.",Neutral
9810,"(102, 116)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9811,"(102, 117)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9812,"(102, 118)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9813,"(102, 119)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall make the traditional order entry processes more practical.,Neutral
9814,"(102, 120)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9815,"(102, 121)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9816,"(102, 122)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9817,"(102, 123)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9818,"(102, 124)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","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.",Neutral
9819,"(102, 125)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9820,"(102, 126)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9821,"(102, 127)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","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.",Neutral
9822,"(102, 128)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9823,"(102, 129)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","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.",Neutral
9824,"(102, 130)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9825,"(102, 131)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall delete history of received immunizations.,Neutral
9826,"(102, 132)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
9827,"(102, 133)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9828,"(102, 134)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",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.,Neutral
9829,"(102, 135)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system will provide the ability to register patients of all types.,Neutral
9830,"(102, 136)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9831,"(102, 137)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
9832,"(102, 138)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9833,"(102, 139)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9834,"(102, 140)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9835,"(102, 141)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9836,"(102, 142)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9837,"(102, 143)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9838,"(102, 144)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9839,"(102, 145)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",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.,Neutral
9840,"(102, 146)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9841,"(102, 147)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9842,"(102, 148)","The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location.","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.",Neutral
9843,"(103, 104)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall allow a user to foward notification to someone else at the site.,Neutral
9844,"(103, 105)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9845,"(103, 106)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9846,"(103, 107)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9847,"(103, 108)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9848,"(103, 109)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9849,"(103, 110)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall allow concurrent membership in more than one User Class.,Neutral
9850,"(103, 111)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall allow membership in only one User Class.,Neutral
9851,"(103, 112)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9852,"(103, 113)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"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.",Neutral
9853,"(103, 114)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall improve accessibility of online clinical information and results.,Neutral
9854,"(103, 115)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"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.",Neutral
9855,"(103, 116)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9856,"(103, 117)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9857,"(103, 118)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9858,"(103, 119)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall make the traditional order entry processes more practical.,Neutral
9859,"(103, 120)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9860,"(103, 121)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9861,"(103, 122)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9862,"(103, 123)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9863,"(103, 124)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"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.",Neutral
9864,"(103, 125)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9865,"(103, 126)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9866,"(103, 127)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"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.",Neutral
9867,"(103, 128)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9868,"(103, 129)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"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.",Neutral
9869,"(103, 130)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9870,"(103, 131)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall delete history of received immunizations.,Neutral
9871,"(103, 132)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9872,"(103, 133)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9873,"(103, 134)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,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.,Neutral
9874,"(103, 135)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system will provide the ability to register patients of all types.,Neutral
9875,"(103, 136)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9876,"(103, 137)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9877,"(103, 138)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9878,"(103, 139)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9879,"(103, 140)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9880,"(103, 141)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9881,"(103, 142)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9882,"(103, 143)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9883,"(103, 144)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9884,"(103, 145)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,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.,Neutral
9885,"(103, 146)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9886,"(103, 147)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9887,"(103, 148)",The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it.,"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.",Neutral
9888,"(104, 105)",The system shall allow a user to foward notification to someone else at the site.,The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,Neutral
9889,"(104, 106)",The system shall allow a user to foward notification to someone else at the site.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9890,"(104, 107)",The system shall allow a user to foward notification to someone else at the site.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9891,"(104, 108)",The system shall allow a user to foward notification to someone else at the site.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9892,"(104, 109)",The system shall allow a user to foward notification to someone else at the site.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9893,"(104, 110)",The system shall allow a user to foward notification to someone else at the site.,The system shall allow concurrent membership in more than one User Class.,Neutral
9894,"(104, 111)",The system shall allow a user to foward notification to someone else at the site.,The system shall allow membership in only one User Class.,Neutral
9895,"(104, 112)",The system shall allow a user to foward notification to someone else at the site.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9896,"(104, 113)",The system shall allow a user to foward notification to someone else at the site.,"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.",Neutral
9897,"(104, 114)",The system shall allow a user to foward notification to someone else at the site.,The system shall improve accessibility of online clinical information and results.,Neutral
9898,"(104, 115)",The system shall allow a user to foward notification to someone else at the site.,"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.",Neutral
9899,"(104, 116)",The system shall allow a user to foward notification to someone else at the site.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9900,"(104, 117)",The system shall allow a user to foward notification to someone else at the site.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9901,"(104, 118)",The system shall allow a user to foward notification to someone else at the site.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9902,"(104, 119)",The system shall allow a user to foward notification to someone else at the site.,The system shall make the traditional order entry processes more practical.,Neutral
9903,"(104, 120)",The system shall allow a user to foward notification to someone else at the site.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9904,"(104, 121)",The system shall allow a user to foward notification to someone else at the site.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9905,"(104, 122)",The system shall allow a user to foward notification to someone else at the site.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9906,"(104, 123)",The system shall allow a user to foward notification to someone else at the site.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9907,"(104, 124)",The system shall allow a user to foward notification to someone else at the site.,"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.",Neutral
9908,"(104, 125)",The system shall allow a user to foward notification to someone else at the site.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9909,"(104, 126)",The system shall allow a user to foward notification to someone else at the site.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9910,"(104, 127)",The system shall allow a user to foward notification to someone else at the site.,"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.",Neutral
9911,"(104, 128)",The system shall allow a user to foward notification to someone else at the site.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9912,"(104, 129)",The system shall allow a user to foward notification to someone else at the site.,"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.",Neutral
9913,"(104, 130)",The system shall allow a user to foward notification to someone else at the site.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9914,"(104, 131)",The system shall allow a user to foward notification to someone else at the site.,The system shall delete history of received immunizations.,Neutral
9915,"(104, 132)",The system shall allow a user to foward notification to someone else at the site.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9916,"(104, 133)",The system shall allow a user to foward notification to someone else at the site.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9917,"(104, 134)",The system shall allow a user to foward notification to someone else at the site.,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.,Neutral
9918,"(104, 135)",The system shall allow a user to foward notification to someone else at the site.,The system will provide the ability to register patients of all types.,Neutral
9919,"(104, 136)",The system shall allow a user to foward notification to someone else at the site.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9920,"(104, 137)",The system shall allow a user to foward notification to someone else at the site.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9921,"(104, 138)",The system shall allow a user to foward notification to someone else at the site.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9922,"(104, 139)",The system shall allow a user to foward notification to someone else at the site.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9923,"(104, 140)",The system shall allow a user to foward notification to someone else at the site.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9924,"(104, 141)",The system shall allow a user to foward notification to someone else at the site.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9925,"(104, 142)",The system shall allow a user to foward notification to someone else at the site.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9926,"(104, 143)",The system shall allow a user to foward notification to someone else at the site.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9927,"(104, 144)",The system shall allow a user to foward notification to someone else at the site.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9928,"(104, 145)",The system shall allow a user to foward notification to someone else at the site.,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.,Neutral
9929,"(104, 146)",The system shall allow a user to foward notification to someone else at the site.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9930,"(104, 147)",The system shall allow a user to foward notification to someone else at the site.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9931,"(104, 148)",The system shall allow a user to foward notification to someone else at the site.,"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.",Neutral
9932,"(105, 106)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"The system shall define, populate, and retrieve information about user classes.",Neutral
9933,"(105, 107)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9934,"(105, 108)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9935,"(105, 109)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9936,"(105, 110)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall allow concurrent membership in more than one User Class.,Neutral
9937,"(105, 111)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall allow membership in only one User Class.,Neutral
9938,"(105, 112)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9939,"(105, 113)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"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.",Neutral
9940,"(105, 114)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall improve accessibility of online clinical information and results.,Neutral
9941,"(105, 115)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"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.",Neutral
9942,"(105, 116)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9943,"(105, 117)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9944,"(105, 118)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9945,"(105, 119)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall make the traditional order entry processes more practical.,Neutral
9946,"(105, 120)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9947,"(105, 121)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9948,"(105, 122)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9949,"(105, 123)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9950,"(105, 124)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"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.",Neutral
9951,"(105, 125)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9952,"(105, 126)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9953,"(105, 127)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"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.",Neutral
9954,"(105, 128)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9955,"(105, 129)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"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.",Neutral
9956,"(105, 130)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9957,"(105, 131)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall delete history of received immunizations.,Neutral
9958,"(105, 132)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
9959,"(105, 133)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
9960,"(105, 134)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,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.,Neutral
9961,"(105, 135)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system will provide the ability to register patients of all types.,Neutral
9962,"(105, 136)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
9963,"(105, 137)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
9964,"(105, 138)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
9965,"(105, 139)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
9966,"(105, 140)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
9967,"(105, 141)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
9968,"(105, 142)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
9969,"(105, 143)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
9970,"(105, 144)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
9971,"(105, 145)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,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.,Neutral
9972,"(105, 146)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
9973,"(105, 147)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
9974,"(105, 148)",The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed.,"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.",Neutral
9975,"(106, 107)","The system shall define, populate, and retrieve information about user classes.",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9976,"(106, 108)","The system shall define, populate, and retrieve information about user classes.",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Neutral
9977,"(106, 109)","The system shall define, populate, and retrieve information about user classes.",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
9978,"(106, 110)","The system shall define, populate, and retrieve information about user classes.",The system shall allow concurrent membership in more than one User Class.,Neutral
9979,"(106, 111)","The system shall define, populate, and retrieve information about user classes.",The system shall allow membership in only one User Class.,Neutral
9980,"(106, 112)","The system shall define, populate, and retrieve information about user classes.",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
9981,"(106, 113)","The system shall define, populate, and retrieve information about user classes.","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.",Neutral
9982,"(106, 114)","The system shall define, populate, and retrieve information about user classes.",The system shall improve accessibility of online clinical information and results.,Neutral
9983,"(106, 115)","The system shall define, populate, and retrieve information about user classes.","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.",Neutral
9984,"(106, 116)","The system shall define, populate, and retrieve information about user classes.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
9985,"(106, 117)","The system shall define, populate, and retrieve information about user classes.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
9986,"(106, 118)","The system shall define, populate, and retrieve information about user classes.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
9987,"(106, 119)","The system shall define, populate, and retrieve information about user classes.",The system shall make the traditional order entry processes more practical.,Neutral
9988,"(106, 120)","The system shall define, populate, and retrieve information about user classes.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
9989,"(106, 121)","The system shall define, populate, and retrieve information about user classes.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
9990,"(106, 122)","The system shall define, populate, and retrieve information about user classes.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
9991,"(106, 123)","The system shall define, populate, and retrieve information about user classes.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
9992,"(106, 124)","The system shall define, populate, and retrieve information about user classes.","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.",Neutral
9993,"(106, 125)","The system shall define, populate, and retrieve information about user classes.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
9994,"(106, 126)","The system shall define, populate, and retrieve information about user classes.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
9995,"(106, 127)","The system shall define, populate, and retrieve information about user classes.","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.",Neutral
9996,"(106, 128)","The system shall define, populate, and retrieve information about user classes.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
9997,"(106, 129)","The system shall define, populate, and retrieve information about user classes.","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.",Neutral
9998,"(106, 130)","The system shall define, populate, and retrieve information about user classes.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
9999,"(106, 131)","The system shall define, populate, and retrieve information about user classes.",The system shall delete history of received immunizations.,Neutral
10000,"(106, 132)","The system shall define, populate, and retrieve information about user classes.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
10001,"(106, 133)","The system shall define, populate, and retrieve information about user classes.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10002,"(106, 134)","The system shall define, populate, and retrieve information about user classes.",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.,Neutral
10003,"(106, 135)","The system shall define, populate, and retrieve information about user classes.",The system will provide the ability to register patients of all types.,Neutral
10004,"(106, 136)","The system shall define, populate, and retrieve information about user classes.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10005,"(106, 137)","The system shall define, populate, and retrieve information about user classes.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10006,"(106, 138)","The system shall define, populate, and retrieve information about user classes.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10007,"(106, 139)","The system shall define, populate, and retrieve information about user classes.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10008,"(106, 140)","The system shall define, populate, and retrieve information about user classes.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10009,"(106, 141)","The system shall define, populate, and retrieve information about user classes.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10010,"(106, 142)","The system shall define, populate, and retrieve information about user classes.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10011,"(106, 143)","The system shall define, populate, and retrieve information about user classes.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10012,"(106, 144)","The system shall define, populate, and retrieve information about user classes.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10013,"(106, 145)","The system shall define, populate, and retrieve information about user classes.",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.,Neutral
10014,"(106, 146)","The system shall define, populate, and retrieve information about user classes.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10015,"(106, 147)","The system shall define, populate, and retrieve information about user classes.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10016,"(106, 148)","The system shall define, populate, and retrieve information about user classes.","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.",Neutral
10017,"(107, 108)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,Conflict
10018,"(107, 109)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
10019,"(107, 110)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall allow concurrent membership in more than one User Class.,Neutral
10020,"(107, 111)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall allow membership in only one User Class.,Neutral
10021,"(107, 112)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
10022,"(107, 113)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"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.",Neutral
10023,"(107, 114)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall improve accessibility of online clinical information and results.,Neutral
10024,"(107, 115)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"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.",Neutral
10025,"(107, 116)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
10026,"(107, 117)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
10027,"(107, 118)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
10028,"(107, 119)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall make the traditional order entry processes more practical.,Neutral
10029,"(107, 120)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10030,"(107, 121)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10031,"(107, 122)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10032,"(107, 123)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10033,"(107, 124)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"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.",Neutral
10034,"(107, 125)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10035,"(107, 126)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10036,"(107, 127)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"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.",Neutral
10037,"(107, 128)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10038,"(107, 129)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"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.",Neutral
10039,"(107, 130)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10040,"(107, 131)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall delete history of received immunizations.,Neutral
10041,"(107, 132)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10042,"(107, 133)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10043,"(107, 134)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,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.,Neutral
10044,"(107, 135)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system will provide the ability to register patients of all types.,Neutral
10045,"(107, 136)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10046,"(107, 137)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10047,"(107, 138)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10048,"(107, 139)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10049,"(107, 140)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10050,"(107, 141)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10051,"(107, 142)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10052,"(107, 143)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10053,"(107, 144)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10054,"(107, 145)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,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.,Neutral
10055,"(107, 146)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10056,"(107, 147)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10057,"(107, 148)",The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure.,"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.",Neutral
10058,"(108, 109)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,Neutral
10059,"(108, 110)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall allow concurrent membership in more than one User Class.,Neutral
10060,"(108, 111)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall allow membership in only one User Class.,Neutral
10061,"(108, 112)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
10062,"(108, 113)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"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.",Neutral
10063,"(108, 114)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall improve accessibility of online clinical information and results.,Neutral
10064,"(108, 115)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"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.",Neutral
10065,"(108, 116)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
10066,"(108, 117)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
10067,"(108, 118)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
10068,"(108, 119)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall make the traditional order entry processes more practical.,Neutral
10069,"(108, 120)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10070,"(108, 121)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10071,"(108, 122)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10072,"(108, 123)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10073,"(108, 124)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"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.",Neutral
10074,"(108, 125)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10075,"(108, 126)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10076,"(108, 127)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"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.",Neutral
10077,"(108, 128)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10078,"(108, 129)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"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.",Neutral
10079,"(108, 130)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10080,"(108, 131)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall delete history of received immunizations.,Neutral
10081,"(108, 132)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10082,"(108, 133)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10083,"(108, 134)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,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.,Neutral
10084,"(108, 135)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system will provide the ability to register patients of all types.,Neutral
10085,"(108, 136)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10086,"(108, 137)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10087,"(108, 138)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10088,"(108, 139)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10089,"(108, 140)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10090,"(108, 141)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10091,"(108, 142)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10092,"(108, 143)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10093,"(108, 144)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10094,"(108, 145)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,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.,Neutral
10095,"(108, 146)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10096,"(108, 147)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10097,"(108, 148)",The system shall allow 100 hierarchies of subclasses to be created in the User Hierarchy Class structure.,"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.",Neutral
10098,"(109, 110)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall allow concurrent membership in more than one User Class.,Neutral
10099,"(109, 111)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall allow membership in only one User Class.,Neutral
10100,"(109, 112)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
10101,"(109, 113)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"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.",Neutral
10102,"(109, 114)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall improve accessibility of online clinical information and results.,Neutral
10103,"(109, 115)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"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.",Neutral
10104,"(109, 116)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
10105,"(109, 117)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
10106,"(109, 118)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
10107,"(109, 119)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall make the traditional order entry processes more practical.,Neutral
10108,"(109, 120)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10109,"(109, 121)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10110,"(109, 122)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10111,"(109, 123)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10112,"(109, 124)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"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.",Neutral
10113,"(109, 125)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10114,"(109, 126)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10115,"(109, 127)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"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.",Neutral
10116,"(109, 128)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10117,"(109, 129)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"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.",Neutral
10118,"(109, 130)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10119,"(109, 131)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall delete history of received immunizations.,Neutral
10120,"(109, 132)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10121,"(109, 133)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10122,"(109, 134)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,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.,Neutral
10123,"(109, 135)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system will provide the ability to register patients of all types.,Neutral
10124,"(109, 136)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10125,"(109, 137)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10126,"(109, 138)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10127,"(109, 139)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10128,"(109, 140)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10129,"(109, 141)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10130,"(109, 142)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10131,"(109, 143)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10132,"(109, 144)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10133,"(109, 145)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,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.,Neutral
10134,"(109, 146)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10135,"(109, 147)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10136,"(109, 148)",The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop.,"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.",Neutral
10137,"(110, 111)",The system shall allow concurrent membership in more than one User Class.,The system shall allow membership in only one User Class.,Conflict
10138,"(110, 112)",The system shall allow concurrent membership in more than one User Class.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
10139,"(110, 113)",The system shall allow concurrent membership in more than one User Class.,"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.",Neutral
10140,"(110, 114)",The system shall allow concurrent membership in more than one User Class.,The system shall improve accessibility of online clinical information and results.,Neutral
10141,"(110, 115)",The system shall allow concurrent membership in more than one User Class.,"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.",Neutral
10142,"(110, 116)",The system shall allow concurrent membership in more than one User Class.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
10143,"(110, 117)",The system shall allow concurrent membership in more than one User Class.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
10144,"(110, 118)",The system shall allow concurrent membership in more than one User Class.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
10145,"(110, 119)",The system shall allow concurrent membership in more than one User Class.,The system shall make the traditional order entry processes more practical.,Neutral
10146,"(110, 120)",The system shall allow concurrent membership in more than one User Class.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10147,"(110, 121)",The system shall allow concurrent membership in more than one User Class.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10148,"(110, 122)",The system shall allow concurrent membership in more than one User Class.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10149,"(110, 123)",The system shall allow concurrent membership in more than one User Class.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10150,"(110, 124)",The system shall allow concurrent membership in more than one User Class.,"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.",Neutral
10151,"(110, 125)",The system shall allow concurrent membership in more than one User Class.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10152,"(110, 126)",The system shall allow concurrent membership in more than one User Class.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10153,"(110, 127)",The system shall allow concurrent membership in more than one User Class.,"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.",Neutral
10154,"(110, 128)",The system shall allow concurrent membership in more than one User Class.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10155,"(110, 129)",The system shall allow concurrent membership in more than one User Class.,"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.",Neutral
10156,"(110, 130)",The system shall allow concurrent membership in more than one User Class.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10157,"(110, 131)",The system shall allow concurrent membership in more than one User Class.,The system shall delete history of received immunizations.,Neutral
10158,"(110, 132)",The system shall allow concurrent membership in more than one User Class.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10159,"(110, 133)",The system shall allow concurrent membership in more than one User Class.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10160,"(110, 134)",The system shall allow concurrent membership in more than one User Class.,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.,Neutral
10161,"(110, 135)",The system shall allow concurrent membership in more than one User Class.,The system will provide the ability to register patients of all types.,Neutral
10162,"(110, 136)",The system shall allow concurrent membership in more than one User Class.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10163,"(110, 137)",The system shall allow concurrent membership in more than one User Class.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10164,"(110, 138)",The system shall allow concurrent membership in more than one User Class.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10165,"(110, 139)",The system shall allow concurrent membership in more than one User Class.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10166,"(110, 140)",The system shall allow concurrent membership in more than one User Class.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10167,"(110, 141)",The system shall allow concurrent membership in more than one User Class.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10168,"(110, 142)",The system shall allow concurrent membership in more than one User Class.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10169,"(110, 143)",The system shall allow concurrent membership in more than one User Class.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10170,"(110, 144)",The system shall allow concurrent membership in more than one User Class.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10171,"(110, 145)",The system shall allow concurrent membership in more than one User Class.,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.,Neutral
10172,"(110, 146)",The system shall allow concurrent membership in more than one User Class.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10173,"(110, 147)",The system shall allow concurrent membership in more than one User Class.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10174,"(110, 148)",The system shall allow concurrent membership in more than one User Class.,"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.",Neutral
10175,"(111, 112)",The system shall allow membership in only one User Class.,The system shall automatically include membership in a given User Class to all member of subclasses of that class.,Neutral
10176,"(111, 113)",The system shall allow membership in only one User Class.,"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.",Neutral
10177,"(111, 114)",The system shall allow membership in only one User Class.,The system shall improve accessibility of online clinical information and results.,Neutral
10178,"(111, 115)",The system shall allow membership in only one User Class.,"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.",Neutral
10179,"(111, 116)",The system shall allow membership in only one User Class.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
10180,"(111, 117)",The system shall allow membership in only one User Class.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
10181,"(111, 118)",The system shall allow membership in only one User Class.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
10182,"(111, 119)",The system shall allow membership in only one User Class.,The system shall make the traditional order entry processes more practical.,Neutral
10183,"(111, 120)",The system shall allow membership in only one User Class.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10184,"(111, 121)",The system shall allow membership in only one User Class.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10185,"(111, 122)",The system shall allow membership in only one User Class.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10186,"(111, 123)",The system shall allow membership in only one User Class.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10187,"(111, 124)",The system shall allow membership in only one User Class.,"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.",Neutral
10188,"(111, 125)",The system shall allow membership in only one User Class.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10189,"(111, 126)",The system shall allow membership in only one User Class.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10190,"(111, 127)",The system shall allow membership in only one User Class.,"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.",Neutral
10191,"(111, 128)",The system shall allow membership in only one User Class.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10192,"(111, 129)",The system shall allow membership in only one User Class.,"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.",Neutral
10193,"(111, 130)",The system shall allow membership in only one User Class.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10194,"(111, 131)",The system shall allow membership in only one User Class.,The system shall delete history of received immunizations.,Neutral
10195,"(111, 132)",The system shall allow membership in only one User Class.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10196,"(111, 133)",The system shall allow membership in only one User Class.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10197,"(111, 134)",The system shall allow membership in only one User Class.,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.,Neutral
10198,"(111, 135)",The system shall allow membership in only one User Class.,The system will provide the ability to register patients of all types.,Neutral
10199,"(111, 136)",The system shall allow membership in only one User Class.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10200,"(111, 137)",The system shall allow membership in only one User Class.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10201,"(111, 138)",The system shall allow membership in only one User Class.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10202,"(111, 139)",The system shall allow membership in only one User Class.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10203,"(111, 140)",The system shall allow membership in only one User Class.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10204,"(111, 141)",The system shall allow membership in only one User Class.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10205,"(111, 142)",The system shall allow membership in only one User Class.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10206,"(111, 143)",The system shall allow membership in only one User Class.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10207,"(111, 144)",The system shall allow membership in only one User Class.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10208,"(111, 145)",The system shall allow membership in only one User Class.,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.,Neutral
10209,"(111, 146)",The system shall allow membership in only one User Class.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10210,"(111, 147)",The system shall allow membership in only one User Class.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10211,"(111, 148)",The system shall allow membership in only one User Class.,"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.",Neutral
10212,"(112, 113)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"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.",Neutral
10213,"(112, 114)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall improve accessibility of online clinical information and results.,Neutral
10214,"(112, 115)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"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.",Neutral
10215,"(112, 116)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
10216,"(112, 117)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
10217,"(112, 118)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
10218,"(112, 119)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall make the traditional order entry processes more practical.,Neutral
10219,"(112, 120)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10220,"(112, 121)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10221,"(112, 122)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10222,"(112, 123)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10223,"(112, 124)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"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.",Neutral
10224,"(112, 125)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10225,"(112, 126)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10226,"(112, 127)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"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.",Neutral
10227,"(112, 128)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10228,"(112, 129)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"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.",Neutral
10229,"(112, 130)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10230,"(112, 131)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall delete history of received immunizations.,Neutral
10231,"(112, 132)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10232,"(112, 133)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10233,"(112, 134)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,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.,Neutral
10234,"(112, 135)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system will provide the ability to register patients of all types.,Neutral
10235,"(112, 136)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10236,"(112, 137)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10237,"(112, 138)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10238,"(112, 139)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10239,"(112, 140)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10240,"(112, 141)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10241,"(112, 142)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10242,"(112, 143)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10243,"(112, 144)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10244,"(112, 145)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,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.,Neutral
10245,"(112, 146)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10246,"(112, 147)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10247,"(112, 148)",The system shall automatically include membership in a given User Class to all member of subclasses of that class.,"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.",Neutral
10248,"(113, 114)","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.",The system shall improve accessibility of online clinical information and results.,Neutral
10249,"(113, 115)","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.","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.",Neutral
10250,"(113, 116)","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.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
10251,"(113, 117)","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.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
10252,"(113, 118)","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.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
10253,"(113, 119)","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.",The system shall make the traditional order entry processes more practical.,Neutral
10254,"(113, 120)","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.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10255,"(113, 121)","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.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10256,"(113, 122)","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.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10257,"(113, 123)","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.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10258,"(113, 124)","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.","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.",Neutral
10259,"(113, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10260,"(113, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10261,"(113, 127)","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.","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.",Neutral
10262,"(113, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10263,"(113, 129)","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.","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.",Neutral
10264,"(113, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10265,"(113, 131)","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.",The system shall delete history of received immunizations.,Neutral
10266,"(113, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
10267,"(113, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10268,"(113, 134)","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.",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.,Neutral
10269,"(113, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
10270,"(113, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10271,"(113, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10272,"(113, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10273,"(113, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10274,"(113, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10275,"(113, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10276,"(113, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10277,"(113, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10278,"(113, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10279,"(113, 145)","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.",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.,Neutral
10280,"(113, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10281,"(113, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10282,"(113, 148)","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.","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.",Neutral
10283,"(114, 115)",The system shall improve accessibility of online clinical information and results.,"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.",Neutral
10284,"(114, 116)",The system shall improve accessibility of online clinical information and results.,"The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
10285,"(114, 117)",The system shall improve accessibility of online clinical information and results.,"The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
10286,"(114, 118)",The system shall improve accessibility of online clinical information and results.,The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
10287,"(114, 119)",The system shall improve accessibility of online clinical information and results.,The system shall make the traditional order entry processes more practical.,Neutral
10288,"(114, 120)",The system shall improve accessibility of online clinical information and results.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10289,"(114, 121)",The system shall improve accessibility of online clinical information and results.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10290,"(114, 122)",The system shall improve accessibility of online clinical information and results.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10291,"(114, 123)",The system shall improve accessibility of online clinical information and results.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10292,"(114, 124)",The system shall improve accessibility of online clinical information and results.,"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.",Neutral
10293,"(114, 125)",The system shall improve accessibility of online clinical information and results.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10294,"(114, 126)",The system shall improve accessibility of online clinical information and results.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10295,"(114, 127)",The system shall improve accessibility of online clinical information and results.,"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.",Neutral
10296,"(114, 128)",The system shall improve accessibility of online clinical information and results.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10297,"(114, 129)",The system shall improve accessibility of online clinical information and results.,"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.",Neutral
10298,"(114, 130)",The system shall improve accessibility of online clinical information and results.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10299,"(114, 131)",The system shall improve accessibility of online clinical information and results.,The system shall delete history of received immunizations.,Neutral
10300,"(114, 132)",The system shall improve accessibility of online clinical information and results.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10301,"(114, 133)",The system shall improve accessibility of online clinical information and results.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10302,"(114, 134)",The system shall improve accessibility of online clinical information and results.,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.,Neutral
10303,"(114, 135)",The system shall improve accessibility of online clinical information and results.,The system will provide the ability to register patients of all types.,Neutral
10304,"(114, 136)",The system shall improve accessibility of online clinical information and results.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10305,"(114, 137)",The system shall improve accessibility of online clinical information and results.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10306,"(114, 138)",The system shall improve accessibility of online clinical information and results.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10307,"(114, 139)",The system shall improve accessibility of online clinical information and results.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10308,"(114, 140)",The system shall improve accessibility of online clinical information and results.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10309,"(114, 141)",The system shall improve accessibility of online clinical information and results.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10310,"(114, 142)",The system shall improve accessibility of online clinical information and results.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10311,"(114, 143)",The system shall improve accessibility of online clinical information and results.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10312,"(114, 144)",The system shall improve accessibility of online clinical information and results.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10313,"(114, 145)",The system shall improve accessibility of online clinical information and results.,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.,Neutral
10314,"(114, 146)",The system shall improve accessibility of online clinical information and results.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10315,"(114, 147)",The system shall improve accessibility of online clinical information and results.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10316,"(114, 148)",The system shall improve accessibility of online clinical information and results.,"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.",Neutral
10317,"(115, 116)","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.","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",Neutral
10318,"(115, 117)","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.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
10319,"(115, 118)","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.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
10320,"(115, 119)","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.",The system shall make the traditional order entry processes more practical.,Neutral
10321,"(115, 120)","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.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10322,"(115, 121)","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.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10323,"(115, 122)","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.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10324,"(115, 123)","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.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10325,"(115, 124)","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.","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.",Neutral
10326,"(115, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10327,"(115, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10328,"(115, 127)","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.","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.",Neutral
10329,"(115, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10330,"(115, 129)","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.","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.",Neutral
10331,"(115, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10332,"(115, 131)","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.",The system shall delete history of received immunizations.,Neutral
10333,"(115, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
10334,"(115, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10335,"(115, 134)","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.",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.,Neutral
10336,"(115, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
10337,"(115, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10338,"(115, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10339,"(115, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10340,"(115, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10341,"(115, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10342,"(115, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10343,"(115, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10344,"(115, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10345,"(115, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10346,"(115, 145)","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.",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.,Neutral
10347,"(115, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10348,"(115, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10349,"(115, 148)","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.","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.",Neutral
10350,"(116, 117)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",Neutral
10351,"(116, 118)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
10352,"(116, 119)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall make the traditional order entry processes more practical.,Neutral
10353,"(116, 120)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10354,"(116, 121)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10355,"(116, 122)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10356,"(116, 123)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10357,"(116, 124)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.","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.",Neutral
10358,"(116, 125)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10359,"(116, 126)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10360,"(116, 127)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.","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.",Neutral
10361,"(116, 128)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10362,"(116, 129)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.","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.",Neutral
10363,"(116, 130)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10364,"(116, 131)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall delete history of received immunizations.,Neutral
10365,"(116, 132)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
10366,"(116, 133)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10367,"(116, 134)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",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.,Neutral
10368,"(116, 135)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system will provide the ability to register patients of all types.,Neutral
10369,"(116, 136)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10370,"(116, 137)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10371,"(116, 138)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10372,"(116, 139)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10373,"(116, 140)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10374,"(116, 141)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10375,"(116, 142)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10376,"(116, 143)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10377,"(116, 144)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10378,"(116, 145)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",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.,Neutral
10379,"(116, 146)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10380,"(116, 147)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10381,"(116, 148)","The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose.","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.",Neutral
10382,"(117, 118)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,Neutral
10383,"(117, 119)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall make the traditional order entry processes more practical.,Neutral
10384,"(117, 120)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10385,"(117, 121)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10386,"(117, 122)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10387,"(117, 123)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10388,"(117, 124)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.","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.",Neutral
10389,"(117, 125)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10390,"(117, 126)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10391,"(117, 127)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.","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.",Neutral
10392,"(117, 128)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10393,"(117, 129)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.","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.",Neutral
10394,"(117, 130)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10395,"(117, 131)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall delete history of received immunizations.,Neutral
10396,"(117, 132)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
10397,"(117, 133)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10398,"(117, 134)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",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.,Neutral
10399,"(117, 135)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system will provide the ability to register patients of all types.,Neutral
10400,"(117, 136)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10401,"(117, 137)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10402,"(117, 138)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10403,"(117, 139)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10404,"(117, 140)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10405,"(117, 141)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10406,"(117, 142)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10407,"(117, 143)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10408,"(117, 144)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10409,"(117, 145)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",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.,Neutral
10410,"(117, 146)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10411,"(117, 147)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10412,"(117, 148)","The system shall integrate orders with progress notes, results, procedures, diagnosis, and Problem List.","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.",Neutral
10413,"(118, 119)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall make the traditional order entry processes more practical.,Conflict
10414,"(118, 120)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10415,"(118, 121)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10416,"(118, 122)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10417,"(118, 123)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10418,"(118, 124)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,"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.",Neutral
10419,"(118, 125)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10420,"(118, 126)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10421,"(118, 127)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,"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.",Neutral
10422,"(118, 128)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10423,"(118, 129)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,"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.",Neutral
10424,"(118, 130)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10425,"(118, 131)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall delete history of received immunizations.,Neutral
10426,"(118, 132)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10427,"(118, 133)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10428,"(118, 134)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,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.,Neutral
10429,"(118, 135)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system will provide the ability to register patients of all types.,Neutral
10430,"(118, 136)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10431,"(118, 137)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10432,"(118, 138)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10433,"(118, 139)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10434,"(118, 140)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10435,"(118, 141)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10436,"(118, 142)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10437,"(118, 143)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10438,"(118, 144)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10439,"(118, 145)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,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.,Neutral
10440,"(118, 146)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10441,"(118, 147)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10442,"(118, 148)",The system shall mimic traditional order entry processes where necessary to accommodate established clinical practices.,"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.",Neutral
10443,"(119, 120)",The system shall make the traditional order entry processes more practical.,The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,Neutral
10444,"(119, 121)",The system shall make the traditional order entry processes more practical.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Neutral
10445,"(119, 122)",The system shall make the traditional order entry processes more practical.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10446,"(119, 123)",The system shall make the traditional order entry processes more practical.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10447,"(119, 124)",The system shall make the traditional order entry processes more practical.,"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.",Neutral
10448,"(119, 125)",The system shall make the traditional order entry processes more practical.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10449,"(119, 126)",The system shall make the traditional order entry processes more practical.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10450,"(119, 127)",The system shall make the traditional order entry processes more practical.,"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.",Neutral
10451,"(119, 128)",The system shall make the traditional order entry processes more practical.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10452,"(119, 129)",The system shall make the traditional order entry processes more practical.,"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.",Neutral
10453,"(119, 130)",The system shall make the traditional order entry processes more practical.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10454,"(119, 131)",The system shall make the traditional order entry processes more practical.,The system shall delete history of received immunizations.,Neutral
10455,"(119, 132)",The system shall make the traditional order entry processes more practical.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10456,"(119, 133)",The system shall make the traditional order entry processes more practical.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10457,"(119, 134)",The system shall make the traditional order entry processes more practical.,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.,Neutral
10458,"(119, 135)",The system shall make the traditional order entry processes more practical.,The system will provide the ability to register patients of all types.,Neutral
10459,"(119, 136)",The system shall make the traditional order entry processes more practical.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10460,"(119, 137)",The system shall make the traditional order entry processes more practical.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10461,"(119, 138)",The system shall make the traditional order entry processes more practical.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10462,"(119, 139)",The system shall make the traditional order entry processes more practical.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10463,"(119, 140)",The system shall make the traditional order entry processes more practical.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10464,"(119, 141)",The system shall make the traditional order entry processes more practical.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10465,"(119, 142)",The system shall make the traditional order entry processes more practical.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10466,"(119, 143)",The system shall make the traditional order entry processes more practical.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10467,"(119, 144)",The system shall make the traditional order entry processes more practical.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10468,"(119, 145)",The system shall make the traditional order entry processes more practical.,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.,Neutral
10469,"(119, 146)",The system shall make the traditional order entry processes more practical.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10470,"(119, 147)",The system shall make the traditional order entry processes more practical.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10471,"(119, 148)",The system shall make the traditional order entry processes more practical.,"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.",Neutral
10472,"(120, 121)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,Conflict
10473,"(120, 122)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10474,"(120, 123)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10475,"(120, 124)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,"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.",Neutral
10476,"(120, 125)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10477,"(120, 126)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10478,"(120, 127)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,"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.",Neutral
10479,"(120, 128)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10480,"(120, 129)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,"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.",Neutral
10481,"(120, 130)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10482,"(120, 131)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall delete history of received immunizations.,Neutral
10483,"(120, 132)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10484,"(120, 133)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10485,"(120, 134)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,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.,Neutral
10486,"(120, 135)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system will provide the ability to register patients of all types.,Neutral
10487,"(120, 136)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10488,"(120, 137)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10489,"(120, 138)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10490,"(120, 139)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10491,"(120, 140)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10492,"(120, 141)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10493,"(120, 142)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10494,"(120, 143)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10495,"(120, 144)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10496,"(120, 145)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,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.,Neutral
10497,"(120, 146)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10498,"(120, 147)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10499,"(120, 148)",The system's design shall follow hospital work flow patterns and allow local site and individual customization to make it fit specific needs.,"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.",Neutral
10500,"(121, 122)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,Neutral
10501,"(121, 123)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10502,"(121, 124)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,"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.",Neutral
10503,"(121, 125)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10504,"(121, 126)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10505,"(121, 127)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,"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.",Neutral
10506,"(121, 128)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10507,"(121, 129)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,"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.",Neutral
10508,"(121, 130)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10509,"(121, 131)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall delete history of received immunizations.,Neutral
10510,"(121, 132)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10511,"(121, 133)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10512,"(121, 134)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,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.,Neutral
10513,"(121, 135)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system will provide the ability to register patients of all types.,Neutral
10514,"(121, 136)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10515,"(121, 137)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10516,"(121, 138)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10517,"(121, 139)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10518,"(121, 140)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10519,"(121, 141)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10520,"(121, 142)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10521,"(121, 143)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10522,"(121, 144)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10523,"(121, 145)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,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.,Neutral
10524,"(121, 146)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10525,"(121, 147)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10526,"(121, 148)",The system's design shall follow hospital work flow patterns while minimizing individual customization in order to make the system similar across practises.,"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.",Neutral
10527,"(122, 123)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,"The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",Neutral
10528,"(122, 124)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,"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.",Neutral
10529,"(122, 125)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,"The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10530,"(122, 126)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10531,"(122, 127)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,"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.",Neutral
10532,"(122, 128)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10533,"(122, 129)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,"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.",Neutral
10534,"(122, 130)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10535,"(122, 131)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system shall delete history of received immunizations.,Neutral
10536,"(122, 132)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10537,"(122, 133)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10538,"(122, 134)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,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.,Neutral
10539,"(122, 135)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system will provide the ability to register patients of all types.,Neutral
10540,"(122, 136)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10541,"(122, 137)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10542,"(122, 138)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10543,"(122, 139)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10544,"(122, 140)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10545,"(122, 141)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10546,"(122, 142)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10547,"(122, 143)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10548,"(122, 144)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10549,"(122, 145)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,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.,Neutral
10550,"(122, 146)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10551,"(122, 147)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10552,"(122, 148)",The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting.,"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.",Neutral
10553,"(123, 124)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.","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.",Neutral
10554,"(123, 125)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10555,"(123, 126)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10556,"(123, 127)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.","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.",Neutral
10557,"(123, 128)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10558,"(123, 129)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.","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.",Neutral
10559,"(123, 130)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10560,"(123, 131)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system shall delete history of received immunizations.,Neutral
10561,"(123, 132)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
10562,"(123, 133)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10563,"(123, 134)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",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.,Neutral
10564,"(123, 135)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system will provide the ability to register patients of all types.,Neutral
10565,"(123, 136)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10566,"(123, 137)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10567,"(123, 138)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10568,"(123, 139)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10569,"(123, 140)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10570,"(123, 141)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10571,"(123, 142)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10572,"(123, 143)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10573,"(123, 144)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10574,"(123, 145)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",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.,Neutral
10575,"(123, 146)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10576,"(123, 147)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10577,"(123, 148)","The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on.","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.",Neutral
10578,"(124, 125)","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.","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",Neutral
10579,"(124, 126)","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.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10580,"(124, 127)","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.","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.",Neutral
10581,"(124, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10582,"(124, 129)","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.","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.",Neutral
10583,"(124, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10584,"(124, 131)","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.",The system shall delete history of received immunizations.,Neutral
10585,"(124, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
10586,"(124, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10587,"(124, 134)","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.",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.,Neutral
10588,"(124, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
10589,"(124, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10590,"(124, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10591,"(124, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10592,"(124, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10593,"(124, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10594,"(124, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10595,"(124, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10596,"(124, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10597,"(124, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10598,"(124, 145)","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.",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.,Neutral
10599,"(124, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10600,"(124, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10601,"(124, 148)","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.","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.",Neutral
10602,"(125, 126)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,Neutral
10603,"(125, 127)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.","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.",Neutral
10604,"(125, 128)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10605,"(125, 129)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.","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.",Neutral
10606,"(125, 130)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10607,"(125, 131)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system shall delete history of received immunizations.,Neutral
10608,"(125, 132)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
10609,"(125, 133)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10610,"(125, 134)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",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.,Neutral
10611,"(125, 135)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system will provide the ability to register patients of all types.,Neutral
10612,"(125, 136)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10613,"(125, 137)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10614,"(125, 138)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10615,"(125, 139)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10616,"(125, 140)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10617,"(125, 141)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10618,"(125, 142)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10619,"(125, 143)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10620,"(125, 144)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10621,"(125, 145)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",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.,Neutral
10622,"(125, 146)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10623,"(125, 147)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10624,"(125, 148)","The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care.","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.",Neutral
10625,"(126, 127)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,"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.",Neutral
10626,"(126, 128)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,"The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10627,"(126, 129)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,"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.",Neutral
10628,"(126, 130)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,"The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10629,"(126, 131)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,The system shall delete history of received immunizations.,Neutral
10630,"(126, 132)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,The system shall only delete history of recieved immunizations unless user specifies,Neutral
10631,"(126, 133)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10632,"(126, 134)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,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.,Neutral
10633,"(126, 135)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,The system will provide the ability to register patients of all types.,Neutral
10634,"(126, 136)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10635,"(126, 137)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10636,"(126, 138)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10637,"(126, 139)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10638,"(126, 140)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10639,"(126, 141)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10640,"(126, 142)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10641,"(126, 143)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10642,"(126, 144)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10643,"(126, 145)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,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.,Neutral
10644,"(126, 146)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10645,"(126, 147)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10646,"(126, 148)",The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph.,"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.",Neutral
10647,"(127, 128)","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.","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",Neutral
10648,"(127, 129)","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.","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.",Neutral
10649,"(127, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10650,"(127, 131)","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.",The system shall delete history of received immunizations.,Neutral
10651,"(127, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
10652,"(127, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10653,"(127, 134)","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.",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.,Neutral
10654,"(127, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
10655,"(127, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10656,"(127, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10657,"(127, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10658,"(127, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10659,"(127, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10660,"(127, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10661,"(127, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10662,"(127, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10663,"(127, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10664,"(127, 145)","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.",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.,Neutral
10665,"(127, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10666,"(127, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10667,"(127, 148)","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.","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.",Neutral
10668,"(128, 129)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.","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.",Neutral
10669,"(128, 130)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10670,"(128, 131)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",The system shall delete history of received immunizations.,Neutral
10671,"(128, 132)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
10672,"(128, 133)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10673,"(128, 134)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",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.,Neutral
10674,"(128, 135)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",The system will provide the ability to register patients of all types.,Neutral
10675,"(128, 136)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10676,"(128, 137)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10677,"(128, 138)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10678,"(128, 139)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10679,"(128, 140)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10680,"(128, 141)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10681,"(128, 142)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10682,"(128, 143)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10683,"(128, 144)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10684,"(128, 145)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",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.,Neutral
10685,"(128, 146)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10686,"(128, 147)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10687,"(128, 148)","The system shall support requirements for codified data, including diagnosis data using ICD-9 codes.","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.",Neutral
10688,"(129, 130)","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.","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",Neutral
10689,"(129, 131)","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.",The system shall delete history of received immunizations.,Neutral
10690,"(129, 132)","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.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
10691,"(129, 133)","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.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10692,"(129, 134)","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.",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.,Neutral
10693,"(129, 135)","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.",The system will provide the ability to register patients of all types.,Neutral
10694,"(129, 136)","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.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10695,"(129, 137)","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.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10696,"(129, 138)","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.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10697,"(129, 139)","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.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10698,"(129, 140)","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.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10699,"(129, 141)","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.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10700,"(129, 142)","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.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10701,"(129, 143)","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.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10702,"(129, 144)","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.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10703,"(129, 145)","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.",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.,Neutral
10704,"(129, 146)","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.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10705,"(129, 147)","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.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10706,"(129, 148)","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.","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.",Neutral
10707,"(130, 131)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",The system shall delete history of received immunizations.,Neutral
10708,"(130, 132)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",The system shall only delete history of recieved immunizations unless user specifies,Neutral
10709,"(130, 133)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10710,"(130, 134)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",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.,Neutral
10711,"(130, 135)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",The system will provide the ability to register patients of all types.,Neutral
10712,"(130, 136)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10713,"(130, 137)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10714,"(130, 138)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10715,"(130, 139)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10716,"(130, 140)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10717,"(130, 141)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10718,"(130, 142)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10719,"(130, 143)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10720,"(130, 144)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10721,"(130, 145)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",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.,Neutral
10722,"(130, 146)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10723,"(130, 147)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10724,"(130, 148)","The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information.","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.",Neutral
10725,"(131, 132)",The system shall delete history of received immunizations.,The system shall only delete history of recieved immunizations unless user specifies,Conflict
10726,"(131, 133)",The system shall delete history of received immunizations.,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10727,"(131, 134)",The system shall delete history of received immunizations.,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.,Neutral
10728,"(131, 135)",The system shall delete history of received immunizations.,The system will provide the ability to register patients of all types.,Neutral
10729,"(131, 136)",The system shall delete history of received immunizations.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10730,"(131, 137)",The system shall delete history of received immunizations.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10731,"(131, 138)",The system shall delete history of received immunizations.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10732,"(131, 139)",The system shall delete history of received immunizations.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10733,"(131, 140)",The system shall delete history of received immunizations.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10734,"(131, 141)",The system shall delete history of received immunizations.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10735,"(131, 142)",The system shall delete history of received immunizations.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10736,"(131, 143)",The system shall delete history of received immunizations.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10737,"(131, 144)",The system shall delete history of received immunizations.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10738,"(131, 145)",The system shall delete history of received immunizations.,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.,Neutral
10739,"(131, 146)",The system shall delete history of received immunizations.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10740,"(131, 147)",The system shall delete history of received immunizations.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10741,"(131, 148)",The system shall delete history of received immunizations.,"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.",Neutral
10742,"(132, 133)",The system shall only delete history of recieved immunizations unless user specifies,The system shall include capabilities for ordering laboratory tests and reviewing results.,Neutral
10743,"(132, 134)",The system shall only delete history of recieved immunizations unless user specifies,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.,Neutral
10744,"(132, 135)",The system shall only delete history of recieved immunizations unless user specifies,The system will provide the ability to register patients of all types.,Neutral
10745,"(132, 136)",The system shall only delete history of recieved immunizations unless user specifies,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10746,"(132, 137)",The system shall only delete history of recieved immunizations unless user specifies,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10747,"(132, 138)",The system shall only delete history of recieved immunizations unless user specifies,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10748,"(132, 139)",The system shall only delete history of recieved immunizations unless user specifies,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10749,"(132, 140)",The system shall only delete history of recieved immunizations unless user specifies,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10750,"(132, 141)",The system shall only delete history of recieved immunizations unless user specifies,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10751,"(132, 142)",The system shall only delete history of recieved immunizations unless user specifies,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10752,"(132, 143)",The system shall only delete history of recieved immunizations unless user specifies,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10753,"(132, 144)",The system shall only delete history of recieved immunizations unless user specifies,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10754,"(132, 145)",The system shall only delete history of recieved immunizations unless user specifies,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.,Neutral
10755,"(132, 146)",The system shall only delete history of recieved immunizations unless user specifies,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10756,"(132, 147)",The system shall only delete history of recieved immunizations unless user specifies,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10757,"(132, 148)",The system shall only delete history of recieved immunizations unless user specifies,"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.",Neutral
10758,"(133, 134)",The system shall include capabilities for ordering laboratory tests and reviewing results.,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.,Neutral
10759,"(133, 135)",The system shall include capabilities for ordering laboratory tests and reviewing results.,The system will provide the ability to register patients of all types.,Neutral
10760,"(133, 136)",The system shall include capabilities for ordering laboratory tests and reviewing results.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10761,"(133, 137)",The system shall include capabilities for ordering laboratory tests and reviewing results.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10762,"(133, 138)",The system shall include capabilities for ordering laboratory tests and reviewing results.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10763,"(133, 139)",The system shall include capabilities for ordering laboratory tests and reviewing results.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10764,"(133, 140)",The system shall include capabilities for ordering laboratory tests and reviewing results.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10765,"(133, 141)",The system shall include capabilities for ordering laboratory tests and reviewing results.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10766,"(133, 142)",The system shall include capabilities for ordering laboratory tests and reviewing results.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10767,"(133, 143)",The system shall include capabilities for ordering laboratory tests and reviewing results.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10768,"(133, 144)",The system shall include capabilities for ordering laboratory tests and reviewing results.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10769,"(133, 145)",The system shall include capabilities for ordering laboratory tests and reviewing results.,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.,Neutral
10770,"(133, 146)",The system shall include capabilities for ordering laboratory tests and reviewing results.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10771,"(133, 147)",The system shall include capabilities for ordering laboratory tests and reviewing results.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10772,"(133, 148)",The system shall include capabilities for ordering laboratory tests and reviewing results.,"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.",Neutral
10773,"(134, 135)",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.,The system will provide the ability to register patients of all types.,Neutral
10774,"(134, 136)",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.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10775,"(134, 137)",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.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10776,"(134, 138)",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.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10777,"(134, 139)",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.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10778,"(134, 140)",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.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10779,"(134, 141)",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.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10780,"(134, 142)",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.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10781,"(134, 143)",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.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10782,"(134, 144)",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.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10783,"(134, 145)",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.,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.,Neutral
10784,"(134, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10785,"(134, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10786,"(134, 148)",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.,"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.",Neutral
10787,"(135, 136)",The system will provide the ability to register patients of all types.,"The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",Neutral
10788,"(135, 137)",The system will provide the ability to register patients of all types.,The system shall include Standard Laboratory and Medication orderable files.,Neutral
10789,"(135, 138)",The system will provide the ability to register patients of all types.,The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10790,"(135, 139)",The system will provide the ability to register patients of all types.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10791,"(135, 140)",The system will provide the ability to register patients of all types.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10792,"(135, 141)",The system will provide the ability to register patients of all types.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10793,"(135, 142)",The system will provide the ability to register patients of all types.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10794,"(135, 143)",The system will provide the ability to register patients of all types.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10795,"(135, 144)",The system will provide the ability to register patients of all types.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10796,"(135, 145)",The system will provide the ability to register patients of all types.,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.,Neutral
10797,"(135, 146)",The system will provide the ability to register patients of all types.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10798,"(135, 147)",The system will provide the ability to register patients of all types.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10799,"(135, 148)",The system will provide the ability to register patients of all types.,"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.",Neutral
10800,"(136, 137)","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",The system shall include Standard Laboratory and Medication orderable files.,Neutral
10801,"(136, 138)","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",The system shall include non-Standard Laboratory and Medication orderable files.,Neutral
10802,"(136, 139)","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10803,"(136, 140)","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10804,"(136, 141)","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10805,"(136, 142)","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10806,"(136, 143)","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10807,"(136, 144)","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10808,"(136, 145)","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",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.,Neutral
10809,"(136, 146)","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10810,"(136, 147)","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10811,"(136, 148)","The system shall have the capability to capture and store risk, social, and medical factors for each new patient.","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.",Neutral
10812,"(137, 138)",The system shall include Standard Laboratory and Medication orderable files.,The system shall include non-Standard Laboratory and Medication orderable files.,Conflict
10813,"(137, 139)",The system shall include Standard Laboratory and Medication orderable files.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10814,"(137, 140)",The system shall include Standard Laboratory and Medication orderable files.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10815,"(137, 141)",The system shall include Standard Laboratory and Medication orderable files.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10816,"(137, 142)",The system shall include Standard Laboratory and Medication orderable files.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10817,"(137, 143)",The system shall include Standard Laboratory and Medication orderable files.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10818,"(137, 144)",The system shall include Standard Laboratory and Medication orderable files.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10819,"(137, 145)",The system shall include Standard Laboratory and Medication orderable files.,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.,Neutral
10820,"(137, 146)",The system shall include Standard Laboratory and Medication orderable files.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10821,"(137, 147)",The system shall include Standard Laboratory and Medication orderable files.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10822,"(137, 148)",The system shall include Standard Laboratory and Medication orderable files.,"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.",Neutral
10823,"(138, 139)",The system shall include non-Standard Laboratory and Medication orderable files.,The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,Neutral
10824,"(138, 140)",The system shall include non-Standard Laboratory and Medication orderable files.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10825,"(138, 141)",The system shall include non-Standard Laboratory and Medication orderable files.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10826,"(138, 142)",The system shall include non-Standard Laboratory and Medication orderable files.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10827,"(138, 143)",The system shall include non-Standard Laboratory and Medication orderable files.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10828,"(138, 144)",The system shall include non-Standard Laboratory and Medication orderable files.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10829,"(138, 145)",The system shall include non-Standard Laboratory and Medication orderable files.,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.,Neutral
10830,"(138, 146)",The system shall include non-Standard Laboratory and Medication orderable files.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10831,"(138, 147)",The system shall include non-Standard Laboratory and Medication orderable files.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10832,"(138, 148)",The system shall include non-Standard Laboratory and Medication orderable files.,"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.",Neutral
10833,"(139, 140)",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,Neutral
10834,"(139, 141)",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10835,"(139, 142)",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10836,"(139, 143)",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10837,"(139, 144)",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10838,"(139, 145)",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,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.,Neutral
10839,"(139, 146)",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10840,"(139, 147)",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10841,"(139, 148)",The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting.,"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.",Neutral
10842,"(140, 141)",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,Neutral
10843,"(140, 142)",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10844,"(140, 143)",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10845,"(140, 144)",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10846,"(140, 145)",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,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.,Neutral
10847,"(140, 146)",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10848,"(140, 147)",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10849,"(140, 148)",The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems.,"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.",Neutral
10850,"(141, 142)",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,The system shall provide tools for creating business rules that apply to documents used by members of such groups.,Neutral
10851,"(141, 143)",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10852,"(141, 144)",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10853,"(141, 145)",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,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.,Neutral
10854,"(141, 146)",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10855,"(141, 147)",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10856,"(141, 148)",The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital.,"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.",Neutral
10857,"(142, 143)",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,Neutral
10858,"(142, 144)",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10859,"(142, 145)",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,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.,Neutral
10860,"(142, 146)",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10861,"(142, 147)",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10862,"(142, 148)",The system shall provide tools for creating business rules that apply to documents used by members of such groups.,"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.",Neutral
10863,"(143, 144)",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,"The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",Neutral
10864,"(143, 145)",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,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.,Neutral
10865,"(143, 146)",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10866,"(143, 147)",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10867,"(143, 148)",The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service.,"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.",Neutral
10868,"(144, 145)","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",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.,Neutral
10869,"(144, 146)","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.",The system shall only allow clinical users to have full access privileges to all problem list options.,Neutral
10870,"(144, 147)","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10871,"(144, 148)","The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes.","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.",Neutral
10872,"(145, 146)",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.,The system shall only allow clinical users to have full access privileges to all problem list options.,Conflict
10873,"(145, 147)",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.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10874,"(145, 148)",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.,"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.",Neutral
10875,"(146, 147)",The system shall only allow clinical users to have full access privileges to all problem list options.,"The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.",Neutral
10876,"(146, 148)",The system shall only allow clinical users to have full access privileges to all problem list options.,"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.",Neutral
10877,"(147, 148)","The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward.","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.",Neutral