Quick snapshot of your current chain of identity

• How many active autologous patients or treatment streams is your program managing right now? Options: 1-10, 11-50, 51-200, 201-500, 500+
• Which roles own chain-of-identity decisions day to day in your organization? Options: VP Quality/QA, Head of Manufacturing, Clinical Operations Lead, Lab Manager, IT/Integration Lead, Supply Chain/Logistics, Other
• List the systems that currently record sample identity and custody across your workflow Options: LIMS, EHR, Courier TMS, Spreadsheet or shared drive, Paper logs, Laboratory instrument software, Other
• Tell me about the physical labels, tags, and identifiers you use from collection through infusion
• When was the last time a near-miss or identity discrepancy occurred, and what happened
• If an identity error were proven, which site or process would regulators question first Options: Collection sites, Courier handoffs, Manufacturing floor, Local treatment center, Data reconciliation and records, Other

Where identity problems actually surface

• What single identity failure in your recent work would force you to pause enrollment or production
• How often do you see scanning or labeling errors during a typical month Options: Daily, Weekly, Monthly, Quarterly, Rarely/never
• When a near-miss happens, how quickly is it detected and by whom Options: Immediate at collection, During transport, At receipt in manufacturing, During QC testing, Post-release
• Estimate the direct and program-level consequences when an identity event reaches regulatory attention
• Who on your team manages escalation and documentation remediation when chain-of-identity gaps are found Options: QA, Clinical Ops, Manufacturing Ops, Regulatory Affairs, Site PI, Other
• At what point would leadership halt the program due to identity or traceability concerns Options: Any confirmed mix-up, Significant documentation gaps, Repeated near-misses, Failure during FDA inspection, Other

Assumptions that will surprise you during rollout

• Tell me which assumption about your clinical sites or couriers is most likely to break during a rollout
• Give a count of different label templates or printers in use across your sites Options: Single standardized template, 2-5 variants, 6-15 variants, More than 15, Unknown
• Are there sterile environment rules that restrict scanner models or hardware at collection or manufacturing sites Options: Yes, scanner restrictions, Yes, packaging or gowning rules, No major restrictions, Unknown
• Who signs off on changes to labeling or chain-of-custody documentation at each site Options: Local site PI, Clinical Operations, QA, Supply Chain, Other
• Describe any courier chain-of-custody handoff steps that are paper based and cannot be modified
• If a site cannot accept a hardware change because of policy, which constraint would force you to drop that site from a pilot Options: Sterile field rules, Network access denial, Regulatory refusal, Staff refusal, Other

The other ways you might try to solve this

• Imagine you stayed with your current tracking approach, what conditions would make that acceptable
• Select the alternatives you are actively evaluating right now Options: Manual labels and paper chain-of-custody, In-house tracking tool or custom app, Extend existing LIMS module, Commercial patient identity platform, Courier-provided tracking, Other
• Has anyone proposed building an internal tracking solution instead of buying one Options: Yes, formal proposal, Yes, informal plan, No, Unsure
• Estimate the timeline and headcount an internal build would need to reach your compliance requirements
• Name the category of tool you would prefer to keep if it could be extended to cover traceability Options: Existing LIMS, EHR module, Internal barcode app, Third-party logistics tool, Paper process, Other
• Name the outcome that would push you to select an external vendor this quarter instead of continuing internally Options: Faster time to compliance, Lower total cost, Regulatory confidence, Proven zero-mix-up track record, Other

What success looks like for QA and regulators

• What single metric would make QA and your regulators comfortable enough to approve full deployment after a pilot
• Select from these metrics the ones you are currently tracking for chain of identity or sample traceability Options: Mix-up incidents, Near-miss frequency, Time to reconcile, Percent traceable steps, Audit findings, Time from collection to infusion, Other
• List the target values you would set for those metrics during a 3-month pilot
• Identify the roles that must sign regulatory acceptance at site and program level before go-live Options: VP QA, Head of Manufacturing, Clinical Operations Director, Site PI, Regulatory Affairs, Other
• Describe your current process for compiling traceability evidence for inspections and indicate its completeness
• Name the internal process that would trigger purchase and deployment within four weeks after a successful pilot Options: Expedited procurement, Existing budget allocation, Leadership sign-off, Regulatory clearance, Other

Integration gates that will make or break the build

• Point to the integration failure that would stop this project before deployment
• Select the systems that must be integrated for a meaningful pilot Options: LIMS, EHR, Courier TMS, Inventory management, Label printers, RFID middleware, Other
• Are API endpoints available for those systems and is an owner assigned Options: APIs available, owner assigned, APIs available, owner not assigned, APIs not available, Unknown
• Do you have a test environment for each system that can be used within a 4-week window Options: All test environments available, Some available, None available, Unknown
• Rate the readiness of legacy tracking data for mapping and migration Options: Ready and documented, Partial, requires cleaning, Poor quality, Unknown
• Can your IT or integration owner provide credentials and endpoint access within 4 weeks to start integration work Options: Yes, Yes, with conditions, No, Unsure

People, training, and validation, who actually runs the system

• Identify the person or role most likely to veto rollout because the workflow adds operational burden
• Provide a range for how many staff per site would require hands-on training for scanning and chain-of-custody procedures Options: 1-5, 6-15, 16-50, More than 50, Unknown
• List the teams that own validation protocols and documentation for new systems at your sites Options: QA, Validation team, Clinical Ops, Manufacturing Ops, Site QA, Other
• Select the typical validation window from IQ/OQ to PQ for a system of this type Options: 2-4 weeks, 1-2 months, 3-6 months, Longer than 6 months, Unknown
• Explain the impact of staff turnover at collection sites and treatment centers on training and consistent practice
• Would you commit the required validation owner and staff time to run an on-site pilot within the next quarter Options: Yes, No, Maybe with more information

Timeline, budget gates, and deal triggers

• Name the regulatory or audit finding that would stop this project immediately
• Select your target window to complete a pilot and reach a go or no-go decision Options: 4 weeks, 8 weeks, 3 months, 6 months, No fixed timeline
• Indicate the budget cycle or approval gates that would influence whether you sign in the next quarter Options: Current budget available, Needs next budget cycle, Capital approval required, Contract limits, Other
• Assuming the pilot reduces near-misses measurably, identify who has authority to approve enterprise rollout Options: VP QA, CRO, Head of Manufacturing, CEO, Other
• Are there scheduled inspections or audits in the next six months that constrain deployment timing Options: Yes, regulatory inspection, Yes, internal audit, No, Unsure
• Provide the earliest possible phased rollout date your team could commit to after pilot success and regulatory sign-off Options: Immediately, Within 1 month, 1-3 months, 3-6 months, Longer

• Solution Experience Session

• Confirm the current state and its cost to your team
• You confirm the demonstrated workflow eliminates the manual reconciliation and handoff ambiguity described in Discovery.
• Produce a tailored proof-of-concept plan that maps your workflows to test scenarios, hardware and integration needs, and clear success metrics.
• You agree the platform's failure handling closes the regulatory and patient-safety consequences you identified.
• Walk through a full collection-to-infusion workflow using your example data
• Provide two representative near-miss scenarios and anonymized sample records from clinical site, courier, and manufacturing handoffs for PoC testing.
• Replay the near-miss failure scenario and show prevention and remediation
• You accept the proposed proof-of-concept scope and measurable success metrics for the next step.
• Confirm pilot sites, validation owners, and a target 6- to 12-week PoC window for scheduling.
• Validate that this outcome matches your needs
• Agree next evidence and pilot scope

• Solution Experience Session
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Assign and manage unique patient identifiers
• Provision and install barcode and RFID scanners
• Install sterile-environment scanner mounts and enclosures
• Configure electronic chain-of-custody logging
• Integrate platform with source LIMS and EHR endpoints
• Migrate legacy tracking and chain-of-custody records
• Configure role-based access and immutable audit trails
• Deploy courier handoff scanning and transfer logging
• Execute workflow qualification (IQ/OQ/PQ) and scanning validation
• Deliver staff training and standard operating procedures
• Generate audit-ready batch and treatment traceability documentation
• Provide go-live cutover and production support with SLA handover

Assign and manage unique patient identifiers

• Which identifier format do you require for patient-linked materials (numeric, alphanumeric, ISBT-128, UUID)? Options: Numeric, Alphanumeric, ISBT-128, UUID, Other
• How many identifier namespaces must be supported across your sites (clinical site, courier, manufacturing, treatment center)? Options: 1, 2-3, 4-6, 7+
• Who will be the authorized owner of identifier issuance and reconciliation at each site (role or department)?
• What matching rules should the platform use to link identifiers to your LIMS sample IDs and EHR patient IDs (exact match, barcode+DOB, manual reconciliation)? Options: Exact match, Barcode plus DOB, Fuzzy match with manual review, Other
• Are there regulatory labeling standards or trial subject numbering schemes your identifiers must follow? Options: Yes, No
• Describe the identifier lifecycle you need: when should identifiers be generated, retired, or reissued across leukapheresis, manufacturing, and infusion?

Provision and install barcode and RFID scanners

• Which scanning technologies must be supported at each site (1D barcode, 2D barcode, passive RFID, active RFID)? Options: 1D barcode, 2D barcode, Passive RFID, Active RFID
• How many scanners do you estimate per collection room, manufacturing staging area, and infusion bay? Options: 1-2, 3-5, 6+
• Who is your facilities contact for receiving shipment, inventory tagging, and recording scanner serial numbers?
• What environmental constraints must scanners meet (sterile-field compatibility, cleanroom ISO class, chemical wipeability)? Options: Sterile-field compatible, Cleanroom-rated (ISO class), Chemical wipeable, Disposable-sleeve workflow, Other
• When must scanners be deployed relative to your validation windows (before IQ, before OQ, before PQ, by go-live)? Options: Before IQ, Before OQ, Before PQ, By go-live
• Describe your preferred scanner authentication and firmware update process (local USB, mobile device management, secured network push).

Install sterile-environment scanner mounts and enclosures

• What sterile-environment mounting options are required at collection and manufacturing (ceiling mount, wall mount with sealed enclosure, glove port pass-through)? Options: Ceiling mount, Wall mount with sealed enclosure, Glove port pass-through, Benchtop with sterile sleeve, Other
• Are there existing ceiling grid or wall structural constraints at your clinical and manufacturing sites that affect mount selection? Options: Yes, No
• Who will approve mechanical drawings and final mount placement (quality engineer, facility manager, clinical lead)? Options: Quality engineer, Facility manager, Clinical lead, Other
• How should mounts be cleaned and documented between patient procedures to align with your SOPs (chemical wipe, autoclave sleeve, disposable covers)? Options: Chemical wipe, Autoclave sleeve, Disposable covers, Other
• Provide the ISO cleanroom class and gowning requirements for rooms where mounts are installed.
• Where will scanner cabling terminate for power and network at each site (local network closet, PoE switch in room, Wi-Fi access point)? Options: Local network closet, PoE switch in room, Wi-Fi access point, Other

Configure electronic chain-of-custody logging

• What chain-of-custody events must be captured for each product movement (collection, dispatch to courier, receipt at manufacturing, release for infusion)? Options: Collection, Dispatch to courier, Receipt at manufacturing, Release for infusion, Other
• Which data fields must be recorded at each event (scanned ID, timestamp, operator ID, room ID, temperature snapshot)? Options: Scanned ID, Timestamp, Operator ID, Room ID/GPS, Temperature snapshot, Other
• How long must electronic chain-of-custody records be retained to satisfy your audit and regulatory needs? Options: 2 years, 5 years, 15 years, Custom
• Who will approve retention periods and access controls for chain-of-custody logs within your QA organization?
• What export formats are required for chain-of-custody evidence during inspections (signed CSV, audit PDF, EBR export)? Options: Signed CSV, Audit PDF, EBR export, Other
• Are there electronic signature or 21 CFR Part 11 requirements that must be enforced for custody confirmations? Options: Yes, No

Integrate platform with source LIMS and EHR endpoints

• Which LIMS and EHR systems must the platform integrate with at each site (provide system name and version)?
• What integration methods does each endpoint support (REST API, HL7 v2, FHIR, SOAP, secure file drop)? Options: REST API, HL7 v2, FHIR, SOAP, Secure file drop
• Who will provide API credentials, test accounts, and a point of contact for each endpoint owner?
• Which attributes must be exchanged with your LIMS/EHR per custody event (sample ID, patient ID mapping, lot number, event code)? Options: Sample ID, Patient ID mapping, Lot number, Event code, Other
• When are allowed maintenance windows for API testing and data sync with each endpoint? Options: Weekdays 9-5, Evenings, Weekends, Other
• What SLA for API latency and error recovery do you require during manufacturing-critical workflows (max acceptable round-trip time and retry policy)?

Migrate legacy tracking and chain-of-custody records

• How many legacy tracking records and historical chain-of-custody entries need migration (count or date range)? Options: Less than 1,000, 1,000-10,000, 10,000-100,000, 100,000+
• Which legacy record formats must be ingested (spreadsheets, paper scans, LIMS export CSV, custom database)? Options: Spreadsheets, Paper scans, LIMS export CSV, Custom database, Other
• Who will approve the field mapping between legacy records and the platform schema in your quality or IT team?
• What data quality thresholds must migration meet (duplicate rate, missing patient IDs, matching accuracy)? Options: >=99.9% identifier match, >=99% completeness, Custom
• What evidence will validate that legacy migration is complete and acceptable for regulatory inspection (sample reconciliation report, signed migration acceptance by QA, automated completeness report)? Options: Sample reconciliation report, Signed migration acceptance by your quality lead, Automated data completeness report, Other
• Are there PHI masking or encryption requirements for legacy records during transit and at rest? Options: Yes, No

Configure role-based access and immutable audit trails

• How many distinct user roles do you require for clinical, courier, manufacturing, and QA workflows? Options: 1-2, 3-5, 6-10, 10+
• Which actions must be restricted or require secondary sign-off (identifier issuance, release to infusion, custody transfer)? Options: Identifier issuance, Release to infusion, Custody transfer, Other
• Who will approve role definitions and segregation-of-duty exceptions within your organization?
• What retention and immutability controls are required to meet 21 CFR Part 11 and FDA inspection expectations (append-only logs, WORM storage, signed audit reports)? Options: Append-only logs, WORM storage, Signed audit reports, Other
• Are multi-factor authentication and single sign-on integration required for your user base? Options: MFA and SSO required, Only SSO, Only MFA, Neither
• Provide any role-mapping spreadsheets or HR directory artifacts we should ingest to automate account provisioning.

Deploy courier handoff scanning and transfer logging

• Which courier partners and handoff touchpoints are in scope for scanning (collection pickup, handoff to cold-chain vendor, arrival at manufacturing)?
• What handoff acceptance criteria must couriers confirm by scan (seal intact, temperature within range, matching patient ID)? Options: Seal intact, Temperature within range, Matching patient ID, Other
• How should couriers authenticate scans (courier app credentials, one-time PIN, shared device)? Options: Courier app credentials, One-time PIN, Shared device, Other
• Who will manage courier device provisioning, device retirement logs, and device serial reconciliation?
• What offline capture behavior do you require if courier connectivity is lost (local caching with delayed sync up to X hours)? Options: Cache and sync up to 24 hours, Cache and sync up to 72 hours, Real-time required
• Are chain-of-custody timestamps required to be tamper-evident and included in courier SLA metrics? Options: Yes, No

Execute workflow qualification (IQ/OQ/PQ) and scanning validation

• Which sites and workflow steps are in scope for IQ, OQ, and PQ testing (list clinical collection, manufacturing, infusion sites)?
• What scanning accuracy and read-rate thresholds must OQ/PQ tests demonstrate under typical clinical conditions (for example, >=99.9% read rate within 1 second)? Options: >=99.9% read rate within 1s, >=99.5% read rate within 2s, Other
• Who will approve and sign the validation protocol and the final validation report in your QA or validation team?
• What SOPs and test scripts from your quality systems must we use or incorporate during IQ/OQ/PQ validation?
• What defines done for IQ/OQ/PQ such that your QA will accept the deployment (signed validation report, passing test matrix, zero critical findings)? Options: Signed validation report, Passing test matrix as defined, Zero critical findings with documented remediation, Other
• How should failed validation scenarios be documented and remediated to meet your CAPA workflow? Options: Document with CAPA and retest, Document and accept with risk assessment, Other

Deliver staff training and standard operating procedures

• Which user groups require training and certification (clinical collectors, couriers, manufacturing technicians, QA reviewers)? Options: Clinical collectors, Couriers, Manufacturing technicians, QA reviewers, Other
• How many staff per site must be trained and certified to use scanners and the platform? Options: 1-3, 4-10, 11-25, 25+
• What training delivery modes do you prefer (on-site hands-on, remote instructor-led, e-learning modules, train-the-trainer)? Options: On-site hands-on, Remote instructor-led, E-learning modules, Train-the-trainer
• Who will be responsible for issuing training completion certificates and maintaining training records?
• What retraining interval do your SOPs mandate following process changes or validation failures (annually, after changes, other)? Options: Annually, Every 2 years, After changes, Custom
• Are there competency checklists or observed practice forms we should use for staff sign-off? Options: Yes, No

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Order Form / Subscription Agreement
• Data Processing Agreement (DPA) / HIPAA Business Associate Addendum (BAA)
• Regulatory & Validation Responsibility Addendum
• Acceptance Testing and Go-Live Criteria
• Payment Schedule and Milestone Invoice Schedule
• Change Order Agreement
• Termination and Transition Agreement
• Warranty and Support Service Level Attachment

• Go-live health check (weeks 1-4)
• First measurement review (weeks 4-10)
• Acceptance gate and formal acceptance (around day 90)
• Quarterly success review (ongoing)

• Schedule the next quarterly review and circulate the metric pack at least five business days prior to the meeting.
• Restate acceptance criteria and targets
• Produce a documented acceptance decision that records pass/fail for each numeric target recorded in Solution Scope.
• Confirm the incumbent system is decommissioned or formally retained read-only with archived data and closed fallback processes.
• Agree remediation deliverables and a verification date for any conditional or failed criteria.
• Publish the formal acceptance record showing pass/fail per Solution Scope criterion and the buyer signatory statement.
• Execute the incumbent wind-down tasks including data archive verification and closure of legacy operational checklists.
• If conditional acceptance was issued, create a remediation tracker with concrete verification tests and target completion dates.
• Trend review of identity integrity metrics
• Confirm that identity mismatch rate and near-miss event count remain at or below the thresholds agreed in Solution Scope or that remediation plans exist for deviations.
• Ensure all regulatory validation items and documentation remain current and any outstanding items have owners and deadlines.
• Maintain a clear enhancement backlog with acceptance criteria and a scheduled delivery window for high-priority requests.
• Update the shared issues and enhancement channel with the meeting's prioritized backlog and expected release window for each item.
• Create a hardware replacement plan for any scanner models with repeated failures including inventory and procurement lead times.
• Re-confirm success criteria and owners
• Confirm all deployment checklist items are complete or have a documented remediation plan with dates.
• Establish which sites are in active use and which sites remain in validation-only state.
• Agree the remediation tasks and timelines required to reach the first measurement window.
• Publish the deployment validation summary including unresolved defects and target resolution dates.
• Schedule hands-on follow-up training at sites with under 80 percent staff completion within two weeks.
• Confirm and document the data sources that will supply metrics for the first measurement meeting.
• Confirm measurement method and data provenance
• Validate the accuracy of the reported identity mismatch rate and chain-of-identity completion rate and confirm they are derived from the agreed data sources.
• Document root-cause hypotheses for any metric gaps and a prioritized remediation plan with target dates.
• Confirm the timeline to the acceptance gate and the evidence package required for the acceptance meeting.
• Produce a metric extraction and calculation workbook showing raw logs, query scripts, and aggregation steps used to calculate each metric.
• Implement the agreed remediation tasks for top two root causes and record validation steps to demonstrate effect on metrics.
• Schedule the acceptance gate data freeze window and confirm which systems will be read-only during evidence capture.
• Deployment and migration validation status
• Open issue burn-down and regulatory items
• Present first-period metrics
• Present outcome data against each criterion
• Diagnose root causes for gaps
• Document pass/fail per criterion and acceptance decision
• Enhancement and backlog triage
• User onboarding and early usage patterns
• Agree corrective actions and timelines
• Open issues and blockers
• Incumbent system wind-down confirmation
• Operational risks and readiness checks
• Remediation and conditional acceptance plan
• Immediate remediation plan