hc1 is improving all the time. This page is an overview of the features and fixes in the latest release. Information about past releases is available in the pages below.
December 2017 Updates
In response to user feedback, we've made these improvements:
- Related Items lists only display active records. When you click Delete Record on a record detail page or click next to a record in a list, you inactivate that record and prevent it from appearing in search results and lists and reports that are filtered to display only active records. Before, inactivating records didn’t remove them from Related Items lists, however. Now, we’ve added a filter to the Related Items list so it doesn’t display records that are no longer relevant.
If a record is reactivated, it will reappear on Related Items lists. To break the related item relationship and remove a record from a Related Items list, clickin the row of the item you want to remove.
- Sales Rep names no longer show up as just a comma on the Opportunities list. Back in August, we changed the way we store user names from separate fields for First Name and Last Name to one Full Name field. Any users added since August don’t have anything stored in the old First Name and Last Name fields, which is where the code for the Opportunities list was looking for sales rep name information. We’ve updated the code on the Opportunities list to look for the Full Name field instead.
- You no longer see a General Error message when you log out of hc1. Before, an error message stating “An error has occurred. Please contact the system administrator” would sometimes display when you were logging out of an environment at the same time another user was logging in. Now, the Please Sign In page appears whenever you log out of hc1.
- A case record’s Root Cause picklist displays values in the order set in Administration on Relationship Management’s Root Cause page. Before, root causes were displayed in the order shown on the case layout.
- User sort works in Administration’s HRM Access Control. Before, when you would open an access control node’s Users tab and click on the Name column to sort the users alphabetically, you would get this error message: org.hibernate.QueryException: could not resolve property: lastName of: com.hc1.core.tenant.model.tenant.auth.User. This error was a result of the user name changes we made in August. Now, when you click on the Names column, hc1 sorts the users alphabetically by the first letter of the user’s full name.
- You can search for patients in global search without needing the Tenant Setup Read permission. Back in February, we added the Allow Patients to Be Searchable in Global Search box to Administration’s Tenant Settings page so that system administrators could enable users to use the global search bar to search for patients. However, the code that verified whether this box was checked also required Tenant Settings Read permission, which most users don’t have, and would therefore prevent users from accessing this feature. We’ve eliminated this requirement, so users only need PHI permissions to find patients with global search.
- Users with the Interface role can create users and user profiles via the web service. We’ve added authentication permissions to the Interface role to restore its level of access to what it was prior to August.
For more information about the features related to these fixes, click one of the listed Online Help links.
Related items and inactivating/reactivating records:
- Add a Related Item to an Activity
- Remove a Related Item from an Activity
- Inactivate Activities
- Reactivate Activities
Root cause settings:
Picklist settings on user defined layouts:
Access control settings:
Interface role, patient search, and other user permissions: