Ocean
By: OceanMD
Modality: Secure Messaging
Status: Validated
Review start date:
Verified date:
Validated date:
Product version: Version du produit : Version Ocean : Ocean@20230622 Révision SVN : 29264
Verified Virtual Visits Solution Requirements version: 2.0
| Solution Provider Details | |
|---|---|
| Full Legal Name | 2355581 Ontario Inc. (O/a OceanMD) |
| Other operating name(s) | CognisantMD, OceanMD |
| Address | 3080 Yonge Street |
| Internet Home page | https://www.oceanmd.com/ |
| Year Business Started | 2012 |
| Accessibility Information | |
|---|---|
| Accessibility Report | Accessibility report not available. |
| Supported Features | |
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.11: Provide seamless integration with Point of Service systems
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
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.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.11: Provide seamless integration with Point of Service systems
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
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.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