Terminology
Void containers
- A 'container' that is used temporarily to collect a void that is added to a collection/storage container.
- These void containers are barcoded to ensure that the right void goes with the right collection for the right subject.
- Sometimes the same void container is used in an interval, or, new void containers are used for each void.
Interval (collection/storage) containers
- These are the interval containers 'jugs' that are used to store the void in (fridge, etc).
- The number of needed collection containers for an interval is unknown. If a subject is voiding a lot, they may need to add several collection containers to an interval.
Note
- Focuses on a simple urine collection interval process (e.g. does not include a 'clean catch')
- It's possible for there to be 0 (zero), 1 or several urine voids in an interval. Shorter intervals are unlikely to have many voids and longer intervals are unlikely to have 0 or few voids if kidney function remains unaffected and compliance is good
- Safety precautions and associated best practices are out of the scope of this workflow
- Attempts to design a process that does not require a urine monitoring log or a checker
Start Interval
# | ClinSpark Menu | Process |
---|---|---|
1 | Data Collection |
|
2 | Data Collection |
|
3 | Store container for use within the interval |
Urine Void in Interval
Note
A urinal (below left) has been used in the following examples, but may just as easily and interchangeably show a hat (below right).
# | ClinSpark Menu | Process |
---|---|---|
1 | Data Collection |
|
2 | Data Collection |
|
3 | Data Collection | then
Weight Sometimes weight is required for each void but not always
|
4 | Data Collection | Pour into
|
5 |
| |
6 |
| |
7 | Repeat as necessary until the end of the interval. |
End Interval
# | ClinSpark Menu | Process |
---|---|---|
1 | Data Collection |
|
2 | Data Collection |
|
3 | Data Collection |
|
4 | Sample Processing |
|
5 | Sample Processing |
|
6 | Sample Processing |
|
7 | Sample Processing |
|