Arya EHR ( Secure Messaging )
By: Arya Health
Modality: Secure Messaging, Video
Status: Under Review
Verified date:
Product version: Jan 12/2013
Verified Virtual Visits Solution Requirements version: 2.0
The secure messaging modality of this solution has been withdrawn on the basis that it does not meet all mandatory requirements. The video modality of this solution continues to maintain verified status.
| Solution Provider Details | |
|---|---|
| Full Legal Name | Arya Health |
| Address | 2918 Huckleberry Drive |
| Internet Home page | https://aryaehr.com |
| Year Business Started | 4 |
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.12: Support identification of virtual visits eligible for claims submission
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).
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.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.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.2.15: Provide additional data for operational statistics and information
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.
3.2.16: Enable a videoconferencing endpoint to be added to a video visit using a dialing alias
H.323 ID, E.164 or SIP URI.
3.2.17: Provide equipment and connectivity testing
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.
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.
4.2.11: Allow clinicians to flag patient messages as urgent or requiring attention
Physicians participating in the provincial pilot identified the ability to flag patient messages for review as important for triaging and care team collaboration purposes.
4.2.12: Provide a read receipt for messages that can be filtered
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.
4.2.9: Separate clinical and administrative messages
Clinician experience and efficiency can be improved by creating separate inboxes (groups) for administrative versus clinical messages.
5.2.1: Therapeutic Area of Care
Area of Practice.
5.2.2: Name of Regulatory College
5.2.3: Professional Registration Number
5.2.4: Clinical Provider Location (Event Host)
IP Address.
5.2.5: Participant Location (participants)
IP Address.
5.2.6: Participant Location (patient)
IP Address.
5.2.7: Participant Identification (patient)
Participant's name, date of birth, gender, and unique identifier i.e., Health card number