Creating Data Standards

Summary

This guide explains how to create and work with data standards in ENFOS. A data standard defines the criteria that sampling results are evaluated against, organized into reusable standards that can be created in the portfolio hierarchy and applied to the data beneath them. Standards are also the foundation for analyte alerts. This article covers the two types of standards and how they are inherited, how to add a standard through the user interface (UI) or by import file, the information captured in a standard's summary, how rules are structured, and how supporting documents and change history are maintained.

Defining Standards in ENFOS

ENFOS uses two types of standards, which differ in where they are defined: regulatory standards and background standards.

Regulatory Standards

• Defined at any level and inherited down. A regulatory standard placed at a higher level applies to all sites, AOCs, and other levels beneath it, so the same limits do not need to be recreated.
• More restrictive values take precedence. When more than one standard applies at a level, the more restrictive value takes precedence. For example, if a state standard is inherited down to the site level and a site-specific standard also exists, the more restrictive of the two limits applies for each analyte.

Background Standards

Background standards are defined at the site (level 17) or AOC (level 20), depending on where data is assigned in settings. Because background concentrations are specific to the location where samples are collected, these standards are set at the level where data is assigned rather than inherited from a higher level.

Adding a Standard in the User Interface

1. Navigate to Inventory > Scientific Data > Standards at the desired level in the hierarchy.
2. To add a new standard, click Add Standard at the top right of the screen.
3. Populate required fields and click Save. Optional fields are informational only.
4. Upon standard creation, you are taken to the standard's summary page. The Defined At field is automatically populated with the current hierarchy node. See Data Standard Summary section below for more information.
5. To add rules to the standard, click Add Rule.
6. Populate the fields in the popup window and click Add Rule. See Rules section below for more information.
7. To add a standard at a different level, navigate to that node and repeat these steps.

Adding Standards by Import File

1. Navigate to Administration > Transfers > File Import.
2. Select Data from the Module dropdown menu.
3. Select Data Standards from the Import Type dropdown menu.
4. To view the import format and download a blank .CSV template, click Import Formats.
5. Populate the .CSV file with your standard and rules.
6. To load a completed file to ENFOS, return to the File Imports submodule, select Data from the Module dropdown menu, and select Data Standards from the Type dropdown menu.
7. Click Choose File to select your populated file, and click Save to run the import. Once processed, the imported standard(s) appear under Inventory > Scientific Data > Standards for the defined hierarchy.

Data Standard Summary

Once a standard is created, ENFOS displays a summary at the top of the standard that captures the key identifying information:

After the standard is created, the summary also shows where in the hierarchy the standard is defined.

Rules

The Rules section lists every rule applied for the standard. Each rule is shown as a row, and the columns describe how the limit is defined and applied:

Multiplier Rules

A multiplier rule value is a multiple rather than a concentration, so the value itself has no unit. The multiple is applied against the background concentration for the analyte, which does have a unit, and the resulting calculated limit takes its unit from that background concentration. For example, a rule of 1.25 x BG applied to a background concentration of 200 mg/l produces a calculated limit of 250 mg/l. If no background sample is defined for the site or AOC, there is no value to multiply against, so the multiplier rule is ignored.

Supporting Documents

Documents can be added to a data standard to provide backup documentation, such as a PDF of the source regulation or a supporting reference table.

History

The History section tracks changes to the standard over time. As rules, limits, or summary fields are added or edited, the history records what changed, so the evolution of the standard can be reviewed and audited.

Common Questions

What is the difference between a regulatory and a background standard? A regulatory standard can be defined at any level in the hierarchy and is inherited down to every level below it. A background standard is defined at the site or AOC, where data is assigned, because background concentrations are specific to that location, and it is not inherited from a higher level.

What happens when more than one standard applies at the same location? The more restrictive value takes precedence for each analyte. For example, if a state standard inherited to the site level and a site-specific standard both apply, the more restrictive of the two limits is used.

How does a multiplier rule work? The multiplier is applied against the analyte's background concentration, and the calculated limit takes its unit from that background. For example, 1.25 x BG against a background of 200 mg/l yields 250 mg/l. If no background sample is defined for the location, the multiplier rule is ignored.

At what level should I create a standard? Regulatory standards can be created at any level in the hierarchy and apply to that node and all nodes below it. Background standards are created at the site or AOC level where data is assigned. Navigate to the node where you want the standard to apply before adding it.

Do I need a standard before creating an alert? Yes. A standard must exist before you can create an associated analyte alert. See the Creating Analyte Alerts article.

Can I load many standards at once? Yes. Use the Data Standards import file available under Administration > Transfers > File Import.