Use Case:
Participants and the pathology reports are stored in an external database. When user will be adding specimens into OpenSpecimen, the participants/visits will be searched within the OpenSpecimen database and if no match is found then in the external database.
If the match is found in the external database, the participant is registered in OpenSpecimen and the user then adds the samples collected.
Below mentioned code block, is to setup the visit lookup step. For searching the participants, MRN/EMPI can be used and for visits 'Visit name' or 'Accession Number'
| Code Block | ||
|---|---|---|
| ||
{
"name": "visitsLookup",
"data": {
"enable": true,
"matchTable": [
{
"name": "visit.name",
"baseField": "visit.name",
"caption": "Bank Number"
},
{
"name": "visit.visitDate",
"baseField": "visit.visitDate"
},
{
"name": "visit.surgicalPathologyNumber",
"baseField": "visit.surgicalPathologyNumber",
"caption": "Accession Number"
}
],
"searchAttrs": [
{
"attr": "EMPI_MRN",
"caption": "MRN"
},
{
"attr": "VISIT_NAME",
"caption": "Bank Number"
},
{
"attr": "SPR_NO",
"caption": "Accession Number"
}
]
}
} |
On setting up the above JSON for the CP, a new button on the participant list page will appear 'Search Visits'
On clicking 'Search Visits', user will be navigated to a page where participants/visits can be searched across OpenSpecimen and external database(configured)The configured fields will be displayed on the search visits page
On searching for a participant that has 2 visits added, OpenSpecimen will fetch both the visits in the results table. User can then select from these visits and add specimens to them. The fields added in the 'matchTable' section will be displayed as the columns in the results table.
On selecting one of the visits, user is navigated to a page that has all the fields configured for participant and visit. There are 2 options of editing the visit and adding specimens to the visit. If the participant has only visit then user is directly navigated to the visit page.
