‹ Home
Exported

eCR/RCKMS Community of Practice

The purpose of the eCR/RCKMS Community of Practice Basecamp is to provide staff from state, local, territorial, and tribal public health agencies with a venue to participate in peer-to-peer discussions pertaining to using RCKMS. This Basecamp is not intended for formal communications about RCKMS or eCR and will not be moderated by CSTE staff. For technical issues or assistance with RCKMS, please visit www.rckms.org to submit a ticket. Disclaimer: The statements and responses posted on the eCR/RCKMS Community of Practice are solely the views of the authors and do not necessarily represent the official views of CDC or CSTE.
Becky Lampkins, Manager, Surveillance/Informatics Program at CSTEMeredith Lichtenstein, CSTELaura ErhartNancy Barrett, Epi 4/PH Informatics SpecialistRita Altamore, EpidemiologistDavid DiCesareWalter Kemper, ELR Coordinator, NC DHHS Div of Public HealthAmanda Payne, Senior Consultant at J Michael ConsultingJohn Satre, Informatician at Iowa Department of Public HealthShaily Krishan, Program Manager at CSTEJudie HyunKathy Turner, Deputy State Epidemiologist at IDSara Robinson, ID Epi Program Director at Maine CDCMisty Johnson, Informatician, WI DHSCrystal Snare +376 others
Tool Development Ideas by Allison Seidel ·

🛠 Proposed RCKMS Change (May 2023): Cloning Published Reporting Specifications when Making Changes to Published Rules

The RCKMS Administrators routinely advise users that the best practice for making changes to a Reporting Specification is to clone the existing version and make changes to the cloned version, so that previous versions of reportability rule configurations are available for reference and troubleshooting. This practice also ensures that jurisdiction users know which rules are currently published and in effect for their jurisdiction.
 
In keeping with the best practice recommendation, and to better support RCKMS reportability reviews, there will be a planned deployment in May 2023 after which the RCKMS Authoring Tool will no longer support editing or deleting Reporting Specifications that are published to Production or have been retired from Production. As a result of this change, there will be a few changes to Reporting Specifications management:
 
a.     Users will still be able to view Reporting Specifications that have been published to Production, but they won’t be able to save any changes. An eye icon (shown in the screenshot below) will indicate that a Reporting Specification can only be viewed, and not edited:
 
Reporting Specifications List with 'Eye Icon' shown to the right of the condition • Download
 
 
b.     To modify a Reporting Specification’s rules, users will need to clone the Reporting Specification and edit the rules in the cloned version, and then publish the cloned version (thus automatically retiring the previous version).
 
c.     When cloning an existing Reporting Specification, users will be prompted with the following dialog:
 
Cloning Reporting Specification pop-up • Download
Note: As a best practice for version naming, it is recommended to append a version identifier (such as ‘v2’, ‘v3’, etc.) to the source Version ID. This naming method differentiates the cloned version from the original version while preserving the RCKMS release information for reference. For example, in the scenario above, a Version ID of “2.1 Release 20200608 v2” would be appropriate. 
 
For any questions regarding these upcoming changes for cloning of Reporting Specifications or version naming, please reach out to your Authoring Support Associate or submit a REDCap ticket.