Get A-Head
By: Get A-Head Inc.
Modality: Secure Messaging, Video
Status: Verified
Verified date:
Product version: Version 2.6.2
Verified Virtual Visits Solution Requirements version: 2.0
| Solution Provider Details | |
|---|---|
| Full Legal Name | Get A-Head Inc |
| Other operating name(s) | Get A-Head Powered by Keel Mind |
| Address | 2 Bloor Street East |
| Internet Home page | https://www.geta-head.com |
| Year Business Started | 2020 |
| Accessibility Information | |
|---|---|
| Accessibility Report | Accessibility report not available. |
| Supported Features | Closed captions (auto generated, manual, or third-party), Font resizer, Multi-pinning, Online booking |
| Third Party Information | |
|---|---|
| Third party video product vendor | Twilio |
| Third party secure messaging product vendor | Twilio |
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.
2.1.14: Support distribution of patient surveys
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)
2.1.15: Provide ability for virtual visit information to be shared with patients and their caregivers
2.1.17: Will support Canadian English and Canadian French languages
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.
3.2.10: Enable a virtual waiting room
Solutions may allow clinicians to enable a waiting room. This allows clinicians to control when participant(s) join the synchronous video event.
3.2.11: Enable clinicians to export a secure calendar entry and URL for a scheduled video visit
Solutions should enable a scheduled video visit to be integrated into the external calendaring systems of other clinicians (e.g., HIS, EMR, Outlook).
3.2.12: Provide a visual indicator of poor call quality to all participants in an ongoing video virtual visit event
3.2.13: Provide an audio-only option
An audio visit may be an acceptable alternative if insufficient bandwidth is available to support a video visit.
3.2.14: Provide the ability to switch audio and/or video inputs (USB peripherals) during an active 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.
3.3.1: Enable clinicians to import and launch a video visit from a secured iCalendar data source
Enables health care organizations and clinicians to launch a secure video visit.
4.2.10: Enable multiple authorized clinicians to participate in a secure messaging visit
Solutions should allow other care team members to join in a secure messaging visit. This can include reading or creating messages.