Appendix B.docx
DOCX document 31 KB Posted
- Attached to
- Biosequence Search
- Solicitation number
- ACQ-27-0065
About this file
This file is an appendix containing current-state workflow tables documenting the existing processes for biological sequence searching and prior art analysis at the United States Patent and Trademark Office (USPTO). Table B-1 outlines the ten-step sequence search workflow, beginning with confirming searchable sequence listings and proceeding through case file review, identification of search-relevant sequence features, search path selection, search strategy development, search submission, status monitoring, results retrieval, results review, and application of results in examination. The workflow involves multiple systems and tools including PE2E-DAV, SLIC, ABSS (Automated Biological Sequence Search), STIC-EIC, and NCBI BLAST, with examiners and STIC-EIC personnel serving as primary actors. Key challenges identified include manual interpretation requirements, high manual burden in search strategy generation, tool selection dependencies on examiner experience, large and fragmented result files, and time-intensive alignment reviews.
Table B-2 describes the ABSS result review workflow comprising eight steps: organizing result files by database and query, reviewing summary tables to identify highest-level hits, assessing alignment displays for sequence feature correspondence, identifying duplicate records, linking hits to source references, comparing results across files, prioritizing references based on claim scope, and preparing outputs for examination use. Primary burdens and risks throughout this workflow include file fragmentation across databases, difficulty triaging large numbers of hits, labor-intensive alignment review processes, duplicate-heavy outputs, manual and time-consuming tracing from hits to underlying references, and the absence of automated ranking by legal relevance. These workflows serve as the baseline for the related RFI seeking next-generation biosequence search solutions utilizing Super Intelligence-assisted capabilities to improve efficiency and quality in patent examination.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Appendix A.docx | DOCX document | |
| Appendix C.docx | DOCX document | |
| RFI Attachment 3 - Question and Answer Sheet.xlsx | XLSX spreadsheet | |
| RFI Attachment 1 - RFI Response Template_v0.1.xlsx | XLSX spreadsheet | |
| Appendix D.docx | DOCX document | |
| ACQ-27-0065 - RFI Biosequence Tool.pdf | ||
| RFI Attachment 2 - Biosequence Search SOO.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Date: May 1, 2026 Appendix B. Current-State Workflow Tables Table B-1. Current-state sequence search workflow
| Workflow |
| Step No. |
| Step Name |
| Primary Actor |
| Systems / Tools |
| Key Inputs |
| Core Action |
| Key Output |
| Main Burden / Risk |
| Current-State Sequence Search Workflow |
| 1 |
| Confirm sequence listing is searchable |
| Examiner |
| PE2E-DAV, SLIC |
| Application number, sequence-listing status |
| Verify that a valid certified sequence listing is available for search |
| Searchable listing confirmed or issue identified |
| Searching cannot proceed if listing is defective or uncertified |
| Current-State Sequence Search Workflow |
| 2 |
| Review case file |
| Examiner |
| PE2E-DAV, sequence listing |
| Claims, specification, sequence listing, annotations, related file information |
| Review the application to understand the claimed subject matter and relevant sequence context |
| Initial understanding of claim scope and sequence issues |
| Case files may be lengthy, technical, and voluminous |
| Current-State Sequence Search Workflow |
| 3 |
| Identify search-relevant sequence features |
| Examiner |
| PE2E-DAV, sequence listing |
| SEQ ID NOs, fragments, percent identity language, fusions, variants, wildcards, modified residues |
| Determine what sequence embodiments and structural limitations must be searched |
| Search targets identified |
| Requires manual interpretation of technical and legal claim language |
| Current-State Sequence Search Workflow |
| 4 |
| Select search path |
| Examiner |
| ABSS, STIC-EIC 1600 request form, NCBI BLAST where permitted |
| Search targets, claim breadth, expected prior art context |
| Decide whether to use ABSS self-service, a customized STIC search request, textual searching, or a combination |
| Search path selected |
| Tool selection depends on examiner experience and search complexity |
| Current-State Sequence Search Workflow |
| 5 |
| Develop search strategy |
| Examiner |
| ABSS, STIC-EIC 1600 request form |
| Search targets, expected hit types, sequence type, database choices |
| Determine query groupings, search type, search parameters, and databases |
| Search instructions prepared |
| High manual burden; no automated search-strategy generation |
| Current-State Sequence Search Workflow |
| 6 |
| Submit search |
| Examiner or STIC-EIC 1600 |
| ABSS, STIC request form, SWFT |
| Search instructions |
| Run self-service search or submit customized search request |
| Search submitted and queued |
| Broad or complex cases may exceed normal limits or require special handling |
| Current-State Sequence Search Workflow |
| 7 |
| Monitor search status |
| Examiner |
| Email confirmation, SWFT, PE2E-DAV |
| Submission confirmation, workflow status |
| Track whether searches are running or completed |
| Search completion confirmed |
| Results may be posted at different times across files and databases |
| Current-State Sequence Search Workflow |
| 8 |
| Retrieve search results |
| Examiner |
| PE2E-DAV, GenBase UI |
| ABSS result files |
| Open result files by query and database |
| Results available for review |
| Multiple files may need separate review |
| Current-State Sequence Search Workflow |
| 9 |
| Review search results |
| Examiner |
| PE2E-DAV, GenBase UI |
| Summary tables, alignments, duplicate listings, identifiers |
| Manually review results to identify potentially relevant hits and references |
| Candidate prior art references identified |
| Result files can be large, repetitive, and difficult to triage |
| Current-State Sequence Search Workflow |
| 10 |
| Apply results in examination |
| Examiner |
| Examination record tools |
| Candidate references, search record |
| Document the search and use the references in examination |
| Search documented and examination proceeds |
| Requires translation of technical search output into examination use |
Table B-2. ABSS result review workflow
| Workflow |
| Step No. |
| Step Name |
| Primary Actor |
| Systems / Tools |
| Key Inputs |
| Core Action |
| Key Output |
| Main Burden / Risk |
| ABSS Result Review Workflow |
| 1 |
| Organize result files |
| Examiner |
| PE2E-DAV, GenBase UI |
| Result files by database and query |
| Open and organize all files associated with the search |
| Review set assembled |
| Files may be fragmented across databases and posting times |
| ABSS Result Review Workflow |
| 2 |
| Review summary tables |
| Examiner |
| PE2E-DAV, GenBase UI |
| Scores, query-match values, sequence identifiers, lengths |
| Identify the highest-level hits for initial triage |
| Preliminary list of hits |
| Large numbers of hits can obscure the most relevant references |
| ABSS Result Review Workflow |
| 3 |
| Review alignments |
| Examiner |
| PE2E-DAV, GenBase UI |
| Alignment displays, local similarity data |
| Assess how closely each hit corresponds to the claimed sequence features |
| Technical understanding of hit relevance |
| Alignment review is labor-intensive and repetitive |
| ABSS Result Review Workflow |
| 4 |
| Review duplicate records |
| Examiner |
| PE2E-DAV, GenBase UI |
| Duplicate listings, identifiers, dates |
| Determine whether multiple hits point to the same or related records |
| Duplicates grouped mentally by reviewer |
| Duplicate-heavy outputs increase review time |
| ABSS Result Review Workflow |
| 5 |
| Link hits to source references |
| Examiner |
| PE2E-DAV, GenBase UI, patent/publication sources |
| Sequence identifiers, accession numbers, patent identifiers |
| Trace hits back to the underlying references |
| Underlying documents identified |
| Moving from hits to references is manual and time-consuming |
| ABSS Result Review Workflow |
| 6 |
| Compare results across files |
| Examiner |
| PE2E-DAV, GenBase UI |
| Hits from multiple databases and queries |
| Consolidate overlapping or recurring references |
| Cross-file understanding of the result set |
| Relevant references may be spread across many files |
| ABSS Result Review Workflow |
| 7 |
| Prioritize references |
| Examiner |
| Examiner judgment |
| Consolidated result set, claim scope |
| Determine which references are most likely relevant to examination |
| Prioritized prior art set |
| No automated ranking by likely legal relevance |
| ABSS Result Review Workflow |
| 8 |
| Prepare for examination use |
| Examiner |
| Examination record tools |
| Prioritized prior art set |
| Incorporate relevant references into the search record and examination analysis |
| Examination-ready search output |
| Requires both technical and legal synthesis |
File details come from the government source that posted it. Updated .