Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Summary
ClinSpark takes a very conservative approach to modifications that need to be made to locked sample path configurations. This is due to the implications that pathway changes have to barcodes, samples waiting to be collected against an activated activity plan, and collected samples that are still being processed under their original pathway. However, sometimes there are scenarios related to protocol or lab manual changes that must address structural changes to sample pathways after they’ve been made part of an activated activity plan.
Synchronize Samples
Within a sample path configuration, there is a ‘Synchronize Samples’ feature which is designed to allow sites a way to recover from and adapt to late minute sample path changes. Under synchronization scenarios, all transfer barcodes related to the updated sample path must be reprinted. Sites must react to this depending on their operational workflows for barcode printing. Some sites chose to print these barcodes ahead of time, while others do-so at time of collection.
...
This action is reserved for when structural changes have been applied to the sample path after activity plan activation.
This action is only available to users once a sample path has been put into a locked state.
This action will recreate new barcodes for each transfer stepsstep.
Upon synchronization, an audit is stored for each relevant sample, and the event is audited with the given sample path.
If the ‘Include Collected Samples’ option is chosen, all processed steps for the relevant samples will be removed.
If the ‘Recreated Sample Data Items?’ option is unchecked, the sample path data items will not be recreated immediately. This is useful when if a path will be unlocked and steps will be removed.
...
Changes That Require Sample Path Synchronization
When structural changes are made to a sample processing path, those changes can be pushed through to uncollected samples for already-active cohort assignments These changes include:
Sample Path Settings
Editing Specimen Containers
Applies to uncollected samples
Barcode labels may need to be reprinted, as barcode numbers may change
Step Settings
Adding New Steps
Applies to uncollected samples and collected samples which have not yet encountered the added step(s)
Transfer Material Settings
Editing Transfer Material Specimen Containers
Applies to uncollected samples
Barcode labels may need to be reprinted, as barcode numbers may change
Adding New Transfer Materials
Applies to uncollected samples
Changes That Do Not Require Sample Path Synchronization
The following basic changes can be made to a sample processing path without requiring synchronization of the path:
Sample Path Settings
Editing Sample Path Name
Applies to uncollected, collected, and fully processed samples
Step Settings
Adding/Removing/Changing Device Requirements on Steps
Applies to uncollected samples and collected samples which have not yet encountered the edited device step
Editing Step Timing
The timing must not exceed the timing of the step proceeding the edited step
Applies to uncollected samples and collected samples which have not yet encountered the edited step
Editing Step Deviation Windows
Applies to uncollected samples and collected samples which have not yet encountered the edited step
Editing Step Warning/Urgent Seconds
Applies to uncollected samples and collected samples which have not yet encountered the edited step
Editing Step Instructions
Applies to uncollected samples and collected samples which have not yet encountered the edited step
Adding New Steps
Applies only to new Cohort Assignment activations, all previous cohort activiations will not be impacted unless the path is synchronized
Transfer Material Settings
Editing Transfer Material Name
Applies to uncollected, collected, and fully processed samples
Editing Transfer Material Instructions
Applies to uncollected samples and collected samples which have not yet encountered the edited step
Editing Transfer Material External Barcode Requirements
Applies to uncollected samples and collected samples which have not yet encountered the edited step
Adding New Transfer Materials
Applies only to new Cohort Assignment activations, all previous cohort activations will not be impacted unless the path is synchronized
Associating a New Sample Path with an Item
Applies only to new Cohort Assignment activations
Example Scenarios
Now let’s see how this may be used in practice, we can follow some examples.scenarios:
Scenario 1 - Modifying Steps from a Sample Path & Recreating Sample Data
Let’s assume that a trial has begun with sample collection done against a locked path configuration. Some samples have already been processed for that study, while others are awaiting collection/processing. However, a structural change needs to be made where sample transfer tasks need to be removed from an existing pathway. Those structural changes need to propagate over to the samples waiting to be collected against already activated activity plans.
...
When using the ‘Synchronize Samples’ features in this use case, all changes to those existing collection timepoints are made in an audited fashion. Further, any previously printed transfer barcodes related to the sample path must be re-printed.
Scenario 2 - Reprocess Collected Samples
Under rare scenarios, it may be necessary to entirely reprocess samples that have already been collected against a particular pathway. The synchronization feature can support this need whether or not structural changes have happened to the pathway in question.
...
Users must be aware that selecting the ‘Include Collected Samples?’ setting during synchronization will remove all processed steps for existing samples . This occurs in an audited fashion. Once finished, those samples will go back to their original collected state and return for processing within the Samples > Processing areaand be recreated in the Samples > Processing module for reprocessing. Therefore, the ‘Include Collected Samples’ checkbox should be used with extreme caution. Note: an audit trail will be maintained in the Samples > Manage module for already-processed samples, thereby maintaining access to the ‘original’ processing details even after this style of synchronization.
In addition, samples which have been packaged into containers in the Samples > Packaging module will be removed from their containers upon performing this style of synchronization. However, samples which have already been shipped will remain unaffected by this style of synchronization.
Recommended Testing of Synchronized Changes
Due to the implications this feature has to sample processing data integrity, it’s recommended to try this feature set first in a TEST environment in a controlled manner. Staging the current pathway configuration, changes, and expected results against mock data is the best way to see if desired results are met.