Y26-244 - Ultima Library Conversion - Ultima Sample sheet changes

[andrewsparkes]

User story

You can print Ultima Sample Sheets from the Sequencing batch screen. Currently the application type in the Samples Sheets is fixed. This story is to enable the setting of the application preset / type dynamically based on what has been selected in the Submission.
We also need an extra field in the Sample sheet for the specific application type 'Flex Apex v2'.
And there are differences between UG100 and UG200 samples sheets, as UG200 does not understand all the application types yet.

Who are the primary contacts for this story

Mike Q

Who is the nominated tester for UAT

Mike Q or nominated tester

Acceptance criteria

Consider if these features can be featured flagged to decouple testing and deployment.
To be considered successful the solution must allow:

• Sample sheet creation uses the submission value for application type via the requests / orders.
• UG100 understands most of the Application types, for UG200 we have to change most to 'Unprocessed  CRAM'
• For the 'Flex Apex v2' application type, we use it normally for UG100, but we need to set application type to 'Unprocessed  CRAM', and also add an extra field called 'barcode_schema' to value 'ug_efficient_tt' so the machine understands what to do with the special primers used with this type (see Mike's spreadsheet 'January2026 Ultima applications and library conversion primers'
• Check not breaking sample sheet creation for existing sequencing batches

Dependencies

This story is blocked by the following dependencies:
Submissions and pipeline(s) need to be functioning to get this far.
Submission templates in story here
Manual pipeline story here
High throughput pipeline config story
Sequencing batch for Ultima also needs to be working.

References
This story has a non-blocking relationship with:
None

Additional context

Deployment notes
Nothing special as long as sample sheets still work for existing sequencing batches.

[TWJW-SANGER]

I think the following acceptance criteria could be clearer and/or split up:

1. UG100 understands most of the Application types, for UG200 we have to change most to 'Unprocessed CRAM'.

Most but not all - how to we evaluate success?

2. For the 'Flex Apex v2' application type, we use it normally for UG100, but we need to set application type to 'Unprocessed CRAM', and also add an extra field called 'barcode_schema' to value 'ug_efficient_tt' so the machine understands what to do with the special primers used with this type (see Mike's spreadsheet 'January2026 Ultima applications and library conversion primers'

The first part possibly overlaps with the previous criteria.
Also I'm not sure you can add a field to a value?
Could this be rewritten to "Sample sheets for the 'Flex Apex v2' application type include a new field 'barcode_schema' populated with the value 'ug_efficient_tt'. See example in Additional Context" ?

Check not breaking sample sheet creation for existing sequencing batches