id
string | content
string | summary
string | layer
string |
|---|---|---|---|
1674 | The system shall improve accessibility of online clinical information and results. | Requirement |
|
1688 | The system shall integrate all components of the patient record to provide comprehensive and intelligent clinical information access and reporting. | Requirement |
|
1689 | 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. | Requirement |
|
1690 | The system shall be easy to use by improving the user interface to reflect industry standards and principles of usability and user-centered design. | Requirement |
|
1691 | The system shall use HL-7 communications protocol for transferring messages among packages | Requirement |
|
1692 | The system shall allow setting of business rules, document types, user classes, etc. to control access to documents, reports, verification, signing, and so on | Requirement |
|
1693 | 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 | Requirement |
|
1694 | The system shall have pre-defined progress note templates. | Requirement |
|
1695 | The system shall allow creation of personalized templates to fit the specific needs of individual practices. | Requirement |
|
1696 | The system shall include clinical reminders to provide relevant information to providers, at the point of care, for improving patient care. | Requirement |
|
1697 | The system shall include a graphing feature to allow users to view lab test results and vital signs in a graph. | Requirement |
|
1675 | 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. | Requirement |
|
1698 | 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. | Requirement |
|
1699 | The system shall support role-based access for security controls. | Requirement |
|
1700 | The system shall support audit capability. | Requirement |
|
1701 | The system shall support requirements for codified data, including diagnosis data using ICD-9 codes. | Requirement |
|
1702 | 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. | Requirement |
|
1703 | The system shall document discharge summary hospitalization data, as well as procedure and diagnosis-related information. | Requirement |
|
1704 | The system shall capture history of received immunizations. | Requirement |
|
1705 | The system shall include capabilities for ordering laboratory tests and reviewing results. | Requirement |
|
1706 | 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. | Requirement |
|
1707 | 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 | Requirement |
|
1708 | The system shall provide OB/GYN progress note templates based on the IHS progress note templates. | Requirement |
|
1676 | The system shall improve efficiency of entering orders. | Requirement |
|
1677 | The system shall provide a way for user to quickly click on the specifications that he or she wants for each order placed. | Requirement |
|
1678 | The system shall provide an option to so a user can quickly set up orders for frequently placed orders. | Requirement |
|
1679 | The system shall allow several orders to be placed with the ability for a user to sign for them all at once. | Requirement |
|
1680 | The system shall allow event-delay capability for pre-admission, discharge, and transfer orders | Requirement |
|
1709 | The system will provide the ability to register patients of all types. | Requirement |
|
1710 | The system shall have the capability to capture and store risk, social, and medical factors for each new patient. | Requirement |
|
1711 | The system shall allow physician offices to use social security numbers or medical record numbers to identify patients. | Requirement |
|
1712 | The system shall support the requirements for codified data specified by the DOQ-IT quality improvement measures. | Requirement |
|
1713 | The system shall trigger registration reminders when patient meets eligibility requirements for the DOQ-IT program. | Requirement |
|
1714 | The system shall include Standard Laboratory and Medication orderable files. | Requirement |
|
1715 | The system shall include the ability to print prescriptions for signature and fax prescriptions to a local pharmacy with an electronic signature. | Requirement |
|
1716 | The system shall provide a platform for building interfaces to external lab services enabling automated order entry and results reporting. | Requirement |
|
1717 | The system shall provide an open source integration platform to build interfaces to Billing/Practice Management systems. | Requirement |
|
1718 | The system shall require handwritten signatures for outpatient medication orders of schedule 2 and schedule 2n controlled substances due to DEA policy. | Requirement |
|
1719 | The system's pilot program shall use a smart card to digitally sign medication orders. | Requirement |
|
1720 | The system shall require a smart card reader, smart card, and a PIN to digitally sign an order. | Requirement |
|
1721 | The system shall require most orders or documents, such as progress notes, reports, or health summaries, to have an electronic signature. | Requirement |
|
1722 | The system shall not release orders to services or activated until they are signed if they require a signature. | Requirement |
|
1723 | 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. | Requirement |
|
1681 | The system shall allow complete order sets to be predefined and personalized. | Requirement |
|
1724 | The system shall implement a user class hierarchy to identify the roles that different users fulfill within the hospital. | Requirement |
|
1725 | The system shall provide tools for creating business rules that apply to documents used by members of such groups. | Requirement |
|
1734 | The system shall automatically considered any member of a given User Class to be a member of all superclasses of that class. | Requirement |
|
1735 | The system shall automatically include membership in a given User Class to all member of subclasses of that class. | Requirement |
|
1736 | The system shall design the Kernel Person Class File to accommodate the HCFA National Provider System Taxonomy of Professionals/Occupations. | Requirement |
|
1726 | The system shall provide a method for identifying who is AUTHORIZED to do something (for example, sign and order). | Requirement |
|
1727 | The system shall define, populate, and retrieve information about user classes. | Requirement |
|
1728 | The system shall allow user classes to be defined hospital-wide or more narrowly for a specific service. | Requirement |
|
1729 | The system shall allow user classes to be used across VistA to replace and/or complement security keys. | Requirement |
|
1730 | The system shall allow infinite hierarchies of subclasses to be created in the User Hierarchy Class structure. | Requirement |
|
1731 | The system shall allow document types to inherit authorizations from a higher level when using classes to assign roles. | Requirement |
|
1732 | The system shall impose no limitation on the depth or specificity of the User Class hierarchy which a site may choose to develop. | Requirement |
|
1733 | The system shall allow concurrent membership in more than one User Class. | Requirement |
|
1737 | The document-handling system (TIU) shall include Consults/Request Tracking, Discharge Summary, and Progress Notes. | Requirement |
|
1738 | The document-handling system (TIU) shall have boilerplate and cut and paste capabilities. | Requirement |
|
1739 | The system shall allow other VistA applications to access the user class file to determine the role of an employee. | Requirement |
|
1740 | The system shall require provider, location, date and time encounter data to be entered for each visit (or telephone call) with a patient. | Requirement |
|
1741 | 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. | Requirement |
|
1742 | The system shall timeout after a period of inactivity. | Requirement |
|
1743 | The system shall ask the user if the user wants to continue using the system before timing out. | Requirement |
|
1744 | The system shall require the entry of an access code and a verify code to gain access to the system. | Requirement |
|
1745 | The system shall stored the names of users who view remote data in the remote site's database. | Requirement |
|
1746 | The system shall audit sensitive records, enabling a site to follow up on a record accessed by a remote location. | Requirement |
|
1747 | The system shall provide a way to limit the users or sites that have access to remote retrievable data. | Requirement |
|
1748 | 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. | Requirement |
|
1749 | 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. | Requirement |
|
1750 | 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. | Requirement |
|
1751 | 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). | Requirement |
|
1682 | The system shall allow order checking. | Requirement |
|
1683 | The system shall provide background checks on duplicate orders, drug-drug interactions, and many other criteria that a user can choose. | Requirement |
|
1752 | The system shall allow users to enter time in several different formats. | Requirement |
|
1753 | 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. | Requirement |
|
1754 | The system shall require a user to review and sign changed if a user has just entered orders or documents that are unsigned. | Requirement |
|
1755 | 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. | Requirement |
|
1756 | 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. | Requirement |
|
1757 | 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. | Requirement |
|
1758 | The system shall allow the user to group the patient list according to provider, team, specialty, clinic, or ward. | Requirement |
|
1759 | 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. | Requirement |
|
1760 | The system shall display a message indicating the patient?s ability to pay for medical services must be evaluated. | Requirement |
|
1761 | 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. | Requirement |
|
1762 | The system shall indicate that the record is sensitive and may only be viewed by authorized users. | Requirement |
|
1763 | The system shall display a message telling the user that the selected patient is deceased. | Requirement |
|
1764 | 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. | Requirement |
|
1765 | The system shall allow the creation of patient lists or team lists that simplify tasks such as reviewing patient charts, ordering, and signing orders and notes and these lists can be based on wards, clinics, teams, or other groups. | Requirement |
|
1766 | The system shall use patient lists allow a person to quickly locate patients without going through all the patients in the list. | Requirement |
|
1767 | The system shall allow clinicians to create patient lists for who can sign or cosign for each other. | Requirement |
|
1768 | The system shall ensure that all team members receive necessary information about a patient by using patient lists to tie notifications to teams. | Requirement |
|
1769 | The system shall allow notifications to be renewed if the user decides the alert should not go away when the user views it. | Requirement |
|
1778 | 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.) | Requirement |
|
1779 | 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) | Requirement |
|
1780 | The system shall sort notifications based on column heading: Message (alert message or text, alphabetical or reverse alphabetical) | Requirement |
|
1781 | The system shall sort notifications based on column heading: Forwarded By/When (sorts alerts alphabetically and then by time for the same forwarding person) | Requirement |
|
1782 | 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. | Requirement |
|
1770 | The system shall allow a user to foward notification to someone else at the site. | Requirement |
|
1771 | The system shall allow users to disable unwanted notifications as desired. | Requirement |
|
1772 | The system shall not allow mandatory notifications to be disabled. | Requirement |
End of preview. Expand
in Dataset Viewer.
README.md exists but content is empty.
- Downloads last month
- 36