• FEATURES
  • PRICING
  • MARKETPLACE
  • CASE STUDIES
  • BLOG
  • Configuring Specimen Label at Collection Protocol Level does not work

    Hi, Anyone tried the Configuring Specimen Label at Collection Protocol Level in OS 1.1RC3? It seems not working. I configured in the main page of collection protocol, it seems that the collection protocol is saved, but the new specimen still have the label empty.

    Thanks,
    jfeng

    Configuring on the main page of the Collection Protocol is for generation of labels for unplanned specimens. For planned specimens(configured at protocol level), you have to set up the label format at individual parent specimen requirement level. You can refer to “Planned Biospecimen Collection” protocol on demo site “http://demo.openspecimen.org/openspecimen/”. Please register yourself on home page for a free account.

    See attached screenshot where label format is defined as “CP_DEFAULT”. This will use same format as you specified on main page.

    We have improvised this in OS v2.0 where you don’t have to specify at individual requirement level if you specify on main page and you want same format.

    Thanks,
    Poornima

    problem solved. Thanks a lot.

    @pgovindrao Regarding specimen label configuration in general, it is possible to have automatic specimen label generation when collecting individual specimens within a SCG that has multiple anticipated specimens? For example, while automatic specimen label generation is possible when collecting specimens in bulk using the specimen summary view, automatic specimen label generation does not seem possible when collecting specimens individually using the specimen details view.

    Thanks,
    Matt

    Hi @Matthew_Marcetich,

    It should work from even individual specimen page if format specified in its corresponding requirement. It might have been a bug in older version, this works fine in v2.0.

    Thanks,
    Poornima

    Thanks @pgovindrao. We plan to test this in v2.0.

    Another specimen label configuration question:
    When using the event date token (%EVENT_DATE%), it appears this token functions as described in the wiki for parent specimens, though there have been times when it does not function for child specimens. For example: in the attached screenshot, the parent specimens use the corresponding SCG date for visit “SV2”, though the date for child specimens is today’s date (i.e. the date of data entry). In this case, we would like the event date token to insert the SCG date for the child specimens, which is a date other than today’s date.

    This has brought up another question: is there an ideal workflow in OpenSpecimen for creating child specimens in bulk on a date other than the date of parent specimen collection (i.e. if a parent specimen is stored and at a later date processed into derivatives)?

    Thanks,
    Matt

    Hello @Matthew_Marcetich,

    The event_date token is implemented to take the date from collection event, so it doesn’t work well for child specimens as you mentioned. The token has to be enhanced to take Creation Date for child specimens.

    On a side note, collection and received events are not applicable for child specimens. In previous version, they were copied over to children because it could not be queried. Now that query module allows hierarchical queries, we have removed this feature of copying events to child in v2.0.

    Thanks,
    Poornima