Vendor Details
SigMail
- By
- Sigma Healthtech Inc.
- Modality
-
Secure Messaging
Video - Status
- Verified
- Attested Date
- 2021-May-13
- Product Version
- SigMail v3.3.2260+20230112
- Verification standard version
- 2.0
Solution Provider Details
- Full Address
- 2910 South Sheridan Way South,Oakville,ON,L6J 7L9,CA
- Web Site URL
- https://www.sigmail.ca
- Year Business Started
- 2020
Accessibility Information
- Published Accessibility Report
- Contact your vendor to request an accessibility report
- 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
Screen reader support
Third Party Information
- Video Secondary Vendor
- Twilio
- Secure Messaging Secondary Vendor Name
- Microsoft Azure
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.
SigMail
-
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).
IP Address.
Participant's name, date of birth, gender, and unique identifier i.e., Health card number
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.
IP Address.
IP Address.
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.
An audio visit may be an acceptable alternative if insufficient bandwidth is available to support a 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.
Solutions should allow clinicians to send and receive patient agreements and other educational materials relating to virtual services.
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).
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)
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.
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
Physicians participating in the provincial pilot identified the ability to flag patient messages for review as important for triaging and care team collaboration purposes.
Last Updated: June 23, 2025