Data Commit – TEST_ID and TEST

EQuIS creates and assigns new TEST_IDs by using the FN_GET_NEXT_ID function. When EQuIS creates a new TEST_ ID, EQuIS pulls the next test value in line and assigns it a TEST_ID not already contained in EQuIS.

If a test record already exists in the database with the same value (not same TEST_ID), then it will not commit. Existing TEST_IDs are found by referencing FACILITY_ID, SAMPLE_ID, ANALYTIC_METHOD, and the Test Alternate Key (analysis_date, fraction, column_number, test_type, identifier).

Most formats will assign a "-1" on create if the TEST_ID is not found, meaning that there are no parent records associated with the TEST_RECORD, typically in DT_TEST, and will only look in the package and not in the database. Therefore, users must submit the sample, test, and result sections together so that a complete TEST_RECORD may be compiled, helping to avoid a "-1" TEST_ID.

Duplicate rows, typically in DT_RESULT, with a TEST_ID of "-1" can display when the value is not constrained to be unique. This can be related to not having enough Test Alternate Keys (TAKs) selected to make the result unique.

If the format does not match the TAK in the database, the format may be need to be revised. For example, the EQEDD's TAK is ANALYTIC_METHOD, ANALYSIS_DATE, FRACTION, and TEST_TYPE. If the database's TAK includes additional fields, such as COLUMN_NUMBER, the format can be revised as needed. See Making Changes to Format Files on what steps should be taken.

Data Commit – TEST_ID and TEST_ID-1

Data Commit – TEST_ID and TEST_ID-1