Att F- Technical Proposalv2.docx

DOCX document 40 KB Posted

Attached to
RFP 26-87488 IVH Electronic Health Record (EHR)Bid Documents
Solicitation number
RFP 26-87488
Issued by
Tippecanoe County, Indiana

About this file

This is a Technical Proposal Attachment document for RFP 26-87488 Electronic Health Records, establishing detailed requirements for an Electronic Health Records (EHR) system intended for Long-Term Care (LTC) facilities. The RFP requires respondents to address seven major functional categories: Basic Information System capabilities including patient demographics, assessments, care documentation, billing, and regulatory submissions; Basic EMR functionalities covering clinical history, diagnoses, medications, allergies, charting, and care plans; Ancillary and Clinical Administration functions such as orders, medication administration records, and Point of Care documentation; Advanced EMR capabilities focused on clinical decision support, electronic medication administration at point of care, quality analytics, and device integration; External Ancillary Services Integration including pharmacy, referral systems, lab, diagnostics, radiology, eligibility checking, and formula checking; Engagement and Basic Information Exchange features such as physician portals, e-signatures, prescribing, clinical document exchange, and patient/family portals; and Interoperability and Health Information Exchange capabilities for standards-based data exchange with other EHR systems through Health Information Exchanges. The proposal requires respondents to provide measurable performance metrics for all Stage capabilities, including response times, error thresholds, uptime commitments, and interface throughput for use during acceptance testing and contract performance monitoring.

Respondents must demonstrate GovRAMP compliance with current RAMP control matrices, authorization packages, System Security Plans, and continuous monitoring artifacts. The RFP mandates compliance documentation across multiple security and operational standards including HIPAA compliance, Multi-Factor Authentication (MFA) enforcement, system breach notification timelines, third-party compliance certifications, security protocols, encryption standards, and audit logging capabilities. Respondents are required to document their business history in the LTC industry, identify any unique system functionalities or capacities, and provide detailed descriptions of how their system addresses both required and desired functionalities across all seven sections. Integration requirements specify supported standards including HL7 v2.x, FHIR R4, NCPDP, DICOM, and interface modalities such as REST APIs and secure file exchange with comprehensive message and error handling capabilities.

View the file

Other files

File Type Posted
Vendor Networking Opportunities List.xlsx XLSX spreadsheet
Att G - Q&A Template.xlsx XLSX spreadsheet
RFP 26-87488 IVH EHR Main Document.docx DOCX document
Att L - AI - Technical Proposal Questions.docx DOCX document
Att A - IVOSB.docx DOCX document
Att N - Resource Usage Matrix.xlsx XLSX spreadsheet
Att H - Reference Check Form.docx DOCX document
Att B - Sample Contract.docx DOCX document
Att B3 - IOT-SaaS.docx DOCX document
Att B1 - IOT-IaaS.docx DOCX document
Att B2 - IOT-PaaS.docx DOCX document
Att J - Attestation Form.docx DOCX document
Att E - Business Proposal.docx DOCX document
Att D - Cost Proposalv.2.xlsx XLSX spreadsheet
Att C - Indiana Economic Impact Form.xlsx XLSX spreadsheet
Att I - Pre-proposal Network Form.docx DOCX document
Att M - Infrastructure Overview.docx DOCX document
Att K - Scope of Workv2.docx DOCX document
Show all 18

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

RFP 26-87488 Electronic Health Records

TECHNICAL PROPOSAL

ATTACHMENT F

INSTRUCTIONS

· Please supply requested information in the blue-shaded areas and indicate any attachments that have been included.

· Document all attachments with which section and question they pertain to.

General Information

1. Please share a brief history of your business and how long it has been active in the LTC industry?

2. Are there any functionalities or capacities that are unique to your system?

Technical Proposal Questions

For every Stage capability described, the Respondent shall provide measurable performance metrics, such as response time, error thresholds, uptime commitments, interface throughput, or other quantifiable indicators. These metrics will be used during acceptance testing and contract performance monitoring.

1. Basic Information System – Section 1

1.1. Describe how the system completes basic business functions containing patient demographic information for Admissions, Discharge, and Transfers. Required for this Contract

1.2. Describe how the system completes basic business functions for Regulatory, Standard, or Common Assessments (MDS, OASIS, IRF-PAI, InterRAI, etc) or other information that a provider needs to collect. Required for this Contract

1.3 Describe how the system completes basic business functions for care/service documentation by direct care/service staff primarily for accounting and billing purposes. Required for this Contract

1.4 Describe how the system completes basic business functions for accounting and billing capabilities with customization of payors. Required for this Contract

1.5 Describe how the system completes basic business functions for electronic submission of assessment and care documentation data to regulatory agencies (if applicable). Required for this Contract

1.6 Respondents must provide GovRAMP compliance evidence including a current RAMP control matrix, authorization package or letter, System Security Plan (SSP), and continuous monitoring artifacts, if applicable. See Section III. Scope of Work a) Objectives of the Engagement. Required for this Contract

2. Basic EMR-Functionalities – Section 2

2.1. Describe how the system completes basic EHR functionalities for clinical patient/resident/client history. Required for this Contract

2.2. Describe how the system completes basic EHR functionalities for lists of diagnoses, problems, medications, allergies, etc. Required for this Contract

2.3. Describe how the system completes basic EHR functionalities for clinical charting and documentation. Required for this Contract

2.4. Describe how the system completes basic EHR functionalities for care plans. Required for this Contract

2.5. Does the system complete basic EHR functionalities for interdisciplinary notes (e.g. Physician, Nurse, Therapist, Pharmacist, etc.)? If yes, please describe how the system completes the functionalities. Desired

3. Ancillary & Clinical Administration (Non-Integrated) – Section 3

3.1. Describe how the system extends EHR functionalities for orders (medications, lab, radiology, diagnostic tests, therapy, and referrals). Required for this Contract

3.2. Describe how the system extends EHR functionalities for electronic medication administration/treatment/adherence record (if applicable) (not at Point of Care). Required for this Contract

3.3. Describe how the system extends EHR functionalities for Point of Care assessment/service documentation (laptop, tablet, kiosk, etc.). What are the compatible system requirements for operating systems, browsers, etc. for this functionality? Required for this Contract

3.4. Does the system extend EHR functionalities for workflow engines (workflow sheets, next step prompts, alerts, reminders, and tasks)? If yes, please describe how the system completes the functionalities. Desired

3.5. Does the system extend EHR functionalities for results (e.g. medications, labs, radiology, diagnostic tests, therapy, etc.)? If yes, please describe how the system completes the functionalities. Desired

4. Advanced EMR (Internal Quality-Focused) – Section 4

4.1. Describe how the system adds EHR functionalities and capabilities to improve care quality for clinical decision support capabilities (e.g. INTERACT, reducing hospitalization, medications, falls prevention, pressure ulcers prevention, pressure ulcer treatment, wound care, reducing acquired infections, catheterizations, chronic disease management, etc.). Required for this Contract

4.2. Describe how the system adds EHR functionalities and capabilities to improve care quality for electronic medication administration at point of care (eMAR/eTAR, unit dispensing, closed loop verification, and home medication dispensers (if applicable) at point of care. Required for this Contract

4.3. Describe how the system adds EHR functionalities and capabilities to improve care quality for quality reports, analytics, and dashboards (e.g. hospital readmissions, quality measures, and length of stay (if applicable), etc.). Required for this Contract

4.4. Does the system add EHR functionalities and capabilities to improve care quality for therapy documentation at point of care? If yes, please describe how the system completes the functionalities. Desired

4.5. Does the system add EHR functionalities and capabilities to improve care quality for decision support at point of care? If yes, please describe how the system completes the functionalities. Desired

4.6. Does the system add EHR functionalities and capabilities to improve care quality for integration with devices including point of care vital sign devices, telehealth and remote monitoring, medication dispensers, activity monitoring, etc. (if applicable)? If yes, please describe how the system completes the functionalities. Desired

5. External Ancillary Services Integration – Section 5 For each integration question, please specify supported standards (HL7 v2.x, FHIR R4, NCPDP, DICOM), interface modalities (REST APIs, secure file exchange), and message/error handling capabilities.

5.1. Describe how the system completes basic EHR integration functionalities for pharmacy integration. Required for this Contract

5.2. Does the system complete basic EHR integration functionalities for electronic referral and discharge systems of hospitals or other care providers? If yes, please describe how the system completes the functionalities. Desired

5.3. Does the system complete basic EHR integration functionalities for lab integration? If yes, please describe how the system completes the functionalities. Desired

5.4. Does the system complete basic EHR integration functionalities for diagnostics integration? If yes, please describe how the system completes the functionalities. Desired

5.5. Does the system complete basic EHR integration functionalities for radiology integration? If yes, please describe how the system completes the functionalities. Desired

5.6. Does the system complete basic EHR integration functionalities for eligibility/coverage checking (for systems with integrated billing/financials)? If yes, please describe how the system completes the functionalities. Desired

5.7. Does the system complete basic EHR integration functionalities for formula checking? If yes, please describe how the system completes the functionalities. Desired

6. Engagement & Basic Information Exchange – Section 6

6.1. Describe how the system completes engagement and basic information exchange functionalities for physician portal and eSignature. Required for this Contract

6.2. Describe how the system completes engagement and basic information exchange functionalities for prescribing and computerized physician order entry. Required for this Contract

6.3. Describe how the system completes engagement and basic information exchange functionalities for sending and/or receiving clinical care documents, summaries, SBAR, care plans, and other information electronically as in human and machine-readable format (txt, pdf)(e.g. ONC Project Direct, eHealth Data Solution’s CareWatch Connect, etc.) directly to/from other providers. Required for this Contract

6.4. Does the system complete engagement and basic information exchange functionalities for patient/resident portal or export data to personal health records? If yes, please describe how the system completes the functionalities. Desired

6.5. Does the system complete engagement and basic information exchange functionalities for family/caregiver portal or integration with such tools? If yes, please describe how the system completes the functionalities. Desired

6.6. Does the system complete engagement and basic information exchange functionalities for care planning portal or integration with such tools? If yes, please describe how the system completes the functionalities. Desired

6.7. Does the system complete engagement and basic information exchange functionalities for care navigator/care coordinator portal or integration with such tools? If yes, please describe how the system completes the functionalities. Desired

6.8. Does the system complete engagement and basic information exchange functionalities for secure messaging between care team members? If yes, please describe how the system completes the functionalities. Desired

6.9. Does the system complete engagement and basic information exchange functionalities for public health reporting? If yes, please describe how the system completes the functionalities. Desired

7. Interoperability and Health Information Exchange – Section 7

7.1. Describe how the system completes interoperability and health information exchange functionalities for sending/receiving information to/from other EMRs/EHRs (including physician and/or hospital EHRs) electronically through an HIE or exchange entity in a standards-based consumable data format (e.g. XML, HL7, FIHR). Required for this Contract

7.2. Does the system complete interoperability and health information exchange functionalities for sending/receiving information to/from EMRs/EHRs repository in a standards-based consumable data format (e.g. XML, HL7, FIHR)? If yes, please describe how the system completes the functionalities. Desired

7.3. Does the system complete interoperability and health information exchange functionalities for sending/receiving information to/from other EMRs/EHRs (including physician and/or hospital EHRs) electronically directly in a standards-based consumable data format (e.g. XML, HL7, FIHR)? If yes, please describe how the system completes the functionalities. Desired

7.4 Describe system security protocols, encryption standards, and audit logging. Required for this Contract

7.5 Describe how the system meets and maintains HIPAA compliance. Required for this Contract

7.6 Describe how the system meets and maintains MFA enforcement. Required for this Contract

7.7 Describe system breach notification timelines. Required for this Contract

7.8 Describe how third-party compliance certifications are maintained. Required for this Contract

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