Attatchment 2 Technical Specifications.docx

ATTACHMENT 2

Technical Specifications Vital Records Management System Request for Proposal Number 120277 O3 REBID

Bidder Name: _______________________________________________

Important Scoring Dynamic: Attachment 2 – Technical Specifications shall be subject to a “Pass” or “Fail” assessment. Bidder to review Section (I)(P)(2) of the Request for Proposal (RFP) document for understanding the methodology that will be applied. The items highlighted in gold and notated with an asterisk (*) within this document represent the capability and/or requirement that will be subject to the “Pass” or “Fail” assessment, as these are “must” requirements.

Instructions: Bidders shall review the tables below to understand the structure of this document and how to effectively complete this attachment for inclusion with the RFP submission. Use the format provided to complete this attachment in its entirety. DO NOT ALTER THE COLOR CODING, CONTENT, OR FORMAT OF THIS ATTACHMENT.

Failure to include this completed attachment shall result in the bidder’s Solicitation Response being deemed “Non-Responsive.” Bidder may increase the size of the response box to provide the necessary information. If the response includes other attachments, bidder must indicate that information in the response box. Such attachments must be included with the completed “Attachment 2 – Technical Specifications”.

This document is comprised of four (4) separate categories that are expressed in the table directly below. Each category is identified by the following initial characters:

Each category above contains multiple sub-categories. The table directly below describes the functionality of each column:

CAPABILITIES AND/OR REQUIREMENTS

How to complete the Capabilities and/or Requirements: Bidders shall provide information in each respective “Response” box provided. Each individual response shall include the information as indicated. Such responses shall include specific details, characteristics and key aspects to demonstrate the bidder’s proposed solution and how it meets the conformance specification outlined in relation to the project

Architecture Capabilities and/or Requirements

Technology Architecture: Describe the software components, including third-party software products, open-source libraries, and utilities that complete the platform for running a service or supporting an application. This section should document any technical requirements for accessing the software, including but not limited to client desktop installs, etc. Further, the section should clearly outline any State required infrastructure, such as setting up VPN, SFTP, etc., to implement or operate the system.

Network Architecture: Describe the means of communication, the method of sending and receiving information, between the assets in the Technology Architecture.

Application Architecture: Describe how the solution components are assembled and interact to meet the business needs. Describe the solution’s ability to manage and store documents and attachments.

Data Flow Architecture: Describe the data flows into and out of the system boundary, include transmission and storage, along with ports, protocols, and services of all inbound and outbound traffic.

Response:

Response:

• Type of Software – SaaS, PaaS or, IaaS

• Licensing Model- Perpetual or Subscription based licenses

• Single or Multi-Tenant architecture

Response:

Response:

· Section 508 compliance standards (https://www.section508.gov/manage/laws-and-policies/)

· 45 CFR Part 85 (https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-A/part-85)

· State of Nebraska Accessibility requirements (https://nitc.nebraska.gov/standards/index.html#2).

Bidder must confirm that your company has read, understands, and can meet all the capabilities and/or requirements as outlined for each of the items and indicate how your solution will meet such requirements as they relate to the accessibility requirements.

Response:

Security and Compliance Capabilites and Requirements

• DHHS Information Technology (IT) Security Policies and Standards (http://dhhs.ne.gov/ITSecurity).

• Nebraska Information Technology Commission (NITC) Standards and Guidelines (https://nitc.nebraska.gov/standards/index.html).

• Health Insurance Portability and Accountability Act (HIPAA) of 1996.

Bidder must confirm that your company has read, understands, and can meet all the capabilities and/or requirements as outlined for each of the items and indicate how your solution will meet such requirements as they relate to the standards and policies described above.

Response:

Response:

Response:

Response:

Response:

SPC-6

Describe the bidder solution for the following:

• Support for self-service password activities.

• Automatic log-off procedures after determined time of session inactivity.

• Automatic account disablement after 120 days of inactivity.

• Administrators’ ability to lockout user(s).

• Support and approach for single sign-on

• Support and approach for Multi-Factor Authentication

• Automatic locking of account after determined number of failed logon attempts.

Response:

Response:

• How user accounts are assigned and managed.

• How the system provides usage reports, such as a listing of all users and their last usage date.

• How the system supports authorization at an attribute/field level (e.g., edit, view).

Response:

Bidder must confirm that your company has read, understands, and can meet all the capabilities and/or requirements as outlined and indicate how your solution will meet such requirements. As a part of the bidder’s response, at minimum, the State desires specific information regarding the following elements:

· Detail the data elements that are audited.

· Outline the level of audit tracking being maintained.

· Provide a sample of their audit reports.

· Capabilities for automated audit log evaluation to identify security issues.

· How the bidder monitors, identifies, and reports on events impacting the system, such as attacks and other unauthorized use of the system.

Response:

Database/Data Management Capabilities and/or Requirements

Response:

Response:

Response:

:• Ability to import and export data using these file types (XML, JSON, CSV).

• Support for integration using industry standards approaches and principles for REST APIs and Webservices.

• Support for industry integration data standards for Health Level 7 (HL7), Fast Healthcare Interoperability Resources (FHIR), X-12, HIPAA.

Response:

• Documentation to support testing and collaboration with integrating systems.

• Documentation of the system's data dictionary which includes user-defined fields and tables.

Response:

· 45 CFR Part 164.316 (https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C/section-164.316)

· DHHS Vital Records retention schedule is to retain information permanently.

Bidder must confirm that your company has read, understands, and can meet all the capabilities and/or requirements as outlined for each of the items and indicate how your solution will meet such requirements as they relate to the data retention requirements.

Response:

Operations Management Capabilities and/or Requirements

• Procedures for data backup, restoration, communication to the State of Nebraska, and emergency mode operations in the event of:

a. Hardware or Software Failures.

b. Human Error.

c. Natural Disaster; and/or

d. Other unforeseeable emergencies.

Response:

Response:

Response:

• Compliance with the Recovery Time Objective (RTO) of within twelve (12) hours when the system outage is declared as a disaster.

• Compliance with the Recovery Point Objective (RPO) of fifteen (15) minutes of data lost before the disaster event.

Response:

• Overall testing strategy and support for the following testing types: unit testing, system testing, integration testing, regression testing, user acceptance testing (UAT), parallel testing, performance and load testing, manual and automated and/or scripted testing, and end-to-end integration testing.

• Approach to planning and preparing the test/staging environment.

• Approach to conducting each test level.

• Approach for testing nonfunctional requirements (security, performance, etc.)

• Approach to test documentation (e.g., test cases, test scripts, test case matrices added as the design configuration progresses).

• Approach to quality control/quality assurance.

• Approach to test results reporting, traceability, and metrics.

Response:

• Approach to managing software versions to ensure bidder support.

• Approach to Change Management, including defects and enhancements.

• Approach to testing and release management.

• Approach to maintaining integrations with external and internal trading partners.

Response:

Response:

Response:

• The system architecture must support scaling with increased load.

• The system must provide high availability to support minimum disruptions to the business operations.

• The system must handle notifications when a component or interface endpoint is unavailable.

• The system must handle performance functionality and monitoring tools.

• The system must handle recovery of failed transactions because of a component failure.

• The system must be available online 24 hours a day and 7 days a week, 99.9% of the time each month excluding scheduled downtime.

Response:

11/06/2025 Technical Specifications Nebraska Department of Health and Human Services