Opened 10 years ago

Closed 10 years ago

#379 closed task (fixed)

Create "virtual" samples for cases when no specimen is received

Reported by: Nicklas Nordborg Owned by: Nicklas Nordborg
Priority: critical Milestone: Reggie v2.5
Component: net.sf.basedb.reggie Keywords:


This use case has always been a bit awkward to handle. The information that goes with the non-existing specimen (eg. PAD, operation date, etc.) has been added to the "Case" item that is the parent item to the (non-existing) specimen. This was ok when only a single non-existing specimen was associated with a case, but new routines may increase the likelihood that a single "Case" may be merged with more than one no-specimen event. This is messy and one will have to go back to the physical referral forms to know which PAD is associated with which date, etc.

So, the idea is that we should create a "virtual" sample with the subtype "NoSpecimen?" to represent events when no specimen is received. The annotations that are used for normal "Specimen" (eg. PAD, SamplingDate) should be used. This means that there is no longer any need for duplicating information on the parent "Case" item so the PADCase, SamplingDateCase, etc. are no longer needed.

A manual procedure is needed to fix already existing cases that has a no-specimen associated with them. Basically, one has to find all 'Case' items that has a value for ReasonIfNoSpecimen annotation. Then, a new child item with subtype 'NoSpecimen?' should be created and the PAD, and other information copied to it. This should be relatively easy for the majority of the cases which are not merged with other cases. This can probably be handled by batch importers. There are a few cases that are merged. Further investigation is needed before we know how to handle those.

Change History (3)

comment:1 Changed 10 years ago by Nicklas Nordborg

Status: newassigned

comment:2 Changed 10 years ago by Nicklas Nordborg

(In [1608]) References #379: Create "virtual" samples for cases when no specimen is received

I think this should work now, though I have probably not tested every possible scenario with respect to which order the various forms are registered.

In any case, when updating to this version it is important to complete the manual update procedure.

Last edited 10 years ago by Nicklas Nordborg (previous) (diff)

comment:3 Changed 10 years ago by Nicklas Nordborg

Resolution: fixed
Status: assignedclosed

Seems to be working now.

Note: See TracTickets for help on using tickets.