Recruitment Marketing Services

03 April 2024 Patient Advance Care Planning MD Anderson Cancer Center is soliciting bids to implement a comprehensive ACP technology solution and successful integration with Epic, including MyChart®, within an academic health care facility. 03 April 2024 Released 3/22/2024 6:00 PM CDT Type Request for Proposal Open 3/22/2024 6:01 PM CDT Number AIS-CK-01446-RFP Close 4/22/2024 4:00 PM CDT Currency US Dollar 03 April 2024 Contacts Robert Tesoro RPTesoro@mdanderson.org Phone +1 713-792-6847 03 April 2024 Commodity Codes Commodity Code Description 43230000 Software 03 April 202403 April 202403 April 202403 April 202403 April 202403 April 202403 April 202403 April 2024 mailto:RPTesoro@mdanderson.org Scope of Work MD Anderson Cancer Center is soliciting bids to implement a comprehensive Advance Care Planning (ACP) technology solution and successful integration with Epic,

including MyChart®, within an academic health care facility. The purpose of this solicitation is to obtain product information and proposal pricing for a solution that meets the GCC Initiative’s business needs and technical requirements. The resulting contract from this solicitation shall include all costs for implementing the solution, as well as training, technical support, patient support in using the platform and completing documents, change enablement, and ongoing maintenance. The proposer should provide an intuitive application that enhances the MD Anderson Cancer Center experience for patients and their families when it comes to advance care planning. The application should be able to support the completion of advance directive related documents; document uploading; document storage; video display; educational functions; and decision-making aids. The solution must meet MD Anderson Cancer Center’s Information Services and Cybersecurity requirements. In addition to the above, the software solution will provide a mechanism through which patients’ personal goals and priorities are able to be captured and displayed within Epic for care team members to view within their workflows. Pre-submittal Conference A VIRTUAL Pre-Submittal Conference will be held on April 1, 2024 at 8:00AM (CST). Attendance at this meeting is highly recommended, but not required. An RSVP is not required to attend. Conference Call Information Link to Join: Join Zoom Meeting URL: https://mdacc.zoom.us/j/88652586862? Join by Telephone: US: +1 346 248 7799 or +1 253 215 8782 or +1 669 900 6833 or +1 929 205 6099 or +1 301 715 8592 or +1 312 626 6799 or 877 853 5257 (Toll Free) or 888 475 4499 (Toll Free) Meeting ID: 886 5258 6862 Password: 663262 Description https://mdacc.zoom.us/j/88652586862?pwd=eFJOZzhTalFhWC8rRytaR1RmSEh3Zz09 Required to View Event Prerequisites Required to Enter Bid There are no Prerequisites added to this event. 03 April 202403 April 202403 April 202403 April 202403 April 202403 April 202403 April 2024 Buyer Attachments There are no Buyer Attachments added to this event. 03 April 202403 April 202403 April 202403 April 202403 April 202403 April 2024 Questions Required Questions Group 1.1: About MD Anderson Instructions: 1.1.1 To read more "About MD Anderson" please visit the following link: https://www.mdanderson.org/about-md-anderson.html Group 1.2: Facts and History Instructions: 1.2.1 To read about MD Anderson's "Facts and History" please visit the following link: https://www.mdanderson.org/about-md-anderson/facts-history.html Group 1.3: Request for Proposal (RFP) Instructions: 1.3.1 MD Anderson is soliciting Proposals ("Proposals") for the selection of a Supplier(s) for the RFP in accordance with the terms, conditions, and requirements set forth. This RFP provides the information necessary to prepare and submit a Proposal for consideration and ranking by MD Anderson and under the Texas Education Code. 1.3.2 As you navigate the RFP, please ensure that you continue to SAVE all answers by clicking the "Save Progress" button as you navigate through the event. Group 2.1: Addendums Instructions: 2.1.1 This page contains all new information about the RFP after the published date. If there are any changes to the RFP, it will be documented in this section (Addendum). If you receive an e-mail, or an online notification, with the subject "The Sourcing Event is Amended", please visit this page/section for any changes to the event. 2.1.2 Information presented at the Pre-submittal Conference presentation will be posted in this section after the meeting. 2.1.3 The Pre-submittal Conference presentation, HUB Tip Sheet, and Attendee List are attached. Please acknowledge receipt of these documents. Group 3.1: Scope of Work Instructions: 3.1.1 1) Please download and review the attached Scope of Work (SOW). 2) After reviewing the SOW, please acknowledge that it has been read. Group 4.1: Responding to RFP Questions Instructions: 4.1.1 All RFP questions must be answered thoroughly and individually. Please do not reference another response that has been addressed in a previous or subsequent question. To clarify, do not respond to any question with "See question No. ###." Do not attempt to upload a file that has been used previously unless the file is specifically applicable to the individual question. If multiple files will be uploaded as a response, please Zip the files into a single Zip folder. Failure to adhere by these rules may disqualify your response(s). Group 4.2: Disclosure of Interested Parties Mandated by House Bill 1295 Instructions: 4.2.1 MD Anderson must comply with the Disclosure of Interested Parties mandated by House Bill 1295 and as implemented by the Texas Ethics Commission. Before MD Anderson may execute a contract exceeding $1M, the Supplier(s) with which MD Anderson is contracting must submit a completed Form 1295 before or concurrent with Supplier submission of the signed contract to MD Anderson. For more information, please use the following link: https://www.ethics.state.tx.us/filinginfo/1295/ Group 4.3: Disclosure of Interested Parties Mandated Senate Bill 475 Instructions: 4.3.1 Please read and review the attached Disclosure of Interested Parties Mandated Senate Bill 475. Upon completion please acknowledge. Group 4.4: Public Information Act (PIA) Instructions: 03 April 202403 April 202403 April 202403 April 202403 April 2024 4.4.1 All information, documentation, and other material submitted in response to this RFP solicitation is considered non-confidential and/or non-proprietary and is subject to public disclosure under the Texas Public Information Act (Texas Government Code, Chapter 552.001, et seq.) after the agreement is executed. MD Anderson strictly complies with all statutes, court decisions, and opinions of the Texas Attorney General with respect to disclosure of RFP information. Group 4.5: Best Value Instructions: 4.5.1 MD Anderson may select the Proposal(s) that offers the "Best Value" for the institution based on the published selection criteria, its evaluation ranking, and the terms of Texas Government Code 2155.074. MD Anderson may first attempt to negotiate a contract with the selected Supplier(s). MD Anderson may also discuss with the selected Supplier(s) options for a scope or time and price change modification. If MD Anderson and/or its governing Board(s) are unable to reach a contract with the selected Supplier(s) in a timely manner, MD Anderson may formally end negotiations with that Supplier(s) and proceed to the next "Best Value" Supplier(s) in order of the selection ranking until a contract is reached or all Proposals are rejected. Group 4.6: Historically Underutilized Business Submittal Requirements Instructions: 4.6.1 It is the policy of The University of Texas System, and each of it component institutions, to promote and encourage contracting and subcontracting opportunities for Historically Underutilized Businesses (HUB) in all contracts. Accordingly, MD Anderson has adopted the Rider 104-HUB Subcontracting Plan, Policy on Utilization of Historically Underutilized Businesses. This Policy applies to all contracts with an expected (cumulative) value of $100,000 or more. If MD Anderson determines that subcontracting opportunities are probable, then a HUB Subcontracting Plan is a required element of the Proposal. Failure to submit a required HUB Subcontracting Plan will result in rejection of the Proposal. Group 4.7: HUB Statement of Probability Instructions: 4.7.1 MD Anderson has determined that subcontracting opportunities are probable in connection with this procurement solicitation; therefore, a HUB Subcontracting Plan (HSP) is required as part of your Proposal. Each RFP Respondent shall develop and administer an HUB Subcontracting Plan as part of the Proposal in accordance with MD Anderson's Policy on Utilization of Historically Underutilized Businesses (HUB) and Rider 104-HUB Subcontracting Plan. Group 4.8: Type of Contract Instructions: 4.8.1 Any contract resulting from this solicitation will be governed by MD Anderson's Standard Terms and Conditions referenced in the Summary Agreement attached to this RFP. The work associated with this RFP will be awarded as a contract to the Supplier(s) offering the "Best Value" to MD Anderson. Group 4.9: Selection Criteria Instructions: 4.9.1 The successful Supplier(s) selected by MD Anderson, in accordance with the requirements and specifications set forth in this RFP, will be the Supplier(s) which is most advantageous to MD Anderson. MD Anderson's committee members, comprised of key personnel as well as Supply Chain professionals, will evaluate and score approved Proposals. Group 4.10: MD Anderson's Reservation of Rights Instructions: 4.10.1 MD Anderson may evaluate the Proposals based on the anticipated completion of all or any portion of the RFP. MD Anderson reserves the right to divide the RFP into multiple parts, to reject any and all Proposals and re-solicit for new Proposals, or to reject any and all Proposals and temporarily or permanently abandon the RFP. MD Anderson makes no representations, written or oral, that will enter into any form of agreement with Supplier(s) for this RFP. No such representation is intended or should be construed by the issuance of this RFP. Group 4.11: Obligation Instructions: 03 April 202403 April 202403 April 202403 April 202403 April 2024 4.11.1 Neither the transmission of this RFP to a prospective Supplier(s), nor the acceptance of a reply, implies any obligation or commitment by MD Anderson to enter into any contract or undertake any financial obligations with respect to this RFP. After evaluation of all Proposals, MD Anderson intends to conduct negotiations with the Supplier(s) considered best qualified and "Best Valued" to meet its requirements. MD Anderson reserves the right to reject any or all proposals whenever such actions are in its best interest. Group 4.12: No Reimbursement for Costs Instructions: 4.12.1 Supplier(s) acknowledges and accepts that any cost incurred from the Supplier(s) participation in this RFP process shall be at the sole risk and responsibility of the Supplier(s). Supplier(s) submit Proposals at their own risk and expense. Group 4.13: Clarification and Interpretation Instructions: 4.13.1 Any clarifications or interpretations of this RFP that materially affect or change its requirements will be issued by MD Anderson as an Addendum. It is the responsibility of all Supplier(s) to obtain this information in a timely manner. All such Addenda will be due prior to the RFP Close Date. Addenda may be issued by the RFP Point-of-Contact via the SciQuest Sourcing Director Q&A Board or in the Addendum section of this RFP. All communication specific to this RFP shall be exchanged within the SciQuest tool. Group 4.14: Certain Proposals and Contracts Prohibited Instructions: 4.14.1 Under Section 2155.004, Texas Government Code, a state agency may not accept a Proposal or award a contract that includes proposed financial participation by a person with received compensation from the agency to participate in preparing the specifications or request for Proposal on which the Proposal or contract is based. All Supplier(s) must certify their eligibility by acknowledging the following statement: "Under Section 2155.004, Government Code, Supplier(s) certifies that the individual or business entity named in this RFP or contract is not ineligible to receive the specified contract and acknowledges that this contract may be terminated and payment withheld if this certification is inaccurate. Group 4.15: Certain Proposals and Contracts Prohibited (cont...) Instructions: 4.15.1 If a state agency determines that an individual or business entity holding a state contract was ineligible to have the contract, yet accepted the award as described above, the state agency may immediately terminate the contract without further obligation to the Supplier(s). This does not create a cause of action to contest a Proposal or award of a state contract. Group 4.16: Acceptance or Rejection of Proposal Instructions: 4.16.1 This RFP is not an offer to contract. Acceptance of a Proposal neither commits MD Anderson to award a contract to any RFP Respondent, nor limits MD Anderson's rights to negotiate terms in its best interest. MD Anderson reserves the right to accept or reject any or all Proposals in part or whole. MD Anderson reserves the right to request clarification on responses, omissions, or claims made in the RFP. MD Anderson further reserves the right to request modification to a Supplier(s) Proposal in order to provide the optimum solution for strategic team planning. Respondents submitting a Proposal do so with the understanding that MD Anderson reserves the right to select one or more "Supplier(s) of choice" based solely on their RFP response or to evaluate one or more Supplier(s) via additional interviews, site visits, reference checks, and other evaluations. MD Anderson will notify Suppliers of the results when final decisions have been made. Group 4.17: Electronic Information and Technology (EIT) Instructions: 03 April 202403 April 202403 April 202403 April 202403 April 2024 4.17.1 Any acquisition considered EIT as defined by Section 508 (36 CFR Part 1194) requires the submission of a completed Voluntary Accessible Product Template so that can MD Anderson can ascertain conformance with the applicable EIT standards developed by the U.S. Access Board. MD Anderson reserves the right to perform real-world testing of a Supplier's product or service in order to validate claim regarding Section 508 conformance. In order to facilitate this testing, Supplier(s) shall, upon request, provide MD Anderson a copy of the product being considered for purchase for a period of at least 30 calendar days. The version of the product being provided for testing purposes must be equivalent in functionality and features to the commercial version that is under consideration for purchase. MD Anderson, at its sole discretion, will determine the level of conformance with Section 508 on all products being reviewed. Group 4.18: Submission of Proposals Instructions: 4.18.1 MD Anderson is to receive all Supplier(s) Proposals by the RFP close date communicated within the SciQuest Sourcing Director tool. Proposals not received within the specified time frame, and prior to the RFP close date and time, will not be accepted. Supplier(s) are urged not to wait until the last minute to submit their final Proposal. Proposals and final HUB Plans submitted via telephone, fax, or electronic mail (email) will be rejected. Only those submitted via this tool will be accepted. Respondents must provide a response to all "REQUIRED" questions or the system will not accept the submission. Group 4.19: Group Purchasing Instructions: 4.19.1 MD Anderson is an institution of System which consists of nine academic and six health institutions. Texas law authorizes institutions of higher education (defined by Section 61.003, Education Code) to use the group purchasing procurement method (ref. Sections 51.9335, 73.115 and 74.008, Education Code). With this, if an Agreement results from this competitive procurement method, the RFP Respondent acknowledges that additional Texas institutions of higher education may procure from the RFP Respondent and/or Contractor the goods and services set forth in this RFP/Agreement on the same terms and conditions attached herein by entering into a separate contract with RFP Respondent/Contractor, or by concluding an appropriate addendum to the Agreement. Group 4.20: Group Purchasing (cont...) Instructions: 4.20.1 It is understood that: (I) Unless specifically stated otherwise, any volume of goods or services stated in the final Agreement reflects only goods and/or services to be purchased by MD Anderson and does not include potential purchases by other System institutions, and (II) Each System institution is a financially separate entity and will be solely responsible for its own commitments to Contractor. Group 4.21: Point-of-Contact Instructions: 4.21.1 MD Anderson designates the following person as its representative and Point-of-Contact for this RFP. Respondents shall restrict all contact with MD Anderson personnel, specific to this RFP, and direct all questions regarding this RFP, including questions regarding terms and conditions, to the Point-of-Contact: Robert Tesoro, Sourcing Specialist rptesoro@mdanderson.org Note: All communication exchanges should be performed via MD Anderson Sourcing Director tool within the Q&A area. Group 5.1: Pre-Submittal Conference Instructions: 03 April 202403 April 202403 April 202403 April 202403 April 2024 5.1.1 A Pre-Submittal Conference will be held at the following time, date and location below. Attendance at the pre-submittal conference is OPTIONAL and does not require an RSVP. April 1, 2024 at 8:00 AM (CST) Conference Call Information URL: https://mdacc.zoom.us/j/88652586862? Join by Telephone: US: +1 346 248 7799 or +1 253 215 8782 or +1 669 900 6833 or +1 929 205 6099 or +1 301 715 8592 or +1 312 626 6799 or 877 853 5257 (Toll Free) or 888 475 4499 (Toll Free) Meeting ID: 886 5258 6862 Password: 663262 Group 5.2: Critical Dates Instructions: 5.2.1 RFP Published Date: March 22, 2024 Pre-submittal Conference date: April 1, 2024 Supplier Questions Submission End date: April 5, 2024 at 4:00 PM (CST) Supplier Questions & Answer Published date: April 12, 2024 by EOB RFP Close Date: April 22, 2024 Short-List Presentations and/or Demonstrations Dates: June 10 to June 17, 2024 Group 6.1: Riders & Agreements Instructions: 6.1.1 Please read and review the attached Summary Agreement. Upon completion, please acknowledge. 6.1.2 Should your organization take any exceptions to the Summary Agreement, please provide them in the attached Word document in a red-lined format. Upon red-line completion, upload the document back into the tool in an EDITABLE Word format. Should your organization NOT have any exceptions, please upload a CLEAN file confirming no exceptions were taken. 6.1.3 Please read and review the attached Rider 107-Travel Policy. Upon completion, please acknowledge. 6.1.4 Should your organization take any exceptions to the Rider 107-Travel Policy, please provide them in the attached Word document in a red-lined format. Upon red-line completion, upload the document back into the tool in an EDITABLE Word format. Should your organization NOT have any exceptions, upload a CLEAN file confirming no exceptions were taken. 6.1.5 Please read and review the attached Rider 111-Business Associate Agreement. Upon completion, please acknowledge. 6.1.6 Should your organization take any exceptions to the Rider 111-Business Associate Agreement, please provide them in the attached Word document in a red-lined format. Upon red-line completion, upload the document back into the tool in an EDITABLE Word format. Should your organization NOT have any exceptions, upload a CLEAN file confirming no exceptions were taken. 6.1.7 Please read and review the attached Rider 114 Network Connections. Upon completion, please acknowledge. 6.1.8 Should your organization take any exceptions to the Rider 114-Network Connections, please provide them in the attached Word document in a red-lined format. Upon red-line completion, upload the document back into the tool in an EDITABLE Word format. Should your organization NOT have any exceptions, upload a CLEAN file confirming no exceptions were taken. 03 April 202403 April 202403 April 202403 April 202403 April 2024 6.1.9 Please read and review the attached Rider 114-Supply Chain User Acknowledgement. Upon completion, please acknowledge. 6.1.10 Should your organization take any exceptions to the Rider 114-Supply Chain User Acknowledgement, please provide them in the attached Word document in a red-lined format. Upon red-line completion, upload the document back into the tool in an EDITABLE Word format. Should your organization NOT have any exceptions, upload a CLEAN file confirming no exceptions were taken. 6.1.11 Please read and review the attached Rider 116-Invoice Payment Requirements. Upon completion, please acknowledge. 6.1.12 Should your organization take any exceptions to the Rider 116-Invoice Payment Requirements, please provide them in the attached Word document in a red-lined format. Upon red-line completion, upload the document back into the tool in an EDITABLE Word format. Should your organization NOT have any exceptions, upload a CLEAN file confirming no exceptions were taken. Group 6.2: Additional Riders Instructions: 6.2.1 Please download the attached Rider 118-Information Security ASP Assessment Survey and follow the instructions within the document for completion. Upon completion, please upload the final document. Group 7.1: Supplier Rider Attestation Instructions: 7.1.1 Please acknowledge that you have read and understood the calculations associated with the Supplier Rider Attestation Form included in the attached example. 7.1.2 Please download, complete, and sign the Supplier Rider Attestation Form following the instructions provided. Upon completion, upload the executed form as your response. 7.1.3 Please acknowledge that you have properly completed the Supplier Rider Attestation Form. This includes: -Noting your acceptance/rejection to each applicable Rider. -Specifying the Section(s) rejected (if applicable). -Executing the document, including signature. -Ensure that the form DOES NOT reference any previously negotiated terms, conditions, or agreement. Failure to complete and return this form may result in the prospective Supplier's response being disqualified. 7.1.4 Proposed exceptions to MDACC Contract Riders must be noted in the applicable section of the Riders & Agreements portion of the RFP via redlines, and acceptance (or rejection) to those Riders must be documented on the Attestation form accordingly. Any inconsistencies between the proposed exceptions and the information submitted on the Attestation form WILL result in a rejection of the Attestation, and the Attestation WILL be scored as zero points. The RFP Attestation form MUST be signed by an Authorized Representation of the Prospective Supplier. Failure to submit a signed Attestation WILL result in rejection of the Attestation and the Attestation WILL be scored as zero points. Group 8.1: Rider 104 HUB Subcontracting Plan Instructions: 8.1.1 Please download the attached Rider 104-Historically Underutilized Business (HUB) Plan and follow the instructions within the document for completion. Upon MD Anderson's draft review and your formal completion, please upload the final and executed document. 8.1.2 Please acknowledge that you have read/reviewed the HUB tip sheet for information regarding successful HUB plan submissions. 03 April 202403 April 202403 April 202403 April 202403 April 2024 Group 9.1: Contact Information Instructions: 9.1.1 Please provide the contact information, including name, email, phone number and mailing address, of the person that is able to respond to and/or accept any RFP related communication should the occasion arise. Group 9.2: General Functionality, Services & Deliverables Instructions: 9.2.1 Do you currently have this solution successfully installed at any large hospital systems or academic medical centers? If so, please provide a comprehensive list. 9.2.2 Do you have an existing relationship with any component of the UT System? If yes, please specify. 9.2.3 Provide at least three (3) references from large hospital systems or academic medical centers within which your solution is implemented. 9.2.4 Does your platform offer role-based access that can be defined and managed by MD Anderson? Please explain. 9.2.5 Does your solution provide the ability for institutional branding for a seamless patient experience? 9.2.6 Does your solution provide prebuilt dashboards and reports? If so, please describe (e.g. self-service vs. vendor development) 9.2.7 Can reports be scheduled to be sent to users via email on a scheduled or ad-hoc basis? 9.2.8 Can reports be set up to be seen across all departments where the system is being used? 9.2.9 Can users create custom reports? If so, please describe (e.g. self-service vs. vendor development) 9.2.10 Describe your reporting capabilities including the employee experience when creating and executing adhoc requests. Include any integrations with other Reporting tools. (ie PowerBI, Tableau, etc.) 9.2.11 Does the system allow for multiple users to be logged in at the same time for the same section and/or the same patient? If so, please describe limitations and safeguards regarding this feature 9.2.12 Does the system still work if the EHR is down? Please explain any alternate method of access. 9.2.13 Does the system still work if the interfaces are down? Please describe any technical ability to share that status with users in the integrated EHR. 9.2.14 Describe the functionality of the mobile platform to include transactions available on mobile devices. Group 9.3: IT & Cybersecurity Instructions: 9.3.1 Does your platform operate in a cloud environment? 9.3.2 Can you provide details on any certification or compliance standards your cloud platform adheres to? 9.3.3 Please provide any system architecture and information security documentation you have. 9.3.4 Do you have a web & mobile version of the product? 9.3.5 If the site is just web, is it mobile responsive? 9.3.6 Describe the system requirements to run the application and provide software/hardware compatibility matrix. 9.3.7 Do you provide all the software required to fully implement your solution across MD Anderson owned hardware and any hardware you might provide? If no, explain. 9.3.8 Are software installs needed on prem? If yes, explain. 9.3.9 Is hardware needed on prem to support the product? If yes, explain. 9.3.10 If the product is cloud based, which vendor (i.e. - Oracle OCI, AWS, Azure, other) is supporting the infrastructure? (Note: MD Anderson's IT Engineering area may require system specs to review.) 9.3.11 If the product is cloud based, explain the following: How frequently do you update products? How are they rolled out to MDA? Can MD Anderson selectively apply patches? 03 April 202403 April 202403 April 202403 April 202403 April 2024 9.3.12 With respect to data storage, explain the following: What data is stored on premise? What data do you store? Where is the data stored? 9.3.13 What sensitive information, PHI or otherwise, is stored in your system? 9.3.14 Is the product HIPAA compliant? 9.3.15 Explain any 3rd party analytics that are built into or integrated with your platform. 9.3.16 Does your solution have any system monitoring tools and what kind of error logs do you collect? 9.3.17 Do you provide ongoing maintainence to the hardware and software you may provide, both routine and as failures dictate? 9.3.18 Do you provide same-day support as requested by MD Anderson for any issues arising in the hardware or software you may provide? 9.3.19 Do you provide 24-hour contact centers able to field support calls? 9.3.20 Please provide SLAs for post production issues. 9.3.21 Please provide documentation to describe a typical implementation plan/methodology - include references to project deliverables (i.e. - project plan/schedule, functional-technical design, interface data mapping, test plan/Automation, configuration mgt, security matrix, process flow, change management, go-live deployment checklist, etc.) 9.3.22 Are you and any potential production partners able to attend all necessary design and implementation sessions? 9.3.23 Please provide documentation to describe typical implementation plan. 9.3.24 Do you outsource any support processes or hardware to another company? 9.3.25 Do you provide 24x7 support? 9.3.26 Please describe the release cycle management for updates to the application (monthly or quarterly) related to the software enhancements and infrastructure stability. 9.3.27 Do you host a website for customers to access to see if there are reported platform issues being experienced? 9.3.28 Does the platform use a HIE to ingest or send data to/from other healthcare organizations? Please explain. Group 9.4: Inpatient/Ambulatory/Clinical Support Patient Care Areas Instructions: 9.4.1 Does your solution recommend specific advance directive documents to be completed based on what's currently stored in the EHR or related document management systems? 9.4.2 How does a care team member assign advance directive documents to patients? 9.4.3 How does the care team have visibility into whether or not assigned documents have been completed? 9.4.4 How does the care team view complete advance care documents? 9.4.5 Have you successfully interfaced information entered in your platform into Epic clinical workflows? If so, please describe the specific workflow and how it was accomplished. 9.4.6 To what extent is this information visible within Epic? Please describe common workflows or data fields most commonly seen interfaced. 9.4.7 Can free text notes entered by the patient or caregiver be populated into a note in Epic? Please describe. 9.4.8 Please provide a list of prompts/questions available to patients and/or caregivers to document their stated goals. 9.4.9 Are these prompts/questions able to be configured by organization? 9.4.10 Does the solution have the capability of triggering referrals or other actions based on individual responses to advance directive questions? If so, describe. 9.4.11 Explain how your system alerts for any follow up action that may be needed for incomplete advance directive documents. 9.4.12 Does the platform have the capability of reporting which education materials have been accessed and completed by patients? 9.4.13 Does the platform have the capability of reporting how often on demand services are engaged? 9.4.14 Does the platform have the capability of reporting how often advance directives are assigned to patients to complete and by whom? 9.4.15 Does the platform have the capability of reporting document average time to completion and other similar metrics? If so, describe. 03 April 202403 April 202403 April 202403 April 202403 April 2024 9.4.16 What reporting templates are available "out of box" to end users? 9.4.17 Are organizational endusers able to customize any "out of box" reports? Describe if this can be independently performed or dependent upon the vendor to execute. 9.4.18 Are organizational endusers able to build their own reports using your platform? 9.4.19 Describe any other reporting capabilities of the system. Group 9.5: Patient-Facing Software, Services, and Support Instructions: 9.5.1 Explain how patients may access your platform to review advance directive related documents and/or education. 9.5.2 Is the platform available in multiple languages? If yes, please attach list of available languages. 9.5.3 If multiple languages are available, please describe what feature sets are translated (e.g. navigation, education materials, videos, advance directive documents, etc.). 9.5.4 Does the platform have the capability to send notifications to patients when a new document is loaded for review? If so, please describe modalities (e.g. email, text, push notification, etc.). 9.5.5 Explain how advance directive documents are made available to patients on the platform. 9.5.6 Does the platform have the capability of showing progress markers/status towards document completion? If yes, please explain. 9.5.7 Does the platform have the capability of showing progress markers/status for education completion? If yes, please explain. 9.5.8 Can the platform send reminders to the patient when assigned documents are not completed within a specified timeframe? If yes, please explain. 9.5.9 Is platform able to send reminder notifications to patients to review previously entered goals and wishes? Please explain the level of configuration in which organizations are able to set this threshold, including if this is a vendor dependent change or self-initiated by MD Anderson Cancer Center. 9.5.10 Describe any virtual assistant tools available to patients while interacting with your platform. 9.5.11 Is a manned on-demand support center available to patients for assistance when needed? If yes, please describe the type of services provided. Include details such as hours of operation, audio (call) vs video options to patients, etc. 9.5.12 If a manned on demand support center is available, are any support services made available to patients at a cost? If so, please explain 9.5.13 If a manned on-demand support center is available, are there multi-lingual agents? If yes, please provide a list languages and/or related translation services available to patients. 9.5.14 If a manned on-demand support center is available, describe how vendor agents communicate with MD Anderson Cancer Center personnel as needed or at patient's request. 9.5.15 If a manned on-demand support center is available, describe escalation processes in place to manage high-risk or potential risk situations (e.g. self-harm). 9.5.16 Does the platform support proxy access? If yes, please explain. 9.5.17 If proxy logon is not used, does the platform have a way to notate that someone other than the patient is completing the document(s)? 9.5.18 Has the platform ever been integrated with MyChart®? If yes, please explain. 9.5.19 Does the platform offer advance directive education topics? If so, please detail the catalog of topics available and media platform (e.g. video, written material, etc.). 9.5.20 Is the platform capable of uploading custom education content (written and video)? If yes, please explain how this is made possible. 9.5.21 Does the platform develop its own education content? If yes, please provide the titles of available content. 9.5.22 Does the platform use a third-party vendor for it education content? If yes, please provide the name of the vendor and available content vendors. 9.5.23 Can patients document personal goals and wished related to advance care planning within the platform? 9.5.24 If goals/wishes documentation is available, please describe how this is completed (e.g. prepopulated options, themes, free-text, etc.). 9.5.25 Describe what multi-factor authentication options are available to patients using your solution. 03 April 202403 April 202403 April 202403 April 202403 April 2024 9.5.26 Is a patient able to assign a Health Agent using your solution? 9.5.27 Is a patient able to revoke a Health Agent using your solution? 9.5.28 Is a patient able to revoke a notarized advance care document in the system? 9.5.29 What safeguards are in place to differentiate patient vs caregiver roles and entries? 9.5.30 Does your solution support patient video statement of goals and wishes that can be uploaded into the platform? 9.5.31 Does your solution support a voice-to-text for patients to use in place of manual keyboard entry of data? Group 9.6: System Integrations Instructions: 9.6.1 Has your solution successfully integrated with Epic, i.e., EpicCare Ambulatory, EpicCare Inpatient, and MyChart®, in a large academic institution? If so, elaborate and include at least 3 implementations where bi-directional data, i.e., receive patient feed and send data back to Epic, is live. 9.6.2 Has your solution successfully integrated with the following systems (OnBase) in an institution? Please elaborate and include at least 3 implementations where any of these systems are integrated with Epic and live in production. 9.6.3 Do you employ dedicated supporting product engineer(s) to work with us on future integrations as needed? If so, please describe title, role, and responsibility of this individual. 9.6.4 Do you offer any integrations with other external systems? If yes, list the integrations available. 9.6.5 Do you provide comprehensive documentation, including API documentation and system architecture details for the integration? If so, please describe. 9.6.6 Explain the storage capacity of the above storage solution. Please include any tiers, server, or related considerations. 9.6.7 Describe your 3rd party systems integration technology/capability (i.e., file-based, web services/API). 9.6.8 What types of encryption methods are implemented to secure the messages? Group 9.7: User Training and Support Instructions: 9.7.1 Do you provide onsite training at implementation? Please describe. 9.7.2 Provide an example training plan for new users that spans multiple roles (RN/MD/Social Work/Patient Education). Please limit response to 1 page. 9.7.3 Do you provide ongoing training on an as needed basis per MD Anderson request? If so, please describe. 9.7.4 Do you provide web-based instructional videos? Please explain. 9.7.5 Explain what post implementation support, if any, you provide to end users, i.e., help desk, website chat support? 9.7.6 Describe the guided learning capabilities that are built into the User Interface for users to access while navigating. Group 9.8: Implementation Services Instructions: 9.8.1 Do you provide project management services? 9.8.2 Describe any change enablement services you provide to facilitate adoption (incl. customer success services). 9.8.3 Describe any change enablement services you provide to assist with workflow or process redesign. 9.8.4 Describe your implementation methodology and approach. 9.8.5 Describe what the implementation tasks and timeline would look like for MD Anderson. 9.8.6 Describe any post-implementation support or services you provide. Group 10.1: Rider 102 - Fee Schedule Instructions: 10.1.1 Please download the attached Rider 102- Fee Schedule and follow the instructions within the document for completion. Upon completion, please upload the final document. Group 11.1: Value Add 03 April 202403 April 202403 April 202403 April 202403 April 2024 Instructions: 11.1.1 Please use this section to upload any “Value-Added” material(s) related to your organization. To upload multiple files, please zip your files into one single .zip file. 03 April 202403 April 202403 April 202403 April 202403 April 2024 Product Line Items Product Line Items There are no Items added to this event. 03 April 202403 April 202403 April 202403 April 2024 Service Line Items Service Line Items There are no Items added to this event. 03 April 202403 April 202403 April 2024