Bug/defectin CodeFile editedand lostheaderformatOut ofscopeSapiobaselineissueIncorrectnaming ofcontrolsScenarionot inSOPMissingSamplesinworkflowToo manysamplesinworkflowWrongfileuploadedPassedwhen shouldhave failedCLS QCRandomsamples withsame nameas clinicalsamplesUser inwrongUserGroupWrongCLSStatussent to LD"R-scripterror" thatended upbeing usererrorWrongcell lineusedErrorcaused bymanipulatedstatusesSamplemissingfromWorkflowFailed whenshould havepassed CLSQCMissedcontrolreviewPermissionissuesSamplependinginfo not inCLS QCCompletedworkflowwhen itshould nothave beenUser didnot followSOPSamplename in filedoes notmatchsample in WFBug/defectin CodeFile editedand lostheaderformatOut ofscopeSapiobaselineissueIncorrectnaming ofcontrolsScenarionot inSOPMissingSamplesinworkflowToo manysamplesinworkflowWrongfileuploadedPassedwhen shouldhave failedCLS QCRandomsamples withsame nameas clinicalsamplesUser inwrongUserGroupWrongCLSStatussent to LD"R-scripterror" thatended upbeing usererrorWrongcell lineusedErrorcaused bymanipulatedstatusesSamplemissingfromWorkflowFailed whenshould havepassed CLSQCMissedcontrolreviewPermissionissuesSamplependinginfo not inCLS QCCompletedworkflowwhen itshould nothave beenUser didnot followSOPSamplename in filedoes notmatchsample in WF

IDg Bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
  1. Bug/defect in Code
  2. File edited and lost header format
  3. Out of scope
  4. Sapio baseline issue
  5. Incorrect naming of controls
  6. Scenario not in SOP
  7. Missing Samples in workflow
  8. Too many samples in workflow
  9. Wrong file uploaded
  10. Passed when should have failed CLS QC
  11. Random samples with same name as clinical samples
  12. User in wrong User Group
  13. Wrong CLS Status sent to LD
  14. "R-script error" that ended up being user error
  15. Wrong cell line used
  16. Error caused by manipulated statuses
  17. Sample missing from Workflow
  18. Failed when should have passed CLS QC
  19. Missed control review
  20. Permission issues
  21. Sample pending info not in CLS QC
  22. Completed workflow when it should not have been
  23. User did not follow SOP
  24. Sample name in file does not match sample in WF