General Operations

The information in this section is to help you access the CCLAS system for your laboratory, including:

  • Logging in to a laboratory—Access to the system requires a user to log in for an CCLAS session, log out, and change login credentials, if required.
  • Using the Home page—Set screen themes, maintain application favourites and widgets.
  • Using the screen interface—Become familiar with how the screen interface works.
  • Working with scope and codes—Understand how scope affects whether you can create or see org-scope or lab-scope entities, and restrictions placed on codes.

Logging in to a Laboratory

To log into CCLAS, you need a user account and password. When you log in, you are prompted for:

  • User code (which is not laboratory specific)
  • Password (which is validated against a LDAP account, and is not laboratory specific)
  • Laboratory (combo, with the default laboratory pre-filled in).

The level of access you have is dependent on your level of responsibility. As an example, a Laboratory Manager has the ability to validate data entry values, whilst a Laboratory Operator does not have that function.

Each user has a list of security permissions, each of which comprise a role and laboratory. A user can have multiple roles per laboratory. A security permission can comprise a role for all laboratories.

A role is a collection of rights to applications, methods and attributes.

When you log into a laboratory, each role applicable to you for that laboratory is overlaid to set your initial security permission such that, you obtain the highest (most power) access rights and permissions from all roles that you have for the laboratory:

  • If any role gives full access to an application, then full access is granted to that application.
  • If any role gives read-write access to a class attribute, then read-write access is granted to that attribute.
  • If any role gives full access to a class method, then full access is granted to that method.
  • Some methods allow for split-level operational security:
    • If an object is an org-scope object then only a user with a security level of 'Org Only' or 'Lab and Org' or 'Full' can execute that method. If an object is a lab-scope object then only a security level of 'Lab Only', 'Lab and Org' or 'Full' can execute that method.
    • As access levels are hierarchy based, if the user has roles with both 'Lab Only' and 'Org Only', then the user account acts like they have access level 'Lab and Org'.
    • If any role gives access level 'Lab and Org' to a method, then effectively, an access level of 'Full' is granted to that method. The PREFERENCE and SCRIPT class methods are an exception to this rule as they have multiple levels that are different to Lab and Org.
    • The following objects have methods (for example, Create, SaveAs, Update, Read, Search, Delete) which are implemented with split-level operational security:
      • Biofields
      • Canned Comments and Canned Comment Groups
      • Category Types and Categories
      • Clients, Client Addresses, Contacts, Contact Addresses, Projects, Client Quotes
      • Container Types
      • Cost Centres
      • Devices
      • Hazards
      • Instrument Groups
      • Methods and Method Accreditations
      • Products, Product Hazards, Product Specifications
      • Product Specification Groups
      • QC Masks
      • QC Types
      • Range Tables
      • Rounding Tables
      • Sample Handlings
      • Schemes, Scheme Version and Scheme Version Analytes
      • Scheme Groups
      • Specifications
      • Standards, Standard Lots and Specifications
      • Units

    The following objects and methods (specific methods) are implemented with split-level operational security:

    • Biofield: Approve, Unapprove and ImportBiofields
    • PriceBook: UpdatePrices
    • Product: Activate, Approve, Unapprove, Promote, Suspend, ImportPRoducts
    • Scheme: Approve, Unapprove, ImportSchemes
    • Specification: Activate, Suspend, Promote
    • SpecificationSchemeVersionAnalyte: CreateFromAnalyte
    • Standard: Activate, Deactivate, Promote, Suspend, Approve, Unapprove

Using the Home Page

The home page is where system message, favourites and history widgets are available.

Using the Screen Interface

This section explains some of the components you see when you use the screen interface. It also describes the functionality of the components and how they are used, including fields, grids, error messages, and so on.

Working with Scope and Codes

Some CCLAS entities are created above the organisation level, at the instance level. These entities are visible to all CCLAS users.

Many CCLAS entities are created either at organisation level or laboratory level—these are referred to as org-scope or lab-scope entities, respectively. Some CCLAS entities are created at laboratory level only.

Org-scope entities are visible to all users who log into a laboratory linked to the particular organisation, although some exceptions apply to price codes where an org-scope price code that is linked to an org-scope scheme or analyte is not visible until the laboratory enables the scheme for use in their laboratory. Lab-scope entities are visible to all users who log into the particular laboratory.

When you create any entity in CCLAS, its usage scope must be selected, after which, the usage scope cannot be changed. Depending upon the type of entity, it could have a scope of either:

  • Outside of the organisation and laboratory, at instance level—These entities are visible to all users regardless of the Laboratory that the user logged into for the session.
  • Organisation-scope—These entities are only visible to a user who is logged into any laboratory within the organisation.
  • Laboratory-scope—These entities are only visible to a user who is logged into the laboratory.