Using a Master Test Library

Forms See also

LIBMAN—LibMan Form

Maintaining Schemes

Maintaining Procedures

Overview

The Libman application is used to download schemes or procedures from a master test library and copy them into the local test library for the laboratory. Affectively, the test library are the tables associated with the Method schema.

The difference between the master and local test libraries is that the laboratories within the master represent types of laboratories (for example, gas, food, alcohol) as well as physical laboratories. The schemes in the master test library then act as template schemes for all the laboratories that use it. The master test library should contain all the laboratory codes as defined in the local test library since these may be required for the interchange of scheme analysis between the laboratories (using the SCHEME_REFER structure). That would be the only reason to define these in the master test library.

This process is pertinent to laboratory and QC managers who configure the analytical environment for the corporation and laboratory.

Process

The Libman application is designed to cater for master test libraries that exist as relational databases (SQL Server), or an XML file on the same or another database server as the CCLAS database. The database containing the master test library is defined by the RemoteDatabaseLocation LIBMAN program setting. Note that the remote database location may actually point to the local CCLAS database.

The Master Test Library for schemes and procedures is maintained under the Libman node of the Libman application.

The AccessLevel LIBMAN program setting controls user access to the Libman application.

Schemes

The AccessLevel LIBMANSCHEME program setting controls user access to the Libman » Schemes node.

Access schemes in the Master Test Library

Where the IgnoreLOB LIBMAN program setting is disabled, the list of available schemes is restricted to those with the same line of business as the laboratory code to which the current staff member is logged in.

The list of schemes displayed for downloading from the master test library are those that do not exist for the same scheme version in the local database, for the laboratory code to which the current staff member is logged in,

Also, where the ShowAllVersions LIBMANSCHEME program setting is enabled, then all versions a scheme are displayed from the master test library, and where disabled, then only the most recent version of a scheme is displayed.

Download schemes from the Master Test Library

When the schemes are downloaded:

  • The scheme record is downloaded to the SCHEME table in the local CCLAS database. The scheme's LABCODE is set to the laboratory code to which the current user is logged in, and the scheme's MLB_LABCODE is set to the master test library scheme's laboratory code.
  • Each comma-separated SCHEME table field listed in the SchemeBlankFields LIBMANSCHEME program setting is cleared.
  • The associated records for the scheme analytes are downloaded to the SCHEME_ANALYTE table in the local CCLAS database.
  • Each comma-separated SCHEME_ANALYTE table field listed in the SchemeAnalyteBlankFields LIBMANSCHEME program setting is cleared.
  • The associated records from the UNIT and ROUNDING tables are downloaded, unless they are listed in the SchemeAnalyteBlankFields LIBMANSCHEME program setting, in which case they are cleared. These unit and rounding records include those associated with:
    • SCHEME_ANALYTE.ANAUNITCODE
    • SCHEME_ANALYTE.REPUNITCODE
    • SCHEME_ANALYTE.TABLECODE
  • When rounding tables are imported, the conversion of dots to commas and vice versa is dependent upon the number format of the computer used to download the schemes.
  • The associated records from the SCHEME_REFER table are downloaded.
  • Audit records for the export are written in the master test library database, for the SCHEME, UNIT and ROUNDING table changes, to record what was downloaded, and by which staff member.
  • Audit records for the import are written in the local CCLAS database, for the SCHEME, UNIT and ROUNDING table changes, to record what was downloaded, and by which staff member.
Procedures

The AccessLevel LIBMANPROCREG program setting controls user access to the Libman » Procedures node.

Access procedures in the Master Test Library

Where the IgnoreLOB LIBMAN program setting is disabled, the list of available procedures is restricted to those with the same line of business as the laboratory code to which the current staff member is logged in.

The list of procedures displayed for downloading from the master test library are those that do not exist in the local database for the laboratory code to which the current staff member is logged in.

Download procedures from the Master Test Library

When procedures are downloaded:

  • The procedure record is downloaded to the PROCREG table in the local CCLAS database.
  • Each comma-separated PROCREG table field listed in the ProcRegBlankFields LIBMANPROCREG program setting is cleared.
  • The associated records for the procedure schemes are downloaded to the PROCREG_SCHEME table in the local CCLAS database.
  • Each comma-separated PROCREG_SCHEME table field listed in the ProcRegSchemeBlankFields LIBMANPROCREG program setting is cleared.
  • The associated records for the procedure scheme analytes are downloaded to the PROCREG_SCHEME_ANALYTE table.
  • Each comma-separated PROCREG_SCHEME_ANALYTE table field listed in the ProcRegSchemeAnalyteBlankFields LIBMANPROCREG program setting is cleared.
  • The associated records from the UNIT and ROUNDING tables are downloaded, unless they are listed in the ProcRegSchemeAnalyteBlankFields LIBMANPROCREG program setting, in which case they are cleared. These unit and rounding records include those associated with:
    • PROCREG_SCHEME_ANALYTE.ANAUNITCODE
    • PROCREG_SCHEME_ANALYTE.REPUNITCODE
    • PROCEREG_SCHEME_ANALYTE.TABLECODE.
  • When rounding tables are imported, the conversion of dots to commas and vice versa is dependent upon the number format of the computer used to download the schemes.
  • Where all schemes within the procedure are not contained within the local laboratory, then the schemes are also downloaded.
  • Audit records for the export are written in the master test library database, for the PROCREG, SCHEME, UNIT and ROUNDING table changes, to record what was downloaded, and by which staff member.
  • Audit records for the import are written in the local CCLAS database, for the PROCREG, SCHEME, UNIT and ROUNDING table changes, to record what was downloaded, and by which staff member.