ATTACHMENT_D_-_Core_Features_Solution.xlsx
XLSX spreadsheet 27 KB Posted
- Attached to
- Integrated Electronic Health Record (EHR) and Social Service Case Management System - Human Services ARPA
- Solicitation number
- 23-0840-RFP
- Issued by
- Pinellas County, Clewiston City, Florida
About this file
This document is an Attachment D Core Features Solution Functionality Response Chart for an Integrated Electronic Health Record (EHR) and Social Service Case Management System procurement by Florida's Human Services department, solicited through RFP #23-0840-P. The procurement seeks a comprehensive technology solution to enable proactive service delivery, community care coordination, program planning, and critical decision support across healthcare and social service domains. The proposed system must integrate electronic health record functionality with social service case management capabilities, supporting functions such as patient scheduling, billing, lab integration, e-prescribing, telehealth, document management, and comprehensive reporting across medical and social service environments.
The project is funded through ARPA (American Rescue Plan Act) resources and aims to create a unified, scalable platform that supports client management across multiple human service programs, primary care medical services, partner information exchanges, and predictive analytics. Key technical requirements include mandatory compliance with HIPAA, Section 508/ADA standards, support for diverse integration capabilities (including Oracle E-Business Suite, Granicus Legistar, Microsoft PowerBI, Everbridge, and ESRI ArcGIS), robust security features, role-based access controls, and the ability to support complex reporting needs including HRSA, UDS, and NCQA reporting formats. The solution must provide comprehensive functionality across electronic health records, social service case management, client self-service portals, provider management, and advanced analytics capabilities.
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
Sheet1
ATTACHMENT D: Core Features Solution Functionality Response Chart
| Along with the Vendor’s overview of the proposed solution with success criteria and use case review, the Vendor must include the chart below with a response for each of the key requirement functionalities detailed. Please note that these include a representative list of key requirements for review and response but are not all inclusive of the full list of requirements which should be included in a standard, modern system implementation. A more complete list of requirements will be reviewed and finalized as part of the discovery and requirements documenting process with the successful vendor. |
| Vendor Name: __________________________________________________ |
| Please note the response code below for use in the functionality response chart. Please indicate corresponding code under the response column and provide explanation and detail about the functionality and evidence their claim within the vendor comments |
| Description | Code |
| Available Out of the Box for Proposed Solution | OOB |
| Configurable | CNF |
| No Code/Low Code | LC |
| Module at Additional Cost | MOD |
| Available through 3rd Party Software (Included) | 3rd |
| Available through 3rd Party Software (Not Included) | 3rd NI |
| Available through Customization | CUS |
| In Development for Future Release (Notes must include timeframe for release) | FUT |
| Not Available | NA |
| Core Features of Solution | ||||
| Electronic Health Record Core Features | ||||
| Category | Functional Questions (Does solution…) | Response | Vendor Comments | |
| 1 | Charting | Have native charting functions that support minimal user entry. | Select | |
| 1.1 | Include automated coding support such as ICD-10 diagnostic coding, CPT coding and Evaluation and Management advice with annual updates. | Select | ||
| 1.2 | Support flow charting (labs, vital signs, growth parameters). | Select | ||
| 1.3 | Have automated data syncing across system to avoid divergent data. | Select | ||
| 1.4 | Have and support customizable templates, forms, and assessment tools. | Select | ||
| 1.5 | Have remote charting. | Select | ||
| 1.6 | Support digital signatures. | Select | ||
| 1.7 | Have ability to modify notes with audit tracking and note locking. | Select | ||
| 1.8 | Support automated workflows. | Select | ||
| 1.9 | Support alerts and flags and prompts to assure client safety and compliance. | Select | ||
| 1.10 | Perform automated quality checks such as alerting for missing signatures, notes, vitals, etc. | Select | ||
| 1.11 | Provide client dashboard for at-a-glance status with medical summary view with prescription & does, lab results, pending labs, diagnosis lists, allergies, and notes. | Select | ||
| 1.12 | Provide decision support tools. | Select | ||
| 2 | Reporting | Support data collection from wearables and medical devices. | Select | |
| 2.1 | Support cross-continuum and predictive analytics. | Select | ||
| 2.2 | Support population health management. | Select | ||
| 2.3 | Provide meaningful use dashboarding. | Select | ||
| 2.4 | Provide prescription, e-prescription, medication list, patient Rx history, and drug interaction reports. | Select | ||
| 2.5 | Provide patient list and eligibility reports. | Select | ||
| 2.6 | Provide referrals report to track referrals, requests, outcomes, and notes. | Select | ||
| 2.7 | Provide trends, activity, audit reporting. | Select | ||
| 2.8 | Have ability to dynamically build and export custom reports/data based on selected system variables. | Select | ||
| 2.9 | Ability to receive, track, and direct incoming referrals. | Select | ||
| 2.10 | Supports the design and generation of reports that align to a range of standards such as UDS, CMS, NCQA, and other formats determined necessary. | Select | ||
| 2.11 | Support creation of a real-time/active patient dashboard with key demographic, visit data, labs, results, medications, and notes. | Select | ||
| 3 | Billing | Support electronic billing and payment tracking. | Select | |
| 3.1 | Support electronic eligibility verification for claims. | Select | ||
| 4 | Lab Integration | Support interoperability between laboratory and medical practice. | Select | |
| 4.1 | Provide patient portal access to results with simple charts and graphs, support abilities to display and review lab orders and results abnormalities. | Select | ||
| 4.2 | Support timely notification of lab results to appropriate staff as well as easy routing and tracking of results. | Select | ||
| 5 | Client Self Services Portal (Medical) | Support messaging and communication with SMS and Email. | Select | |
| 5.1 | Support easy client registration and access in mobile environment in ADA compliant environment. (MANDATORY) | Select | ||
| 5.2 | Support appointment booking, amendment, and cancellation. | Select | ||
| 5.3 | Support access to test results, prescriptions, education materials, and patient records. | Select | ||
| 5.4 | Support effective and secure patient access and password management. | Select | ||
| 5.5 | Support ease of uploading documentation for case file. | Select | ||
| 5.6 | Support alerts, flags, and reminders for patient notification and guidance. | Select | ||
| 5.7 | Support the creation, update, and maintenance or patient education materials including ability to source and share 3rd party materials through the client portal. | Select | ||
| 5.8 | Support capability for patient to sign consent, treatment decisions, and authorizations electronically. | Select | ||
| 5.9 | Support B2C authentication for accounts when clients wish to use existing Google, Facebook, Microsoft accounts. | Select | ||
| 6 | Medical Case Management | Support information collaboration and shared patient records across affiliated providers | Select | |
| 6.1 | Support creation and management of patient care plans including alignment with Social Determinants of Health. | Select | ||
| 6.2 | Support effective tracking and monitoring of care plan milestones to proactively address patient care. | Select | ||
| 6.3 | Provide clinic decision support. | Select | ||
| 6.4 | Support chronic disease management functions. | Select | ||
| 6.5 | Supports Continuity of Care Document and record. | Select | ||
| 6.6 | Support progress notes templates that are problem oriented and can, at the user’s option, be linked to a diagnosis or client record. | Select | ||
| 6.7 | Provide administrative tools to build care plans, guidelines, and protocols for use during patient care planning with simple discharge instructions to patient guidance. | Select | ||
| 6.8 | Support results display as a flow sheet and/or graphical formats. | Select | ||
| 6.9 | Support administrative tools to build care plans, guidelines, and protocols during patient care planning. | Select | ||
| 6.10 | Support automatic documentation of patient specific discharge instructions in care plan. | Select | ||
| 6.11 | Support clinician/provider alerts on patient care and reminders for common tasks and operational flows. | Select | ||
| 7 | E-prescribing | Maintain and display complete and current medications list. | Select | |
| 7.1 | Support easy mobile access. | Select | ||
| 7.2 | Support electronic prior authorization processes. | Select | ||
| 7.3 | Provide medication decision support. | Select | ||
| 7.4 | Automate formulary compliance. | Select | ||
| 7.5 | Support reporting on controlled substance. | Select | ||
| 7.6 | Support refill requests and processing. | Select | ||
| 7.7 | Describe the audit features for E-Prescribing. | Select | ||
| 7.8 | Support automated PDMP review through integrated State of Florida E-FORSCE procedure. | Select | ||
| 7.9 | Support identification of drug interaction, contraindications, and warnings (prescription, over the counter) at the point of medication ordering. (Including drug to drug, drug allergy, drug to disease, and drug to pregnancy) | Select | ||
| 8 | Patient Scheduling | Support addition/deletion/edit of patient visits and consent management and authorizations | Select | |
| 8.1 | Support patient scheduling functions. | Select | ||
| 9 | Practice Management | Support preparation of CMS 1500 claims. | Select | |
| 9.1 | Support inventory management. | Select | ||
| 9.2 | Support medical, administrative, and operations staff scheduling. | Select | ||
| 9.3 | Support integration of medical devices such as imaging, wearable devices, smart pumps, monitors, etc. | Select | ||
| 9.4 | Support two-way standard interfacing laboratory, radiology, pharmacy, and other compliant information systems. Please explain current interfaces supported within EHR. | Select | ||
| 9.5 | Support tracking and management of sliding scale fee processes for programs when defined. | Select | ||
| 10 | Telehealth | Allow for integrated telehealth service delivery. | Select | |
| 10.1 | Support provider-initiated connection of scheduled appointment with client simply selecting to join session. | Select | ||
| 11 | Specialty Referrals | Provide dynamic scheduling and referral to specialty care services affiliated with the program. | Select | |
| 11.1 | Provide referral acceptance feedback from provider. | Select | ||
| 11.2 | Provide service delivery/outcome feedback. | Select | ||
| 11.3 | Receive and tracking patient records from specialty care provider to allow for central data management approach. | Select | ||
| 12 | Medical Document Management | Provide effective document management functionality for easy inclusion of patient documents into system records. | Select | |
| 12.1 | Provide OCR capabilities for information population from external sources. | Select | ||
| 12.2 | Provide document validation and sign-off and automated workflows. | Select | ||
| 12.3 | Support integration with other 3rd party document management solutions. (mobile dictation software, etc) | Select | ||
| 13 | Community Partner Portal | Provide secure access to client information based on program, agency, and/or provider. | Select | |
| 13.1 | Provide access to analyses, dashboards, and other program information. | Select | ||
| 13.2 | Provide ability to upload required documentation in a range of formats for eligibility review. | Select | ||
| 13.3 | Support configurable approach to adding additional program types with separate requirements and ability to directly refer client to collaborating programs and services. | Select | ||
| 14 | EHR Security/HIPAA Compliance | Maintain strict compliance with federal and state regulatory guidance on managing health records. | Select | |
| 14.1 | Support Encrypted database features. | Select | ||
| 14.2 | Allow for detailed audit controls to monitor access, entries, and changes. | Select | ||
| 14.3 | Allow for detailed audit controls to monitor access, entries, and changes. | Select | ||
| Social Service Core Features: |
| Category | Functional Questions (Does solution…) | Response | Vendor Comments | |
| 1 | Reception | Support a reception log with check in times and reminders. | Select | |
| 1.1 | Solution allows for automatic case lookup tied to incoming call to populate screen. | Select | ||
| 2 | Intake and Scheduling | Support automated workflows. | Select | |
| 2.1 | Support appointment management and reminders, missed appoint notifications, follow-up reminders, etc. | Select | ||
| 3 | Document Management | Support various, non-health related client documents, program documentation, and other key documents to be scanned, uploaded, linked and stored. | Select | |
| 3.1 | Support integration with other 3rd party document management solutions. (mobile dictation software, etc) | Select | ||
| 3.2 | Support a range of file types for attachment from scanned images, smart documents, wav files, mov, gifs, and other formats. Please describe. | Select | ||
| 4 | Client Self Service Portal (eligibility) | Support easy access to client registration and documentation processes in mobile, ADA compliant environment. (MANDATORY) | Select | |
| 4.1 | Support detailed eligibility documentation interface that walks the client through collection of each specified item and ability to adjust required items. | Select | ||
| 4.2 | Support provider and community partner eligibility lookup for clients. | Select | ||
| 5 | Case Review | Support detailed assessment for program eligibility, updates on changes and case statuses/case load reviews. | Select | |
| 5.1 | Support completion and issuance of claims forms for benefits in the manner required by the federal government. | Select | ||
| 5.2 | Support auto-population of federal benefits forms with client demographics and dynamically selected items already in the system to prepare for easy submission. | Select | ||
| 5.3 | Support claims tracking for submission, under review, granted, and appeals status with ability to add case notes. | Select | ||
| 5.4 | Support escalation flow for manual and automatic reviews as defined by County. | Select | ||
| 6 | Assignment Tasking and Tracking | Support effective workflow of new/existing client submissions and inquiries. | Select | |
| 6.1 | Allow for supervisor review and assignment/reassignment. | Select | ||
| 6.2 | Support QA of case records and determinations to ensure consistency, timeliness, completeness, and accuracy of case files. | Select | ||
| 7 | Client Data Management | Support tracking of services and internal benefits/assistance provided on behalf of client. | Select | |
| 7.1 | Support service and program level information and service types defined by the County. | Select | ||
| 7.2 | Allow for tracking of grant, contract, and provider associated with service and program to better track performance. | Select | ||
| 7.3 | Supports assessment and scoring for service planning. | Select | ||
| 7.4 | Solution supports a single, unified client list across all health and social service components. (MANDATORY) | Select | ||
| 7.5 | Support all client transactions and services accessible in one place with flags for specific programs/services engaged in and active/not active designation. | Select | ||
| 7.6 | Support additional of user-defined/agency-defined, non-standard client demographic fields such as family size, monthly income, homeless status, etc. | Select | ||
| 7.7 | Support and enforce unique client identifier across the system and maintain a unified client index. | Select | ||
| 8 | Benefits Tracking and Management | Support tracking of local, state, and federal benefits cases managed both internally and by external partners including client detail, case status, and supporting documentation. | Select | |
| 8.1 | Support submissions for benefits to Social Security Administration. | Select | ||
| 8.2 | Support ongoing tracking of benefits receive by program. | Select | ||
| 9 | Social Service Case Management & Navigation | Support individual and family case plans. | Select | |
| 9.1 | Support development/integration of common assessments and case management tools within the system. | Select | ||
| 10 | Eligibility Determination | Support configurable eligibility rules associated to each program. | Select | |
| 10.1 | Support monitoring of eligibility for federal programs such as Medicaid as a prompt for eligibility determination. | Select | ||
| 10.2 | Support assessment and scoring for eligibility determination that is program specific. | Select | ||
| 11 | Internal Program and Process Tracking | Support client level and aggregate data intake to allow for effective monitoring of program service delivery. | Select | |
| 11.1 | Support ability to perform care coordination across programs leveraging a unified client list for client level data. | Select | ||
| 12 | External Program Tracking & Management | Support client level and aggregate data intake to allow for effective monitoring of program service delivery in the community. | Select | |
| 12.1 | Support ability to perform care coordination across programs leveraging a unified client list for client level data. | Select | ||
| 13 | Invoice Management and Reconciliation | Support workflow for receipt of invoices and supporting documentation, flexible task assignment and review, edits to line items on invoice, approvals, notes, and electronic submission to the Clerk’s office for final payment processing. | Select | |
| 13.1 | Support audit and documentation trace of all transactions. | Select | ||
| 13.2 | Support ability to submit ‘split’ invoice payment request for part of an invoice while awaiting further documentation with clear notation of paid versus unpaid balance tracked in system and sent with invoice. | Select | ||
| 13.3 | Support reconciliation for all providers and vendors participating in County grant and contracted programs and HIPAA compliant document exchange/management for all financial/accounting documents. This includes, but is not limited to, generating account numbers, traceability of invoices, and voucher processes. | Select | ||
| 13.4 | Support clear transaction flow with user defined verifications, authorization, escalation procedures, and auditing enforced programmatically. | Select | ||
| 14 | Provider Management and Tracking | Support provider portal and workflow to allow for shared document coordination, submission of reports and invoices, validation of invoiced services, supporting documentation, etc. | Select | |
| 14.1 | Support assignment of providers to specific or groups of programs, contracts, grants, and client services. | Select | ||
| 14.2 | Support a unified vendor list populated in alignment with Oracle system. (MANDATORY) | Select | ||
| Analytics & Integration Features: |
| Category | Functional Questions (Does solution…) | Response | Vendor Comments | |
| 1 | Ad Hoc Reporting, Analytics, and Alerts | Ad hoc reporting by users an option and standard defined reports. | Select | |
| 1.1 | Support Health Resources and Services Administration (HRSA), Uniform Data System (UDS) reporting and National Committee for Quality Assurance (NCQA), Patient Centered Medical Home (PCMH) reporting. | Select | ||
| 1.2 | Support 3rd party report writing products. | Select | ||
| 1.3 | Support complex analyses across the system data based on defined conditions or condition combinations, events, and thresholds (ie: ER visit over 3 times within 4 months, new event within 3 months of a different defined event, etc.) | Select | ||
| 1.4 | Support monitoring and alerts for defined events, abuse of services, or other reasons that require attention across the data. | Select | ||
| 1.5 | Support ad hoc file extraction in formats compatible with common Microsoft products such as Excel, Word, Power BI, etc. as well as SAS, Tableau, and other standard market packages. | Select | ||
| 2 | Service Transactions and Outcomes | Support real-time and retrospective trending, analysis, and reporting or clinical, operational, demographic, or other user specified data. | Select | |
| 2.1 | Support dynamic, secure information exchange with external systems. | Select | ||
| 3 | Integration to Internal Systems | Support integration to Oracle E-Business Suite. (Exhibit A) | Select | |
| 3.1 | Support integration to Granicus Legistar. Exhibit A) | Select | ||
| 3.2 | Support integration to Microsoft PowerBI (Exhibit A) | Select | ||
| 3.3 | Support integration with Everbridge call notification system. (Exhibit A) | Select | ||
| 3.4 | Support integration with ESRI ArcGIS Enterprise. (Exhibit A) | Select | ||
| 4 | Data Intake, Ingestion, and Exchange | Support critical, client level data integration from various external partner sources. (Exhibit A) | Select | |
| 5 | Integration of Key External Sources | Support critical integrations with external sources for information exchange and direct inquiries: (Exhibit A) | Select | |
| 6 | Performance Dashboards | Support solution-based analytical dashboards that support management review, performance, status updates, alerts, outcomes, effective workflow, and trends. | Select | |
| Select | ||||
| 7 | Tracking Contract and Grant Performance | Support service reporting from providers assigned to clients, programs, contracts, and grants to effectively manage performance. | Select | |
| 8 | Fiscal Tracking of Programs and Services | Support provider invoices and payment tracking tied to clients, programs, contracts, and grants. | Select | |
| Support integration to Oracle E-Business Suite | Select | |||
| 8.1 | Tracking incoming invoices and requests for payment as well as outgoing billing workflow (such as CMS claims). | Select | ||
| Other Technical Features and Functions: |
| Category | Functional Questions (Does solution…) | Response | Vendor Comments | |
| 1 | Technical Environment | Provides implementation at fixed site and mobile locations hardware and operating system agnostic. . | Select | |
| 1.1 | Provide an API-driven internal system architecture. | Select | ||
| 1.2 | Describe core data integration capabilities from standard API availability to adopted standards for HL7, FHIR, etc. | Select | ||
| 2 | Infrastructure and Technology | All public facing components of the solution meet Section 508/ADA requirements (MANDATORY) | Select | |
| Select | ||||
| 3 | Security and Security Features | Describe how the product meets all HIPAA, HITECH, and other security requirements. | Select | |
| 3.1 | Product provides different levels of security based on User Role, Site, and/or Enterprise settings. | Select | ||
| 3.2 | Describe the audit process within the product. | Select | ||
| 3.3 | Describe the product's ability to create new security rights/roles based on new workflows or enhancements (e.g., customer-developed content such as Psych notes or departmental flowsheets). | Select | ||
| 3.4 | Describe how the patient’s data is secured at all times and in all modules of the product (e.g., strong password protection or other user authentication, data encrypted at rest, data encrypted in motion). | Select | ||
| 3.5 | Describe hardware security requirements | Select | ||
| 3.6 | Support detailed auditing and tracking of user tasks. | Select | ||
| 3.7 | Support encrypted storage | Select | ||
| 3.8 | Solution meets or exceeds all aspects of the Health Insurance Portability and Accountability Act (HIPAA) Privacy and Security requirements. Describe your solution’s compliance including support for the ingestion and exchange of information with community partners and programs in a secure, HIPAA compliant environment. (MANDATORY) | Select | ||
| 3.9 | Support authentication through Okta using SAML/OAuth. | Select | ||
| 4 | Licensing Model | How is the product licensed? | Select | |
| 4.1 | Are licenses purchased per user, concurrent, per module, etc? | Select | ||
| 4.2 | Define ‘user’ if it relates to the licensing model (i.e., FTE MD, all clinical staff, social services, community providers, patients, etc). | Select | ||
| 5 | Vendor Support | Provide a detailed list of each with your standard SLA for each support program. | Select | |
| 5.1 | What are your support statistics (# of Support Calls to the % of resolutions at each severity level)? | Select | ||
| 5.2 | Define the Support Structure (Tiered Approach, Client assigned 1 point of contact, etc.) | Select | ||
| 5.3 | Who has ownership of the following? | Select | ||
| 1. Data | Select | |||
| 2. Software | Select | |||
| 3. Enhancements or Customizations Paid for by Customer | Select | |||
| 4. Hardware | Select | |||
| 5. Servers | Select | |||
| 6. Workstations | Select | |||
| 6 | Training | Describe Training plan for the implementation in detail | Select | |
| 7 | Lawsuits and Legal | Vendor agrees to accept County agreement standard terms and conditions without modification | Select | |
| 8 | Contract Terms and Vendor Guarantees | Support escrow of the source code for this product for duration of contract. | Select |
&"-,Bold"&12INTEGRATED ELECTRONIC HEALTH RECORD (EHR) AND SOCIAL SERVICE CASE MANAGEMENT SYSTEM - HUMAN SERVICES
RFP # 23-0840-P
File details come from the government source that posted it. Updated .