US Situational Awareness Framework for Reporting (US SAFR) Implementation Guide
1.0.0 - STU 1

US Situational Awareness Framework for Reporting (US SAFR) Implementation Guide - Downloaded Version 1.0.0 See the Directory of published versions

## actors

Page standards status: Informative

### Actors

This implementation guide defines the following actors. Note, it is possible for a given system to play the role of multiple actors. For example, an EHR could be both the Data Source and digital Quality Measure (Measure), Evaluation Engine when calculating a measure internally. Likewise a system residing at NHSN that queries the Data Source remotely, evaluates those data, produces MeasureReport bundles, and validates the result may be both the Measure Evaluation Engine and MeasureReport Recipient. For more context, see Reporting Scenarios.

- Measure Evaluation Engine A system that retrieves data from the Data Source and evaluates those data against one or more measures retrieved from the Measure Source. The resulting MeasureReport bundle and related resources are then sent to the MeasureReport recipient. If the Measure Evaluation Engine uses FHIR APIs then it acts as a US Core Client, a DEQM Reporter Client, and implements the $evaluation-measure operation. Note, however, that it is acceptable for a Measure Evaluation Engine to use other means to create a MeasureReport (i.e. pull data from legacy systems that don't support FHIR and produce a MeasureReport resource directly).

- Data Source A system containing data (typically patient data, but could be situational awareness data) that will be evaluated against one or more measures. This may be a FHIR server, an EHR with a FHIR endpoint (facade), an internal data store when the Data Source and Measure Evaluation Engine actors are played by the same system such as an EHR that does it's own measure evaluation, or it may be a system containing other data such as situational awareness data that is reporting via CSV or other format. When FHIR enabled, the Data Source acts as a US Core Server

- Data Aggregator For some example use cases, such as bed capacity reporting, data from multiple Data Source actors may be aggregated by a single system before measure evaluation. A Data Aggregator also plays the role of a Data Source once aggregation is complete. An example would be a state public health agency aggregating data from all facilities in the state before using those data to produce a MeasureReport containing bed capacity data for the entire state. When FHIR enabled, a Data Aggregator acts as a US Core Server when playing the role of a Data Source after aggregation. During aggregation, the Data Aggregator acts similar to the SANER options for aggregation, but implements its own CapabilityStatement due to the incompatibilities between DEQM and SANER.

- Measure Source A system at NHSN, federal and jurisdictional Public Health Agencies including State, Tribal, Local and Territorial (STLT) Health Departments that stores FHIR resources such as Measure, Library, ValueSet, etc. that are used for Measure Reporting. The Measure Evaluation Engine queries the Measure Source for the latest Measure content before querying the Patient Data Source and performing measure evaluation. The Measure Source acts as a CQFM Publishable Measure Repository

- MeasureReport Recipient A system at NHSN, federal and jurisdictional Public Health Agencies including State, Tribal, Local and Territorial (STLT) Health Departments that receives MeasureReport bundles from the Measure Evaluation Engine and validates the result against the profiles in this implementation guide, and potentially other measure-specific profiles that are distributed with the measures themselves. The MeasureReport Recipient acts as a DEQM Receiver Server, provides write access to Bundle resources containing MeasureReport and other related resources, and implements the $validate operation.