WestCare's Electronic Health Record
This product is self-developed and is not marketed, therefore the mandatory disclosure requirement is satisfied per the below webpage available through the CHPL.
- Developer organization name: WestCare Foundation, Inc
- Date the product was certified: Dec 30, 2019
- Product name and version: Clinical Data System Version 1
- Unique certification number: 15.04.04.2649.Clin.01.00.0.191230
- Certification criteria to which the product has been certified: 170.315 (a)(5, 11); (b)(10); (d)(1-7, 12-13); (g)(3-5)
- CQMs to which the product has been certified: None
- Any additional software the certified product relied upon to demonstrate its compliance with certification criteria: None
- ONC Disclaimer: "This Health IT Module is 2015 Edition compliant and has been certified by an ONC-ACB in accordance with the applicable certification criteria adopted by the Secretary of Health and Human Services. This certification does not represent an endorsement by the U.S. Department of Health and Human Services."
This product is self-developed and is not marketed, therefore the mandatory disclosure requirement is satisfied per the below webpage available through the CHPL.
Mandatory Disclosure Requirement
Electronic Health Information Export
MFA Use Cases for WestCare EHR
WestCare Clinical Data System uses Single-Sign On via Microsoft Entra which requires that a user setup multi-factor authentication using one of the following methods:
- Push multi-factor authentication (MFA) via Microsoft Authenticator app or alternative authenticator app
- Time-based one-time password (TOTP) via Token2 hardware token
- TOTP via email address associated with the user profile or alternative email address
- TOTP via SMS text associated with the mobile number on the user profile or alternative mobile number
- TOTP via phone call associated with the phone number on the user profile or alternative phone number
MFA Frequency is based on a detection algorithm combining various factors such as MAC address, IP address, time of last login, device specs, and more to determine if the user should be challenged for MFA.
