S-DASOBO-00016280 OHA-OHP HCI Portal RFP Att B-2 Reqs Fit-Gap Matrix Analysis v1.1.xlsx

XLSX spreadsheet 63 KB Posted

Attached to
Scheduling Portal Solution for Health Care Interpreters
Solicitation number
S-DASOBO-00016280
Issued by
Oregon

About this file

This is a Requirements Fit-Gap Analysis Matrix for the Oregon Health Authority (OHA) Office of Health Plans (OHP) Health Care Interpreters (HCI) Scheduling and Claims Portal Request for Proposal (RFP). The document serves as a scoring tool for vendors to demonstrate how their proposed solutions address 124 detailed system requirements across nine functional categories: Account Creation and Maintenance, Scheduling, Post-Scheduling, Post-Encounter, Claims, Views/Reports/Analytics, Identity and Access Management (IAM), Infrastructure, Integration, Migration, Reporting, Security, System Administration, and User Experience/User Interface (UX/UI). The State of Oregon is seeking a cost-effective, scalable, configurable, web-based Software-as-a-Service (SaaS) solution to enable healthcare providers to schedule credentialed health care interpreters and manage service claims. Vendors must complete and submit an electronic version of this matrix, selecting response codes for each requirement to indicate whether proposed functionality currently exists, is available with configuration, is available soon through custom development, or is not available. The solution must integrate with the State's Medicaid Management Information System (MMIS), the HCI Central Registry, and various Electronic Health Records (EHR) systems to support provider account creation, patient eligibility verification, HCI registration validation, and claims submission.

The requirements matrix comprises 117 high-priority requirements valued at 1,205 total points and seven medium-priority requirements valued at 35 points, for a maximum possible score of 1,205 points. Vendor responses are scored objectively based on response codes (Currently Exists = 5 points; Available with Configuration = 4.5 points; Available Soon = 0.5 points; Not Available = 0 points) and subjectively based on vendor comments explaining how proposed solutions will implement requirements. Key system capabilities include role-based access control, account creation and validation for multiple user types (HCIs, providers, Coordinated Care Organizations, OHA staff, nonprofits), encounter scheduling and modification, virtual platform support, double-booking prevention, post-encounter documentation, claims submission and status tracking, comprehensive reporting and analytics dashboards, WCAG accessibility compliance, and multi-platform access (desktop, tablet, mobile). Critical non-functional requirements include U.S.-based data storage, 99.9% system uptime, near-real-time transaction response, secure integrations, data export capabilities for migration purposes, and ad-hoc reporting functionality. The file does not specify response deadlines, award dates, contract term, pricing information, set-asides, or incumbent vendor details.

View the file

Other files

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

Instructions and Score Summary HCI Scheduling and Claims Portal Requirements Scoring Matrix

Worksheet Completion Instructions
Proposer shall complete and submit an electronic version of this Requirements matrix to demonstrate how the proposed solution addresses the requirements. Please follow these instructions to complete the scoring matrix.
1ENTER Offeror's Name in cell A12 of this Instructions Tab.
2INDICATE proposed solution type (e.g., SaaS, PaaS, IaaS, or On-Premise) in cell H12 of this Instructions Tab.
3This workbook is arranged in four worksheets or Catagory Tabs:

- Instructions (this tab)

- Feature Descriptions

- Requirements

- TBD-Reports 4 For each detailed Requirement line item on Catagory Tabs with requirements:

a. SELECT ONE of the Response Options from the drop down menu in Column I "Vendor Response Code." The codes in the drop-down list correspond to the codes described in the Vendor Response Code Table below. Vendor Response Codes are used to calculate the Fit/Gap Analysis "objective" evaluation point value.

b. COMPLETE Column J "Comments" with Offeror's or Solution Provider's brief comments that support, explain, or clarify the code selected in Column I.

Comments are not mandatory, but if offered they should succintly describe how the proposed Solution will implement the requirement line item, especially where the required functionality DOES NOT "Currently Exist" in the general release version of the proposed Solution at the time of Offer submission.

DO NOT use these comments to in place of the narrative requested by the RFP.

Vendor Responses (codes and comments) are used for the Fit/Gap "subjective" evaluation point value.

5 ENSURE to provide a respone and comments for each requirement line item. Total number of requirements across the Category Tabs:

Proposers Name:Indicate if this is a Saas, PaaS, IaaS or On-Premise System:
Score
Summary:Total Points0.00.0%%-age High Priority and "Currently Exists"00.0%%-age High Priority and "Available with Configuration"00.0%%-age Medium Requirements and "Currently Exists00%%-age Medium Priority and "Available with Configuration"00%
out ofout ofout ofout ofout of
1205.011711777
Feature Requirements Tab ColumnExplanation of ColumnVendor Reponse Code Table
Column BRequirement IDPointsConditionDescription
Column CType of Requiremnet (Functional/Non-functional)5Currently ExistsOfferor and Solution Provider assert the functionality described by the requirement currently exists in the generally available Solution described in the Offer and is used in their customer's production environment.
Column DRequirement Title4.5Available with ConfigurationThe functionality described in the requirement is --

- Available in the proposed Solution by configuration of existing base code, OR

- On Solution Provider's product roadmap for general availability release within one year of RFQ Release (ensure to include expected date of general availability)

Column EUsers Applies to0.5Available SoonProposed Solution does not currently include functionality to meet the requiremet on the Solution Provider's product roadmap, and would require custom development to provide the functionality.
Column FRequirement Decription0Not AvailableProposed Solution does not provide the functionality and is not on product roadmap for release within one year of RFQ Release. Offeror may provide alternative functional solutions in Offeror's Comments in Column G.
Column GRequirement Priority
Column IVendor Response Code (See table at right)Feature Priority
Column KVendor CommentsPointsConditionDescription
Column LMaximum Points2HighHigh priority requirement for the proposed solution - manditory
Column MVendor Points (auto calculated)1MediumMedium priority requirment for the proposed solution - desirable

Feature Descriptions

Feature TitleFeature Description
Account Creation and MaintenanceAllows users (e.g., OHA Admin, CCOs, interpreters, providers, scheduling coordinators) to register, update personal information, and manage account credentials. This includes unique settings that pertain to different accounts with various permissions (i.e. notifications, schedules).
SchedulingScheduling enables Providers, CCOs, and Customer Service users to create, assign, and manage interpreter encounters. It supports selecting encounter details, preventing double booking, handling modifications, coordinating multiple HCIs, sharing encounter information, choosing direct assign or pool selection, viewing CBA rates, and accessing virtual modality tools. The system will maintain a record of a patient’s HCI preferences, filters and display qualified HCIs based on language, distance, availability, modality, and other criteria.
Post-SchedulingCore post scheduling functionality that allows Providers, CCOs, and Customer Service to modify or cancel interpreter encounters, track lifecycle changes, and receive system notifications related to HCI responses or lack of response. This feature also supports the actions required when an encounter becomes unclaimed or when no HCI is available, including the ability to trigger an overflow process.
Post-EncounterEnable Providers and HCIs to complete all required post encounter tasks—such as updating encounter duration, rating the HCI, submitting feedback or complaints, and creating private notes with strict role based visibility. These capabilities ensure accurate encounter records, support claim readiness, capture feedback for service improvement, and protect sensitive information through HIPAA compliant, auditable controls.
ClaimsSupports submission of interpreter service claims, including encounter details (e.g. date/time, length of visit, HCI rate, provider, and patient details). The system will support automatic reimbursement calculations based on predetermined rate logic. Users must be able to request changes to submitted claims, with all modifications subject to approval by authorized personnel. The system will track and maintain a complete audit trail of all claim submissions, change requests, and approvals.
Views, Reporting, & AnalyticsOffers dashboards and filterable reports for tracking interpreter utilization, encounter trends, and claim metrics. The types of reports and accessible data will be restricted based on user type and role-based access. Will support an environment for ad hoc reporting.
IAM (Identity & Access Management)Allows for configuration of role-based access control and ability to track and export user actions (e.g., login attempts, change history).
InfrastructureDescribes the underlying technical architecture, including hosting, scalability, uptime requirements, and disaster recovery.
IntegrationFacilitates secure data exchange with external systems (e.g., EHRs, Medicaid Management Information System, and the HCI Central Registry), to streamline workflows. Integrations will be used to verify service eligibility, Medicaid billing providers, credentialed HCIs, and EHR integration.
MigrationTransfers historical data (e.g., provider profiles from MMIS) from existing systems into the Scheduling and Claims Portal.
ReportingSets standards around the searching capabilities and ease of generating various types of operational, claims, and compliance reports.
SecurityImplements role-based access control, manage deactivation of accounts, and sets standards for necessary agency required security compliance.
System AdministrationProvides tools for managing users, permissions, system settings, and sets website standards.
UX/UI (User Experience/User Interface)Focuses on intuitive design, accessibility (WCAG compliance), and mobile/web responsiveness to ensure ease of use for all user types.

Requirements

IDReq IDTypeRequirement TitleUsers Applied ToRequirement
User Story or High-Level CapabilityItem PriorityItem ValueVendor Response
CodeVendor Response ValueVendor Comments
(Explain how the requirement would be met if it does not currently exist)Maximum PointsVendor Points
Account Creation and Maintenance
1ACC1FunctionalRole Based AccessScheduling and Claims Portal UserAS A Scheduling and Claims Portal User,

I NEED to have role based security access,

SO THAT I can control the look and feel, as well as data and access, of the Scheduling and Claims Portal, by User GroupHigh2ERROR:#N/A10
2ACC2FunctionalAccount Creation- HCIHCIAS A HCI,

I NEED to create an account that is validated by the OHA Central Registry (Interpreter),

SO THAT I can access the Interpreters Scheduling and Claims Portal and manage scheduling occurrences and associated data, as well as submit claims and check claim status.High2ERROR:#N/A10
3ACC3FunctionalAccount Creation- ProviderProviderAS A Provider,

I NEED to create an account that is validated by MMIS,

SO THAT I can access the Interpreters Scheduling and Claims Portal and manage scheduling occurrences and associated data.High2ERROR:#N/A10
4ACC4FunctionalAccount Creation- OHA UserOHA UserAS A OHA User,

I NEED to have an account created by an OHA Admin,

SO THAT I can access the Interpreters Scheduling and Claims PortalHigh2ERROR:#N/A10
5ACC5FunctionalAccount Creation- OHA AdminOHA AdminAS A OHA Admin,

I NEED to have an account created by an OHA Admin,

SO THAT I can access the Interpreters Scheduling and Claims PortalHigh2ERROR:#N/A10
6ACC6FunctionalAccount Creation- CCOCCOAS A CCO,

I NEED to create an account that is validated by MMIS,

SO THAT I can access the Interpreters Scheduling and Claims PortalHigh2ERROR:#N/A10
7ACC7FunctionalAccount Creation- Non ProfitNonprofitAS A Nonprofit,

I NEED to have a account created by an OHA Admin,

SO THAT I can access the Interpreters Scheduling and Claims PortalHigh2ERROR:#N/A10
8ACC8FunctionalUser Name RecoveryScheduling and Claims Portal UserAS A Scheduling and Claims Portal User,

I NEED to be able to find out what my user name is, if I forgot it,

SO THAT I can log into my accountHigh2ERROR:#N/A10
9ACC9FunctionalPassword ResetScheduling and Claims Portal UserAS A Scheduling and Claims Portal User,

I NEED to be able to reset my password, if I forgot it,

SO THAT I can log into my accountHigh2ERROR:#N/A10
10ACC10FunctionalExisting account Sign-InHCIAS A HCI,

I NEED to log into my account,

SO THAT I can manage scheduling and claimsHigh2ERROR:#N/A10
11ACC11FunctionalHCI recurring account validation, with registryScheduling and Claims PortalAS A Scheduling and Claims Portal,

I NEED to validate that the HCI is still valid with the Registry on a regular basis,

SO THAT I do not allow access to an invalid userHigh2ERROR:#N/A10
12ACC12FunctionalNotification PreferencesScheduling and Claims Portal UserAS A Scheduling and Claims Portal User,

I NEED to be able to set notification preferences,

SO THAT I can manage my communication preferencesHigh2ERROR:#N/A10
13ACC13FunctionalProvider recurring account validation, with MMISScheduling and Claims PortalAS A Scheduling and Claims Portal,

I NEED to validate that the Provider is still valid with MMIS on a regular basis,

SO THAT I do not allow access to an invalid userHigh2ERROR:#N/A10
Scheduling
55SCH1FunctionalInitial Provider Encounter CreationProviderAS A Provider,

I NEED to create an encounter with an HCI for a specific language (filter), and as part of this creation, prepopulate my static data (ex - Provider #), and get a prompt for my dynamic data (ex- patient name) as required,

SO THAT an HCI can be assigned and the occurrence has data needed for a claim submissionHigh2ERROR:#N/A10
56SCH2FunctionalPatient HCI preferencesProviderAS A Provider,

I NEED to be able to save patient specific HCI preferences (likes or don't like),

SO THAT the preferred HCI can be prioritized.High2ERROR:#N/A10
57SCH3FunctionalProvider reviews open encountersProviderAS A Provider,

I NEED to be able to view open encounters,

SO THAT I can see which are accepted, declined, or still open, or which encounters haven't been 'claimed'.High2ERROR:#N/A10
58SCH4FunctionalInitial CCO Encounter CreationCCOAS A CCO,

I NEED to create an encounter with an HCI for a specific language,

SO THAT my patient and I can communicateHigh2ERROR:#N/A10
59SCH5FunctionalModification to EncounterCCOAS A CCO,

I NEED to be able to Modify an existing encounter,

SO THAT the encounter is happening at the appropriate time, with the appropriate participants, in the correct location, and modality.High2ERROR:#N/A10
60SCH6FunctionalCCO receives an encounter acceptance/denial/cancelation from HCICCOAS A CCO,

I NEED to be notified that the HCI has responded (acceptance/denial/cancelation) to an encounter,

SO THAT my patient and I can communicateHigh2ERROR:#N/A10
61SCH7FunctionalCCO cancels encounterCCOAS A CCO,

I NEED to be able to cancel an encounter,

SO THAT the HCI is notified and can potentially be available for another encounter.High2ERROR:#N/A10
62SCH8FunctionalCCO reviews open encountersCCOAS A CCO,

I NEED to be able to view open encounters,

SO THAT I can see which are accepted, declined, or still open, or which encounters haven't been 'claimed'.High2ERROR:#N/A10
63SCH9FunctionalHCI accepts encounterHCIAS A HCI,

I NEED to respond to an encounter,

SO THAT I can fulfill the need for language assistance.High2ERROR:#N/A10
64SCH10FunctionalHCI cancels encounterHCIAS A HCI,

I NEED to be able to cancel my attendance at an encounter,

SO THAT the Provider is notified that I will not be available and can act accordingly.High2ERROR:#N/A10
65SCH11FunctionalEncounter BufferHCIAS A HCI,

I NEED to create a time buffer between encounters for driving or personal time,

SO THAT I can manage my availability around my daily schedule as I accept encounters.High2ERROR:#N/A10
66SCH12FunctionalMedical SpecialtyHCIAS A HCI,

I NEED the provider to enter a mandatory Specialty field,

SO THAT I have a more concise idea of the vocabulary I will need to leverage.High2ERROR:#N/A10
67SCH13FunctionalHCI can't make Face to Face but can do a different modalityHCIAS A HCI,

I NEED be able to notify a Provider that I am 'stuck in traffic', but can pull over and facetime or call,

SO THAT so that the Provider has the option of changing Modality or trying to find a new HCI for the encounterHigh2ERROR:#N/A10
68SCH14FunctionalHCI declines direct assignment encounterHCIAS A HCI,

I NEED be able to decline a request,

SO THAT the Provider knows that I am not interestedHigh2ERROR:#N/A10
70SCH15FunctionalHCI short duration modification of Schedule (in Portal)HCIAS A HCI,

I NEED to modify my availability for a short duration for something like a vacation, Dr appt, or extra availability.,

SO THAT Providers know when I am available or not.High2ERROR:#N/A10
71SCH16FunctionalHCI open pool encounterHCIAS A HCI,

I NEED to be able to see filtered (for my language) unclaimed encounters,

SO THAT I can view unclaimed encounters, to see if I want to accept any of themHigh2ERROR:#N/A10
72SCH17FunctionalProvider Tier selectionProviderAS A Provider,

I NEED to be able to assign HCI's to a tier level within my Provider scheduling interface,

SO THAT I can assign an encounter or send the encounter out to multiple HCI's.High2ERROR:#N/A10
73SCH18FunctionalPatient Eligibility and CCO check at time of creationProviderAS A Provider,

I NEED to check Patient eligibility data and CCO enrollment,

SO THAT I can verify eligibility and CCO affiliation.High2ERROR:#N/A10
74SCH19FunctionalPatient becomes Ineligible after occurrence has been scheduledProviderAS A Provider,

I NEED to be notified when a Patient becomes ineligible and the occurrence reflects that an action needs to be taken by me (Badge, Flag, visual indicator),

SO THAT I can go through my process for addressing this scenario.High2ERROR:#N/A10
75SCH20FunctionalHCI becomes Ineligible after occurrence has been scheduledProvider, NonprofitAS A Provider, Nonprofit,

I NEED to be notified when an HCI becomes ineligible and the occurrence reflects that an action needs to be taken by the Provider (Badge, Flag, visual indicator),

SO THAT the provider can go through their process for addressing this scenario.High2ERROR:#N/A10
76SCH21FunctionalVirtual PlatformsHCI, ProviderAS A HCI, Provider,

I NEED a virtual platform like Teams or Zoom for non-in person modality or a change of modality,

SO THAT I have a convenient way to connect virtually with the participants in an encounterHigh2ERROR:#N/A10
77SCH22FunctionalDouble Booking preventionScheduling and Claims PortalAS A Scheduling and Claims Portal,

I NEED to prevent an HCI from Double booking an encounter (the HCI should not see conflicting encounters, if they have selected one),

SO THAT encounters do not get missed because the HCI can't be in 2 places at onceHigh2ERROR:#N/A10
78SCH23FunctionalDisplay CBA ratesHCI, Provider, CCO, Nonprofit, OHA Admin, OHA UserAS A HCI, Provider, CCO, Nonprofit, OHA Admin, OHA User,

I NEED to be able to view current CBA rates,

SO THAT I understand the reimbursement scheduleHigh2ERROR:#N/A10
79SCH24FunctionalPatient specific infoProviderAS A Provider,

I NEED to be able to pass on information to the HCI for a specific encounter,

SO THAT I can inform the HCI of best needs for patientHigh2ERROR:#N/A10
80SCH25FunctionalSchedule multiple HCI at same timeProviderAS A Provider,

I NEED to be able to schedule multiple HCI's for the same encounter,

SO THAT for example, if I have a long (1.5hr+) encounter requiring ASL, I can have 2 HCI's that can relieve each other.High2ERROR:#N/A10
81SCH26FunctionalAccept/Deny Modification to EncounterHCIAS A HCI,

I NEED to be able to respond to a modification of an existing encounter,

SO THAT if there is a change in time, location, modality, etc., I can accept or deny the changes.High2ERROR:#N/A10
82SCH27FunctionalPool or Direct Assignment SelectionProviderAS A Provider,

I NEED to be able to choose between direct assign or pool when creating/modifying an encounter,

SO THAT I have the flexibility to select a known/preferred HCIs or allow for any qualified (language, gender, modality, etc.) HCI to select an encounter from a pool.High2ERROR:#N/A10
83SCH28FunctionalTypes of Encounter ModalitiesProviderAS A Provider,

I NEED to be able to select modality (virtual, telephone, in-person),

SO THAT the HCI knows the modality of the encounterHigh2ERROR:#N/A10
84SCH29FunctionalHCI Scheduling AvailabilityProviderAs A Provider,

I NEED to see count total of available HCIs for my encounter based on my filters (e.g. modality, distance, language, specific dates/times),

SO THAT I have an indication of potential HCIs available in the pool.Medium1ERROR:#N/A5
85SCH30FunctionalPatient Eligibility and CCO check at time of creationProviderAS A Provider,

I NEED to check Patient eligibility data and CCO enrollment,

SO THAT I can verify eligibility and CCO affiliation.High2ERROR:#N/A10
86SCH31FunctionalPatient becomes Ineligible after encounter has been scheduledProviderAS A Provider,

I NEED to be notified when a Patient becomes ineligible and the encounter reflects that an action needs to be taken by me (Badge, Flag, visual indicator),

SO THAT I can go thru my process for addressing this scenario.High2ERROR:#N/A10
87SCH32Non-FunctionalPatient CCO change after encounter has been scheduledProviderAS A Provider,

I NEED to be notified when a Patient's CCO enrollment changes and the encounter reflects that an action needs to be taken by me (Badge, Flag, visual indicator),

SO THAT I can verify CCO affiliation.High2ERROR:#N/A10
88SCH33FunctionalCCO check at time of creationProviderAS A Provider,

I NEED to check Patient CCO enrollment,

SO THAT I can verify CCO affiliation for claim submission.High2ERROR:#N/A10
Post Scheduling
41PSC1FunctionalModification to EncounterProviderAS A Provider,

I NEED to be able to Modify an existing encounter,

SO THAT if there is a change in time, location, modality, etc., I do not need to create a new encounterHigh2ERROR:#N/A10
42PSC2FunctionalProvider receives an encounter acceptance/denial/cancelation from HCIProviderAS A Provider,

I NEED to be notified that the HCI has responded (acceptance/denial/cancelation) to an encounter,

SO THAT I can notify my patient and reschedule encounter if necessaryHigh2ERROR:#N/A10
43PSC3FunctionalProvider cancels encounterProviderAS A Provider,

I NEED I need to be able to cancel an encounter,

SO THAT the HCI is notified and can potentially be available for another encounter.High2ERROR:#N/A10
44PSC4FunctionalHCI doesn't respond to an direct assign encounter requestProviderAS A Provider,

I NEED to be able to be notified or view when an HCI has not accepted an encounter,

SO THAT I can create a process for handling an 'unclaimed' direct assigned encounterHigh2ERROR:#N/A10
45PSC5FunctionalNo HCI has responded to a open pool assign encounter requestProviderAS A Provider,

I NEED to be able to be notified or view when no HCI has accepted an encounter. (example; notification within 48hrs),

SO THAT I can create a process for handling an 'unclaimed' open pool encounterHigh2ERROR:#N/A10
46PSC6FunctionalOverflowProviderAS A Provider,

I NEED to have a solution for finding an HCI if there isn't one available in the Registry,

SO THAT I can fulfill my due diligence to have an HCI assigned to an encounterHigh2ERROR:#N/A10
47PSC7FunctionalProvider Customer ServiceProviderAS A Provider,

I NEED Customer Service to manage/modify any irregularities to existing encounters,

SO THAT I do not have the administrative burden of making sure that an HCI is assigned to my encounter.High2ERROR:#N/A10
48PSC8FunctionalHCI Customer ServiceHCIAS A HCI,

I NEED Customer Service to bridge any non-technical customer service needs,

SO THAT I can get resolution or be triaged to appropriate parties (workforce development, OHA provider enrollment Services, CCO, etc.).High2ERROR:#N/A10
Post-Encounter
37PEN1FunctionalProvider Post encounter claimProviderAS A Provider,

I NEED to complete post booking, including changes to duration of occurrence and rating the HCI,

SO THAT I can fulfill my requirement for the HCI, to be able to submit a claim, and give constructive feedback for HCI development opportunities.High2ERROR:#N/A10
38PEN2FunctionalUser FeedbackScheduling and Claims Portal UserAS A Scheduling and Claims Portal User,

I NEED to be able to submit feedback

SO THAT data can be collected as potential feedback/complaints.High2ERROR:#N/A10
39PEN3FunctionalPrivate Visit NotesProviderAS A Provider,

I NEED the ability to create and manage private notes linked to the encounter, with strict role-based visibility (only I and my role can see my notes),

So that I can document important details for internal reference or claims purposes without exposing my notes to other roles, while maintaining HIPAA compliance and auditability.Medium1ERROR:#N/A5
40PEN4FunctionalPrivate Visit NotesHCIAS A HCI,

I NEED the ability to create and manage private notes linked to the encounter, with strict role-based visibility (only I can see my notes),

So that I can document important details for internal reference or claims purposes without exposing my notes to other roles, while maintaining HIPAA compliance and auditability.Medium1ERROR:#N/A5
Claims
14CLM1FunctionalHCI adds additional reimbursements cost (non-service)HCIAS A HCI,

I NEED to be able to submit additional cost for reimbursement for things like parking and milage,

SO THAT I can be reimbursedHigh2ERROR:#N/A10
15CLM2FunctionalHCI submits a ClaimHCIAS A HCI,

I NEED to be able to submit a claim for attending an encounter,

SO THAT I can get paid for the encounterHigh2ERROR:#N/A10
16CLM3FunctionalHCI makes a request to change a ClaimHCIAS A HCI,

I NEED be able to request a change to an encounter to reflect the actual Duration,

SO THAT the claim will reflect the correct duration for payment.Medium1ERROR:#N/A5
17CLM4FunctionalProvider is notified of a request to change a ClaimProviderAS A Provider,

I NEED to be notified when a request for a change to the encounter has been submitted,

SO THAT I can make the change to the encounterHigh2ERROR:#N/A10
18CLM5FunctionalProvider doesn't accept or doesn't respond to an HCI claim change request.HCIAS A HCI ,

I NEED to be able to submit a claim for attending an encounter, even if the duration of the encounter is in dispute,

SO THAT I can get paidHigh2ERROR:#N/A10
19CLM6FunctionalClaims are sent by EDI x12Scheduling and Claims PortalAS A Scheduling and Claims Portal,

I NEED to submit Claims to MMIS,

SO THAT MMIS can go thru the process of submitting paymentHigh2ERROR:#N/A10
20CLM7FunctionalSubmit Retroactive Claim - Provider approvedHCIAS A HCI,

I NEED to submit a retroactive claim that the Provider has approved,

SO THAT I can be paid for time that has been adjusted by the ProviderHigh2ERROR:#N/A10
21CLM8FunctionalHCI checks a claim statusHCIAS A HCI ,

I NEED to check the status of a submitted claim/s,

SO THAT I can track the claims process and know about when to expect payment or to follow up on something.High2ERROR:#N/A10
Views-Reports-Analytics
110VRA1FunctionalSchedule ViewHCI, Provider, CCOAS A HCI, Provider, CCO,

I NEED to see a schedule view of encounters,

SO THAT I can manage or reference encounters in a given time bracketHigh2ERROR:#N/A10
111VRA2FunctionalEncounter HistoryHCI, Provider, CCOAS A HCI, Provider, CCO,

I NEED to be able to view changes and modifications to occurrences ,

SO THAT I have the history needed, if there is a dispute or other issue that needs to be resolved.High2ERROR:#N/A10
112VRA3FunctionalHCI Claims viewHCIAS A HCI,

I NEED to be able to see a list of my unsubmitted, pending, and historic claims in a list or dashboard format. ,

SO THAT I can mange my submitted and unsubmitted claims regardless of status.High2ERROR:#N/A10
113VRA4FunctionalHCI Encounter viewHCIAS A HCI,

I NEED to view encounter information in the scheduling and claims portal,

SO THAT I can identify which encounters still require claim submission or access the data for other operational or reporting purposes.High2ERROR:#N/A10
114VRA5FunctionalView/report unclaimed encounters, post encounterCCO, Nonprofit, OHA Admin, OHA UserAS A CCO, Nonprofit, OHA Admin, OHA User,

I NEED to be able to see unclaimed encounters,

SO THAT I can do analysis against how well encounters are being fulfilled or unfulfilledHigh2ERROR:#N/A10
115VRA6FunctionalProvider follow-upProviderAS A Provider,

I NEED be able to see how long it takes me to 'close out' an encounter,

SO THAT I can understand my response time and adjust if needed.High2ERROR:#N/A10
116VRA7FunctionalHCI data for CCOProviderAS A Provider,

I NEED HCI data including; CCO Name, Member ID, Visit Date, Modality, Language, Registry or not registry (OHA, Certified/Qualified), Interpreters registry number, Claims filed. That is applicable to my CCO,

SO THAT I can use this data in my Reporting metricsHigh2ERROR:#N/A10
117VRA8FunctionalCCO ReportingCCOAS A CCO,

I NEED monthly/quarterly/annual metrics reporting (3-6 reports per group (Provider, HCI, OHA, Nonprofit)),

SO THAT I can see the trends in my KPI's (Key Performance Indicator)High2ERROR:#N/A10
118VRA9FunctionalProvider ReportingProviderAS A Provider,

I NEED monthly/quarterly/annual metrics reporting,

SO THAT I can see the trends in my KPI's. Fill Rate/Completion report to OHA, etc.…High2ERROR:#N/A10
119VRA10FunctionalNon profit ReportingNonprofitAS A Nonprofit,

I NEED monthly/quarterly/annual metrics reporting,

SO THAT I can see the trends in my KPI's. Fill Rate report to OHA, etc.…High2ERROR:#N/A10
120VRA11FunctionalOHA Admin ReportingOHA AdminAS A OHA Admin,

I NEED monthly/quarterly/annual metrics reporting,

SO THAT I can see the trends in my KPI's. Unfulfilled encounters by language and location. Outstanding encounters that haven't submitted a claim, Responsiveness of providers to HCI requests, HCI encounter return(by time for Provider to respond), etc.…High2ERROR:#N/A10
121VRA12FunctionalChange LogNonprofit, OHA Admin, OHA UserAS A Nonprofit, OHA Admin, OHA User,

I NEED to see changes to the data in a way that I can understand,

SO THAT I can monitor and do research against changes to the data.High2ERROR:#N/A10
122VRA13FunctionalLanguage ListScheduling and Claims PortalAS A Scheduling and Claims Portal,

I NEED a master list of languages/dialects,

SO THAT there is a standard, sharable list of language/dialects that can be leveraged by the portal and is accessible to usersHigh2ERROR:#N/A10
123VRA14FunctionalHCI Fill/Completion rate ReportNonprofitAS A Nonprofit,

I NEED to report out fill rate vs completion rate of HCI's that accepted encounters,

SO THAT I can report against these KPI's per SB1578High2ERROR:#N/A10
124VRA15FunctionalIn-language Encounter ReportProviderAS A Provider,

I NEED to be able to be able to report Bilingual Licensed Clinicians and provided interpreter services,

SO THAT I can report out encounters by in-language providersHigh2ERROR:#N/A10
IAM
22IAM1Non-FunctionalNF Role Based AccessNFThe system shall support configurable role based access control.High2ERROR:#N/A10
23IAM2Non-FunctionalNF Change LogNFThe system shall be able to track and report against all changes and change attempts to the system via change log tracking.High2ERROR:#N/A10
Infrastructure
24INF1Non-FunctionalSystem LogNFThe system will create Logs for both scheduled and ad-hoc incidents and responses.High2ERROR:#N/A10
25INF2Non-FunctionalData Storage U.S.NFThe system shall operate and store all data within the continental U.S., its possessions, and territories.High2ERROR:#N/A10
26INF3Non-FunctionalScalabilityNFThe system shall support seamless scalability of concurrent users without instability or a degradation in performance.High2ERROR:#N/A10
27INF4Non-FunctionalReliabilityNFThe system shall support an uptime of 99.9%.High2ERROR:#N/A10
28INF5Non-FunctionalTech Help DeskNFThe system shall provide support staff for technical issues.High2ERROR:#N/A10
29INF6Non-FunctionalLatencyNFThe system shall support near real-time transactional response time (e.g., data submission, database query).High2ERROR:#N/A10
30INF7Non-FunctionalProgress IndicatorNFThe system shall provide an indicator (progress bar) of action in progress for actions with a response time greater than near real time.High2ERROR:#N/A10
31INF8Non-FunctionalData ExportNFThe system shall support the logical export of historical and current data to facilitate migration to an alternative vendor's platform, should the State choose to transition providersHigh2ERROR:#N/A10
Integration
32INT1FunctionalRequirement around EPIC/EHR integrationsScheduling and Claims PortalAS A Scheduling and Claims Portal,

I NEED to have integration points for various EHR systems in Oregon, around HCI Scheduling,

SO THAT I get EHR connectivity and acceptance of the Scheduling and Claims PortalHigh2ERROR:#N/A10
33INT2FunctionalIntegration with MMISScheduling and Claims PortalAS A Scheduling and Claims Portal,

I NEED to give and receive data from MMIS, around Provider data, Patient eligibility, HCI registration, and claims submission and status,

SO THAT the Scheduling and Claims Portal can prepopulate data for Provider account creation, check for Patient eligibility or ineligibility (recurring), HCI registration in MMIS, and HCI claims submission and status.High2ERROR:#N/A10
34INT3FunctionalIntegration with the RegistryScheduling and Claims PortalAS A Scheduling and Claims Portal,

I NEED to get HCI information from the interpreter registry,

SO THAT I know availability, location, registry ID, certified/qualified language, and other types of data in the registry.High2ERROR:#N/A10
35INT4Non-FunctionalAPI IntegrationNFThe system shall allow for and make available custom API's for the purpose of integration.High2ERROR:#N/A10
Migration
36MIG1FunctionalProvider Migration for Pre-Account CreationOHA AdminAS A OHA Admin,

I NEED to pre-load Provider accounts from existing MMIS data,

SO THAT the majority of data needed to create a Provider user account can be prepopulatedHigh2ERROR:#N/A10
Reporting
49REP1Non-FunctionalAd-hoc ReportingNFThe system shall allow Internal Users to create, run, save, and re-run parameterized reports utilizing any data in the application for which the Internal User has the required permissions to access. (sandbox, ad-hoc)High2ERROR:#N/A10
50REP2Non-FunctionalClaim StatusNFThe system shall allow for claims information and claims history to be accessible for Users.High2ERROR:#N/A10
51REP3Non-FunctionalDashboardsNFThe system shall provide the ability to create dashboards that combine information from the system.High2ERROR:#N/A10
52REP4Non-FunctionalSearch FunctionNFThe system shall enable Admin Users to view and search User information, date, billing number, facility, Medicaid id, registry id, NPI id, number and assigned employees to see records. This is not an exhaustive list.Medium1ERROR:#N/A5
53REP5Non-FunctionalSmart Search FunctionNFThe system shall support wildcard searching, in it's searches, so that searching is intuitive and identifies relevant results. (for example; ability to search using partial names. Partial name search shall support both wildcards (*, ?) and default “starts with” matching (e.g., entering “Joh” returns “John,” “Johnson,” “Johnsen”))High2ERROR:#N/A10
54REP6Non-FunctionalData RetentionNFThe system shall adhere to the state data retention standards (OAR 943-120-0180). (7yrs)High2ERROR:#N/A10
Security
89SEC1FunctionalSecurity Compliance (RFP)Scheduling and Claims PortalAs the Scheduling and Claims Portal,

I NEED to be able to support the Security and Compliance standards and requirements mandated in the [RFP section 2.4 11],

SO THAT I can administer the correct access across the portal safely and securely.High2ERROR:#N/A10
90SEC2FunctionalOHA/Admin role to manage user accountsOHA AdminAS A OHA Admin,

I NEED to be able to manage all User accounts,

SO THAT I can administer the correct access across the portalHigh2ERROR:#N/A10
91SEC3Non-FunctionalAccount Source ValidationNFThe system shall also support disabling accounts that are inactive based on the source validation of the account. (Registry/HCI, MMIS/Provider)High2ERROR:#N/A10
System Administration
92SAD1Non-FunctionalOHA Admin UserNFThe system shall allow Administrative Users to access/edit the user permissions associated with users accounts.High2ERROR:#N/A10
93SAD2Non-FunctionalOther Admin UserNFThe system shall allow for admin groups to administrate or segregate users within their domain.Medium1ERROR:#N/A5
94SAD3Non-FunctionalWCAGNFThe system shall support website accessibility standards as referenced at https://www.oregon.gov/pages/accessibility.aspx,at go-live, and will update to newer versions of WCAG within 2 years of WCAG version release.High2ERROR:#N/A10
95SAD4FunctionalCCO Portal DataOHA AdminAs A OHA Admin,

I NEED to store CCO Data,

SO THAT the system has the data it needs to run claims eligibility for CCO.High2ERROR:#N/A10
UX-UI
96UX1FunctionalTooltipsScheduling and Claims Portal UserAS A Scheduling and Claims Portal User,

I NEED to be able to see tooltips for various elements within the portal,

SO THAT I can get more information around a specific fields or gain insight into what kind of data the Portal wantsHigh2ERROR:#N/A10
97UX2FunctionalSpotlight interpreter, patient, or doctor (pinning)HCI, ProviderAS A HCI, Provider,

I NEED to be able to spotlight/pin speakers ,

SO THAT they are prominent displayed in the videoHigh2ERROR:#N/A10
98UX3FunctionalSave Filter ProviderProviderAS A Provider,

I NEED to be able to save a filter 'default',

SO THAT when I log into the system and look for an HCI, I only get HCI's that are working in the geographical region that I have saved my filter on.High2ERROR:#N/A10
99UX4FunctionalSave Filter ProviderHCIAS AN HCI,

I NEED to be able to save a filter 'default',

SO THAT when I log into the system and look for occurrences, I only get occurrence options that are in the geographical region that I have saved my filter on.High2ERROR:#N/A10
100UX5FunctionalNotification FormatsScheduling and Claims PortalAS A Scheduling and Claims Portal,

I NEED to support email, text messaging, and in-tool notifications about special events,

SO THAT that I am notified/reminded of an eventHigh2ERROR:#N/A10
101UX6FunctionalNotification TriggersScheduling and Claims PortalAS A Scheduling and Claims Portal,

I NEED to be notified of an event (new encounter, modification to existing encounter, acceptance of encounter (pool or direct assigned), denial of encounter (previously accepted or direct assigned), up-coming encounter reminders, open claim reminders, etc.),

SO THAT that I am made aware of or reminded of an eventHigh2ERROR:#N/A10
102UX7Non-FunctionalCross-system SearchNFThe system shall allow for intuitive cross-system search by standard and custom data fields.High2ERROR:#N/A10
103UX8Non-FunctionalMultiple Portal Technology Access (cell, tablet, pc)NFThe system shall support desktop, tablet, and mobile users and provide a highly-responsive and intuitive design (scalable display). Potentially a supporting companion app.High2ERROR:#N/A10
104UX9Non-FunctionalTechnical Search OptionsNFThe system shall allow for the ability to perform searches that include a wildcard, date ranges, and/or numerical values.High2ERROR:#N/A10
105UX10Non-FunctionalSpecific Landing Page by User RoleNFThe system shall provide a landing page that displays logical information based on the user's type and modules utilized (i.e., pending tasks assigned to the user, applications or visits assigned to the user, and any past due actions assigned to the user) and is configurable by Administrative User.High2ERROR:#N/A10
106UX11Non-FunctionalReport File Type FormatNFThe system shall be able to generate and export all reports in a standard format, compatible with products like Adobe Reader, Microsoft Word, and/or Microsoft Excel.High2ERROR:#N/A10
107UX12Non-FunctionalNo Lockout upload/downloadNFThe system shall support upload operations performed in the background to allow Internal Users continued access to all interface capabilities while files are being uploaded/synced.High2ERROR:#N/A10
108UX13Non-FunctionalConfigurable NotificationsNFThe system shall support the configuration / edit of content to be included in system notifications. (going from eligible to ineligible, any appointment change)Medium1ERROR:#N/A5
109UX14Non-FunctionalPush NotificationNFAs a Scheduling and Claims Portal,

the system needs to support push notifications,

So that users can opt into multiple kinds of notifications for encounter updates, like changes to accepted encounters, as well as notification for new filtered encounters.High2ERROR:#N/A10
110UX15Non-FunctionalNF Password ResetNFThe system shall support self-service password reset for all Users.High2ERROR:#N/A10
# High Requirements"1170# "Currently Exists"Point Total12050
# Medium Requirements70# "Available with Configuration"High11700
Total # Requirements1240# "Available Soon"Medium350
Max PointsVendor Points

Scoring Dropdowns

Item PriorityValue
High2
Medium1
Response OptionValue
Currently Exists5
Available with Configuration4.5
Available soon0.5
Not Available0
Not Yet Scored

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