ATTACHMENT H_S-DASOBO-00010624_Requirements.xlsx
XLSX spreadsheet 45 KB Posted
- Attached to
- Oregon State Based Insurance Marketplace Solution State and local contract opportunity
- Solicitation number
- S-DASOBO-00010624
- Issued by
- Marion County, Oregon
About this file
This document is the Attachment H - SBM Solution Functionality requirements from Request for Proposals (RFP) S-DASOBO-00010624, issued by the Oregon Health Authority (OHA) on behalf of the Oregon Department of Administrative Services (DAS) to procure a State-Based Insurance Marketplace (SBM) Solution Platform and related Customer Assistance Center. The SBM solution must meet 96 technical and business functionality requirements across 8 categories, with a total of 299 subjective points available. Proposers must select from 5 response options for each requirement, with the response indicating the availability of the functionality. The solution must support key features such as account creation, anonymous user experience, plan comparison and enrollment, communication tools, eligibility determination, security and compliance, and reporting capabilities. The contract term and details around pricing, funding, and other salient information are not provided in this attachment.
View the file
Other files for this state and local contract opportunity
Show all 17
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
Tab 1 - Instructions
RFP S-DASOBO-00010624
Attachment H - SBM Solution Functionality
Proposer shall complete and submit an electronic version of Attachment H – SBM Solution Functionality demonstrating how the proposed SBM solution addresses the requirements. Please follow these instructions when completing Attachment H, Tab 2 – Scoring Matrix.
The sheet is protected to only allow entries to be made in columns F and G. Only selections made in Column F will be scored.
The Tab 2 – Scoring Matrix formatting, instructions, and scoring are as follows:
1st Column / Column A: Item #
2nd Column / Column B: Title
3rd Column / Column C: Description
4th Column / Column D: Requirement Category/Type. There are a total of 96 Line Items in 8 categories as follows with the number of line items for each and line item numbers in parentheticals and maximum subjective points by area in red font.
• User Interface/ Experience | 21 Line Items (1 to 21) | 66 POINTS SUBJECTIVE
• Technical | 23 Line Items (22 to 44) | 72 POINTS SUBJECTIVE
• Eligibility | 11 Line Items (45 to 55) | 34 POINTS SUBJECTIVE
• Security | 5 Line Items (56 to 59 and 96) | 16 POINTS SUBJECTIVE
• CAC | 22 Line Items (60 to 81) | 69 POINTS SUBJECTIVE
• Mailroom/ Printshop | 4 Line Items (82 to 85) | 12 POINTS SUBJECTIVE
• Policy/ Regulatory Compliance | 4 Line Items (86 to 89) | 12 POINTS SUBJECTIVE
• Reporting | 6 Line Items (90 to 95) | 19 POINTS SUBJECTIVE
5th Column / Column E: Priority Rating Rating for each requirement based on OHA program priority.
• High Priority = 3
• Medium Priority = 2
• Low Priority = 1
6th Column / Column F: Response For each requirement, select one of five Response options from the drop-down menu. These Response options are:
• Currently Exists – A selection of "Currently Exists" from the drop-down menu asserts that the functionality described by the requirement currently exists in the Proposer's SBM and is in successful public entity production environment. A selection of "Currently Exists" from the drop-down menu equals 5 points multiplied by the requirement’s Priority Rating (shown in Column E).
• Available by UAT (configuration) – This selection must be accompanied by a comment in the comment section, with an explaination or reference. A selection of "Available By UAT (configuration)" from the drop-down menu asserts that the Proposer can meet this requirement with configuration by the start of UAT. A selection of "Available By UAT (configuration)" from the drop-down menu equals 4 points multiplied by the requirement’s Priority Rating.
• Available by UAT (customization) – This selection must be accompanied by a comment in the comment section, with an explaination or reference. A selection of "Available by UAT (customization)" from the drop-down menu asserts that the Proposer can meet this requirement with custom programming by the start of UAT. A selection of "Available by UAT (customization)" from the drop-down menu equals 3 points multiplied by the requirement’s Priority Rating.
• Available Post Rollout (configuration) – This selection must also be accompanied by a comment in the comment section, with an explaination or reference. A selection of "Available Post Rollout (configuration)" from the drop-down menu asserts that the Proposer can meet this requirement with configuration, but the modification would not be available until after the Rollout is complete. A selection of "Available Post Rollout (configuration)" from the drop-down menu equals 2 points multiplied by the requirement’s Priority Rating.
• Available Post Rollout (customization) – This selection must also be accompanied by a comment in the comment section, with an explaination or reference. A selection of "Available Post Rollout (customization)" from the drop-down menu asserts that the Proposer can meet this requirement with custom programming, but the modification would not be available until after the Rollout is complete. A selection of "Available Post Rollout (customization)" from the drop-down menu equals 1 point multiplied by the requirement’s Priority Rating.
• Not Available – A selection of "Not Available" from the drop-down menu asserts that the Proposer cannot meet the requirement with the proposed SBM. A selection of "Not Available" from the drop-down menu equals 0 points.
• Not Yet Scored – The default selection in the Response column, signifying the Proposer has not yet made a selection. Any item remaining as "Not Yet Scored" in a submission will equal 0 points.
7th Column / Column G: Comments Space for Proposer to include any desired comments or clarifications for an individual requirement Response selection.
8th Column / Column H: Auto Calculated Response Selection Points An auto calculated cell showing the points consistent with the Response selection made in Column E.
9th Column / Column I: Maximum Points The maximum points available for each requirement, determined by the score for the Response selection “Currently Exists” multiplied by the requirement’s Priority Rating in Column D.
10th Column / Column J: Auto Calculated Points An auto calculated cell showing the points calculated from multiplying the Auto Calculated Response Selection Points in Column G and the requirement’s Priority Rating in Column D. The sum of all Auto Calculated Points is shown in cell J62.
Definitions:
1. Customization: Customization refers to the process of modifying or tailoring a SaaS solution to meet specific requirements. It involves making changes to the software's functionality, user interface, or features beyond what is available in the standard, out-of-the-box version. Customizations are unique to individual users or organizations and involve coding or development work to achieve the desired outcome.
2. Configuration: Configuration involves the adjustment or setup of settings, options, or parameters within a SaaS solution to meet the requirement. Configuration does not involve making changes to the underlying code or functionality of the software. Instead, it involves selecting options, toggling settings, or defining rules within the software's existing framework to tailor it to specific requirements.
Tab 2 - Scoring Matrix
| Attachment H - Technical and Business Functionality | Completed by Vendor | Auto Populated Fields | Hide Column | Hide Column | ||||
| Item # | Title | Description | Requirement Type | Priority Rating |
High= 3 Medium = 2 Low = 1 Response (Please select from
| drop-down menu) | Comments | |||
| (Explain why and how the requirement would be met) | Auto Calculated Response Selection Points | Maximum Points | ||
| (Response "Currently Exists" x Priority Rating) | Auto Calculated Points | |||
| (Response x Priority Rating) | GAP | |||
| (current state), (future state) | Reference ID (INTERNAL USE) | Response Options | Response Points | |
| 1 | Account Creation | The Solution must provide account relationships so a Primary can create and maintain an account on the Platform. | User Interface/ Experience |
| 21 Line Items | Item No. 1 to 21 | 3 | Not Yet Scored | 15 | current state | 178069, 178081 | Column1 | Column2 | ||||||
| 2 | Primary Account Self Service | The Solution should provide the ability for the Primary to reset their password via self service. | 2 | Not Yet Scored | 10 | current state | 178081 | 5 - Currently Exists | 5 | ||||
| 3 | Anonymous User | The Solution must provide an anonymous user experience for users who have not created an account or logged into their account, to enable them to navigate the Platform for activities such as plan comparison and finding local help. | 3 | Not Yet Scored | 15 | current state | 184778 | 4 - Available by UAT (configuration) | 4 | ||||
| 4 | Additional Roles/Accounts Requirements 1 | The Solution should provide an insurance agent portal so that users with the agent role can assist consumers. | 2 | Not Yet Scored | 10 | future state | 196760 | 3 - Available by UAT (customization) | 3 | ||||
| 5 | Additional Roles/Accounts Requirements 2 | The Solution should provide capabilities so that Agents can filter their book of business by the actions the consumer needs to take. | 1 | Not Yet Scored | 5 | future state | 196760 | 2 - Available Post Rollout (configuration) | 2 | ||||
| 6 | Additional Roles/Accounts Requirements 3 | The Solution should provide a Assister portal so that users with the Assister role can assist consumers who have designated them. | 2 | Not Yet Scored | 10 | future state | 196764 | 1 - Available Post Rollout (customization) | 1 | ||||
| 7 | Additional Roles/Accounts Requirements 4 | The Solution should provide capabilities so that Assisters can filter their book of business by the actions the consumer needs to take. | 1 | Not Yet Scored | 5 | future state | 196764 | 0 - Not Available | 0 | ||||
| 8 | Additional Roles/Accounts Requirements 5 | The Solution should provide a Carrier portal so that users with the carrier role can review Primary cases | 2 | Not Yet Scored | 10 | future state | 196761 | Not Yet Scored | |||||
| 9 | Additional Roles/Accounts Requirements 6 | The Solution should provide State and Consumer Assistance Center (CAC) staff the ability to see all data related to a Primary in a singular interface. | 2 | Not Yet Scored | 10 | future state | 196769 | ||||||
| 10 | Additional Roles/Accounts Requirements 7 | The Solution should provide the ability for users to self service password resets. | 2 | Not Yet Scored | 10 | current state | 196771 | ||||||
| 11 | Additional Roles/Accounts Requirements 8 | The Solution could provide the capability to support Multi-Factor Authentication for Non-primary users. | 1 | Not Yet Scored | 5 | future state | 196771 | ||||||
| 12 | Initial Plan/s Display, Window Shopping and Link to Begin Enrollment Process | The Solution must provide a plan display and a plan comparison tool for a shopping experience, including estimating or determining eligibility and filters for; tax credits, providers, facilities, and prescription drugs. The same display will be used for the anonymous user experience. Current Marketplace Window Shopping Tool example: https://ohim.checkbookhealth.org/ | 3 | Not Yet Scored | 15 | current state | 184781 |
180965, 181263, 181572, 182713
| 13 | Plan display shows cost-sharing for covered drugs | The solution should have a prescription drug search capability for the plan display that shows cost-sharing for covered drugs. | 2 | Not Yet Scored | 10 | future state | 184781 | |||
| 14 | Choosing Different Plans Within a Household | The Solution must have tools to manage different household members and their plans under a Primary account. | 3 | Not Yet Scored | 15 | current state | 180975 | |||
| 15 | Communication Support | The Solution should provide the ability for authorized users to create and maintain notice templates. | 2 | Not Yet Scored | 10 | future state | 187611 | |||
| 16 | Carrier Plan Display Review | The Solution must provide tools and processes for the Carriers to review and approve plan data. | 3 | Not Yet Scored | 15 | future state | 185019 | |||
| 17 | Get Help Function | The Solution must provide a tool to find in-person application assistance, similar to 'Get Help'. | ||||||||
| https://healthcare.oregon.gov/Pages/find-help.aspx | 3 | Not Yet Scored | 15 | future state | 185153 | |||||
| 18 | Auto Reenrollment | The Solution must provide an Auto Reenrollment opt-in mechanism for enrollees. | 3 | Not Yet Scored | 15 | current state | 189422 | |||
| 19 | Web and Mobile Functionality | The Solution must be built to support all features on web and mobile application design/functionality leveraging industry best practices. Examples including the following: consistent user interfaces, allowing navigation via shortcuts, providing informative feedback to the users, allowing users to reverse their actions easily and seamlessly, providing support to users reporting issues or defects that is consistent across all interfaces, and minimizing memory load. | 3 | Not Yet Scored | 15 | future state | 196775 | |||
| 20 | SHOP Calculator | The solution must have Small Business Health Options Program (SHOP) functionality required by 45 CFR, part 155, subpart H, including an estimating tool for plans with costs based on a tiered-composite rating model. (https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-B/part-155) | 3 | Not Yet Scored | 15 | current state | 184780 | |||
| 21 | SHOP Plan Display | The solution should have a plan display to accompany the SHOP cost estimating tool. | 2 | Not Yet Scored | 10 | future state | 184780 | |||
| 22 | Communications in the Platform | The Solution must provide communication strategies and solutions around common events like plan cancellation. | Technical |
| 23 Line Items | Item No. 22 to 44 | 3 | Not Yet Scored | 15 | current state | 182718 | |||||
| 23 | Email Communication | The Solution must provide the ability to send notifications to consumers via email based on communication preference. | 3 | Not Yet Scored | 15 | current state | 186543 | |||
| 24 | SMS Communication | The Solution should provide the ability to send notifications to consumers via text messaging based on communication preference. | 2 | Not Yet Scored | 10 | current state | 186543 | |||
| 25 | Configurability, Data Collection | The Solution must be configurable to Oregon (like REALD and SOGI data collection). | 3 | Not Yet Scored | 15 | future state | 189451 | |||
| 26 | Configurability, Branding | The Solution needs to be configurable for branding specific to Oregon, such as banners, State seal, colors, font size, etc. | 3 | Not Yet Scored | 15 | future state | 189451 | |||
| 27 | Platform Ad-Hoc Reporting | The Solution must provide a way for Program Staff to access data to create ad-hoc Platform reports with tools similar to Power BI and Tableau, including CAC data. | 3 | Not Yet Scored | 15 | future state | 190504, 187617 | |||
| 28 | 834/999 Transaction | The Solution must conform to 834/999 standards for data exchange for both Carriers and the Platform, in the same manner as Healthcare.gov. | ||||||||
| https://www.cms.gov/files/document/ffe-enrollment-manual-2023-5cr-071323.pdf | 3 | Not Yet Scored | 15 | current state | 180967 | |||||
| 29 | Reconciliation Tools | The Solution should provide tools to facilitate data reconciliation between the exchange and carriers | 2 | Not Yet Scored | 10 | future state | 185816 | |||
| 30 | Reconciliation Discrepancies | The Solution should provide the capability to sort and filter data discrepancies between the exchange and carriers | 2 | Not Yet Scored | 10 | future state | 185816 | |||
| 31 | Reconciliation Discrepancy Suppression | The Solution should provide the capability to suppress certain discrepancies from being triggered | 2 | Not Yet Scored | 10 | future state | 185816 | |||
| 32 | EDI - Recieving Provider Data | The Solution must provide EDI connections outside of 834/999 for additional Carrier data traffic related to things like Provider and Formulary data. | 3 | Not Yet Scored | 15 | current state | 185820 | |||
| 33 | Federal Hub | The Solution must be able to meet the CMS requirements for a Marketplace Authority to Connect (ATC) directly to the Federal Data Services Hub (FDSH) for eligibility information verification. | 3 | Not Yet Scored | 15 | current state | 183523, 185816 | |||
| 34 | Additional Data Services | The Solution should provide the capability to connect to other state or commercial data sources. | 2 | Not Yet Scored | 10 | future state | 185816, 185818 | |||
| 35 | Account Creation with ONE data (needs more info) | The Solution must be able to link data from the ONE system for account creation purposes so that a Primary that has been referred from ONE doesn't have to reenter their account data. | 3 | Not Yet Scored | 15 | future state | 178419 | |||
| 36 | Account Matching | The Solution should provide the capability to match incoming data from the ONE system to existing Primary data, if an account already exists. | 2 | Not Yet Scored | 10 | future state | 185816 | |||
| 37 | Account Creation with Migrated data from Healthcare.gov | The Solution must be able to link data migrated from the Healthcare.gov system for account creation purposes so that a Primary that has been enrolled previously in Healthcare.gov doesn't have to reenter their account data. | 3 | Not Yet Scored | 15 | future state | 188339 | |||
| 38 | Oregon Resident Data Migration from Healthcare.gov | The Solution must provide migration of existing Oregon resident Healthcare.gov data to the Marketplace and resolve changes during intial migration (pre-open enrollment) and end of plan year 2026. | 3 | Not Yet Scored | 15 | future state | 184438 | |||
| 39 | Other Healthcare.gov Integration/Migration | The Solution must provide migration for potential additional Healthcare.gov data that would support Agent/ Broker information and CAC data. | 3 | Not Yet Scored | 15 | future state | 189881 | |||
| 40 | Medicaid, MMIS, OHP, One transaction | The Solution must provide account transfer data processes for Oregon's ONE Medicaid system to support applicants (no wrong door) in the same manner as Healthcare.gov. | 3 | Not Yet Scored | 15 | future state | 189887 | |||
| 41 | Accessibility | The Solution must conform to State and Federal accessibility standards (e.g., WCAG: https://www.w3.org/WAI/standards-guidelines/wcag and Section 508: https://section508.gov/create/software-websites and Plain Language standard: https://www.plainlanguage.gov/law). | 3 | Not Yet Scored | 15 | current state | 186547 | |||
| 42 | Adherence to Best Practices | The Platform must be implemented using industry standard architecture best practices, including: Continuous integration and delivery, Automated test coverage, Configurability, Extensibility, Resiliency, Redundancy, Monitoring, and Scalability. | 3 | Not Yet Scored | 15 | current state | 196775 | |||
| 43 | Saving of Digital files in association with a Primary account | The Solution must provide the ability for digital files to be uploaded, saved, and viewed by Marketplace staff or Primary, in association with an account. For example, see Healthcare.gov identity verification (additional document submission). | 3 | Not Yet Scored | 15 | current state | 179483, 179828 | |||
| 44 | Ad hoc document upload | The Solution should provide the capability for authorized users to manually upload documents to a Primary's account/inbox. | 2 | Not Yet Scored | 10 | future state | 196732 | |||
| 45 | Application and Eligibility Determination | The Solution must adhere to federal application and eligibility standards (45 CFR Part 155) for an enrollment application, including opt-in to Auto Re-enrollment and electronic communications. | ||||||||
| https://www.ecfr.gov/current/title-45/part-155/subpart-E | Eligibility |
| 11 Line Items | Item No. 45 to 55 | 3 | Not Yet Scored | 15 | current state | 179210, 179481, 179838, 179962, 179965, 180112, 180154, 180334, 184442, 180339, 180341, 180598, 180966, 182714 | ||||||
| 46 | Periodic Data Matching | The Solution should provide an automated process to conduct Periodic Data Matching (PDM). | 2 | Not Yet Scored | 10 | current state | 196777 | ||||
| 47 | Policy Reinstatement | The Solution should provide authorized users the ability to Reinstate policies. | 2 | Not Yet Scored | 10 | future state | 186546 | ||||
| 48 | Adverse Action | The Solution should provide an automated process to conduct adverse action associated with Data Matching Inconsistencies. | 2 | Not Yet Scored | 10 | future state | 196777 | ||||
| 49 | Configurable Eligibility Parameters | The solution should be configurable for different eligibility criteria to enable account transfers to ONE system for different state health programs (e.g., potential 138-200% FPL account transfers to ONE system for Bridge Health Program) | 2 | Not Yet Scored | 10 | future state | 196738 | ||||
| 50 | Appeal Denial of Eligibility | The Solution must support manual changes to eligibility determinations for manual review and appeals processes | 3 | Not Yet Scored | 15 | current state | 184441 | ||||
| 51 | Multi-Tax Household | The Solution should provide the capability to support Multi Tax Households | 2 | Not Yet Scored | 10 | future state | 196778 | ||||
| 52 | Choosing a Dental Plan | The Solution must have options for enrollment in dental plans appropriate to the situation of the enrollee. | 3 | Not Yet Scored | 15 | current state | 181577 | ||||
| 53 | Account Eligibility Estimate | The Solution should provide the capability to provide an eligibility estimate to the Primary, if enough data is sent from the ONE system. | 2 | Not Yet Scored | 10 | future state | 189887 | ||||
| 54 | Account Auto Enrollment | The Solution could provide the capability to auto enroll a household in a plan | 1 | Not Yet Scored | 5 | current state | 189422 | ||||
| 55 | Auto Redetermination | The Solution must provide an Auto Redetermination processes and methodology for annual eligibility determination of enrollees. | 3 | Not Yet Scored | 15 | current state | 189427 | ||||
| 56 | Roles-based Security | The Solution must support role based security for marketplace roles, like; Primary, CAC staff, State Staff, Community Partners, Assisters, Agents, Carriers, etc. | Security |
| 5 Line Items | Item No. 56 to 59 and 96 | 3 | Not Yet Scored | 15 | current state | 182734 | ||||||
| 57 | MARS-E - Code of Federal regulations (ECFR) title 45 | The Solution must continuously conform to the Minimum Acceptable Risk Standards for Exchanges (MARS-E) standards as required by CMS. | |||||||||
| https://www.cms.gov/files/document/mars-e-v2-2-vol-1final-signed08032021-1.pdf | 3 | Not Yet Scored | 15 | current state | 190537 | ||||||
| 58 | State of Oregon Cyber Security | The Solution must conform to State of Oregon Cyber Security standards and requirements. | |||||||||
| https://www.oregon.gov/eis/cyber-security-services/Documents/2019StatewideInformationAndCyberSecurityStandardsV1.0.pdf | 3 | Not Yet Scored | 15 | future state | 190541 | ||||||
| 59 | Information Security Monitoring | The Solution must provide and manage Information Security/privacy oversight & monitoring subject to periodic State and Federal audits. | 3 | Not Yet Scored | 15 | current state | 190541 | ||||
| 60 | Call Center Requirements | The Solution must provide help and education regarding health plans, eligibility, application assistance, etc, for Marketplace users (Primaries, Assisters, Carriers, Agents, etc) through telephone, internet Chat, and E-mail. | CAC |
| 22 Line Items | Item No. 60 to 81 | 3 | Not Yet Scored | 15 | future state | 186543 | ||||||
| 61 | Call Center Requirements 1 | The Solution should provide automated chat-bot functionality (e.g., password reset) that may include FAQ-level information. | 2 | Not Yet Scored | 10 | future state | 186543 | ||||
| 62 | Call Center Requirements 2 | The Solution should provide a dedicated queue for Assisters and Agents | 2 | Not Yet Scored | 10 | future state | 186543 | ||||
| 63 | Issues, Escalations, Complaints, and Appeals | The Solution must provide staff and processes to resolve issues, escalations, complaints, manual reviews, and provide assistance with appeals. | 3 | Not Yet Scored | 15 | future state | 186546 | ||||
| 64 | Issues, Escalations, Complaints, and Appeals Requirements 1 | The Solution should provide a single repository to manage Issues, Escalations, Complaints, and Appeals | 2 | Not Yet Scored | 10 | future state | 186546 | ||||
| 65 | Issues, Escalations, Complaints, and Appeals Requirements 2 | The Solution should provide the ability to set reminders for tasks associated with Issues, Escalations, Complaints, and Appeals | 2 | Not Yet Scored | 10 | future state | 186546 | ||||
| 66 | Issues, Escalations, Complaints, and Appeals Requirements 3 | The Solution should provide the ability to assign priority to Issues, Escalations, Complaints, and Appeals | 2 | Not Yet Scored | 10 | future state | 186546 | ||||
| 67 | Workforce Management | The Solution must include CAC workforce management and document associated processes and methodologies. | 3 | Not Yet Scored | 15 | current state | 186548 | ||||
| 68 | CRM (Customer Relationship Management) | The Solution must provide a CRM that is capable of integrating with the Platform that includes ticketing and tracking of previous communications and issues. | 3 | Not Yet Scored | 15 | current state | 186549, 189691 | ||||
| 69 | CRM Integration | The Solution should provide real-time integration between the CRM and the Platform. | 2 | Not Yet Scored | 10 | future state | 189691 | ||||
| 70 | CRM Data Availability | The Solution should provide access to all communication history to authorized users. | 2 | Not Yet Scored | 10 | future state | 186549 | ||||
| 71 | Interactive Voice Response System | The Solution must provide a configurable Interactive Voice Response (IVR) system. | 3 | Not Yet Scored | 15 | current state | 187289 | ||||
| 72 | IVR Capability 1 | The Solution's IVR should provide the capability to authenticate caller identity as needed for automated processes. | 2 | Not Yet Scored | 10 | future state | 187289 | ||||
| 73 | IVR Capability 2 | The Solution should provide application status lookups for authenticated callers. | 2 | Not Yet Scored | 10 | future state | 187289 | ||||
| 74 | IVR Capability 3 | The Solution should provide configurable hold messages to callers in queue. | 2 | Not Yet Scored | 10 | future state | 187289 | ||||
| 75 | IVR Capability 4 | The Solution should provide expected wait time while callers are in queue. | 2 | Not Yet Scored | 10 | future state | 187289 | ||||
| 76 | IVR Capability 5 | The Solution should provide the capability for consumers to request and schedule a return call. | 2 | Not Yet Scored | 10 | future state | 187289 | ||||
| 77 | IVR Capability 6 | The Solution's IVR should provide the capability to route the caller to appropriately trained staff based on menu selection and/or application status. | 2 | Not Yet Scored | 10 | future state | 187289 | ||||
| 78 | IVR Capability 7 | The Solution should provide the capability for consumers to hold their place in the queue. | 2 | Not Yet Scored | 10 | future state | 187289 | ||||
| 79 | IVR Capability 8 | The Solution should provide the ability to auto-dial lists of consumers who have provided auto-dial consent. | 2 | Not Yet Scored | 10 | future state | 187289 | ||||
| 80 | IVR Capability 9 | The Solution should provide the ability to route callers to other phone numbers when appropriate (Medicaid, Carriers etc.). | 2 | Not Yet Scored | 10 | future state | 187289 | ||||
| 81 | Customer Satisfaction Surveys | The Solution must conduct customer satisfaction surveys at a configurable cadence on an opt-in basis. | 3 | Not Yet Scored | 15 | current state | 186543 | ||||
| 82 | Print Shop | The Solution must generate correspondence including notices and marketing materials. | Mailroom/ Printshop |
| 4 Lines | Line No. 82 to 85 | 3 | Not Yet Scored | 15 | current state | 187611 | |||||
| 83 | Print Shop Tax Envelope | The Solution should provide the capability to send 1095-A documents in envelopes designated as containing important tax documents. | 2 | Not Yet Scored | 10 | current state | 187611 | |||
| 84 | Print Shop Notice Bundling | The Solution should provide the capability to combine multiple pieces of correspondence to the Primary on a single day in one envelope. | 2 | Not Yet Scored | 10 | future state | 187611 | |||
| 85 | Mailroom | The Solution must be able to send and recieve physical mail and digitize the correspondence. | 3 | Not Yet Scored | 15 | current state | 187729 | |||
| 86 | Compliance with State and Federal Regulations | The Solution must be compliant with federal and state requirements, including Oregon Administrative Rules, Oregon Revised Statutes, and the rules and regulations issued by CMS. |
CMS: https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-B/part-155 Oregon Administrative Rules, Chapter 945: https://secure.sos.state.or.us/oard/displayChapterRules.action?selectedChapter=190 Oregon Revised Statutes, Chapter 741: https://www.oregonlegislature.gov/bills_laws/ors/ors741.html Policy/ Regulatory Compliance
| 4 Line Items | Item No. 86 to 89 | 3 | Not Yet Scored | 15 | current state | 196783 | ||||||
| 87 | Ongoing Compliance with State and Federal Regulations | The Solution must remain compliant with any changes to federal or state law that may occur year-over-year, including compliance through regular software updates. | 3 | Not Yet Scored | 15 | current state | 196783 | ||||
| 88 | Languages | The Solution must support public-facing notifications/communications that are ADA (Americans with Disabilities Act of 1990) and WCAG 2.2 (or current) compliant in multiple languages based on user preferences. Preferred languages include, but are not limited to, the following: English, Spanish, Simplified Chinese, Traditional Chinese, Arabic, Russian, Somali, and Vietnamese. | 3 | Not Yet Scored | 15 | future state | 186547 | ||||
| 89 | Electronic Reporting Facilitation | The Solution must facilitate electronic reporting to IRS and CMS, Mars-E certification, auditing/reporting, and US Internal Revenue Service Publication 1075 security compliance. | 3 | Not Yet Scored | 15 | current state | 196791 | ||||
| 90 | Platform Canned Reports | The Solution must provide normal, regular, canned reports for Oregon including open enrollment reports, Centers for Medicare & Medicaid Services (CMS) required reports, CAC data, etc. | Reporting |
| 6 Line Items | Item No. 90 to 95 | 3 | Not Yet Scored | 15 | future state | 190483 | |||||||
| 91 | CMS Canned Reports - Bi-Annual Metrics | The Solution should provide the CMS Bi-Annual Metrics report out of the box | 2 | Not Yet Scored | 10 | future state | 190483 | |||||
| 92 | CMS Canned Reports - Bi-Weekly Metrics | The Solution should provide the CMS Bi-Weekly OE Metrics report out of the box | 2 | Not Yet Scored | 10 | future state | 190483 | |||||
| 93 | CMS Canned Reports - Expanded Metrics | The Solution should provide the CMS Expanded OE Metrics report out of the box | 2 | Not Yet Scored | 10 | future state | 190483 | |||||
| 94 | User Fee Report | The Solution should provide the User Fee Report out of the box | 2 | Not Yet Scored | 10 | future state | 190483 | |||||
| 95 | Platform New Canned Reports | The Solution must provide a process for creating new canned reports. | 3 | Not Yet Scored | 15 | future state | 190486 | |||||
| 96 | Physical location of solution vendor, subcontractors, and data | The Solution vendor, any subcontractors, and any data handled by the solution must be located and remain within the contintental United States. | Security | 3 | Not Yet Scored | 15 | current state | 190541 | ||||
| Auto Calculated Total Score | 0 | |||||||||||
| Score based on 7.5% (150 points out of 2,000 total points) weighting in Round 1: | 0 |
&"Arial,Bold"&12TWIST to Web Requirements Traceability Matrix for Request for Proposals
&P of &N https://devops.dhsoha.state.or.us/DHSOHA/cb1a82eb-dddf-46ab-8709-5fa6da2ebc89/_workitems/edit/184778
File details come from the government source that posted it. Updated .