Vendor Details
Maple
- By
-
Maple Corporation
- Modality
- Secure Messaging , Video
- Status
-
Verified
- Verification Date
-
2021-March-04
- Product Version
-
Version du produit : Version 4.11.24 | 1678744015 | v87 et supérieur
- Verification standard version
-
2.0
Solution Provider Details
- Full Address
-
355 Adelaide Street West, Suite 100, Toronto, ON, M5V 1S2, CA
- Web Site URL
- https://www.getmaple.ca/
- Year Business Started
-
2015
Accessibility Information
- Published Accessibility Report
- VPAT/ACR
- Supported Features
- Avoids using colour alone to convey meaning (example: uses symbols to show out of range results, not just red-coloured text) , Font resizer , Keyboard accessibility , Screen reader support
Third Party Information
- Video Secondary Vendor
-
Twilio Inc.
Recommended Requirements
Vendors need to meet all mandatory requirements in the standard to become Verified. Recommended requirements are additional requirements that health service providers may find beneficial for their clinical practices. Below is a list of recommended requirements that this solution meets. Recommended requirements are based solely on vendor’s information provided to Ontario Health and not verified or validated by Ontario Health.
Maple
-
Solutions should allow clinicians to send and receive patient agreements and other educational materials relating to virtual services.
Stand-alone solutions should demonstrate seamless integration, which should include elements such as;
- Single sign-on with PoS login credentials
- Receiving patient context (identification) information from PoS systems
- Automatically sending clinical information to PoS patient records as discreet data
- Sending virtual visit notifications to the PoS
- Calendar information
Solutions should not automatically trigger claims submission for all completed virtual visits.
Solutions can assist clinicians to identify virtual visits that are eligible for claims (e.g., offering a “billable” vs “nonbillable” flag).
Virtual visit solutions will allow providers to send surveys to patients in order to:
- Administer certain types of clinical questionnaires prior to an encounter (e.g., relating to mental health, child development, post-operative care)
- Support quality improvement efforts and patient experience reporting (e.g., at the end of a virtual care encounter)
Solutions should integrate with provincial provider identity and access management services and Ontario Identity Access Management (ONEID) using latest standards (e.g., OAuth).
Once available, solutions should integrate with the provincial patient digital Identity Authentication and Authorization (IAA) services.
Future versions of the standard will provide further guidance.Solutions will support Canada’s official languages of English and French. Clinicians should be able to use (read, write, and edit) information in the chosen language.
The Solution Provider’s website can also be read in chosen language, including but not limited to training materials and release notes.Clinicians should authenticate using more than one piece of evidence to access the solution (2FA).
Examples:
- FOB + PIN
- Password + Security question
- Password + Authentication app
- Authenticator + SMS/Phone call
Solutions may allow clinicians to enable a waiting room. This allows clinicians to control when participant(s) join the synchronous video event. Solutions should enable a scheduled video visit to be integrated into the external calendaring systems of other clinicians (e.g., HIS, EMR, Outlook).
An audio visit may be an acceptable alternative if insufficient bandwidth is available to support a video visit.
Solutions should allow different audio and video sources to be used during an event. For example, the clinician could use a standard webcam and a hand-held exam camera in the same event.
This data could include:
- Negotiated media codecs
- Role of each participant (host, guest) in the event.
- Performance data such as packet loss, jitter.
A common issue that would require investigation is degraded video and audio during a video visit.
H.323 ID, E.164 or SIP URI.
Solutions will allow patients and caregivers to perform equipment (i.e., audio and/or video) and connectivity tests (i.e., Wi-Fi) and send reports to clinics prior to virtual visits.
Solutions will enable patients to import a scheduled event into their calendaring systems (e.g., Google calendar, iCal, Outlook, etc.). Solutions will enable patients to forward a scheduled event to caregivers to participate in the event.
Enables health care organizations and clinicians to launch a secure video visit.
Supported Interoperability Protocols:
H.323, SIP, WebRTC
Audio Protocols:
G.711(a/µ), G.719, G.722, G.722.1, G.722.1 Annex C, Siren7™, Siren14™, G.729, G.729A, G.729B, Opus, MPEG-4 AAC-LD, Speex, SILK, AAC-LC
Video Codecs:
H.261, H.263, H.263++, H.264 (Constrained Baseline Profile, Baseline Profile and High Profile), H.264 SVC (UCIF Profiles 0, 1)
VP8, VP9
Content Sharing:
H.239 (for H.323)
BFCP (for SIP)
VP8, VP9 (for WebRTC high framerate)
Firewall Traversal:
H323 – H.460.17, H.460.18, H.460.19
SIP/WebRTC: STUN, TURN, ICEClinician experience and efficiency can be improved by creating separate inboxes (groups) for administrative versus clinical messages.
Physicians participating in the provincial pilot identified this feature as important in order to confirm that medical advice has been received before a visit can be completed.
Area of Practice.
IP Address.
IP Address.
IP Address.
-
/content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/2-1-11, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/2-1-12, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/2-1-14, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/2-1-15, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/2-1-16, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/2-1-17, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/2-1-18, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/2-1-9, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/3-2-10, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/3-2-11, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/3-2-12, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/3-2-13, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/3-2-14, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/3-2-15, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/3-2-16, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/3-2-17, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/3-2-18, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/3-3-1, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/3-3-2, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/4-2-12, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/4-2-9, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/5-2-1, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/5-2-2, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/5-2-3, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/5-2-4, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/5-2-5, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/5-2-6, /content/experience-fragments/ontariohealth/language-masters/en/recommended-requirements/5-2-8
Last Updated: June 23, 2025