Response Form for Technical Requirements.docx

DOCX document 61 KB Posted

Attached to
[REPOST] 988 NSPL Crisis Call Center & BH Integrated Referral System
Solicitation number
2023HCA15
Issued by
Adams County, Asotin County, Benton County, Chelan County, Clallam County, Clark County, Columbia County, Cowlitz County, Douglas County, Ferry County, Franklin County, Garfield County, Grant County, Grays Harbor County, Island County, Jefferson County, King County, Kitsap County, Kittitas County, Klickitat County, Lewis County, Lincoln County, Mason County, Okanogan County, Pacific County, Pend Oreille County, Pierce County, San Juan County, Skagit County, Skamania County, Snohomish County, Spokane County, Stevens County, Thurston County, Wahkiakum County, Walla Walla County, Whatcom County, Whitman County, Yakima County, Asotin City, Clarkston City, Clarkston Heights-Vineland CDP, West Clarkston-Highland CDP, Benton City, Chelan City, Chelan Falls CDP, Clallam Bay CDP, Lewisville CDP, Rock Island City, Pacific Beach CDP, Whidbey Island Station CDP, Mercer Island City, Pacific City, Bainbridge Island City, Kingston CDP, Kitsap Lake CDP, Kittitas City, Klickitat CDP, Okanogan City, Anderson Island CDP, Fort Lewis CDP, Fox Island CDP, Herron Island CDP, Ketron Island CDP, North Fort Lewis CDP, Raft Island CDP, Stevenson City, Hat Island CDP, Lake Stevens City, Snohomish City, Spokane City, Spokane Valley City, Puget Island CDP, Garfield Town, Yakima City, Washington

About this file

This document is a Response Form for Technical Requirements issued by the Washington State Healthcare Authority (HCA) and Washington Department of Health (DOH) for a state and local contract opportunity. The contract opportunity is for a system that meets the needs of House Bill 1477, which requires enhancements to the crisis call and response platform and the behavioral health integrated client referral system. The response form covers requirements across multiple sections, including cloud-based solutions, SaaS/COTS solutions, natural system boundaries, data governance, data security and system management, privacy and protocols, and tribal data sovereignty. Responders are required to indicate compliance, core functionality, third-party involvement, and custom development for each requirement, as well as provide detailed responses describing their approach.

The contract opportunity is for Thurston County, Washington (FIPS Code 53067). The document does not provide information on pricing terms, set asides, incumbents, current environment, funding requirements and sources, or award dates. However, it does indicate that the system must meet federal certification and performance standards defined in 42 C.F.R. 433.112(b) and the Medicaid Information Technology Architecture (MITA) initiative and framework.

View the file

Other files

File Type Posted
RFI 2023HCA15 Q&A Round 2.pdf PDF
Enforcement_Tracking_Input_Screens.docx DOCX document
RFI 2023HCA15 - Q&A Round 1.pdf.crdownload CRDOWNLOAD file
RFI 2023HCA15 - Q&A Round 1.pdf PDF
RFI 2023HCA15 - 2nd Schedule Update.pdf PDF
2023HCA15 - 988 RFI.pdf PDF
Response Form for Functional Requirements.docx DOCX document
RFI 2023HCA15 - Schedule Update.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Response Form for Technical Requirements

TECHNICAL RESPONSE

Responder must use this provided response form for responding to the Technical Section.

For each requirement identified below, complete the provided tables’ information as follows:

a) Comply: Insert an “X” if the Responder’s offering complies with the requirement and leave blank if the Responder’s offering does not comply with the requirement. Responder must also indicate how it will comply, where a, b and c are not mutually exclusive.

b) Core: Insert an “X” if the Responder currently provides this requirement through their solution “out of the box” without any custom development. If implemented in another state or non-state entity, it can be adapted from another entity “as-is” or with little modification for Washington State.

c) Custom: Insert an “X” if the Responder proposes to meet this requirement through custom development or through moderate or extensive modification to the system and leave blank if the Responder does not require custom development or moderate/extensive modifications to meet this requirement. Note: indicate “custom” for those features that require substantial or “from the ground up” development efforts, including moderate or extensive modifications to a transfer system.

d) 3rd Party: Insert an “X” if the Responder proposes to meet this requirement through a relationship with another party (e.g., a sub-contractor, or other 3rd party) and leave blank if the Responder does not plan to form a relationship with another firm to meet this requirement.

Response: Insert a complete description of the Responder’s approach to meeting this requirement. Insert the response directly in the table, using as much space as needed. Responders are highly encouraged to explain responses in sufficient detail to meet the requirement and not provide single-line responses.

REQUIREMENTS TABLE ON THE FOLLOWING PAGE

HCA RFP No.Page 3 of 128
Washington State

Health Care Authority and Department of Health

Page 24 of 58
RFI 2023HCA15

Response Form for Technical Requirements

Technology Section

Req. #
Requirement
(1)

Comply (a) Core (b) 3rd Party (c) Custom

Section I: Cloud-based solutions

I.1
Describe how your system(s) leverages cloud-based technology and scaling based on needs.
☐☐☐☐
Response:
I.2
Describe how your system supports needed storage consistent with data retention policies.
☐☐☐☐
Response:
I.3
Describe how you engage, support, manage and segregate roles, data, and implement security across the system.
☐☐☐☐
Response:
I.4
Describe how your system will keep up with future trends in cloud technology.
☐☐☐☐
Response:
I.5
Tell us anything else you would like us to know about your cloud-based solutions.
☐☐☐☐
Response:

Section II. SaaS/COTS solutions

II.1
Describe how your system(s) allows us to leverage SaaS technology and shared resources.
☐☐☐☐
Response:
II.2
Describe how your system is configured and administered.
☐☐☐☐
Response:
II.3
Describe any coding or configuration that would need to be done for implementation of the system.
☐☐☐☐
Response:
II.4
Describe how your system supports new features.
☐☐☐☐
Response:
II.5
Describe how your system supports implementations of external technology that would need to interoperate with your system.
☐☐☐☐
Response:
II.6
Tell us anything else you would like us to know about SaaS/COTS solutions.
☐☐☐☐
Response:

Section III. Natural System Boundaries

III.1
Describe how your system(s) supports API or any technology that would allow your system to be interoperable with other systems.
☐☐☐☐
Response:
III.2
Describe how your system(s) help the state reduce disruptions and maintain a high availability environment.
☐☐☐☐
Response:
III.3
Describe how you keeps costs down for the state when there are major issues, downtime, and major disruptions.
☐☐☐☐
Response:
III.4
Describe how your system meets or exceeds Federal certification and performance standards by meeting the conditions defined in 42 C.F.R. 433.112(b) and those principles established under the Medicaid Information Technology Architecture (MITA) initiative and framework.
☐☐☐☒
Response:
III.5
Tell us how you reduce risks in your systems
☐☐☐☐
Response:
III.6
Tell us how you have loose coupling in your system
☐☐☐☐
Response:
III.7
Describe the ability of the primary vendor to add, change or decouple features and components, as needed, to integrate and interoperate with tools/modules offered by partnering vendors, including Electronic Health Records (EHRs).
☐☐☐☐
Response:
III.8
Tell us anything else you would like us to know regarding natural system boundaries.
☐☐☐☐
Response:

Technology Section

Section IV. Data Governance

Req. #
Requirement
(1)

Comply (a) Core (b) 3rd Party (c) Custom

IV.1
Describe how your system supports data segregations and roles for the various listed groups and users (including Tribal governments, urban Indian health organizations, and tribal organizations)
☐☐☐☐
Response:
IV.2
Describe any agreements that are needed for your systems and list:
•What type of agreement,
•And who the parties are in these agreements.
☐☐☐☐
Response:
IV.3
Tell us anything else you would like us to know regarding data governance.
☐☐☐☐
Response:

END OF SECTION 1.1.2

Technology Section

Section V. Data Security and System Management

Req. #
Requirement
(1)

Comply (a) Core (b) 3rd Party (c) Custom

V.1
Describe how your system supports each of the items: Data Disclosure
☐☐☐☐
Response:
V.2
Describe how your system supports each of the items: Business Impact Analysis (BIA)
☐☐☐☐
Response:
V.3
Describe how your system supports each of the items: Data Backup and Recovery
☐☐☐☐
Response:
V.4
Describe how your system supports each of the items: Disaster Recovery Plan (DRP)
☐☐☐☐
Response:
V.5
Describe how your system supports each of the items: Continuity of Operations Plan (COOP)
☐☐☐☐
Response:
V.6
Describe how your system supports each of the items: Technical Support
☐☐☐☐
Response:
V.7
Describe how your system supports each of the items: Maintenance
☐☐☐☐
Response:
V.8
Describe how your system supports each of the items: Data Archiving for Security
☐☐☐☐
Response:
V.9
Describe how your system supports each of the items: Disposal of Data
☐☐☐☐
Response:
V.10
Describe how your system supports each of the items: Location Security
☐☐☐☐
Response:
V.11
Describe how your system supports each of the items: Encryption (in transit and at rest)
☐☐☐☐
Response:
V.12
Describe how your system supports each of the items: Data Sources
☐☐☐☐
Response:
V.13
Describe how your system supports each of the items: Data Interoperability Requirements
☐☐☐☐
Response:
V.14
Describe how your system supports each of the items: Extensibility, Scalability, and Availability
☐☐☐☐
Response:
V.15
Tell us anything else you would like us to know about data security and system management.
☐☐☐☐
Response:

Technology Section

Section VI. Privacy and Protocols

Req. #
Requirement
(1)

Comply (a) Core (b) 3rd Party (c) Custom

VI.1
Describe how your system supports privacy for each of the items listed above.:

Washington State law (Chapter 9.73 RCW: PRIVACY, VIOLATING RIGHT OF (wa.gov)): most importantly the Uniform Health Care Information Act (UHCIA Chapter 70.02 RCW), which contains federal privacy and security laws;

☐☐☐☐
Response:
VI.2
Describe how your system supports privacy for each of the items listed above:

HIPAA

☐☐☐☐
Response:
VI.3
Describe how your system supports privacy for each of the items listed above:

42 CFR Part 2.

☐☐☐☐
Response:
VI.4
Tell us anything else you would like us to know regarding privacy and protocols.
☐☐☐☐
Response:

END OF SECTION 1.1.4

Technology Section

Section VII. Tribal Data Sovereignty

Req. #
Requirement
(1)

Comply (a) Core (b) 3rd Party (c) Custom

VII.1
Tell us how your system supports tribal data sovereignty if it has not already been addressed in the section for data segregation. If it has, please put “Addressed in Data Segregation section”
☐☐☐☐
Response:
VII.2
Tell us anything else you would like us to know regarding Tribal data sovereignty.
☐☐☐☐
Response:

END OF TECHNICAL SECTION

Washington State Health Care Authority and Department of Health

Page 1 of 12
RFI 2023HCA15

Response Form for Technical Requirements

File details come from the government source that posted it. Updated .