ONRx
Solution Provider Details | |
---|---|
Full Legal Name | Ontario Health Alliance |
Address | 1720 Howard Avenue |
Internet Home page | ONHealth Alliance - ONRx |
Year Business Started | 2020 |
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.13: Provide automated verification of patient's Ontario Health Insurance Plan (OHIP) number
Automated OHIP verification can assist clinicians from a claims and medico-legal perspective. It can also make patient registration processes more efficient.
Solutions should verify that the 10-digit OHIP number format is valid.
Solutions can also:
- Verify that number is associated with the patient by matching with registration details
- Verify that the patient’s OHIP number is valid through MOHLTC Health Card Validation (HCV)
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.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.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.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.
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.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