VA118-17-R-2324-A00003003.xlsx
XLSX spreadsheet 539 KB Posted
- Attached to
- Electronic Health Record Modernization Federal contract opportunity
- Solicitation number
- VA11817R2324
About this file
VA118-17-R-2324 A00003 003 - VA EHRM Non-Functional RTM (Amended 2.16.2018) - Redacted.xlsx
View the file
Other files for this federal contract opportunity
Show all 50
Electronic Health Record Modernization has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Summary
| VA EHRM RTM Non-Functional Requirements Summary | |
| Updated: 22Jan2018 |
VA RTM Non-Functional Requirements VA Informatics Requirements
| Requirement Type | Count | Requirement Type / Cat | Count |
| Final | Final | ||
| 508 Compliance | 1 | Compatibility | 13 |
| Access Management | 20 | Functional Suitability | 15 |
| Data Management | 4 | Maintainability | 6 |
| Identity Management | 21 | Usability | 4 |
| Information Assurance / Security | 11 | Final Total | 38 |
| Interoperability | 19 | ||
| Pharmacy | 7 | ||
| Reliability / Scalability / Maintanability | 4 | ||
| Synchronization: Low-Comm / No-Comm | 1 | ||
| SLA | 12 | ||
| Final Total | 100 |
VA RTM Non-Functional
| Ref # | Capabilities | Definition | RTM Clarification | VA Status | DoD Ref (If Applicable) | Type / Category (ISO/IEC 25010:2011) | Source | VA Owner | Met/Not Met | ||
| (Cerner Field) | Solution Name | ||||||||||
| (Cerner Field) | Development Needed | ||||||||||
| (Cerner Field) | Confirmed in Scope Document | ||||||||||
| (Cerner Field) | Sort Column | ||||||||||
| 508 Compliance | 508 Compliance | ||||||||||
| VA-NF-222 | 508 Compliance | The system shall be 100% compliant with the 2017 revisions for INFORMATION AND COMMUNICATION TECHNOLOGY PROCUREMENTS (SECTION 508), Section 508 of the Rehabilitation Act of 1998, as amended, 29 USC 794(d) and the requirements outlined in the Performance Work Statement. The contractor shall ensure employees with disabilities are offered the same training opportunities via equivalent access and that the training environment is accessible to those with disabilities and the electronic training materials meet section 508 requirements. When documentation is only provided in non-electronic formats, alternate formats usable by people with disabilities shall be provided by material originator upon request. | Final | ||||||||
| 36706 | Usability | DEA.040201 Human Interface (767938) | 508 Compliance | ||||||||
| Access Management | Access Management | ||||||||||
| VA-NF-6 | Access Management | The system shall conform to both DoD and VA standardized access management methods | Final | 36656 | Compatibility | EHRM Lead | Access Management | ||||
| VA-NF-7 | Data Access | The system shall support the ability to access data elements using open standard-based interfaces including legacy data | Final | 10 | Compatibility | EHRM Lead | Access Management | ||||
| VA-NF-8 | Information Access | The system shall initially provide role-based access and allow for finer grained access in the future | Final | 36670 | Security | EHRM Lead | Access Management | ||||
| VA-NF-9 | PKI Infrastructure | The system shall use VA-approved public key infrastructure (PKI) certificates in PKI-based identity authentication processes for component business and mission processes | Final | 36686 | Security | EHRM Lead | Access Management | ||||
| VA-NF-10 | User Configuration | The system shall enable role configuration to fit VA business needs | Final | 36698 | Security | EHRM Lead | Access Management | ||||
| VA-NF-11 | User Login - PIV | The system shall provide the ability of the user to log in to the system via a VA PIV card and/or use the VA's Authentication service and trusted token | Final | 36699 | Security | EHRM Lead | Access Management | ||||
| VA-NF-38 | User Provisioning | The system shall be able to provision and de-provision users into Cerner Active Directory and Applications both manually and automated with VA's Enterprise provisioning service. | Final | 38497 | Functional Suitability | EHRM Lead | Access Management | ||||
| VA-NF-43 | Single Sign-On | The system shall allow users access to multiple applications using a single means of authentication maintaining User context across all Cerner applications (e.g., valid DoD CAC/ VA PIV combined with personal identification number (PIN)) | Final | 45884 | Usability | EHRM Lead | Access Management | ||||
| VA-NF-45 | Identity - Joint Legacy Viewer | The system shall integrate Joint Legacy Viewer connectivity (e.g., launch button) with the EHR solution, to include context management using the user ID, patient ID, and patient encounter location ID. | Final | 170452 | Functional Suitability | EHRM Lead | Access Management | ||||
| VA-NF-47 | Self Service Credentials | Self Service applications shall allow for federated credentials to be used to access the system | Final | Usability | EHRM Lead | Access Management | |||||
| VA-NF-48 | Self Service Authentication | Self Service applications shall allow for authentication from VA authentication service | Final | Compatibility | EHRM Lead | Access Management | |||||
| VA-NF-49 | Patient Context | Maintain patient context throughout all Cerner applications and SSO sessions | Final | Functional Suitability | EHRM Lead | Access Management | |||||
| VA-NF-50 | User Logon - TAP | After initial 2 factor authentication, a user shall be allowed to use TAP to resume session | Final | Security | EHRM Lead | Access Management | |||||
| VA-NF-51 | Emergency Access Non-Two Factor Authentication | The system shall support a temporary non-two factor authentication for emergency situations | Final | Security | EHRM Lead | Access Management | |||||
| VA-NF-55 | Automated Provisioning | The system shall allow for an automated way to provision and deprovision users into the Cerner Active Directory and all Cerner Application | Final | Functional Suitability | EHRM Lead | Access Management | |||||
| VA-NF-56 | Account Disable | The System shall provide the ability to disable user accounts after a configurable time period of inactivity and manually at any point to prevent further access | Final | Security | EHRM Lead | Access Management | |||||
| VA-NF-58 | Security Audit | The system shall audit all access control functions (i.e. authentication, authorization events, log on attempts, etc..) | Final | Security | EHRM Lead | Access Management | |||||
| VA-NF-39 | Web Application Identity Management And access management | The web applications for the system shall implement identity management and access management | Final | 38498 | Functional Suitability | EHRM Lead | Access Management | ||||
| VA-NF-46 | Self Service Applications | The self-service/patient portals shall implement identity management and access management | Final | Functional Suitability | EHRM Lead | Access Management | |||||
| VA-NF-S03 | Re-Authentication | The system shall be able to re-authenticate a user based on business needs (I.E. – electronic signature of basic orders or other types of system transactions. | Final | Functional Suitability | EHRM Lead | Access Management | |||||
| Data Management | Data Management | ||||||||||
| VA-NF-113 | Legal/Regulatory | The vendor shall provide a solution to archive the complete medical record from VistA (need to identify all of the components from within the VistA product) The archiving solution shall place the legacy data in a relational database The solution shall provide a link/API access from an individual patients Cerner Millennium chart to the patients archived record The archiving solution shall be searchable by account IDs, name, social security number, or data source The archiving solution shall be capable of archiving patient records from the Cerner Millennium system | Final | Security | FFRDC - MITRE | Data Management | |||||
| VA-NF-134 | Data Write Back to Legacy Systems | The system shall support integration with a data syndication mechanism to write back data to VA Legacy systems | Final | Functional Suitability | Contractor - BAH | Data Management | |||||
| VA-NF-137 | Tape Backup and Long Term Storage | The system shall support capability for encrypted back up to tape and long term storage, per VA mandate. | Final | Functional Suitability | Contractor - BAH | Data Management | |||||
| VA-NF-175 | VA Data Model | The system shall conform to the VA EA Enterprise Logical Data Model (ELDM) | Final | Functional Suitability | DEA.04.01.01 Enterprise Data (767919) | Data Management | |||||
| Identity Management | Identity Management | ||||||||||
| VA-NF-5 | Identity Management | The system shall use VA standardized identity management framework | Final | 36655 | Compatibility | EHRM Lead | Identity Management | ||||
| VA-NF-13 | Patient Identity - Identifier | The system shall use the DoD Identifier as the uniform person identifier with the VA ICN as an association | Final | 38432 | Functional Suitability | EHRM Lead | Identity Management | ||||
| VA-NF-15 | Patient Identity - Synchronization | The system shall be able to synchronize all patient identities to the enterprise Identity Management System (i.e., DEERS, MVI) | Final | 38434 | Security | EHRM Lead | Identity Management | ||||
| VA-NF-17 | Patient Identity - Patient Identifier | The system shall be able to retrieve patient identity information (i.e. name, DOB, gender) from the enterprise Identity Management System (i.e., DEERS, MVI) using the DoD Identifier (aka EDI_PI) or ICN | Final | 38436 | Functional Suitability | EHRM Lead | Identity Management | ||||
| VA-NF-18 | Patient Identity - Person Identifier | The system shall be able to retrieve patient identity information (i.e. name, DOB, gender) from the enterprise Identity Management System (i.e., DEERS, MVI) using alternate identity traits or alternate person identifiers (e.g., SSN, TIN, FIN, ICN, SecID, DFN, etc.) | Final | 38437 | Functional Suitability | EHRM Lead | Identity Management | ||||
| VA-NF-19 | Patient Identity - Additional Traits | The system shall be able to display returned additional candidate traits to assist the operator in selecting the correct patient from the list of search candidates | Removed | 38439 | Functional Suitability | EHRM Lead | Cindy Bias | Identity Management | |||
| VA-NF-20 | Patient Identity - Primary Search | The system shall conduct the primary patient search against the enterprise Identity Management System (i.e., DEERS, MVI) | Final | 38441 | Functional Suitability | EHRM Lead | Identity Management | ||||
| VA-NF-21 | Patient Identity - Card Scan | The system shall be able to obtain the DoD or VA Identifier by scanning the patient's DoD or VA Identification Cards (barcode) | Final | 38442 | Functional Suitability | EHRM Lead | Identity Management | ||||
| VA-NF-22 | Patient Identity - Trait Update | The system shall be able to enforce an identity trait update authorization code | Removed | 38444 | Functional Suitability | EHRM Lead | Cindy Bias | Identity Management | |||
| VA-NF-23 | Patient Identity - Trait Retrieve | The system shall retrieve identity traits from the enterprise Identity Management System (i.e., DEERS, MVI) prior to updating patient traits | Final | 38445 | Functional Suitability | EHRM Lead | Identity Management | ||||
| VA-NF-24 | Patient Identity - Patient Search | When communications allow, the system shall enforce a search to the enterprise Identity Management System (i.e., DEERS, MVI) prior to adding a new patient | Final | 38446 | Functional Suitability | EHRM Lead | Identity Management | ||||
| VA-NF-25 | Patient Identity - Add Patient | The system shall be able to add a patient to the enterprise Identity Management System (i.e., DEERS, MVI) | Final | 38447 | Functional Suitability | EHRM Lead | Identity Management | ||||
| VA-NF-27 | Patient Identity - Maintenance Notifications | The system shall consume identity maintenance notifications from the enterprise Identity Management System (i.e., DEERS, MVI) | Final | 38451 | Functional Suitability | EHRM Lead | Identity Management | ||||
| VA-NF-28 | Patient Identity - Identity Updates | The system shall apply identity updates from the identity maintenance notifications | Removed | 38452 | Functional Suitability | EHRM Lead | Cindy Bias | Identity Management | |||
| VA-NF-29 | Patient Identity - DoD Identifier | When the enterprise Identity Management System (i.e., DEERS, MVI) is not available, the system shall add patients using the DoD or VA Identifier, if it is available from a reliable source (e.g., from an ID card) | Final | 38453 | Functional Suitability | EHRM Lead | Identity Management | ||||
| VA-NF-30 | Patient Identity - Interim Identifier | When the enterprise Identity Management System (i.e., DEERS, MVI) is not available and no reliable source for the DoD or VA Identifier is offered, the system shall use an enterprise-unique Interim Patient Identifier | Final | 38454 | Functional Suitability | EHRM Lead | Identity Management | ||||
| VA-NF-31 | Patient Identity - Added Synchronization No Comm | The system shall synchronize all Interim Patient Identifiers added during a loss of connectivity once connectivity to the enterprise Identity Management System (i.e., DEERS, MVI) is restored | Final | 38455 | Reliability | EHRM Lead | Identity Management | ||||
| VA-NF-32 | Patient Information - Retrieve | The system shall be able to retrieve patient contact information (e.g., addresses, phone numbers, email) from the VA enterprise system using the VA or DoD Identifier | Final | 38458 | Compatibility | EHRM Lead | Identity Management | ||||
| VA-NF-33 | Patient Registry Info - Retrieve | The system shall be able to retrieve patient registry information (e.g., preferred language, religion, next of kin) from the VA enterprise System using the VA or DoD Identifier | Final | 38462 | Compatibility | EHRM Lead | Identity Management | ||||
| VA-NF-34 | Patient Eligibility - Retrieve | The system shall be able to retrieve patient eligibility information (e.g., Dates of Coverage, allowed coverage - direct care, dental, network, pharm and current beneficiary status) from the VA enterprise System using the VA or DoD Identifier | Final | 38466 | Compatibility | EHRM Lead | Identity Management | ||||
| VA-NF-35 | Patient OHI - Retrieve | The system shall be able to retrieve patient commercial health insurance information from the VA enterprise system using the VA or DoD Identifier | Final | 38468 | Compatibility | EHRM Lead | Identity Management | ||||
| VA-NF-40 | Patient Identity - VA Card Scan | The system shall be able to obtain the DoD Identifier and VA's ICN by scanning the patient's VA Identification Cards (barcode) | Duplicate of VA-NF-40 |
| Card scan needs to pull both identifiers | Removed | 40517 | Functional Suitability | EHRM Lead | Cindy Bias | Identity Management | |||||
| VA-NF-41 | Patient Identity - Manual Entry | The system shall be able to accept the DoD dentifier and/or other key identity traits by manual entry | VA will require searches based on a wider variety of identity traits to be entered manually. | Removed | 40518 | Functional Suitability | EHRM Lead | Cindy Bias | Identity Management | ||
| VA-NF-42 | Patient Identity - Updated Synchronization No Comm | The system shall synchronize all identities updated during a loss of connectivity once connectivity to the enterprise Identity Management System (i.e., DEERS; MVI) is restored | Final | 40519 | Reliability | EHRM Lead | Identity Management | ||||
| VA-NF-52 | External Patient Identifier Management for exchanges | The system shall support the matching of External Patient IDs coming in through eHealth Exchange/CommonWell and other community partner systems. | Final | Compatibility | EHRM Lead | Identity Management | |||||
| VA-NF-T77 | Referral UID | All information exchange related to a referral will maintain the unique referral identifier. | Final | Functional Suitability | Functional | Identity Management | |||||
| Information Assurance / Security | Information Assurance / Security | ||||||||||
| VA-NF-165 | Hardware-accelerated Encryption | The system shall enable the use of hardware-accelerated encryption | Final | 40497 |
36659 38504 36658
| Security | VA Enterprise Design Patterns: Interoperability and Data Sharing, Data Storage v1.0 | Information Assurance / Security | |||||||
| VA-NF-167 | Encryption at Scale | The system shall enable the use of key management technologies to facilitate encryption at scale | Final | Functional Suitability | VA Enterprise Design Patterns: Interoperability and Data Sharing, Data Storage v1.0 | Information Assurance / Security | |||
| VA-NF-T112 | Data Encryption | The system shall support the encryption of Controlled Unclassified Information (CUI) Data at Rest for all system data | All data stored by the system is encrypted using approved VA encryption methods | Removed | 38504 | Security | Casey Johle | Information Assurance / Security | |
| VA-NF-170 | Data Access Layer | The system shall have application logic access and data managed via a data access layer or established data services instead of directly accessing the database | Final | Security | DEA.04.02.03 Data Handling (767864) | Information Assurance / Security | |||
| VA-NF-171 | Application Logic | The system shall have application logic that does not need database implementation details (e.g., data base URLs, internal file formats, schema information) | Final | Security | DEA.04.02.03 Data Handling (767864) | Information Assurance / Security | |||
| VA-NF-189 | Systems Monitoring and Alerts - Common Services | The system shall implement common services for logging, error handling, monitoring/alerting. | Final | 36665-ID |
40514-Track
| Functional Suitability | Contractor - BAH | Information Assurance / Security | ||||
| VA-NF-T105 | Systems Monitoring and Alerts - Capacity Planning | The system shall provide performance monitoring data suitable for capacity planning and projections at a configurable interval with no more than a 12 hour delay from real time. | ||||
| Final | Performance Efficiency | Capacity Performance Engineering Division/EPMO | Information Assurance / Security | |||
| VA-NF-T106 | Systems Monitoring and Alerts - Compliance Evaluation | The system shall provide monitoring data suitable for evaulating compliance with any defined performance requirements. |
The environment shall be validated to support the performance monitoring requirements via live production monitoring.
Recommend remove from RTM, addressed in RHO scope document
Covered in Proposed Response Time Commitment and Remedy
| Removed | Performance Efficiency | Capacity Performance Engineering Division/EPMO | Kelly, Ed | Information Assurance / Security | |
| VA-NF-207 | FIPS 140-2 Data Encryption | Solution shall support FIPS 140-2 encryption for data at rest and data in transit | Recommend remove from RTM, addressed in RHO scope document |
Covered in b.6 security (Data in Transit) and Critical Facilities (Data at Rest)
| Removed | 36658, 36659, 38504, 40497 | Security | VA Enterprise Design Patterns: Interoperability and Data Sharing, Data Storage v1.0 | Casey Johle | Information Assurance / Security |
| VA-NF-208 | In-memory Data Security | Solution shall observe operating system security for data stored in-memory | Recommend remove from RTM, is validated by SCQC and should be handled in PWS 5.4 rather than here and referenced in PWS 5.4 |
Rene’---> agree remove
| Removed | 36671 | Security | VA Enterprise Design Patterns: Interoperability and Data Sharing, Data Storage v1.0 | Casey Johle | Information Assurance / Security | |||||
| VA-NF-214 | IP Addresses | Application code shall be free of hard-coded IP addresses | Removed | 36683 | Functional Suitability | DEA.04.04.07 Infrastructure Standards (767850) | Casey Johle | Information Assurance / Security | ||
| VA-NF-T01 | Access Control | The system shall lock after a specified period of inactivity regardless of how the system is accessed in accordance with VA Cybersecurity controls. | Recommend remove from RTM, addressed in RHO scope document |
Rene’---> agree remove, actually in PWS 5.4
| Removed | 36448 | Security | EHRM Lead | Casey Johle | Information Assurance / Security | |||||
| VA-NF-T02 | Approved Software (SW) List | The system shall be compliant with VA approved software | Final | 2 | Security | EHRM Lead | Information Assurance / Security | |||
| VA-NF-T03 | Data Encryption - Mobile Device | The system shall employ full-device encryption or container encryption to protect the confidentiality and integrity of information on mobile devices. | Final | 40497 | Security | EHRM Lead | Information Assurance / Security | |||
| VA-NF-T05 | Technical Event Management - Identify | The system shall, at a minimum, generate audit records for the following events when technically possible: Actions of system administrators and operator; production of printed output; new objects and deletion of objects in user address space; security-relevant events; system configuration activities and events; events relating to use of privileges; all events relating to user identification and authentication; and the setting of user identifiers. | Final | 36665 | Security | EHRM Lead | Information Assurance / Security | |||
| VA-NF-T06 | Hosting | The system shall comply with the requirements for a "Cloud First" policy as established by the Federal CIO. The CIO has required Agencies to evaluate the feasibility of a cloud service prior to hardware and software acquisition. | Final | 21 | Security | EHRM Lead | Information Assurance / Security | |||
| VA-NF-T08 | Cybersecurity | The system shall meet the NIST high baseline impact level in order to obtain at ATO (VA Risk Management Framework). | VA Handbook 6500 | |||||||
| https://www.va.gov/vapubs/viewPublication.asp?Pub_ID=793&FType=2 | Removed | 36671 | Security | EHRM Lead | Casey Johle | Information Assurance / Security | ||||
| VA-NF-T12 | Wireless LAN Communication | The system shall support wireless local-area network communication in accordance with VA wireless policy | Final | 36702 | Security | EHRM Lead | Information Assurance / Security | |||
| Interoperability | Interoperability | |||||||||
| VA-NF-142 | Interoperability - SOAP Implementation | SOAP-based service implementations shall follow WS Interoperability Basic Profile, and WS Interoperability Basic Security Profile standards | Final | Compatibility | DEA.04.03.02 Messaging Standards (767863) | Interoperability | ||||
| VA-NF-143 | Interoperability - XML Schema | XML messages shall conform to an XML definition written in accordance with XML Schema v1.0, XML Schema v1.1, Schematron or the latest DISR accepted version | Final | Compatibility | DEA.04.03.02 Messaging Standards (767863) | Interoperability | ||||
| VA-NF-144 | Interoperability - ReST Message Conformance | ReST messages shall conform to W3C guidance | Final | Compatibility | DEA.04.03.02 Messaging Standards (767863) | Interoperability | ||||
| VA-NF-177 | Interoperability - Data Standards | The system shall support the use of the health data standards identified in the VA DoD Health Information Technical Standards Profile and by the VA DoD Interagency Clinical Informatics board, including following common data standards: National Information Exchange Model NIEM; Health Level 7 HL7; Logical Observation Identifiers, Names and Codes LOINC; Systematized Nomenclature of Medicine SNOMED; RxNorm, MedRT, ICD, CPT, HCPCS, Veteran Information Model VIM; and Healthcare Information Technology Standards Panel HITSP as well as VA/DOD/IPO extensions to these standards | Final | 38546 |
38551
| 36707 | Compatibility | DEA.04.01.01 Enterprise Data (767919) | Interoperability | ||||||
| VA-NF-T51 | Health Information Exchange | System must be capable of generating the following cCDA document types Care Plan including Home Health Plan of Care (HHPoC), Consultation Note, Continuity of Care Document (CCD), Diagnostic Imaging Reports (DIR), Discharge Summary, History and Physical (H&P), Operative Note, Procedure Note, Progress Note, Referral Note, Transfer Summary, Unstructured Document, Patient Generated Document (US Realm Header). | Final | 38546 | Functional Suitability | EHRM Lead | Interoperability | ||
| VA-NF-T52 | Health Information Exchange | The system must be capable of bidirectional data exchange with eHealth Exchange, CareQuality | Final | 38554 | Compatibility | EHRM Lead | Interoperability | ||
| Pharmacy | Pharmacy | ||||||||
| VA-NF-T53 | Pharmacy - Multiple DEA Numbers | The system shall provide the capability to enter, display, edit, and report multiple DEA numbers per prescriber | Final | Functional Suitability | EHRM Lead | Pharmacy | |||
| VA-NF-T54 | Pharmacy - Institutional DEA Numbers | The system shall provide the capability to enter, display, edit, and report institutional DEA numbers | Final | Functional Suitability | EHRM Lead | Pharmacy | |||
| VA-NF-T55 | Pharmacy - DEA assignment based on location | The system shall provide logic to assign the correct DEA number to a prescription based upon prescriber location. | Final | Functional Suitability | EHRM Lead | Pharmacy | |||
| VA-NF-T56 | Pharmacy - PDMP state mandated transmissions | The system shall support transmission of state mandated data elements for controlled substances dispensed to the PDMP of the state of the pharmacy where the prescription was generated no less than once each night. | Final | Functional Suitability | EHRM Lead | Pharmacy | |||
| VA-NF-T57 | Pharmacy - PDMP tranmission by status | The system shall support filtering and restricting PDMP transmissions by Veteran status. | Final | Functional Suitability | EHRM Lead | Pharmacy | |||
| VA-NF-T58 | Pharmacy - MULTUM licenses | The vendor shall provide licenses and professional services for MULTUM for VistA sites so the VA can have a consolidated drug database system. The vendor will provide an accessible and computatle, and up-to-date equivalence table matching each MULTUM medication code with a clinically equivalent RxNorm code. | Final | Functional Suitability | EHRM Lead | Pharmacy | |||
| VA-NF-T66 | Pharmacy - Remaining Refills | The system shall not require pharmacists to manually re-enter prescriptions that have remaining refills during transition. Existing prescriptions with remaining refills will be available in Cerner and actionable. | Final | Functional Suitability | EHRM Lead | Pharmacy | |||
| Reliability / Scalability / Maintanability | Reliability / Scalability / Maintanability | ||||||||
| VA-NF-T78 | Critical Care | Includes Critical Care - automated workflows and documentation supporting critical care multi-disciplinary teams; Device Connectivity - automated collection of medical data from medical devices to ensure right data, right format, right time. | Final | 36695-Workflow | |||||
| 36673-medical device | Functional Suitability | Functional | Reliability / Scalability / Maintanability | ||||||
| VA-NF-T107 | Disaster Recovery | The system shall met disaster recovery requirements which specify both RTO and RPO requirements as measured by DR tests (annual). | Current Mission Critical Systems in VA like Heatlh Data Repository is 12 hours Recovery Time Objective. 2 hours Recovery Point Objective. |
Recommend remove from RTM, addressed in RHO scope document and PWS 5.3.1 Agreee – RPO and RTO are clearly defined in RHO
| Removed | Performance Efficiency | Capacity Performance Engineering Division/EPMO | Kelly, Ed | Reliability / Scalability / Maintanability | |||||
| VA-NF-160 | Change Management | The system shall provide a documented test solution for any platform/application iteration that introduces changes with the potential to impact end-user performance or compute and storage resources | Final | Maintainability | DEA.04.04.06 Capacity and Scalability (767971) | Reliability / Scalability / Maintanability | |||
| VA-NF-151 | Solution Scalability | The system shall support both horizontal and vertical solution scalability. | Final | 36679 |
36680 36692 38600 38604 38605 38606 38607 38616 38617 38618 38619 38620 38621
| Portability | DEA.04.04.06 Capacity and Scalability (767971) | Reliability / Scalability / Maintanability | ||||||
| Synchronization: Low-Comm / No-Comm | Synchronization: Low-Comm / No-Comm | |||||||
| VA-NF-118 | Low-Comm / No- Comm: Home Health | The system shall have the capability to document vitals, encountering/procedure codes, labs, orders, and medications offline, and synch up later for Home Health. | Final | 40513 | Functional Suitability | FFRDC - MITRE | Synchronization: Low-Comm / No-Comm | |
| Imaging | ||||||||
| VA-NF-B04 | COOP/DR for Imaging | For COOP/DR: The system shall be able to identify what images exist, and which of those are in the cache, when a medical center is disconnected from Cerner Data Center. | ||||||
| Final | Reliability / Scalability / Maintanability | |||||||
| Interoperability | ||||||||
| VA-NF-Z02 | FHIR | System shall support the generation of FHIR resources in multiple versions in parallel (e.g.: DTSU 1.0, DTSU V2.0) | Final | VA Lead | Interoperability | |||
| VA-NF-Z03 | Consent | The system shall meet 45 CFR 170.315 (b)(7-8) | Final | VA Lead | Interoperability | |||
| VA-NF-Z04 | Consent | The system will be able to manage all manner of consent "decrees" placed by Veterans and their providers. Including: Consent to share all documents, restriction of certain types of documents, restriction of partners with whom documents can be shared, revocation of consent decrees. | Final | VA Lead | Interoperability | |||
| VA-NF-Z05 | Consent | The system will be able to support future conversions from one consent methodology to another, ie from opt-in to opt-out. | Final | VA Lead | Interoperability | |||
| VA-NF-Z06 | Consent | System shall provide a means for patients to fill in, digitally sign (VA approved signature service), and submit electronic consent directives for chart update. | Final | VA Lead | Interoperability | |||
| VA-NF-Z07 | Consent | System shall handle interfaces with external products for capture, storage, receipt and implementation of consent directives to enable Veteran online consent management from a number of different locations and interfaces, including kiosks, home pc's and the eBenefits portal. These only authorization will automatically update the Veteran medical record | Final | VA Lead | Interoperability | |||
| VA-NF-Z08 | Consent | As required by policy, System shall automatically opt-out those patients whose authorizations have expired until a new authorization is entered | Final | VA Lead | Interoperability | |||
| VA-NF-Z09 | HIE | System shall provide patients with VA defined on-line help and access to Frequently Asked Questions (FAQ) with answers for help with the online process for submitting consent directives or questions about the VHIE program (patient user interface). | Final | VA Lead | Interoperability | |||
| VA-NF-Z10 | HIE | The system will be capable of extracting all transactional data related to consents to analytical warehouse for monitoring (by person, partner, status etc.) | Final | VA Lead | Interoperability | |||
| VA-NF-Z11 | HIE | The system shall support VA electronic exchange of health records via other interoperable networks (e.g. CareQuality, CommonWell Health Alliance, DirectTrust, National Association for Trusted Exchange) by supporting their specifications, security and content specifications | Final | VA Lead | Interoperability | |||
| VA-NF-Z12 | HIE | The system shall provide dashboard to monitor data exchanges and provide access to VA exchange performance reports, such as numbers of Veterans documents sent and received and response times. System shall be able to analyze, report and display the performance of outbound transactions [PD, QD, RD, Doc Submission, Direct messages] (average response time, # of total transactions/month, # of failed transactions, point of failures, why failed and where failed, error code w/explanation, other metadata: sent to which partner, sent by which user, mode of request (ROI/pre-fetch/e-benefits/MHV), purpose of use etc.). | Final | VA Lead | Interoperability | |||
| VA-NF-Z13 | HIE | System shall interface with Record Locator Services provided by CommonWell and other standards-based networks, as approved through joint governance. | Final | VA Lead | Interoperability | |||
| VA-NF-Z14 | HIE | By IOC, the system shall connect with all current eHealth Exchange VA partners | Final | VA Lead | Interoperability | |||
| Informatics | ||||||||
| VA-NF-T46 | Legal Discovery | The system shall support provenance (chain of custody or ownership) and pedigree (processing history how the data was produced or incorporated) and enable identification, collection, and production of data according to source, custody and ownership and display of data in business, logical, legal or physical models. | Final | Functional Suitability | EHRM Lead |
| Service Level Agreement (SLA) | |||||||
| VA-NF-000 | SLA Baseline as delivered to DoD | The system shall provide, as a baseline, the service level agreement as specified in the Cerner SLA Commercial Offering and MHS Genesis SLA. | Final | Performance Efficiency | SLA | ||
| VA-NF-94 | Accuracy | ||||||
| Successful Transaction Ratio – The Mission Critical System should return an overall percentage of transactions for a specific operation initiated by a user that are completed successfully (no timeout or other errors detected) within a specified mix of peak and/or non-peak period within targets established by the Project Team. values for mission critical systems are at least 99.9% of the time (99.9% of the transactions being successful), with a goal of 100% of the transactions. | Final | Performance Efficiency | EHRM Lead | SLA | |||
| VA-NF-86 | Availability | User Operational Availability - System availability exclusive of planned downtime shall be 99.9% for the Tier I production systems as defined in the Hosting Scope document. System availability exclusive of planned downtime shall be 99.9% for the HA-CAS production systems as defined in the Hosting Scope document. HealtheIntent components required for data migration and continuity of care shall have the same SLA and penalties as Tier I production systems as defined in the Hosting Scope document. |
| The System shall be available (uptime not excluding planned downtime) at a percentage of total possible operational time at least 99.9% of the time (downtime not to exceed xx hours/year or xxx minutes/ month), with a goal of 99.99% of the time (downtime not to exceed 0.876 hours/year or 4.38 minutes/month). | Final | partial - 38423, 38582 | Reliability | EHRM Lead | SLA | |
| VA-NF-100 | Capacity & Scalability | The provider-facing solutions shall scale to support 328,000 named users and to accommodate current and future VA usage patterns. |
| Solution shall support the expected concurrent processing of data by end-users and other connections commensurate with the rate of 190,000 concurrent users or connections. | Final | Performance Efficiency | EHRM Lead | SLA | ||||||
| VA-NF-146 | Compute Resource Consumption | Compute resource consumption shall be tested against established requirements and workload projections and supported by a continuous capacity plan to include methods, tools, and processes for monitoring, reporting, and adjusting the operational systems | Final | Performance Efficiency | DEA.04.04.06 Capacity and Scalability (767971) | SLA | ||||
| VA-NF-179 | Enterprise Service Level Criteria - Maintenance | System maintenance shall be during non-clinical hours as coordinated through joint governance | Final | Maintainability | EHRM Lead | SLA | ||||
| VA-NF-181 | Enterprise Service Level Criteria - System Outage | The system shall recover within minutes (when failover is an option) and 2-8 hours (when failover is not an option) | Final | Reliability | EHRM Lead | SLA | ||||
| VA-NF-223 | Operational Threshold | Threshold = 99.9% (System and application availability to support type of care provided at individual medical units wherever they are located). | Final | 38423, 38582 | Performance Efficiency | eHMP NONF3192 | SLA | |||
| VA-NF-T110 | System Recovery | The vendor shall maintain an environment that demonstrates a recovery time objective (RTO) of less than 60 minutes for any service location(s). |
| Final | Reliability | Capacity Performance Engineering Division/EPMO | SLA | ||
| VA-NF-T111 | System Recovery | The vendor shall maintain an environment that demonstrates a recovery point objective (RPO) of less than 10 minutes for any service location(s). |
| Final | Reliability | Capacity Performance Engineering Division/EPMO | SLA | |||||
| VA-NF-XXX1 | Customer Support | Average Speed to Answer will be <= 40 seconds | Final | Customer Support | Enterprise Service Desk | SLA | ||
| VA-NF-XXX2 | Customer Support | Abandonment Rate will be <=5% of all calls presented | Final | Customer Support | Enterprise Service Desk | SLA |
Innovations Backlog
| Ref # | Capabilities | Definition | RTM Clarification | VA Status | DoD Ref (If Applicable) | Type / Category (ISO/IEC 25010:2011) | Source | VA Owner | Met/Not Met | |
| (Cerner Field) | Solution Name | |||||||||
| (Cerner Field) | Development Needed | |||||||||
| (Cerner Field) | Sort Column | |||||||||
| Informatics | Time Categories for Informatics capabilites below |
• Now: Capability Exists in Current Cerner Product
• Now+ : Capability substantially exists today, progress is planned or expected
• 1-3: Capability could exist in 1-3 years
| • >3: Capability will take longer than 3 years | Informatics | ||||||
| VA-NF-T13 | Informatics - Data Content | VHA must be able to capture complete, accurate, richly detailed health data in a “close to clinician meaning” manner using accepted standards in order to deliver high quality, consistent care to Veterans. ML1 [>3] | Final | Compatibility | EHRM Lead | ||
| Informatics RTM 1.1 | Informatics | ||||||
| VA-NF-T14 | Informatics - Data Content | In the process of capturing complete and accurate records, VHA must minimize unnecessary documentation burdens that clinicians face. These burdens decrease face-to-face time for clinical care, thereby impairing care quality, patient satisfaction, and clinician satisfaction. Integrated, re-usable, standards-based, computable terminology allows clinicians to “document once” and the system to re-use that data “many times”. (Cognitive Support) ML2 [NOW] | Final | Usability | EHRM Lead | ||
| Informatics RTM 1.2 | Informatics | ||||||
| VA-NF-T15 | Informatics - Data Content | VHA must be able to ingest standards-based data and information from medical devices or via manual entry with associated metadata such as provenance [TP1] [NOW] | Final | Compatibility | EHRM Lead | ||
| Informatics RTM 1.3 | Informatics | ||||||
| VA-NF-T16 | Informatics - Data Content | VHA must be able to access validated and unvalidated standards-based medical device data for research and analysis in development of evidenced -based practice. Validated device data should be part of the health record and unvalidated device data should be stored but not part of the patient’s record [TP2] [> 3] | Final | Compatibility | EHRM Lead | ||
| Informatics RTM 1.4 | Informatics | ||||||
| VA-NF-T17 | Informatics - Data Content | VHA needs to be able to track patient location in any care venue via multiple techniques such as manual entry or radio-frequency wrist band. Data should be able to be integrated across methods and over time. VHA also needs to be able to tie location data to organizational units (wards, clinics etc) TP3 | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 1.5 | Informatics | ||||||
| VA-NF-T18 | Informatics - Data Reuse | VHA must be able to use clinical data collected at the point of care (e.g., exam rooms, patient's home) for clinical decision support and research regardless of the care site, clinic type, provider type (including patients) or data entry form employed. Clinical data elements must be collected in a standardized and consistent way across venues to facilitate reuse. (Data exchange, CDS, quality) SHB1 [NOW] | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 2.1 | Informatics | ||||||
| VA-NF-T19 | Informatics - Data Reuse | VHA must be able to access and reuse its clinical data in perpetuity without licensing restrictions. (Data exchange) SHB2 | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 2.2 | Informatics | ||||||
| VA-NF-T20 | Informatics - Care Integration | VHA must operate with academic affiliate partners, Community Care partners, DoD, and public health agencies. Standards-based clinical terminology is required for such operations across a continuum of care. (Data Exchange, Process Continuity) ML3 [NOW] | Final | Compatibility | EHRM Lead | ||
| Informatics RTM 3.1 | Informatics | ||||||
| VA-NF-T21 | Informatics - Care Integration | VHA must be able to provide demonstrably high-quality collaborative care in the community without delay or waste or elevated risk. (Data Exchange, Process Continuity, Quality, Safety Value) SHB6 [NOW +] | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 3.2 | Informatics | ||||||
| VA-NF-T22 | Informatics - Care Integration | VHA requires effective integration of a longitudinal record from multiple sources despite technology and information representation disparities via concurrent support of multiple versions of data structures in support of both standards transition periods to newer releases, and interchange with systems supporting older versions of the standard (Data Exchange, Evolution) KSR2 [NOW] | Final | Compatibility | EHRM Lead | ||
| Informatics RTM 3.3 | Informatics | ||||||
| VA-NF-T23 | Informatics - Care Integration | VA must be able to seamlessly integrate with HIE and external-to-EHR shared services to provide for a seamless experience and to more effectively integrate in community care efforts, as well as with other parts of VA (e.g., identity management). This includes but is not limited to the EHR product ability to support external shared services (SOA services, such as identity management, care plan service, scheduling, etc.) accessed via standards-based APIs. (Process Continuity, Evolution, Extension) KSR5 [NOW +] | Final | Compatibility | EHRM Lead | ||
| informatics RTM 3.4 | Informatics | ||||||
| VA-NF-T24 | Informatics - Care Integration | VHA requires the ability to deliver seamless care via distributed care processes, both as a referrer to external care and a referral recipient for externally-initiated care activities. (Data Exchange, Process Continuity) KSR7 [NOW +] | Final | Compatibility | EHRM Lead | ||
| Informatics RTM 3.5 | Informatics | ||||||
| VA-NF-T25 | Informatics - Clinical Decision Support | VA providers and patients EHR experience should be enhanced based on clinical knowledge, analytics, context and situational awareness. (Cognitive Support, innovation) BG3 [NOW] | Final | Compatibility | EHRM Lead | ||
| Informatics RTM 4.1 | Informatics | ||||||
| VA-NF-T26 | Informatics - Clinical Decision Support | VA must be able to utilize specialty external (non-Cerner) standards-based clinical decision support capabilities, such as predictive analytics and enhanced point-of-care decision support to improve clinical quality management and VA clinical efficacy. (CDS, Cognitive Support, Extension, Innovation) KSR4 [1-3] | Final | Compatibility | EHRM Lead | ||
| Informatics RTM 4.2 | Informatics | ||||||
| VA-NF-T27 | Informatics - Clinical Decision Support | VA requires a sandbox to support VA developing the knowledge necessary to leverage the strengths of the new EHR and to align CDS efforts with the to-be host system. The sandbox shall facilitate the following: conforming to national HIT standards, capitalizing on open-source resources, capitalizing on the experience and efforts of Department of Defense and other federal partners, preserving and building on decades of institutional knowledge and experience as represented in VistA and CPRS, future-proofing knowledge-based systems, customizing CDS to account for site-specific variation and available resources and determining points of necessary standardization within VA, creating best practices for developing multi-tiered CDS and other forms of user performance augmentation, developing process for supporting design, implementation, and evaluation of CDS to maximize impact. (CDS, Cognitive Support, Innovation) DLM4 [NOW] | Final | Maintainability | EHRM Lead | ||
| Informatics RTM 4.3 | Informatics | ||||||
| VA-NF-T28 | Informatics - Clinical Decision Support | VHA requires tools that facilitate decision making by the healthcare team and the homecare team including computerized alerts and reminders to care providers and patients; clinical guidelines; condition-specific order sets; focused patient data reports and summaries; documentation templates; diagnostic support, and contextually relevant reference information (CDS) DLM1 [NOW] | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 4.4 | Informatics | ||||||
| VA-NF-T29 | Informatics - Clinical Decision Support | VHA requires information that is filtered, organized and presented in a way that supports the current workflow, allowing the user to make an informed decision quickly and take action. (CDS, Cognitive Support, Innovation) DLM2 [NOW] | Final | Usability | EHRM Lead | ||
| Informatics RTM 4.5 | Informatics | ||||||
| VA-NF-T30 | Informatics - Clinical Decision Support | VHA requires different types of CDS appropriate to optimize different processes of care in different settings and across venues (CDS, Process Continuity, Data Exchange, Extension, Innovation) DLM3 [NOW] | Final | Usability | EHRM Lead | ||
| Informatics RTM 4.6 | Informatics | ||||||
| VA-NF-T31 | Informatics - Clinical Decision Support | VA requires CDS applications that operate as components of a comprehensive EHR system. DLM6 [NOW] | Final | Maintainability | EHRM Lead | ||
| informatics RTM 4.7 | Informatics | ||||||
| VA-NF-T32 | Informatics - Clinical Decision Support | VA requires CDS interventions that address the CDS Five Rights by providing the right information (evidence-based guidance, response to clinical need), to the right people (entire care team – including the patient), through the right channels (e.g., EHR, mobile device, patient portal), in the right formats (e.g., order sets, flow-sheets, dashboards, patient lists), at the right times (CDS) DLM7 [NOW] | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 4.8 | Informatics | ||||||
| VA-NF-T91 | Informatics - Content Integration | VA needs to be able to purchase/acquire and easily deploy standards-based clinical decision support content such as order sets, documentation templates and clinical rules. (Extension, CDS) SHB3 [NOW +] | Final | Maintainability | EHRM Lead | ||
| Informatics RTM 5.1 | Informatics | ||||||
| VA-NF-T92 | Informatics - Content Integration | VA must be able to integrate clinical data, knowledge resources, and workflow across care venues. (CDS, Cognitive Support, Process Continuity, Evolution, Innovation) BG1 [MISSED] | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 5.2 | Informatics | ||||||
| VA-NF-T93 | Informatics - Content Integration | VHA requires extension and import of clinical knowledge (code systems, ontologies, etc.) from external sources, allowing it to more accurately and rapidly ingest best-practices as they are come available from clinical professional societies and peer healthcare delivery organizations. (CDS, Cognitive Support, Extension, Innovation) KSR3 [NOW +] | Final | Compatibility | EHRM Lead | ||
| Informatics RTM 5.3 | Informatics | ||||||
| VA-NF-T94 | Informatics - Content Management | The VA must be able to use CDS, Process Interoperability and Cognitive support mechanisms reliably and consistently over time and across venues of care. The VA must have the ability to monitor and manage all CDS, Process Interoperability and Cognitive Support mechanisms and all dependent subcomponents such as code systems and other data representations (CDS Cognitive Support, Quality, Safety) SHB7 [1-3] | Final | Maintainability | EHRM Lead | ||
| Informatics RTM 6.1 | Informatics | ||||||
| VA-NF-T33 | Informatics - Content Management | VHA must effectively integrate and manage veteran data from heterogeneous external partners that will include versioned structural representations of data, including but not limited to CIMI Model Instances and patient data constructs represented in these structures. (Data Exchange, Evolution) KSR1 [NOW HealtheIintent] | Final | Compatibility | EHRM Lead | ||
| Informatics RTM 6.2 | Informatics | ||||||
| VA-NF-T34 | Informatics - Content Management | The VA must continuously evaluate quality, safety, and value using data sets that cover a time period of 5 years or more (5 year survival for cancer patients is an important benchmark). The VA must have the ability to manage changes in code systems and other data representations over the time period, in order to reliably and consistently assess quality, safety, and value. (Quality, Safety, Value, Evolution) KEC4 [NOW +] | Final | Maintainability | EHRM Lead | ||
| Informatics RTM 6.3 | Informatics | ||||||
| VA-NF-T35 | Informatics - Content Management | VA must be able to extend existing standards content with new codes in a timely and accurate manner. The VA must also have a process by which these extensions are reconciled with the relevant standards. KEC5 [NOW] | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 6.4 | Informatics | ||||||
| VA-NF-T36 | Informatics - Content Management | The VA must ensure that all uses of clinical data must be demonstrably safe for patient care, through the computation and evaluation of metrics, system analysis, and statistical sampling. The VA must never be faced with a circumstance where patient harm resulted from unsafe processing of clinical data, such as sending data through a defective map that may result in errors of care. (Safety, Data Exchange, CDS, Process Continuity, Cognitive Support) KEC2 [NOW +] | Final | Usability | EHRM Lead | ||
| Informatics RTM 6.5 | Informatics | ||||||
| VA-NF-T37 | Informatics - Content Management | VHA must be able to create, modify, maintain, publish, monitor and govern clinical content of all types including terminology, ECA rules, order sets, documentation templates, clinical pathways, guidelines, work flows and governance at enterprise scale. All artifacts must be versioned and their interdependencies known and agily managed. To achieve these goals, integrated tooling for knowledge engineering and knowledge management are required. [1-3] | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 6.6 | Informatics | ||||||
| VA-NF-T38 | Informatics - Content Management | VHA must be able to "mass customize" ("localization") clinical content to meet local needs without inducing undesirable variation in enterprise assets such as coded clinical observations from the point of care. Controlled mass customization should be achieved by creating tools that separate concerns, respect architectural layers, support versioning and dependency management, and have the ability to classify artifact subcomponents into categories of permitted variation. [NOW] | Final | Maintainability | EHRM Lead | ||
| Informatics RTM 6.7 | Informatics | ||||||
| VA-NF-T39 | Informatics - Workflow | VHA must be able to develop, extend and bi-directionally share standards-based care protocols and workflows with external care partners in order to improve care quality, care consistency and enhance VHA’s ability to come into compliance with best-practices in a more timely and accurate way. Expected industry standards such as BPMN, CMMN, DMN (Process Continuity, Quality, Safety Value) KSR6 [>3] | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 7.1 | Informatics | ||||||
| VA-NF-T40 | Informatics - Workflow | VHA requires CDS that is designed using a reference taxonomy of its choosing, such as The Reference Taxonomy of Clinical Workflows or the Clinical Care Ontology that provides a common set of terms to CDS designers and implementers to support communication about CDS and its use in clinical workflows. (CDS) DLM9 [1-3] | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 7.2 | Informatics | ||||||
| VA-NF-T41 | Informatics - Workflow | VHA requires CDS tools and repositories, to enable workflow-related organization and searches. (CDS) DLM10 [NOW +] | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 7.3 | Informatics | ||||||
| VA-NF-T42 | Informatics - Workflow | VHA requires CDS tools that are tagged with terms from a reference taxonomy of its choosing, such as The Reference Taxonomy of Clinical Workflows or the Clinical Care Ontology, to inform practices about the intended use of CDS. (CDS) [1-3] | Final | Functional Suitability | EHRM Lead | ||
| Informatics RTM 7.4 | Informatics | ||||||
| VA-NF-T43 | Informatics - Workflow | VHA requires CDS that is implemented using maps of workflows that have been developed using a reference taxonomy of its choosing, such as The Reference Taxonomy of Clinical Workflows. (CDS) DLM12 [1-3] | Final | Compatibility | EHRM Lead | ||
| Informatics RTM 7.5 | Informatics |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it.