‹ 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
Posted by Shahidah Williams ·

RCKMS May Tool Deployment: In Production Wednesday May 17, 2023

Please be informed that the RCKMS May Tool Deployment is in production as of today, Wednesday, May 17th. An in-tool notification with the release notes was sent to RCKMS users today.
The deployment includes three new features that are intended to support your jurisdiction’s authoring efforts.
 
Key updates include:
  1. Reporting Specification Status Filter: As is, reporting specifications tagged with the following statuses will be displayed: In Progress, Ready for Test, Published to Test, Ready for Production Use, and Published to Production. Reporting specifications that have been retired will not show in the default list. Users will now be able to filter conditions by selecting a status of their choice for viewing ease.
  2. Disabled Features for Certain Statuses: Reporting specifications can no longer be edited or deleted if they are tagged with the statuses: Published to Production or Retired from Production. To easily identify which reporting specifications have these statuses for your jurisdiction, you may use the filter feature noted above.
           To edit a given reporting specification, users will now have to clone the existing version                 and reinitiate the publishing process. By disabling the edit feature, users can have a                       clearer understanding of any authoring changes made before they go into effect.

   3. “Last Updated” Field Reflects Accurate Time: Prior to this enhancement, users were                   unable to accurately determine when a reporting specification was last edited. Now, users            can see the last time a change to a given condition was made and saved. Viewing a reporting specification will not cause this field to update.

If you have any questions, or would like a 1-on-1 walkthrough of these enhancements, please feel free to reach out to your assigned Authoring Support Associate. Thank you!