Response Form for Functional Requirements.docx

DOCX document 78 KB Posted May 10, 2023

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

Written by GovTribe AI · Apr 3, 2024

This document is a Response Form for Functional Requirements for a state and local contract opportunity issued by the Washington State Healthcare Authority (HCA) and Washington Department of Health (DOH). The opportunity involves the procurement and implementation of a system to meet the requirements of House Bill 1477, which mandates enhancements to the crisis call and response platform and the behavioral health integrated client referral system. The response form covers functional requirements across various sections, including Call Center Platform, Responder Dispatching, Resource Directory, Provider Portal, Referrals and Appointments, Consent Management, Electronic Documents, Bed Registry, and Reporting. Responders must use the provided form to indicate compliance, identify core capabilities, custom development needs, and third-party relationships for each requirement. The contract opportunity is limited to Thurston County, Washington.

The document does not provide details on pricing terms, set-asides, incumbent vendors, funding sources, or amounts. However, it emphasizes the need for efficient and timely system functionality, interoperability, and stakeholder engagement throughout the implementation process.

View the file

Other files

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

On GovTribe

Work with this file

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Response Form for Functional Requirements

FUNCTIONAL RESPONSE

Responder must use this provided response form for responding to the Functional 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 3 of 22

RFI 2023HCA15

Response Form for Functional Requirements

Functional Section

Req. #

Requirement

(1)

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

Section VIII. Call Center Platform: Create, Assign, & Track (follow-up)

VIII.1

Describe how your system supports each of the following:

Encounter Intake (Call/SMS/Chat)

☐	☐	☐	☐
Response:

VIII.2

Describe how your system supports each of the following:

Telephony/IVR/CTI Integration

☐	☐	☐	☐
Response:

VIII.3

Describe how your system supports each of the following:

In-state Call Routing

☐	☐	☐	☐
Response:

VIII.4

Describe how your system supports each of the following:

GPS location of caller

☐	☐	☐	☐
Response:

VIII.5

Describe how your system supports each of the following:

Caller history information

☐	☐	☐
☐
Response:

VIII.6

Describe how your system supports each of the following:

Crisis alerts

☐	☐	☐	☐
Response:

VIII.7

Describe how your system supports each of the following:

Referrals

☐	☐	☐	☐
Response:

VIII.8

Describe how your system supports each of the following:

Follow-up

☐	☐	☐	☐
Response:

VIII.9

Describe how your system supports each of the following:

System outages

☐	☐	☐	☐
Response:

VIII.10

Describe how your system supports each of the following:

Provider Integration

☐	☐	☐	☐
Response:

VIII.11

Describe how your system supports each of the following:

Workforce Management, including call taker availability

☐	☐	☐	☐
Response:

VIII.12
Name the specific standards that are applicable and used in each of your systems/tools for each of the functions listed above (Section 8.1.) to support interoperable exchange, re-use, and access, including the standards identified in the Technical Requirements below.
☐	☐	☐	☐
Response:

VIII.13
Describe how your system will support in-state call routing while aligning with national call center efforts.
☐	☐	☐	☐
Response:

VIII.14
Describe the issues associated with using geolocation of crisis callers and how your system(s) does (or will) address or mitigate these concerns (upon FCC approval).
☐	☐	☐	☐
Response:

VIII.15
Describe the issues associated with sending, receiving, retrieving, and using electronic information from providers and how your system(s) does (or will) address or mitigate these concerns.
☐	☐	☐	☐
Response:

VIII.16
Describe the issues associated with sending, receiving, retrieving, and using electronic information from providers and how your system(s) does (or will) address or mitigate these concerns.
☐	☐	☐	☐
Response:

VIII.17
Describe how you engage, support, and manage stakeholder implementation of systems/tools in Section 8.1.
☐	☐	☐	☐
Response:

VIII.18
Tell us anything else that you would like us to know regarding functionality needed for the Call Center Platform.
☐	☐	☐	☐
Response:

Section IX. Responder Dispatching: Identify, Dispatch, & Track

IX.1

Describe how your system supports each of the following:

GPS (i.e., Geolocation) Responder Tracking;

☐	☐	☐	☐
Response:

IX.2

Describe how your system supports each of the following:

Dispatch Coordination

☐	☐	☐	☐
Response:

IX.3

Describe how your system supports each of the following:

Resource Map (including updates).

☐	☐	☐	☐
Response:

IX.4
Name the specific standards that are applicable and used in each of your systems/tools to support interoperable exchange, re-use, and access regarding each of the functions listed above (Section 9.1) including the standards identified in the Technical Requirements in Section 4 above.
☐	☐	☐	☐
Response:

IX.5
Describe how your system will support efficient and timely response for in-state calls routing while aligning with national 988 NSPL crisis call center efforts.
☐	☐	☐	☐
Response:

IX.6
Describe the issues associated with using geolocation for crisis responders and how your system(s) does (or will) address or mitigate these concerns, including supporting responder tracking and dispatch in areas that are unserved/underserved by broadband.
☐	☐	☐	☐
Response:

IX.7
Describe how you engage, support, and manage stakeholder implementation of systems/tools in Section 9.1.
☐	☐	☐	☐
Response:

IX.8
Tell us anything else that you would like us to know regarding functionality needed for Responder Dispatching.
☐	☐	☐	☐
Response:

Section X. Resource Directory: Access, Use, Query, & Share

X.1

Describe how your system supports:

Access to and use of multiple external resource directories

☐	☐	☐	☐
Response:

X.2

Describe how your system supports:

Querying resource availability

☐	☐	☐	☐
Response:

X.3

Describe how your system supports:

Displaying results

☐	☐	☐	☐
Response:

X.4

Describe how your system supports:

Sharing resource information with callers and providers.

☐	☐	☐	☐
Response:

X.5
Name the specific standards that are applicable and used in each of your systems/tools to support interoperable exchange and re-use for accessing and using external resource directories (described in Section 10.1.)
☐	☐	☐	☐
Response:

X.6
Describe how your system supports efficient and timely access and use of external resource directories.
☐	☐	☐	☐
Response:

X.7
Describe any issues associated with your systems/tools in accessing and using external resource directories and how these issues have been/will be resolved.
☐	☐	☐	☐
Response:

X.8
Tell us anything else that you would like us to know regarding functionality needed for Resource Directories.
☐	☐	☐	☐
Response:

Functional Section

Section XI. Provider Portal: Search, Create, Request, Exchange (Ingest & Share), and Manage Account

Req. #

Requirement

(1)

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

XI.1

Describe how your system supports:

For providers without integration capabilities, accessing and searching a portal, creating requests via a portal, downloading information from a portal, and managing access and use of the portal.

☐	☐	☐	☐
Response:

XI.2

Describe how your system supports:

For providers with integration capabilities, accessing and searching a portal, creating requests via a portal, downloading information from a portal, and managing access and use of the portal.

☐	☐	☐	☐
Response:

XI.3
Name the specific standards that are applicable and used in each of your systems/tools to support interoperable access and use of the provider portal.
☐	☐	☐	☐
Response:

XI.4
Describe how your system supports efficient and timely access to and use of the provider portal.
☐	☐	☐	☐
Response:

XI.5
Describe any issues associated with your systems/tools in supporting provider portals (e.g., including electronic use) and how these issues have been/will be resolved.
☐	☐	☐	☐
Response:

XI.6
Describe how you engage, support, and manage stakeholder implementation of systems/tools in Section 11.1.
☐	☐	☐	☐
Response:

XI.7
Tell us anything else that you would like us to know regarding functionality needed for Provider Portal.
☐	☐	☐	☐
Response:

Functional Section

Section XII. Referrals and Appointments: Search, Create, Assign, & Track

Req. #

Requirement

(1)

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

XII.1

Describe how your system(s) supports:

Next Day Appointments;

☐	☐	☐	☐
Response:

XII.2

Describe how your system(s) supports:

Closed loop referrals

☐	☐	☐	☐
Response:

XII.3

Describe how your system(s) supports:

Provider to Provider referrals.

☐	☐	☐	☐
Response:

XII.4
Name the specific standards that are applicable and used in each of your systems/tools to support the interoperable creation and exchange of next day appointments and referrals (described in Section 12.1.).
☐	☐	☐	☐
Response:

XII.5
Describe how your system supports efficient and timely access to needed appointments and referrals from the perspectives of the client, provider, and system.
☐	☐	☐	☐
Response:

XII.6
Describe any issues and challenges associated with your systems/tools in supporting next day appointments, referrals, and closed loop referrals, and how these issues have been/will be resolved.
☐	☐	☐	☐
Response:

XII.7
Describe how you engage, support, and manage stakeholder implementation of systems/tools in Section 12.1.
☐	☐	☐	☐
Response:

XII.8
Tell us anything else that you would like us to know regarding functionality needed for Referrals and Appointments.
☐	☐	☐	☐
Response:

Functional Section

Section XIII. Manage Consent: Capture, Share, & Retrieve

Req. #

Requirement

(1)

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

XIII.1.a

Describe how your system(s) supports:

Compliance with federal and state privacy requirements;

☐	☐	☐	☐
Response:

XIII.1.b

Describe how your system(s) supports:

Capturing, sharing, retrieving, and documenting the individual’s consent;

☐	☐	☐	☐
Response:

XIII.1.c

Describe how your system(s) supports:

Revoking consent upon request

☐	☐	☐	☐
Response:

XIII.1.d

Describe how your system(s) supports:

Overriding the need to obtain consent to share information when necessary to protect the individual and/or community’s health and safety.

☐	☐	☐	☐
Response:

XIII.2
Name the specific standards that are applicable and used in each of your systems/tools to support creation and exchange of a caller’s consent to share information, including verbal, paper, and electronic consent.
☐	☐	☐	☐
Response:

XIII.3
Describe how your system supports efficient and timely gathering of client consent and appropriate information sharing.
☐	☐	☐	☐
Response:

XIII.4
Describe any issues associated with your systems/tools in capturing, sharing, retrieving, documenting, and revoking consent upon an individual’s request; and how these issues have been/will be resolved.
☐	☐	☐	☐
Response:

XIII.5

Describe how you engage, support, and manage stakeholder implementation of systems/tools in Section XIII.1.

☐	☐	☐	☐
Response:

XIII.6
Tell us anything else that you would like us to know regarding functionality needed to manage Consent.
☐	☐	☐	☐
Response:

Functional Section

Section XIV. Electronic Documents: Create, Display, Modify, & Exchange

Req. #

Requirement

(1)

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

XIV.1

Describe how your system(s) supports needed functionality for:

LRAs

☐	☐	☐	☐
Response:

XIV.2

Describe how your system(s) supports needed functionality for:

MHADs

☐	☐	☐	☐
Response:

XIV.3

Describe how your system(s) supports needed functionality for:

Crisis plans

☐	☐	☐	☐
Response:

XIV.4

Describe how your system(s) supports needed functionality for:

Assessments, including risk assessments and level of care assessments

☐	☐	☐	☐
Response:

XIV.5

Describe how your system(s) supports needed functionality for:

Safety plans

☐	☐	☐	☐
Response:

XIV.6
Describe how your system supports/will support the use of a cloud-based repository to maintain and access documents (as needed).
☐	☐	☐	☐
Response:

XIV.7
Name the specific standards that are applicable and used in each of your systems/tools to support the interoperable creation, receipt, exchange, display, and revocation of documents required in Section 14.1.
☐	☐	☐	☐
Response:

XIV.8
Describe how your system supports efficient and timely creation, receipt, updates, transmission, and revocation of documents required in Section 14.1.
☐	☐	☐	☐
Response:

XIV.9
Describe any issues associated with your systems/tools in receiving, exchanging, displaying, and revoking documents in Section 14.1. and how these issues have been/will be resolved.
☐	☐	☐	☐
Response:

XIV.10
Describe how you engage, support, and manage stakeholder implementation of systems/tools in Section 14.1. and use of a cloud-based repository.
☐	☐	☐	☐
Response:

XIV.11
Tell us anything else that you would like us to know regarding functionality needed regarding Electronic Documents.
☐	☐	☐	☐
Response:

Functional Section

Section XV: Bed Registry: Display, Search, Refer, Update, Collect, Capture, Report

Req. #

Requirement

(1)

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

XV.1

Describe how your system(s) supports functionality for:

Displaying needed real-time bed availability information and characteristics

☐	☐	☐	☐
Response:

XV.2

Describe how your system(s) supports functionality for:

Updating of bed availability information

☐	☐	☐	☐
Response:

XV.3

Describe how your system(s) supports functionality for:

Searching for and referring to open beds

☐	☐	☐	☐
Response:

XV.4

Describe how your solution(s) may support the following:

DOH and HCA would prefer bed registries be available on a public facing website to encourage accessibility.

☐	☐	☐	☐
Response:

XV.5

Describe how your system(s) supports functionality for:

Reporting on user defined bed metrics.

☐	☐	☐	☐
Response:

XV.6
Name the specific standards that are applicable and used in each of your systems/tools to support interoperable use of bed registries including the functionality described in Section 15.1.
☐	☐	☐	☐
Response:

XV.7
Describe how your system supports efficient and timely updates, search, access, and reports of information required in Section 15.1.
☐	☐	☐	☐
Response:

XV.8
Describe any issues associated with your systems/tools in displaying, updating, searching, and reporting on bed registry information; and how these issues have been/will be resolved.
☐	☐	☐	☐
Response:

XV.9
Describe how you engage, support, and manage stakeholder implementation of systems/tools in Section 15.1.
☐	☐	☐	☐
Response:

XV.10
Tell us anything else that you would like us to know regarding functionality needed for Bed Registries.
☐	☐	☐	☐
Response:

Functional Section

Section XVI: Reporting: Create, Customize & Share

Req. #

Requirement

(1)

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

XVI.1

Describe how your system(s) supports needed functionality for:

Standard and custom reports

☐	☐	☐	☐
Response:

XVI.2

Describe how your system(s) supports needed functionality for:

Automated electronic and manual reporting processes

☐	☐	☐	☐
Response:

XVI.3

Describe how your system(s) supports needed functionality for:

Generating current and future reports

☐	☐	☐	☐
Response:

XV.4

Describe how your system(s) supports needed functionality for:

Using dashboards

☐	☐	☐	☐
Response:

XV.5

Describe how your system(s) supports needed functionality for:

Supporting interoperability

☐	☐	☐	☐
Response:

XVI.6
Name the specific standards that are applicable and used in each of your systems/tools to support interoperable creation, display, and exchange (send and received) of standard and custom reports (as summarized in Section XVI and the functions described in Section 16.1.).
☐	☐	☐	☐
Response:

XVI.7
Describe how your system supports efficient and timely creation, display, and exchange of standard and user-defined custom reports.
☐	☐	☐	☐
Response:

XVI.8
Describe any issues associated with your systems/tools in creating, displaying, and exchanging standard and user-defined custom reports; and how these issues have been/will be resolved.
☐	☐	☐	☐
Response:

XVI.9
Describe how you engage, support, and manage stakeholder implementation of systems/tools in Section 16.1.
☐	☐	☐	☐
Response:

XVI.10
Tell us anything else that you would like us to know regarding functionality needed for Reporting.
☐	☐	☐	☐
Response:

END OF FUNCTIONAL SECTION

Washington State Health Care Authority and Department of Health

Page 28 of 58

RFI 2023HCA15

Response Form for Functional Requirements

File details come from the government source that posted it. Updated Apr 3, 2024.