Anonymous
My feedback
9 results found
-
1 voteAnonymous
shared this idea
·
-
2 votes
Thank you for the suggestion, we greatly appreciate the feedback.
Anonymous
shared this idea
·
-
1 vote
This has been resolved in a recent update.
An error occurred while saving the comment Anonymous
shared this idea
·
-
4 votes
Do you have any documentation or web links that explain the requirements you’re asking about?
An error occurred while saving the comment Anonymous
commented
We would need to know what patient, forms, were accessed so that we can audit those requests as needed. Thanks!
An error occurred while saving the comment Anonymous
commented
I am not a compliance specialist; however, I have been informed by my compliance team that HIPAA requires that any application log all access to patient ePHI, not just modifications to that data. Since we moved to OMSVision, we've already encountered scenarios where read access has been questioned. What I'm looking for is a log of all form/content access for every user in the app.
This excerpt was taken from this site: https://www.hipaajournal.com/hipaa-compliance-checklist/
You all probably have a HIPAA compliance rep who can confirm.Technical Safeguards: Introduce activity logs and audit controls: Required - The audit controls required under the technical safeguards are there to register attempted access to ePHI and record what is done with that data once it has been accessed.
From what I can tell, we need audit logging of what users view not just what they change.
Anonymous
shared this idea
·
-
4 votes
An error occurred while saving the comment 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!
An error occurred while saving the comment 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!
Anonymous
supported this idea
·
-
2 votes
Thanks for the request.
Anonymous
shared this idea
·
-
11 votes
An error occurred while saving the comment Anonymous
commented
Reporting functionality within OMS Vision is difficult. Unless you already know where to look for a report it's difficult to find them. My clinical team is often asking for detailed information about how to verify different aspects of their clinical work, most recently, verifying that procedures have been accurately documented.
To start with, move all reports into the report tab. That way, people can easily find existing reports.
Next, build a custom report option that can be used by clinical staff/support to sort, filter, and analyze their data. Thanks!
Anonymous
supported this idea
·
-
1 vote
This is part of a feature we’re working on for the release of 17.1, it’s currently in beta.
Anonymous
shared this idea
·
-
2 votes
An error occurred while saving the comment Anonymous
commented
Suggestion: optionally filter inactive doctors from lists
In what version of the application should this be resolved? Thanks!