Operational reports share several characteristics. They are time-sensitive, since they support work that is happening now and must reflect current data. They are easily accessible in Hyperspace, so that staff can run them within their workflow without leaving the application. They are small and focused on individual users or teams, returning a short list of items that need action and not large volumes of data. These correspond to the first three options. Operational reports are not run through the Clarity nightly batch process, because that would make the data a day old, which defeats their purpose. They use Chronicles-based tools, such as Reporting Workbench, which read current data directly. Keeping operational reports focused also protects system performance, since the operational database must serve clinical users at the same time. When a stakeholder requests a report that needs both current data and large historical volumes, the analyst may need to separate the requirement into an operational list and an analytical report, each built with the tool that suits it.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit