Handle core biopsies

[Nicklas Nordborg]

Some patients may have a core biopsy taken at some time (typically a couple of months) before operation. In this case we may receive two sets of specimen under the same scan-b number. There will also be two sets of blood samples under the same number. To distinguish the two cases it has been decided that the barcode for the core biopsy-related forms should have a 'C' as suffix. This need to be handled by the various wizards. The specimen registration wizard should automatically set the BiopsyType=SpecimenCoreBiopsy annotation and the blood registration wizard need a new annotation type: BloodSample=PreNeo, PreOp

Both wizard also need to make sure that specimen and blood items are created with unique names, which means that they need to continue with the usual numerical suffixes from the last used index. Eg. the core biopsies are registered as NNNN.1, NNNN.2, and the regular specimen will then continue NNNN.3, NNNN.4 etc.

[Nicklas Nordborg]

(In [1614]) References #381: Handle core biopsies

The blood registration wizard should now support this. It can be enabled/disabled per site depending on settings in the new Site class. Currently, it is only enabled for Lund.

[Nicklas Nordborg]

(In [1622]) References #381: Handle core biopsies

Added support to the consent registration wizard and fixed blood registration wizard to also find consent-related and patient information in other blood samples for the same case (with or without 'C' suffix).

[Nicklas Nordborg]

(In [1623]) References #381: Handle core biopsies

Added support to the specimen and personal information registration wizards. Basic cases should be ok, but need more testing of the complex cases (eg. bi-lateral cases, merging cases, receiving forms out-of-order, etc.)

[Nicklas Nordborg]

(In [1625]) References #381: Handle core biopsies

Second blood sample suffix should be '.b2' (not '.b1').

[Nicklas Nordborg]

(In [1626]) References #381: Handle core biopsies

Do not link specimen with cases that have been registered to hold consent-information (for Yes) only since the case may have to be merged with another case once we know the patient information.

[Nicklas Nordborg]

Seems to be working as expected in all the common use cases that we can think of.