incorporate a force password change feature to comply with HIPPA
incorporate a force password change feature to comply with HIPPA regulations / recommendations
-
Anonymous commented
I saw another post where the user was told that this request is a training issue and that they should use the LDAP feature. I've worked for a software company previously where software was shifted to LDAP integration and am fully aware of how invasive this kind of update is. Converting software to LDAP integration affects every aspect of the software and can result in major security issues (exposed patient data, user access issues, etc). I'm open to the change long-term; however, I won't put my data at risk or impose undue frustration on my clinical team. Could someone please answer some questions about this feature? How long has it been available to the software? How many clients currently use the feature? Do you have a guide/checklist for implementing that feature? What documentation exists regarding that feature?
Thanks!
-
Anonymous commented
The criteria for password security and timeline requirements vary between the different groups. My office is on 90 day timeline but other suggestions ask for every 6 months. Enhanced security should be added as an optional feature which gives administrators the ability set security policy according to his/her institutions policy.
Additionally, we need the ability to enforce a security policy (passwords must be X characters long, contain uppers & lowers, numbers, and not reused within X amount of passwords). These could also be added as optional features which individual offices can enable as they see fit.
Thanks!