Column Icons change how data is presented in the results grid of a Reporting Workbench report. They provide visual cues directly in the report’s output, helping you interpret statuses, categories, or patterns as you view the results. Because of this, the feature affects the actual results content you see in the Reporting Workbench, not just aspects like chart legends, headers, or a raw data export. In short, it influences the results portion of the report when you generate or view it.

Dynamic extensions are reusable blocks of code in Epic that extend how Chronicles data is read and written, with each extension defining a value or a set of values to filter on. They run at runtime and provide flexible, configurable criteria that drive data access across different Epic processes without changing the underlying code. This isn’t about pre-run scripts or static values embedded in a template, and it isn’t about security roles. It’s about injecting runtime, filterable criteria into Chronicles operations so the same code can be reused in different contexts by supplying different values. For example, a dynamic extension might specify a department or date range to filter encounters, and that filter can be adjusted without rewriting the logic.

A query template defines the blueprint for how data will be retrieved. It specifies which master files or data sources to search and which parameters can be used to constrain the search. This makes the template reusable and ensures consistency, since users can supply values for those parameters without changing the underlying query structure. It doesn’t control how the results are presented, how end users interact with the UI, or any default formatting—that’s handled by other parts of the reporting or presentation layer.

Dynamic extensions are the mechanism that provides values to dynamic parameters used by templates. They exist as records in the LPP master file, and templates read these records to obtain the actual values to plug into their dynamic parameters at runtime. This setup keeps the template logic stable while allowing the input data to change simply by updating the extension records. They’re not blocks of code in the system registry, they aren’t used to format report dates, and they aren’t standalone values stored in Chronicles, so the described role—records in the LPP master file that supply values to dynamic parameters—best captures how dynamic extensions function.