Cloud DX Connected Health Platform
Solution Provider Details | |
---|---|
Full Legal Name | Cloud Diagnostics Canada ULC |
Other operating name(s) | Cloud Dx |
Address | 72 Victoria St. South |
Internet Home page | https://ca.pulsewavedx.com |
Year Business Started | 2014 |
Accessibility Information | |
---|---|
Accessibility Report | Accessibility report not available. |
Supported Features | Avoids using colour alone to convey meaning (example: uses symbols to show out of range results, not just red-coloured text), Dark or high contrast modes, Font resizer, Keyboard accessibility, Multi-pinning, Multi-spotlight |
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.10: Meets Web Content Accessibility Guidelines (WCAG) 2.0 Level AA requirements or higher
Solutions should have web and user interfaces that provide accessibility to Ontarians with disabilities; and comply with the Accessibility for Ontarians with Disabilities Act (AODA).
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.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.
2.1.18: Enable verification of clinician identity using multi-factor authentication
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
2.1.9: Manage patient agreements for virtual visit services
Solutions should allow clinicians to send and receive patient agreements and other educational materials relating to virtual services.
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).