Loading Sample and Result Data

<< Click to Display Table of Contents >>

EQuIS 7  >>  EDP > EDP Format Files, Open, Data Review, Tools, EDP Professional and EDP Enterprise > Professional >

Loading Sample and Result Data

EQuIS Professional uses EDP to enhance error detection and data loading. Therefore, one of the fundamental requirements when loading data through EQuIS Professional is that the Sample Data be loaded at the same time as the Result Data, even if they have already been loaded into the database. Doing this will identify any orphan records before you attempt to commit them to the database.

 

Following is a scenario that some EQuIS clients may frequently encounter, along with several associated data loading steps:

 

Scenario 1: Field Staff Provides Field Sample Data

Lab loads the Sample data into EQuIS.

Lab uses a Commit type of "Insert Only" to ensure that the SYS_SAMPLE_CODES are unique to the system.

Lab Data sent to client (Test, Result, and possibly Batch data).

 

Option A: Lab Sample Data Provided

 

Typically, labs provide a sample section of data that includes their lab samples and samples that they received from the field staff. If so:

Load the Sample, Test, and Result (and possibly Batch) sections from the lab.

Resolve any errors.

Create the package.

Commit the data into the system using "Insert and Merge" to fill in the blank fields in the database, but leave any populated fields like SYS_LOC_CODE populated in the database.

 

Option B: Lab Does not Provide Sample Data

Load Sample data from field staff.

Load Test, and Result, (and possibly Batch) sections from the lab.

Resolve any errors (a potential error might be that the lab provides you with Test, Result (and possibly Batch) information for samples created at the lab which will need sample data entered for them).

Resolve any errors.

Create the package.

Commit the data into the system using "Insert and Merge" to fill in the blank fields in the database, but leave any populated fields like SYS_LOC_CODE populated in the database.

 

The reverse may also occur where you receive lab data before Field data:

 

Scenario 2: Lab Data Arrives (Test, Result, and Possibly Batch Data)

 

Option C: Lab Sample Data Provided - Must Happen in this Scenario

 

Typically, labs provide a sample section of data that includes their lab samples, and samples that they received from the field staff. If so:

Load the Sample, Test, and Result, (possibly Batch) sections from the lab.

Resolve any errors.

Create the package.

Commit the data into the system using "Insert and Merge" to fill in the blank fields in the database, but leave any populated fields like SYS_LOC_CODE populated in the database.

Field Data arrives.

Load the Sample data into EQuIS.

Using a Commit type of "Insert and Update" to update the sample types to the correct values (assuming Lab assumes that all samples are Normal, you will want to update those with "FD" field duplicate values.