Introduction
OpenSpecimen allows specimens to be collected as per a specific event calendar for clinical trial-based protocols. This will enable you to pre-define specimens in CP and collect planned specimens as shown below:
However, this page does not have all the fields that might be required for a specific protocol and isn’t configurable. Using CP workflows configuration, you can configure additional fields to be captured after this step. You can configure any visit/specimen default and custom fields to capture value for them. Refer to the 'Collection Protocol Level Configuration' section to add workflow at the CP level.
The nth step works as an update option. The specimens are collected at the specimen collection page and only the values for the fields are updated in the nth step.
The below table explains different sections of the nth step:
Section | Details |
|---|---|
visitFields | If visit fields need to be displayed on the nth step, this section must be added. There will be only one section of this displaying one row for a visit being collected. |
fields | Within visitFields section, include all fields to be displayed in a table format within the 'fields' section of JSON. |
title | Title of each section/table in the nth step. |
fieldGroups | If fields need to be displayed in separate sections or tables, multiple sections can be within fieldGroups. For example: 'Primary Specimen details', 'Aliquot details' etc. Each section can have a title, criteria, and set of fields. |
criteria | This defines conditions for displaying fields in each section. For example 'Centrifuge event details' section can be displayed only for 'Whole Blood' & 'Primary' specimens. |
Example 1: Display Anatomic Site, Laterality, and Spun Event for Whole Blood Specimens
Example JSON to configure the setup that is shown in the above screenshot:
Example 2: Display ‘Processed By' and ‘Processed Time’ fields only for 'PBMC’ and 'Plasma' samples
Example JSON to configure the setup that is shown in the above screenshot:
Example 3: Display Concentration for Derived Specimens.
{
"name" : "specimenCollection",
"view" : null,
"ctrl" : null,
"data" : {
"defCollectionDate" : "current_date",
"fieldGroups" : [ {
"title" : "Derived Level",
"criteria" : {
"op" : "AND",
"rules" : [ {
"field" : "specimen.lineage",
"op" : "==",
"value" : "'Derived'"
}]
},
"fields" : [ {
"name" : "specimen.label",
"baseField" : "specimen.label",
"type" : "span"
}, {
"name" : "specimen.type",
"baseField" : "specimen.type",
"type" : "span"
}, {
"name" : "specimen.concentration",
"baseField" : "specimen.concentration",
"caption" : "Concentration"
}]
} ]
}
}
Example 4: Display Specimen Requirement Label
{
"name" : "specimen.reqLabel",
"baseField" : "specimen.reqLabel",
"caption" : "Specimen Requirement Name"
}
Example JSON to configure the setup that is shown in the above screenshot:
You need to add ‘specimen.reqLabel’ in the dictionary section as well before adding the field in the Nth step.
Example 5: Display Specimen Custom Fields on the nth step.
{
"name" : "specimenCollection",
"view" : null,
"ctrl" : null,
"data" : {
"fieldGroups" : [ {
"title" : "Surepath Solution Remarks",
"criteria" : {
"op" : "OR",
"rules" : [ {
"field" : "specimen.lineage",
"op" : "==",
"value" : "'New'"
} ]
},
"fields" : [ {
"name" : "specimen.label",
"baseField" : "specimen.label",
"type" : "span"
}, {
"name" : "specimen.extensionDetail.attrsMap.surepath_solution_remarks",
"baseField" : "specimen.extensionDetail.attrsMap.surepath_solution_remarks"
} ]
} ]
}
}
NOTE
The subform field is not supported in the nth step. This is because the sub-form is a 1:many relation with the main form, and it is not possible to display the 1:many field in the nth step.
A radio button is not supported on the nth step.
Once the workflow is uploaded, refresh your browser page once and then collect samples.
The nth step page will appear after the default specimen collection page.
Example 5: Display Specimen Custom Fields with selectively defaulted values
{
"name" : "specimenCollection",
"view" : null,
"ctrl" : null,
"data" : {
"showCollectionEvent" : false,
"showReceivedEvent" : false,
"defCollectionDate" : "current_date",
"fieldGroups" : [ {
"title" : "PB - Cryopreserved Cells",
"criteria" : {
"op" : "AND",
"rules" : [ {
"field" : "specimen.lineage",
"op" : "==",
"value" : "'Aliquot'"
}, {
"field" : "specimen.parentLabel",
"op" : ".indexOf('BCC') == ",
"value" : "0"
} ]
},
"enableCofrc" : false,
"fields" : [ {
"name" : "specimen.label",
"baseField" : "specimen.label",
"type" : "span"
}, {
"name" : "specimen.parentLabel",
"baseField" : "specimen.parentLabel",
"type" : "span"
}, {
"name" : "specimen.type",
"baseField" : "specimen.type",
"type" : "span"
}, {
"name" : "specimen.extensionDetail.attrsMap.cell_count",
"baseField" : "specimen.extensionDetail.attrsMap.cell_count",
"caption" : "Cell Count",
"defaultValue": "10.00"
} ]
}, {
"title" : "PB - Cell Pellet",
"criteria" : {
"op" : "AND",
"rules" : [ {
"field" : "specimen.lineage",
"op" : "==",
"value" : "'Aliquot'"
}, {
"field" : "specimen.parentLabel",
"op" : ".indexOf('BCP') == ",
"value" : "0"
} ]
},
"enableCofrc" : false,
"fields" : [ {
"name" : "specimen.label",
"baseField" : "specimen.label",
"type" : "span"
}, {
"name" : "specimen.parentLabel",
"baseField" : "specimen.parentLabel",
"type" : "span"
}, {
"name" : "specimen.type",
"baseField" : "specimen.type",
"type" : "span"
}, {
"name" : "specimen.extensionDetail.attrsMap.cell_count",
"baseField" : "specimen.extensionDetail.attrsMap.cell_count",
"caption" : "Cell Count"
} ]
}
}
Example 6: Display Specimen Custom Fields based for specific Specimen Types
Example 7: Close Parent Specimen on the nth step
Configure Visit Fields on the nth Step
The visit fields - 'Clinical Diagnoses', 'Clinical Status', 'Surgical Pathology Number' etc. are not displayed on the specimen collection page when collecting planned samples. The specimen collection page is currently not configurable to add visit level fields. These fields can be configured on the nth step and will be displayed only for planned specimens.
'visitFields' section is used to add visit fields on the nth step. You need to add the dictionary section as well before adding the fields in the Nth step.
{
"name": "specimenCollection",
"data": {
"visitFields": {
"title": "Visit Details",
"fields": [
[ {
"name" : "visit.status",
"baseField" : "visit.status"
}, {
"name": "visit.name",
"baseField": "visit.name",
"type": "span",
"width": "150px"
}, {
"name": "visit.clinicalDiagnoses",
"baseField": "visit.clinicalDiagnoses",
"width": "200px"
}, {
"name": "visit.comments",
"baseField": "visit.comments",
"width": "200px"
}
]
]
},
"fieldGroups": [ {
"title": "Frozen Event",
"criteria": {
"op": "AND",
"rules": [ {
"field": "specimen.specimenClass",
"op": "==",
"value": "'Tissue'"
}
]
},
"fields": [ {
"name": "specimen.label",
"baseField": "specimen.label",
"type": "span"
}, {
"name": "specimen.type",
"baseField": "specimen.type",
"type": "span"
}, {
"name": "events.SpecimenFrozenEvent.time",
"baseField": "specimen.events.SpecimenFrozenEvent.time"
}, {
"name": "events.SpecimenFrozenEvent.user",
"baseField": "specimen.events.SpecimenFrozenEvent.user"
}, {
"name": "events.SpecimenFrozenEvent.frozenMethod",
"baseField": "specimen.events.SpecimenFrozenEvent.frozenMethod"
}
]
}
]
}
}
Hide Fields/Table on Specimen Collection Page (v7.1)
The idea is to allow CP admins to hide the columns/tables whose values are derived from the other field values displayed on the screen and submit them to the backend/API.
Example: Processing event information for child specimens needs to be derived from its parent specimen automatically
Previously, to achieve that, you would have to show that fields/table in the step. As a resolution, now you will be able to hide the fields and tables on the step.
Before hiding the 'Aliquot: Processing Details' section on the specimen collection page:
After hiding the 'Aliquot: Processing Details':
Example JSON to configure the setup that is shown in the above screenshot:
Show/Hide Visit, Collection, and Received Event Fields (v7.1)
Use-Cases
Sometimes specimens are collected in the clinic but not yet received by the biobank when the clinic staff enters the details. So the received event is not needed on the specimen collection page.
Collection times are different for each primary specimen. So instead of collecting one time for all, you will collect different times in the nth step.
The options are to be added in the “specimenCollection” section of the workflows JSON as illustrated below:
{
"name": "specimenCollection",
"data": {
"showVisitDetails": false,
"showCollectionEvent": false,
"showReceivedEvent": true,
"defReceiveQuality": "To be Received", //defaults received qualtity to 'To be Received'
"defCollectionStatus" : "Collected", //defaults collection status to 'Collected'
"defCollectionDate" : "current_date", // (v8.1) defaults collection and received dates to current date. The supported values are none, current_date and visit_date.
...
}
}
The above configuration hides visit fields, collection event fields, and displays the received event fields. When the above configuration is not present, all the fields are displayed by default.
From v8.1, the collection and receive dates would be blank by default. You can set the collection and receive dates as below:
Code | Description |
|---|---|
defCollectionDate = 'visit_date' | The common collection and receive dates will be the same as whatever is populated in the visit date field. |
defCollectionDate = 'current_date' | The collection and receive dates will be the current/present date/time. |
defCollectionDate = 'none' | You are forced to select a date for collection and received fields. |
Screenshot before configuration:
Screenshot after configuration:
Example JSON to configure the setup that is shown in the above screenshot:
Remove the default visit date(v10.0)
{
"name": "specimenCollection",
"data": {
"defVisitDate": "none"
}
}
Once you added the above code "defVisitDate": "none" in the "specimenCollection section”, you can see the visit date field empty. OpenSpecimen will ask the user to enter the date to proceed further.
Display Specimen Events at the nth Step
You can display specimen events at the nth step like frozen event, fixed event, spun event, etc at the nth step.
Example: Display Frozen Event for Whole Blood Specimens
Example JSON to configure the setup that is shown in the above screenshot: