As part of our efforts to simplify and streamline our compliance tools we are aligning our Rounding application with the more unified approach to compliance standards management.
To help your organization manage all your compliance in one central spot, we have moved the Code Libraries section of the Rounding setup to the Admin Console, where your core compliance libraries are managed and maintained.
Getting to the new Compliance Standards Library
Because of the shift to the Admin Console, you will no longer be able to manage the code library from within the Rounding application. Click on the App Switcher (waffle button) in the upper right corner and open the Admin Console. If you do not see the Admin Console in your App Switcher menu and you are authorized to manage the Code Libraries for your Rounding application, you may need to reach out to your department’s administrator to have this option added to your User Role Permissions.
As part of the new feature set, we have introduced a new Menu Role option in the Admin Console for Rounding Compliance Standards. This is where all the configuration of Rounding compliance standards (formerly Code Libraries) is located.
CMS Core Roles can have this menu option added if needed by adjusting the Menu Role Configuration option for that menu item.
Managing your Compliance Standards for Rounding
Depending on your role permissions, you may see both the Core Compliance Standards menu (currently under the Reports heading) as well as the Rounding Compliance Standards menu (under the Rounding heading). These are mirrored, so both landing pages will show your code libraries for anything you’ve configured for core, as well as anything you had previously built as Rounding code libraries. The visibility of your code libraries can be controlled separately so that only the pertinent codes needed for each application are shown in each.
*Note that you cannot edit or delete code libraries that you created in one in the other, to prevent accidental changes in either. It is recommended that you begin to associate your Round Libraries with the code libraries that your organization uses for the core application so that everything can be managed more easily.
When you go to the Rounding Compliance Standards configuration page it will show you the list of all your current Code Libraries from both the Core application and any you had previously built for your Rounding application. By default, libraries created in the Core compliance configuration are set to not visible for Rounding and libraries created in the Rounding compliance configuration are set to not visible for the Core.
The hierarchy now allows for creating a Code Library (Joint Commission, DNV, NFPA for example) with the actual standards for that library organized underneath, and then the elements organized underneath the standards they belong to and all visible from the landing page. This can aid your organization in staying on top of updates to code libraries as well as making it easy to find and edit existing code used throughout the application for compliance.
You will also be able to configure visibility to make sure that your teams see only the standards that are applicable and important to them. You can set a whole Code Library as visible or not visible and select individual Standards’ and Elements’ visibility at the individual segment level, as well as manage the visibility for Rounding separately from the Core visibility. This allows for adding additional Code Library items specifically used for Rounding while also limiting the amount of clutter for Core usage.
In order to flexibly meet the needs of various organizations, we have made it possible to have different visibility settings for every segment, however we have also provided a quick tool if you want them uniform across multiple segments, to Copy Visibility Settings To multiple segments. Simply set the visibility for the Compliance Standards to what you want and then use the Copy button at the top right of the landing page to open the dialog for selecting the other segments you want identical. This will copy the settings for all standards that are the same in both segments – if you have added standards to an individual segment rather than managing them at a shared segment level, the copy function will not affect those.
In addition, we have added the ability to reorganize standards. If you would like to reorganize standards that your organization created over time, you have the ability to create a new parent Code Library and then you can edit those standards into the new Code Library by selecting the Code Library from the dropdown in the Edit Standard page. This will move the Standard and all associated Elements to the identified Code Library.
Configuring Compliance Standards and Elements
Compliance Standards
The Rounding Compliance Standard configuration page has three fields that can be configured, depending on the Standard and where it has come from. The Standards that FSI loads directly into your system cannot be edited (for instance Joint Commission 2026), as they are maintained based on the actual language of the published Code Library, however you CAN add new Elements to our Compliance Standards if necessary. Code libraries that you create and maintain can be edited, renamed, and moved as needed.
Compliance Elements
There are a couple of new fields added to the Compliance Element configuration page itself, as well as some updated terminology to bring more clarity and better suit a broader range of Compliance data – Linked Compliance Elements and Asset Categories are new to this configuration page.
First, since many Compliance Standards reference other standards from other Authorities Having Jurisdictions, we have added the ability to link Elements from one Code Library to Elements from other AHJ’s Code Libraries, aligning your work to identify compliance across multiple bodies of compliance. When you click on the + Linked Compliance Element button a selection window opens where you can select another Code Library’s Element to link to the current one.
Second, we have added the ability to select one or more Asset Categories associated with the Compliance Standard Elements in order to better organize and classify assets all the way through the compliance documentation. This will also allow for narrowing the scope of your EBinders reporting, especially with the more condensed new format of Joint Commission standards as well as the organization of DNV standards, and increase your search capabilities.
Using the Compliance Standards in the Rounding Application
Previously in Rounding, Code Libraries were managed at a single, flat level, where you could only identify one level of code. While they can still be managed that way, you now have the ability to organize by Standard and element, to stay in line with our other compliance tools and give you better clarity on your round findings.
When you navigate to the Round Libraries option within the Rounding application clicking the , gear icon and you click on the Library Items button on a round library you are taken to the same Library Items list as before. However, now when you click the edit pencil to edit an individual library item, the configuration page that opens now has an additional option. You can select the Compliance Standard as before, and now you can also select compliance elements that belong to that standard, further enabling better detail on your findings and compliance.
Below is an example of the single level of compliance standard previously allowed by Rounding and how it will appear in the new screen.
You can see that the Compliance standard that is selected there has no elements selected, but the element is referenced in the item description. Now you can select one or more elements to also include in the library item to be more specific about what the item covers for compliance purposes.
With this update, in order to bring work orders created by findings in line with other core created work orders, you will also now see the code language within the work orders that have compliance standards linked to the finding.
Migration of current Code Library Data
As part of the shift from holding the Code Library separately within the Rounding application, we have migrated all your current code libraries into the new Rounding Compliance Standards so that there is no disruption. Moving forward, as you want to adjust your Rounding code references to any new codes, you will have the ability to use the single source of Standards that is maintained within the Admin Console and eventually clear out any old code references that have less information.
Comments
0 comments
Please sign in to leave a comment.