2021075-RFP - Electronic Medical Records (EMR) Solution

Invitation to Proponents

1. A brief description of the proponent and proposed team members including, but not limited to, project manager and technical lead
2. A description of its knowledge, skills, and experience relevant to the deliverables
3. A description of their experience implementing and supporting the EMR solution in at least 3 projects of similar scope undertaken in the previous 5 years

1. Describe all non-production and production environments that will be available to the University. Including configuration management between each environment.
   1. Provide an Implementation Plan that lists the key milestones of how the proposed solution is to be implemented. The Implementation Plan should include the following elements presented in this order: General implementation approach (strategy, methodology, etc.)
   2. Timeline for implementation - from start-to-finish that accommodates a final deployment Go-Live date of April 1st, 2022.
   3. Set up and configuration of solution
   4. SSO and OMD integrations
   5. User interface configuration
   6. Testing (Functional, Integrated, Performance, and Security)
   7. User Training
   8. Provision of solution documentation and manuals
   9. Resources and support plan to accompany the users during the immediate post Go-Live warranty phase
2. Describe the level of training support for various roles
3. Describe the process and any tools (including issue trackers) for reporting issues and bugs and user configuration requests
4. Provide any relevant technical and end-user manuals and documentation
5. Describe the architecture of the solution and include any relevant diagrams (component, logical, data flow, etc.

1. Provide a service level description that includes: maintenance, help-desk/single-access point to the support services, incident management, problem management, escalation process, change management;
2. Describe ongoing training (user and system administrator training, user & configuration guides, etc.), implementation & configuration assistance, and product support / maintenance. Please indicate to what extent this is chargeable.
3. Describe how communications will be performed with the University (changes, incidents, updates, etc.) and its users, as well as what tools and methods will be used for official and unofficial communications.
4. Describe in detail your upgrade process, patch/bug fix process and the roadmap of releases for all aspects of the solution.
5. Provide a description of system performance, including performance metrics, concurrency limits, historical data and monitoring tools and reports.
6. Provide a description of the shared responsibility model between the University and the proponent (must be clearly delineated). For this, describe more specifically what are the responsibilities of each party with regards to different aspects of the solution (such as application-level controls, identity and access management, etc.), and with regards to support.
7. Please indicate if a user community is available. When available, please describe the topics (particularly discussions on innovations) and how easily information is found. (
8. Provide a clear model defining cost control parameters (usage-based and overages included).
9. Describe any limitations pertaining to the solution, including, but not limited to the following: number of users, space quotas, file upload limits, file type restrictions, bandwidth limitations, access limitations, SMS messaging quota (i.e. maximum number of texts to patients).

1. A high-level of performance, high availability and uptime, with less than 0.01% of unplanned downtime per year.
2. Describe the frequency and how backups are performed, as well as the disaster recovery strategy. How do you ensure the solution can be recovered?
3. Cloud infrastructure security and application security.
4. The ability to withstand cyberattacks such as distributed denial-of-service attacks (DDoS attacks).  
5. Describe how you ensure both the product and hosting data centre are ISO 27001 and/or SOC 2 compliant.
6. Describe how you perform regular vulnerability scans (internal/external) and penetration testing on the hosting infrastructure.
7. Describe how Client data is encrypted in transit (i.e. transmitted over a network) and encrypted at rest.
8. The product should offer a mobile version or is mobile friendly.  Please provide a clear roadmap for new features and enhanced functionality.

1. Describe how the product is able to import and integrate data from different EMR solutions
2. Describe how the product is able to access and integrate data from provincial databases (ex. OLIS) as per the requirements set out by OntarioMD.
3. Describe how your product uses any 3rd party  plug-ins or have exclusions?
4. Describe if your EMR solution includes “new connections” or integrations with 3rd party labs (e.g. Dynacare/LifeLabs).
5. Describe how the product supports invoking RESTful APIs that are secured using OAuth2 protocol.
6. Describe which APIs are delivered by the product that expose business logic and objects for external systems to consume.  

1. Describe how the product is an intuitive patient-management system that captures, organizes, and displays clinical and patient data in a user-friendly way.
2. Describe the product’s patient portal module and how it can accommodate patient and doctor scheduling.
3. Describe how the product is capable of presenting a bilingual (French/English) patient-facing user interface.
4. Describe how the product is able to integrate the interactions between different medical disciplines and specializations (ex. between physicians and psychologists) and facilitate patient flow.
5. Describe how the product provides improved recording of allergies.
6. Describe the product’s virtual care functionality (videoconferencing with patients), if included.
7. Please describe how your product functionalities and interfaces improve the student experience. How does your product improve the patient-doctor experience?
8. Describe how the product is able to accommodate patient billing. This includes OHIP and RAMQ invoicing, self-pay patients, and cash book.
1. The product should have the ability to print multiple prescriptions at once, reduce the possibility of fraud with watermarked prescriptions along with physician ability to select optional access to drug decisions and drug-interaction warnings.
10. Describe the product’s robust and comprehensive reporting features and analytics.
11. Describe how the product is able to house common medical forms as well handle the creation of forms by users
12. Describe how the product produces medical notes and templates for notes.
13. Describe how the product is capable of exporting data
14. Does your product provide any other value-added features not specifically requested in the RFP? If yes, please describe.