Attachment L System Requirements.xlsx
XLSX spreadsheet 33 KB Posted
- Solicitation number
- S-44300-00017529
- Issued by
- Oregon
About this file
This is a System Requirements attachment for a Request for Proposals issued by the State of Oregon, acting through the Oregon Health Authority, to procure a fully managed Software-as-a-Service solution for the Prescription Drug Monitoring Program system. The attachment specifies 30 critical system requirements organized across six functional areas: Security, Privacy & Compliance; Data Collection, Validation & Retention; Reporting, Dashboards & Analytics; Search & Query Tools; User Access, Roles & Authentication; and Communication & Support. Requirements are prioritized as Critical (Priority 1), High (Priority 2), or Moderate (Priority 3), with 24 total High-priority requirements identified. Proposers must complete and submit the Requirements sheet as part of their response, providing indicators for each requirement that reflect whether the functionality meets base system capabilities, will meet by the proposed go-live date, or cannot be met. Any modifications to the workbook outside of designated response fields results in automatic disqualification.
Proposer responses are scored on a 0-3 point scale, with requirements that meet base system functionality receiving 3 points, those meeting by go-live date receiving 1 point, and those that cannot be met receiving 0 points. The scoring matrix applies different weightings for High-priority requirements (6 points for base functionality), Medium-priority requirements (4 points for base functionality), and Low-priority requirements (2 points for base functionality). Critical requirements include data encryption in transit, at rest, and in use; SOC2 Type 2 and HITRUST security certifications; 99% uptime with support for 31,000+ concurrent users; comprehensive data collection with DEA, NPI, and NDC validation; 24/7/365 daily data processing; and 24/7/365 in-house helpdesk support.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment B Disclosure Affadavit.docx | DOCX document | |
| Attachment I Scope of Work.pdf | ||
| Attachment G Rsponsibility Inquiry.docx | DOCX document | |
| Attachment K Service Req and Proposal Crosswalk.xlsx | XLSX spreadsheet | |
| Attachment C Propoer Information.docx | DOCX document | |
| Attachment E cost sheet.docx | DOCX document | |
| Attachment A Sample Contract~5.pdf | ||
| AttachmentM OStandards Spreadsheet.xlsx | XLSX spreadsheet | |
| 6070 - S-44300-00017529 PDMP RFP.pdf | ||
| Attachment D Reference Check.docx | DOCX document | |
| Attachment F DISADVANTAGED BUSINESS FORM.docx | DOCX document | |
| Attachment H Enhancements and Hourly Rates.xlsx | XLSX spreadsheet |
Show all 12
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
| RFP 6070 Prescription Drug Montoring Program (PDMP) |
| Proposer Instructions - Responding to Attachment L |
| Proposer Name: |
| Table of Contents | ||
| Tab No. | Requirements Functional Area | Number of Requirements |
| 1 | Instructions Tab | |
| 2 | REQUIREMENTS - High | 24 |
| 2 | REQUIREMENTS - Medium | 0 |
| 3 | REQUIREMENTS - LOW | |
| Total Requirements | 24 | |
| Instructions: Enter Proposer name on Line 6 in the Instructions Tab. Proposer must complete and submit the Requirements sheet as part of its Proposal. To be considered for evaluation, the Requirements sheet must include a response in the column titled "Proposer Response" based on the description of indicators below. For a requirement that receives an indicator other than "1," utilize the Proposer Comments, Descriptions, and Explanation field to provide additional information. | ||
| 1- Meets with base system functionality | Feature/Function is included in the base solution (out of the box functionality) | |
| 2 - Will meet within proposed Go-Live date | Feature/function will be available by a future release to meet the go-live date. Proposer should provide the planned delivery date of the future release in comment area and how it intends to accomplish the new functionality (e.g. customization, configuration, third-party integration). | |
| 3 - Will not meet | Feature/function cannot be provided. | |
| Proposers stating that functions will be supplied will be contractually obligated to warrant their claim. In the event that such functionality is not available in the current release, the Proposer will be liable for any additional services and/or costs associated with developing or procuring such functionality. |
| Any modification to this workbook outside of the "Proposer Response" and "Proposer Comments, Descriptions, and Explanation" fields is an automatic disqualification from the Request for Proposal. | |
| Prioritization of Requirements | |
| High | A Critical requirement without which the product is not acceptable. |
| Medium | A necessary but deferrable requirement which makes the product less usable but still functional. |
| Low | A nice feature to have if there are resources but the product functions well without it. |
| Proposer’s response to the Requirements in the table of contents above will be scored on a 0 - 3 point scale based on the ability of Proposer to deliver functionality. The following range of points will be given, factoring priority, and Proposer’s ability to deliver a Solution providing the function, and related effort to deliver. |
| Point Scale | ||
| Functionality | Point Scale | |
| 1- Meets with base system functionality | 3 | |
| 2 - Will meet within proposed Go-Live date | 1 | |
| 3 - Will not meet | 0 |
Requirements
| Total Score | ||||||||
| Category | Subcategory | Short Name | Description | Priority | Proposer Response | Proposer Comments, Descriptions, and Explanation | Score | 0 |
| 1. Security, Privacy & Compliance | Data encryption (in transit, at rest, and in use) | High | -- | |||||
| 1. Security, Privacy & Compliance | Security certifications (SOC2 Type 2, HITRUST, vulnerability scans) | High | ||||||
| 1. Security, Privacy & Compliance | Disaster recovery plan & full data backup | High | ||||||
| 1. Security, Privacy & Compliance | Secure web access with 99% uptime and support for 31,000+ concurrent users | High | ||||||
| 1. Security, Privacy & Compliance | Maintenance schedule (weekly windows, bi-weekly deployments) | MED | ||||||
| 1. Security, Privacy & Compliance | System scalability & fault tolerance | Low | ||||||
| 2. Data Collection, Validation & Retention | Secure data upload mechanism (ASAP formats, 24/7 availability, secure channels) | High | ||||||
| 2. Data Collection, Validation & Retention | Comprehensive data elements (patient, prescriber, drug, refill, diagnosis, etc.) | High | ||||||
| 2. Data Collection, Validation & Retention | DEA, NPI, and NDC validation and conversion | High | ||||||
| 2. Data Collection, Validation & Retention | Automated data removal & 36-month retention enforcement | High | ||||||
| 2. Data Collection, Validation & Retention | Daily data processing (24/7/365 ingestion and availability) | High | ||||||
| 2. Data Collection, Validation & Retention | Standardization of data | Med | ||||||
| 2. Data Collection, Validation & Retention | Patient record clustering (alias resolution, DOB/address variations) | Med | ||||||
| 3. Reporting, Dashboards & Analytics | Ad hoc report creation & queries (GUI-based, customizable) | Med | ||||||
| 3. Reporting, Dashboards & Analytics | Audit history & user activity reporting (full traceability) | Med | ||||||
| 3. Reporting, Dashboards & Analytics | Federal grant reporting (MME, opioid trends, user types, etc.) | Med | ||||||
| 3. Reporting, Dashboards & Analytics | Interactive dashboards (grant metrics, prescribing trends, user activity) | Med | -- | |||||
| 3. Reporting, Dashboards & Analytics | Prescriber report cards (quarterly summaries, QA checks, DEA status) | Med | ||||||
| 3. Reporting, Dashboards & Analytics | Ad hoc audit reports (non-reporting or rejected dispensers) | Med | ||||||
| 4. Search & Query Tools | Advanced query tools (relational, multi-dimensional, flexible search criteria) | Med | ||||||
| 4. Search & Query Tools | Prescriber & delegate queries (DEA-based, role-based access) | Med | ||||||
| 4. Search & Query Tools | Full audit history reports for patient access | Med | ||||||
| 5. Access, Roles & Authentication | 5. User Access, Roles & Authentication | Provider authorization verification for integrated access | High | |||||
| 5. Access, Roles & Authentication | User registration & authentication (email verification, password security, lockouts) | High | ||||||
| 5. Access, Roles & Authentication | Role-based permissions & delegate management (including annual re-verification) | High | ||||||
| 5. Access, Roles & Authentication | Delegate workflow (supervisor approval, activity tracking, annual re-verification) | Med | ||||||
| 5. Access, Roles & Authentication | Configurable registration settings (role-based fields, document uploads) | Low | ||||||
| 6. Communication & Support | 24/7/365 in-house helpdesk support (non-outsourced) | High | ||||||
| 6. Communication & Support | Messaging & broadcast alerts (portal announcements, direct messages) | Med | ||||||
| 6. Communication & Support | Customizable tile view & user dashboards (alerts, recent activity, quick links) | Low |
General
| list of the Top 30 Requirements for the Oregon PDMP system, categorized by function and assigned a priority level from 1 to 3, where: | |
| 1 | 1 = Critical (must-have for compliance, security, or core functionality) |
| 2 | 2 = High (important for usability, performance, or operational efficiency) |
| 3 | 3 = Moderate (enhances value, flexibility, or user experience) |
| 4 |
Top 30 Oregon PDMP Requirements, now categorized by functional area and still ranked by priority (1 = Critical, 2 = High, 3 = Moderate):
| 🔐 1. Security, Privacy & Compliance | ||
| # | Requirement | Priority |
| 1 | Data encryption (in transit, at rest, and in use) | 1 |
| 2 | Security certifications (SOC2 Type 2, HITRUST, vulnerability scans) | 1 |
| 3 | Disaster recovery plan & full data backup | 1 |
| 4 | Secure web access with 99% uptime and support for 31,000+ concurrent users | 1 |
| 5 | Maintenance schedule (weekly windows, bi-weekly deployments) | 2 |
| 6 | System scalability & fault tolerance | 3 |
| 🧾 2. Data Collection, Validation & Retention | ||
| # | Requirement | Priority |
| 7 | Secure data upload mechanism (ASAP formats, 24/7 availability, secure channels) | 1 |
| 8 | Comprehensive data elements (patient, prescriber, drug, refill, diagnosis, etc.) | 1 |
| 9 | DEA, NPI, and NDC validation and conversion | 1 |
| 10 | Automated data removal & 36-month retention enforcement | 1 |
| 11 | Daily data processing (24/7/365 ingestion and availability) | 1 |
| 12 | Standardization of data | 2 |
| 13 | Patient record clustering (alias resolution, DOB/address variations) | 2 |
| 📊 3. Reporting, Dashboards & Analytics | ||
| # | Requirement | Priority |
| 14 | Ad hoc report creation & queries (GUI-based, customizable) | 2 |
| 15 | Audit history & user activity reporting (full traceability) | 2 |
| 16 | Federal grant reporting (MME, opioid trends, user types, etc.) | 2 |
| 17 | Interactive dashboards (grant metrics, prescribing trends, user activity) | 2 |
| 18 | Prescriber report cards (quarterly summaries, QA checks, DEA status) | 2 |
| 19 | Ad hoc audit reports (non-reporting or rejected dispensers) | 2 |
| 🔍 4. Search & Query Tools | ||
| # | Requirement | Priority |
| 20 | Advanced query tools (relational, multi-dimensional, flexible search criteria) | 2 |
| 21 | Prescriber & delegate queries (DEA-based, role-based access) | 2 |
| 22 | Full audit history reports for patient access | 2 |
| 👥 5. User Access, Roles & Authentication | ||
| # | Requirement | Priority |
| 23 | Provider authorization verification for integrated access | 1 |
| 24 | User registration & authentication (email verification, password security, lockouts) | 1 |
| 25 | Role-based permissions & delegate management (including annual re-verification) | 1 |
| 26 | Delegate workflow (supervisor approval, activity tracking, annual re-verification) | 2 |
| 27 | Configurable registration settings (role-based fields, document uploads) | 3 |
| 📬 6. Communication & Support | ||
| # | Requirement | Priority |
| 28 | 24/7/365 in-house helpdesk support (non-outsourced) | 1 |
| 29 | Messaging & broadcast alerts (portal announcements, direct messages) | 2 |
| 30 | Customizable tile view & user dashboards (alerts, recent activity, quick links) | 3 |
Scoring Matrix
| High | Medium | Low | |
| 1- Meets with base system functionality | 6 | 4 | 2 |
| 2 - Will meet within proposed Go-Live date | 5 | 3 | 1 |
| 3 - Will not meet | 0 | 0 | 0 |
| High | 2 |
| Medium | 3 |
| Low | 4 |
File details come from the government source that posted it. Updated .