This page provides an index of help articles related to LIMS Static Data, and also gives some general guidance on how each object interacts with the others.
“Static data” forms the basis of all “test execution data” that’s generated. For some execution data such as Lab Tests, the static data provides a template for the Lab Results and Lab Inputs that Vault should create when a Lab Test is created, based on the effective Lab Method. Some execution data is used in conjunction with static data to produce new records, such as Lab Result Evaluations, which are created when comparing Lab Specification Criteria to Lab Results.
Static Data covers the following key areas in Vault LIMS:
About Static Data Build Order
Due to Vault LIMS version control, there is a prescribed order of operations when building your static data. The Result Definitions in your Lab Methods can be referenced in calculations as well as Lab Specification Criteria, so it is important to understand the impact a change may have on the rest of your static data.
- First, create your Lab Method, including the Result Definitions and any calculations, and move it to the Effective state type.
- Next, create your Lab Protocol, referencing effective Lab Methods from the Sample Definitions you add to the protocol, and, after qualifying any cross-method calculation variables, move it to the Effective state type.
- Finally, create your Lab Specifications, referencing a Material and an effective Lab Protocol, allowing you to create Lab Specification Criteria referencing Result Definitions from Lab Methods on its Sample Definitions.
- Before moving your Lab Specification to the Effective state type, ensure you have created mapping records that instruct LIMS which Country or Organization this Specification is for.
About New Effective Protocol Versions
Lab Specifications reference a specific protocol version, and the Lab Specification Criteria reference specific Sample Definitions within the protocol version. If you create a new protocol version and make it effective, moving the prior protocol version to Superseded, you must also update any Lab Specifications referencing the superseded protocol version, ensuring your Lab Specification Criteria have been re-targeted to the correct Sample Definitions.
About New Effective Lab Method Versions
Lab Protocols contain Sample Definitions, which reference specific Lab Method versions. If you create a new Lab Method version and make it effective, moving the prior Lab Method version to Superseded, you will also need to update any protocols referencing the superseded Lab Method version.
If your Lab Method contains Result Definitions with cross-method variables, you will need to ensure the Protocol Variable Targets on your new protocol version are pointing to the correct Sample Definitions and Result Definitions.
These changes to your protocol require you to make changes to your Lab Specification and its Lab Specification Criteria.
For Static Data Admins to build a set of Vault LIMS static data and make changes where necessary, they must have a security profile or role which grants them Read, Create, and Edit permissions for the following objects and their related objects:
- Lab Method
- Lab Method Group (Read only)
- Lab Result Definition
- Lab Method Step
- Lab Protocol
- Lab Protocol Group (Read only)
- Lab Sample Definition
- Lab Sample Definition Method (also requires Delete permissions)
- Lab Specification
- Lab Specification Group (Read only)
- Lab Specification Criteria
- Lab Result Picklist
- Lab Result Picklist Option
In addition, Static Data Admins should have View permissions for the following objects in order to manage static data records:
- Unit of Measure
To view and manage calculation formulas, a user needs a permission set with View access to the Calculation Formula object control permission on the Lab Result Definition object.