<< Click to Display Table of Contents >> Navigation:  EQuIS Library > Formats > EarthSoft Standard Formats > EQEDD Format

Format Name: EQEDD

File Name: EQEDD.zip

Source: EDP Standalone, EQuIS Professional, and EQuIS Enterprise

Export(s): Yes (see section below)

Enumeration File: Not applicable

 

 

Description: The EQEDD format is one of the most extensive/detailed standard EQuIS formats. It contains sections for location, lab, and field data. It is a good generic format to begin importing data.

 

 

Installation Instructions: The EQEDD format is included in the installation of EDP Standalone and EQuIS Professional in the \Formats\EarthSoft folder. This format is also installed with EQuIS Enterprise and is configured (by default) to be available in the Enterprise EDP EDD Upload widget. The default configuration settings should be reviewed and modified to meet user needs (see the Add or Modify Enterprise EDP Formats article). The default commit type is Insert and Update.

 

 

Overview: The EQEDD format is divided into three separate sections: Field, Lab and Files_v1. The Files_v1 section can be used to load a file to an EQuIS database in EDP. See Uploading Files in EDP for additional information. To load new data into the database, a blank EDD (Electronic Data Deliverable) of the format can be generated. Click on the Home tab and select Blank EDD in the Tools group.

 

Columns in the EQEDD format use different tables for their reference value lookups. The EQuIS EDD Description file includes which tables are used for the reference value source. Download the EQuIS EDD Description file in EDP or the Enterprise EDP EDD Upload Widget.  

 

 

Limitations/Assumptions: The checks and mappings in any EDD format involve assumptions. The following are assumptions and limitations for the EQEDD format.

•Test Alternate Key (TAK) fields available in the format: SAMPLE_ID, ANALYTIC_METHOD, ANALYSIS_DATE, FRACTION, TEST_TYPE and IDENTIFIER.  

•FieldSample_v1 section typically is populated with field generated data. LabSample_v1 tab is typically populated with lab generated data. For any single sample in a single EDD, populate either FieldSample_v1 or LabSample_v1, but not both, since both sections map to the same database table.

•FieldSample_v1.sample_matrix_code and LabSample_v1.sample_matrix_code are lookups to RT_MATRIX.MATRIX_CODE for records with MATRIX_CLASS is null or 'FIELD'.

•In the FieldResults_v1 section, result_value is always required.

•WaterLevel_v1.water_level_elev field is automatically calculated by subtracting the water_level_depth from the historical_reference_elev. If water_level_elev is manually populated, the calculated value will not overwrite the manually populated value.

•For any single sample, populate either the TestResults_v1 or TestResultsQC_v1 section, but not both, since both sections map to the same database table.

•The TestResultsQC_v1 section should be used if QC data are included (e.g., in qc_spike, qc_spike_recovery, qc_spike_lcl, qc_spike_ucl, etc.).  

•For both the TestResults_v1 and TestResultsQC_v1 sections, the result_value is required when the detect_flag = 'Y' and result_type_code = 'TRG' or 'TIC'. The error appears the on detect_flag field.

•The EQEDD format can be used to load new locations (SYS_LOC_CODE) and to submit new information for location (SYS_LOC_CODE) records already in the database.

•All sections containing the sys_loc_code column will function as explained below.

•If the sys_loc_code field is populated, the format will check against the Location tab to see if this data exists.

•If the Location section of the format file is empty, the sys_loc_code fields will check the database to see if the locations exist (Professional EDP Only).

•If the location does not exist in the database or the Location section, an error will occur on the commit stage.

•The following four fields in the TestResults_v1 section of the format can be used for radiological data management in EQuIS:

•uncertainty: The uncertainty of the counting error, valid values include "1 sigma" or "2 sigma". This field is required if the counting_error field is populated.

•minimum_detectable_conc: The lowest concentration of an analyte that can be detected. This value should be in the same units as DT_RESULT.RESULT_UNIT.

•critical_value: Critical value as reported by the laboratory.

•counting_error: For tests that depend on counting, this is the error as reported by the laboratory. This value should be in the same units as DT_RESULT.RESULT_UNIT.

 

 

Exports: The data returned will be automatically filtered by the facility to which the user is connected, as well as by the parameters selected prior to running the report. See the Exports from Professional EDP article for more information about running exports.