‹ 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
Created

Planned RCKMS May Tool Deployment

When
With
Allison Seidel
Notes
Backend UI Enhancements
Added error handling to ensure all necessary quantitative fields are populated when authoring criteria rules.
 
eICR Processing Updates
We’ve made the following changes to the processing of eICR data elements:
  1. The ClinicalDocument/effectiveTime data element has been added to the vMR as DOCUMENT_EFFECTIVE_TIME for use in timeboxing calculations.
  2. RCKMS now supports proper handling of problem observations in eICRs that include a negation indicator of "true." Previously, it was possible for RCKMS to evaluate a Social History observation or a problem or diagnosis with an assertion of pregnancy and negationInd="true" as "pregnant" instead of "not pregnant." RCKMS now correctly evaluates such cases as "not pregnant." Potentially impacted RCKMS conditions are those that include pregnancy criteria: Down Syndrome, Hepatitis B, Hepatitis C, Rubella, Toxoplasmosis, and Zika. This fix addresses the immediate issue of pregnancy evaluation identified in Production. Negation indicator processing for non-observation entries will be accommodated in an upcoming RCKMS release, if needed.
  3. Updated determination of reference time for evaluation of active patient addresses.
  4. Corrected an issue where the codeSystemName and displayName values for /observation/interpretationCode were transposed when converted to the vMR.
Frontend UI Enhancements
  1. Added the ability to filter the ‘Reporting Specification’ list by status. By default, reporting specifications in the following statuses are displayed: In Progress, Ready for Test, Published to Test, Ready for Production Use, and Published to Production. Users can change status selections in the new ‘Filters’ dialog. Note that filter selections are reset to the default each time the Reporting Specification list is loaded.
  2. Added instructive text to the 'Clone Reporting Specifications' and 'Import Reporting Specifications' dialogs.
  3. Disabled the ability to edit or delete reporting specifications in 'Published to Production' or 'Retired from Production' status. An eye icon to the right of the ‘Last Published’ field in the ‘Reporting Specification’ list indicates a specification is view-only. To author changes, users must clone the existing version of the reporting specification, make the desired changes in the cloned version, and re-publish.
  4. The Reporting Specification ‘Last Updated’ field now accurately reflects the last time a change to the specification was saved.
  5. Fixed an issue where the ‘Last Published’ date for conditions published to Production updated when publishing to Test. The ‘Last Published’ date now correctly reflects the last time the reporting specification was published to the applicable environment.
Performance Optimizations
Optimized database queries related to adding and importing default reporting specifications to decrease the time required for these operations.
 
Preliminary Changes for Timeboxing
The following changes have been made in preparation for timeboxing support. Note that changes will not be visible in the user interface until the in-tool release of timebox-eligible conditions:
  1. Added the ability to enable timeboxing and set a Timebox Duration value for timebox eligible criteria.
  2. Added support for the timebox calculation function to the RCKMS Rules Generation Service.
  3. Added support for timebox evaluation to eICR processing.
  4. Added new System Properties to support timeboxing.
  5. Added support for appending the Timebox Duration to criteria labels in the Specifications grid, on the Criteria/Logic Sets tab, and in the Reportability Response.
Reporting Enhancements
We’ve made the following enhancements to the Condition Details Report:
  1. Inactive criteria no longer display in the Logic Set Details.
  2. The Criteria Status is now indicated on the Criteria tab of the Excel version of the report.
  3. In anticipation of timeboxing support, a “Timebox Eligible” label and “Timebox Duration” field have been added to the HTML and Excel versions of the report.
Routine Maintenance
We’ve updated RCKMS services to address low and medium level security vulnerabilities.