# Managing Sequence Data for 16S rRNA Gene Identification ## Quick Answer - Store 16S rRNA sequence data in standardized formats like FASTA and FASTQ with unique identifiers to enable reproducible microbial identifications. - Apply quality filtering and trimming before database comparison, then document every parameter used in the analysis pipeline. - Sequence data interpretation requires professional judgment because database entries may contain misannotations or incomplete taxonomic information. ## At a Glance | Data Management Step | Primary Purpose | Common Output | Key Consideration | | --- | --- | --- | --- | | Raw sequence storage | Preserve original instrument output without alteration | FASTQ files with quality scores | Store on redundant media with checksums | | Quality filtering | Remove low-confidence bases and adapter contamination | Trimmed FASTA or FASTQ files | Record quality thresholds before analysis | | Database selection | Enable taxonomic assignment through reference comparison | BLAST or alignment results | Match database to sample type and target region | | Metadata curation | Link sequences to sample origin and processing history | Spreadsheet or database records | Maintain chain of custody for clinical or regulatory use | | Final identification report | Document the identification outcome and its confidence | Laboratory report with sequence and database match | Include limitations and escalation criteria | ## Scope and Purpose of Sequence Data Management The 16S rRNA gene is a conserved genetic target used to identify bacteria through sequence comparison. Laboratory personnel generate sequence data from cultured isolates or directly from clinical and environmental samples. The accuracy of the resulting identification depends on the quality of the sequence data and the integrity of the reference databases used for comparison. Poor data management practices can lead to misidentification, wasted resources, and incorrect conclusions in clinical or research settings. This article provides practical guidance for managing 16S rRNA sequence data across the laboratory workflow. The focus is on storage formats, quality control, database selection, metadata management, and documentation practices that support accurate and reproducible identifications. The guidance applies to diagnostic laboratories, research facilities, and educational settings where 16S rRNA sequencing is used for bacterial identification. ## Core Principles of 16S rRNA Sequence Data Management ### The Role of the 16S rRNA Gene in Bacterial Identification The 16S rRNA gene encodes a component of the bacterial ribosome and contains both conserved and variable regions. The conserved regions allow universal primers to amplify the gene across diverse bacterial species, while the variable regions provide sequence differences that distinguish taxa. Comparing an unknown sequence to a reference database allows laboratory personnel to identify the most closely related known species. The gene is approximately 1,500 base pairs in length, but many sequencing workflows target specific variable regions instead of the full gene. The choice of target region affects the resolution of the identification. Some species are difficult to distinguish using partial sequences, and the laboratory must recognize these limitations when reporting results. ### Sequence Data Formats and Their Uses Raw sequence data from modern sequencing platforms is typically stored in FASTQ format, which includes both the nucleotide sequence and a quality score for each base. After quality filtering and trimming, the data may be converted to FASTA format, which contains only the nucleotide sequence without quality scores. Both formats are plain text and can be stored in standard file systems. The choice of format depends on the stage of the workflow. Raw data should remain in FASTQ format to preserve quality information. Processed data used for database comparison can be in FASTA format. The laboratory should maintain both the raw and processed files to allow reanalysis if needed. ### Reference Databases and Their Limitations Reference databases contain 16S rRNA sequences from characterized bacterial strains. These databases are curated by different organizations and vary in their coverage and annotation quality. Some databases specialize in clinical pathogens, while others focus on environmental microorganisms. The choice of database affects the identification result. Database entries may contain errors in species names, and some entries are not associated with type strains. A type strain is a reference strain that defines a species. Sequences from type strains provide the most reliable basis for identification. The laboratory should verify that the database includes type strain sequences for the taxa of interest. ## Practical Workflow for Sequence Data Management ### Step 1: Establish a File Naming Convention A consistent file naming convention is the foundation of sequence data management. Each file name should include the sample identifier, the sequencing run identifier, and the date. The convention should be documented in the laboratory manual and followed by all personnel. A recommended format is: ``` [SampleID]_[RunID]_[Date]_[SequencingPlatform].fastq ``` For example: ``` CLIN-2024-00123_RUN-045_2025-01-15_MiSeq.fastq ``` The sample identifier should match the identifier used in the laboratory information system and the metadata records. This linkage allows the sequence data to be traced back to the original sample. ### Step 2: Preserve Raw Data Raw sequence data must be preserved without modification. The raw files serve as the permanent record of the sequencing run and allow the analysis to be repeated if needed. Raw data should be stored on a redundant storage system with regular backups. The laboratory should record the checksum for each raw data file. A checksum is a calculated value that changes if the file is altered. Recording checksums allows the laboratory to verify that the data has not been corrupted during storage or transfer. ### Step 3: Perform Quality Control Quality control is the process of assessing the quality of the sequence data before analysis. The quality scores in the FASTQ file indicate the probability that each base call is correct. Low-quality bases can lead to errors in the final identification. The laboratory should establish quality thresholds for the sequencing run. The thresholds should be based on the sequencing platform and the intended use of the data. The quality control step includes: - Reviewing the total number of reads generated - Assessing the quality score distribution across the reads - Checking for adapter contamination - Trimming low-quality bases from the ends of reads The quality control parameters should be documented in the analysis record. This documentation allows the analysis to be reproduced and the quality of the identification to be assessed. ### Step 4: Assemble and Trim Sequences For paired-end sequencing, the forward and reverse reads must be assembled into a single sequence. The assembly step requires the reads to overlap. The overlap length and the quality of the overlap affect the accuracy of the assembled sequence. After assembly, the sequence should be trimmed to remove low-quality regions and any remaining adapter sequences. The trimmed sequence is then used for the database comparison. The trimming parameters should be documented. ### Step 5: Compare Sequences to Reference Databases The trimmed sequence is compared to the reference database using a sequence alignment tool. The tool identifies the reference sequences that are most similar to the unknown sequence. The output includes the percent identity and the number of base differences between the unknown sequence and each reference sequence. The interpretation of the alignment results requires professional judgment. A high percent identity to a reference sequence supports the identification, but the laboratory must consider the length of the sequence and the quality of the reference entry. The laboratory should have a policy for the minimum percent identity and the minimum sequence length required for a confident identification. ### Step 6: Record the Identification and Its Limitations The final identification should be recorded in the laboratory information system. The record should include the sequence data, the database used, the alignment results, and the interpretation. The record should also note any limitations of the identification, such as the inability to distinguish between closely related species. The identification record should be reviewed by a second qualified individual before the result is reported. This review step provides a check on the interpretation and reduces the risk of reporting an incorrect identification. ## Metadata Management for Sequence Data ### The Role of Metadata in Data Interpretation Metadata is the contextual information that describes the sequence data. Metadata includes the sample source, the collection date, the sample type, the DNA extraction method, the primers used, and the sequencing platform. This information is essential for interpreting the sequence data and for reproducing the analysis. The laboratory should record metadata at the time of sample processing. Recording metadata at the time of processing reduces the risk of information loss. The metadata should be stored in a structured format, such as a spreadsheet or a database, and should be linked to the sequence data files. ### Metadata Fields for 16S rRNA Sequence Data The following metadata fields are recommended for each sequence: | Metadata Field | Description | Example | | --- | --- | --- | | Sample identifier | Unique identifier for the biological sample | CLIN-2025-001 | | Sample source | Origin of the sample | Blood culture | | Collection date | Date the sample was collected | 2025-03-10 | | DNA extraction method | Method used to extract DNA | Commercial kit | | Target region | Variable region of the 16S rRNA gene | V1-V3 | | Primer sequences | Sequences of the primers used for amplification | Forward and reverse primer sequences | | Sequencing platform | Instrument used for sequencing | Illumina MiSeq | | Analysis software | Software and version used for analysis | Software name and version | | Database used | Reference database and version | Database name and version | | Analyst | Person who performed the analysis | Analyst name | The metadata should be reviewed for completeness before the identification is reported. Missing metadata can prevent the identification from being reproduced or verified. ## Quality Control and Quality Assurance ### Quality Control of Sequence Data Quality control is the process of verifying that the sequence data meets the established quality thresholds. The quality control steps are performed during the analysis workflow and include the checks described in the workflow section. The laboratory should establish quality control procedures that are specific to the sequencing platform and the analysis pipeline. The procedures should be documented and followed consistently. The quality control results should be recorded for each sample. ### Quality Assurance of the Identification Process Quality assurance is the process of verifying that the identification process is working correctly. Quality assurance includes the use of control samples, the review of the identification results, and the participation in proficiency testing programs. Control samples are samples with a known identity that are processed alongside the unknown samples. The control samples verify that the entire workflow, from DNA extraction to sequence analysis, is working correctly. The control samples should be chosen to represent the types of bacteria that the laboratory expects to identify. The laboratory should also participate in proficiency testing programs. Proficiency testing involves the analysis of samples provided by an external organization and the comparison of the results with other laboratories. Proficiency testing provides an external check on the accuracy of the identification process. ### Documentation of Quality Control The laboratory should maintain records of the quality control results. The records should include the control sample results, the quality control parameters, and the review of the identification results. The records should be retained for a period that is consistent with the laboratory quality management system. The documentation should be sufficient to allow the identification process to be audited. An auditor should be able to trace a reported identification back to the sequence data, the quality control results, and the metadata. ## Database Selection and Management ### Criteria for Database Selection The choice of reference database is a critical decision in the identification process. The database should contain sequences from the types of organisms that the laboratory is expected to identify. The database should also be updated regularly to include newly described species. The laboratory should evaluate the database for the following criteria: - Coverage of the relevant taxa - Inclusion of type strain sequences - Quality of the sequence annotations - Frequency of database updates - Documentation of the database version The database version should be recorded for each analysis. The database version is necessary to reproduce the identification results. ### Database Curation and Updates The laboratory should have a process for updating the reference database. The update process should include the verification of the new database version and the documentation of the update. The update should be performed on a regular schedule. The laboratory should also consider the need to add sequences to the database. The laboratory may add sequences from local isolates that are not represented in the public databases. The added sequences should be verified and documented. ### The Risk of Database Errors The reference database may contain errors. The errors can be in the sequence or in the annotation. The laboratory should be aware of the potential for database errors and should verify the identification results when the identification is unexpected or when the identification is based on a limited number of database entries. The laboratory should also be aware that the database may contain sequences that are not associated with a type strain. The identification based on these sequences may be less reliable than the identification based on type strain sequences. ## Common Failure Patterns in Sequence Data Management ### Failure to Preserve Raw Data A common failure is the loss of raw data. The raw data may be lost due to storage failure, accidental deletion, or the failure to back up the data. The loss of raw data prevents the analysis from being repeated and the identification from being verified. The laboratory should implement a backup policy that includes the regular backup of raw data to a separate storage system. The backup policy should be tested to ensure that the data can be restored. ### Inconsistent Metadata Inconsistent metadata is another common failure. The metadata may be incomplete, or the metadata may not be linked to the sequence data. The inconsistent metadata prevents the identification from being reproduced and the results from being interpreted. The laboratory should use a structured metadata form and should review the metadata for completeness before the analysis is performed. ### Inappropriate Database Selection The use of an inappropriate database can lead to incorrect identifications. The database may not contain the relevant species, or the database may be outdated. The laboratory should evaluate the database selection and should document the database version. ### Overinterpretation of the Results The overinterpretation of the sequence comparison results is a common failure. The laboratory may report a species-level identification when the sequence data only supports a genus-level identification. The laboratory should have a policy for the interpretation of the results and should document the limitations of the identification. ## Biosafety and Laboratory Practice ### Biosafety Considerations for Sequence Data Management The management of sequence data does not involve the handling of infectious agents. However, the laboratory personnel who generate the sequence data may handle biological samples that contain infectious agents. The laboratory should follow the biosafety practices that are appropriate for the samples being processed. The biosafety practices include the use of appropriate personal protective equipment, the use of a biological safety cabinet when handling infectious agents, and the decontamination of the work surfaces. The laboratory should follow the guidance in the [Biosafety in Microbiological and Biomedical Laboratories](https://www.cdc.gov/labs/bmbl/index.html) for the appropriate biosafety level for the work being performed. ### Decontamination and Waste Disposal The laboratory should have a policy for the decontamination of the samples and the waste generated during the sequencing process. The decontamination policy should be consistent with the biosafety level of the laboratory and the nature of the samples. The laboratory should also have a policy for the disposal of the samples after the sequencing is complete. The disposal policy should be consistent with the applicable regulations and the laboratory quality policy. ## The Role of Professional Judgment and Escalation ### When to Escalate an Identification The laboratory should have a policy for the escalation of the identification results. The escalation is appropriate when the identification is uncertain, when the identification is unexpected, or when the identification has a significant impact on the patient or the public health. The escalation policy should define the criteria for escalation and the person to whom the results should be escalated. The escalation should be documented. ### The Role of the Laboratory Director The laboratory director is responsible for the overall quality of the identification process. The laboratory director should review the identification results and the quality control records. The laboratory director should also ensure that the laboratory personnel are trained and that the laboratory follows the professional standards. The [American Society for Microbiology](https://asm.org/) provides professional education and guidance for the laboratory practice. The laboratory personnel should be aware of the professional standards and should follow the guidance. ## The Role of Sequence Data in Antimicrobial Resistance Surveillance ### The Connection Between Identification and Resistance Testing The identification of the bacterial species is the first step in the management of the bacterial infection. The identification is followed by the antimicrobial susceptibility testing to determine the appropriate treatment. The [Clinical and Laboratory Standards Institute](https://clsi.org/standards/products/microbiology) provides the standards for the antimicrobial susceptibility testing. The sequence data can also be used to detect the genes that are associated with antimicrobial resistance. The detection of the resistance genes can provide information about the potential resistance of the organism. The [World Health Organization](https://www.who.int/health-topics/antimicrobial-resistance) provides the global context for the antimicrobial resistance surveillance. ### The Use of Sequence Data in Surveillance The sequence data can be used for the surveillance of the antimicrobial resistance. The surveillance programs collect the sequence data from the bacterial isolates and analyze the data to track the spread of the resistance. The sequence data can also be used to identify the emergence of the new resistance mechanisms. The laboratory that participates in the surveillance programs should follow the data management practices that are described in this article. The data management practices ensure that the surveillance data is accurate and reproducible. ## The Use of Authenticated Reference Strains ### The Role of Reference Strains in Quality Control The reference strains are the bacterial strains that are used for the quality control of the identification process. The reference strains should be authenticated to ensure that the strain is the species that it is claimed to be. The [American Type Culture Collection](https://www.atcc.org/) provides authenticated reference strains for the quality control. The reference strains should be used as the control samples in the identification process. The reference strains should also be used to verify the performance of the reference database. ### The Documentation of Reference Strains The laboratory should document the reference strains that are used for the quality control. The documentation should include the strain identifier, the source of the strain, and the date of the use. The documentation should be retained for the quality control records. ## The Use of Sequence Data in Food Microbiology ### The Application of 16S rRNA Sequencing in Food Microbiology The 16S rRNA sequencing is used in the food microbiology for the identification of the bacterial isolates from the food samples. The [Bacteriological Analytical Manual](https://www.fda.gov/food/laboratory-methods-food/bacteriological-analytical-manual-bam) provides the official methods for the food microbiology. The sequence data management practices that are described in this section apply to the food microbiology. The laboratory should follow the data management practices to ensure the accuracy of the identification results. ### The Quality Control in Food Microbiology The quality control in the food microbiology includes the use of the reference strains and the participation in the proficiency testing. The quality control ensures that the identification results are accurate and reproducible. ## Common Failure Patterns and Troubleshooting ### Failure Pattern 1: Low Quality Sequence Data The low quality sequence data can result from the poor DNA extraction, the degradation of the DNA, or the sequencing errors. The low quality data can lead to the incorrect identification. The troubleshooting steps include the review of the quality control results, the re-extraction of the DNA, and the re-sequencing of the sample. The laboratory should document the troubleshooting steps and the outcome. ### Failure Pattern 2: No Match in the Database The sequence may not match any sequence in the database. The lack of a match may indicate that the organism is not represented in the database or that the sequence is of poor quality. The laboratory should review the sequence quality and the database selection. ### Failure Pattern 3: Conflicting Identifications The sequence may match multiple species with the same percent identity. The conflicting identifications may be due to the limited resolution of the target region. The laboratory should report the identification at the genus level and should note the limitation. ## The Importance of Data Integrity for Regulatory Purposes ### The Regulatory Context for Sequence Data The sequence data may be used for the regulatory purposes, such as the identification of the bacterial contamination in the food or the clinical samples. The data integrity is the accuracy and the completeness of the data. The data integrity is important for the regulatory purposes. The laboratory should follow the data management practices that are described in this section to ensure the data integrity. The laboratory should also follow the applicable regulations for the data management. ### The Audit Trail for Sequence Data The audit trail is the record of the data processing steps. The audit trail should include the date and the time of the processing steps, the person who performed the steps, and the parameters that were used. The audit trail is important for the verification of the data. ## The Future of 16S rRNA Sequence Data Management The field of the 16S rRNA sequencing is evolving. The new sequencing platforms and the new analysis tools are being developed. The laboratory should stay current with the developments in the field. The laboratory should also be aware of the new databases and the new methods for the sequence analysis. The laboratory should evaluate the new methods and the new databases before the use. ## Building a Sequence Data Review and Correction Workflow ### The Need for a Structured Review Process Laboratory personnel often treat sequence data management as a one-way process where raw data moves through quality filtering, assembly, and database comparison before a final identification is recorded. This linear approach misses a critical control point. Sequence data files, metadata records, and database versions can contain errors that are not visible during routine processing. A structured review and correction workflow provides a formal mechanism for detecting and resolving these errors before they affect identification results. The review workflow described in this section is distinct from the quality control steps performed during initial analysis. Quality control assesses the technical quality of the sequence reads. The review workflow assesses the integrity of the entire data package, including the linkage between files, the completeness of metadata, and the reproducibility of the analysis. This distinction matters because a sequence can pass all technical quality thresholds while still being associated with incorrect sample identifiers, incomplete metadata, or an outdated database version. ### The Three Tier Review Structure A practical review workflow uses three tiers that match the risk level of the identification result. Tier one is the self-review performed by the analyst immediately after the identification is recorded. Tier two is the peer review performed by a second qualified individual before the result is reported. Tier three is the periodic audit performed by the laboratory director or a designated quality officer on a scheduled basis. Tier one self-review should occur within one working day of the analysis. The analyst verifies that the sample identifier in the sequence file matches the identifier in the metadata record. The analyst confirms that the database version is recorded and that the quality control parameters are documented. The analyst also checks that the raw data files are stored in the designated location and that the checksums match the recorded values. Tier two peer review should occur before the identification is reported to the requesting clinician or submitted to a surveillance program. The peer reviewer repeats the database comparison using the recorded parameters and verifies that the same identification is obtained. The peer reviewer also examines the metadata for completeness and checks that the limitations of the identification are documented. The peer review is documented with the reviewer name, the date, and the outcome. Tier three audits should occur at least quarterly. The auditor selects a random sample of completed identifications and traces each one from the raw sequence files through the analysis pipeline to the final report. The auditor verifies that the documented procedures were followed and that the records are complete. The audit findings are documented and any corrective actions are tracked to completion. ### The Correction Log and Its Structure The correction log is the central record of the review workflow. Every correction made to sequence data, metadata, or analysis records is documented in the log. The log is a separate file from the sequence data and is maintained in a location that is accessible to all laboratory personnel but protected from unauthorized modification. The correction log should include the following fields for each entry: | Field | Description | Example | | --- | --- | --- | | Correction identifier | Unique identifier for the correction | CORR-2025-014 | | Date of correction | Date the correction was made | 2025-04-02 | | Sample identifier | The sample affected by the correction | CLIN-2025-00123 | | Original value | The value before the correction | Sample ID CLIN-2025-00122 | | Corrected value | The value after the correction | Sample ID CLIN-2025-00123 | | Reason for correction | Explanation of why the correction was needed | Transcription error in sample label | | Person making the correction | Name of the individual who made the change | J. Smith | | Reviewer | Name of the individual who verified the correction | M. Johnson | | Impact on identification | Whether the correction changed the identification result | No change | The correction log serves two purposes. First, it provides a complete history of changes to the data. Second, it identifies patterns of errors that may indicate a need for additional training or a change in the workflow. For example, if the correction log shows repeated errors in sample identifier transcription, the laboratory should review the sample labeling procedure and consider the use of barcode scanning. ### The Correction Procedure The correction procedure follows a defined sequence of steps. The first step is to identify the error. The error may be identified during the self-review, the peer review, or the audit. The second step is to document the error in the correction log. The documentation includes the date, the sample identifier, the file affected, and the nature of the error. The third step is to determine the impact of the error. The impact assessment considers whether the error affects the identification result, the metadata, or the raw data. The impact assessment also considers whether the error affects other samples in the same sequencing run. If the error is in the sample identifier, the laboratory must check whether the error affects the linkage between the sequence data and the metadata. The fourth step is to make the correction. The correction is made to the metadata record or the analysis record. The raw sequence data is never modified. The raw data is the permanent record of the sequencing run and must be preserved without alteration. If the error is in the raw data file name, the file is renamed and the correction is documented. The original file name is recorded in the correction log. The fifth step is to reanalyze the data if the correction affects the identification. The reanalysis uses the corrected metadata and the same analysis parameters. The reanalysis result is compared to the original result. If the identification changes, the laboratory must notify the requesting clinician and issue a corrected report. The sixth step is to review the correction. The review is performed by a second qualified individual. The reviewer verifies that the correction was made correctly and that the impact assessment was complete. The review is documented in the correction log. ### The Verification of Database Versions The review workflow includes a specific check for database version control. The database version is recorded for each analysis. The review verifies that the recorded version is the version that was actually used. This verification is important because database updates can change the identification result. The laboratory should maintain a database version log. The log records the date of each database update, the version identifier, and the source of the update. The log also records any changes in the number of sequences or the taxonomy associated with the update. The database version log is reviewed during the tier three audit. The review also checks that the database version is appropriate for the sample type. A clinical laboratory that identifies pathogens should use a database that includes the relevant clinical species. A food microbiology laboratory should use a database that includes the relevant foodborne species. The database selection is documented in the analysis record and is reviewed during the peer review. ### The Reconciliation of Sequence Files and Metadata A common failure in sequence data management is the mismatch between the sequence files and the metadata records. The sequence file may contain the correct sequence, but the metadata may be associated with the wrong sample. The review workflow includes a reconciliation step that verifies the linkage between the sequence files and the metadata. The reconciliation step compares the sample identifiers in the sequence file names to the sample identifiers in the metadata records. The comparison is performed using a script or a manual check. The reconciliation also verifies that the number of sequence files matches the number of metadata records for the sequencing run. The reconciliation step is performed during the tier one self-review and the tier two peer review. The reconciliation results are documented in the analysis record. If the reconciliation identifies a mismatch, the mismatch is documented in the correction log and the correction procedure is followed. ### The Documentation of the Review Workflow The review workflow is documented in the laboratory quality manual. The documentation includes the review tiers, the review schedule, the correction log structure, and the responsibilities of the personnel. The documentation also includes the training requirements for the personnel who perform the reviews. The laboratory should maintain the review records for a period that is consistent with the laboratory quality management system. The review records include the correction log, the audit reports, and the documentation of the corrective actions. The review records are available for inspection by the regulatory authorities and the accreditation bodies. ### The Use of the Review Workflow for Training The review workflow provides a source of training material for the laboratory personnel. The correction log identifies the common errors and the patterns of errors. The laboratory director can use the correction log to develop the training sessions that address the specific errors. The training sessions should include the review of the correction log entries and the discussion of the root causes of the errors. The training should also include the practice of the review workflow using the sample data. The training is documented and the training records are retained. ### The Escalation of the Review Findings The review workflow includes the escalation criteria for the findings that require the attention of the laboratory director. The escalation is appropriate when the review identifies a systematic error that affects multiple samples, when the review identifies an error that affects the identification of a clinically significant organism, or when the review identifies a failure in the quality management system. The escalation is documented in the correction log and the laboratory director is notified. The laboratory director reviews the finding and determines the appropriate action. The action may include the corrective action, the additional training, or the revision of the procedure. The action is documented and the action is tracked to completion. ### The Integration of the Review Workflow with the Quality Management System The review workflow is integrated with the quality management system of the laboratory. The quality management system includes the policies and the procedures for the quality of the laboratory results. The review workflow is a component of the quality management system and is subject to the same review and the improvement processes. The laboratory director is responsible for the implementation of the review workflow. The laboratory director ensures that the personnel are trained in the review procedures and that the review is performed consistently. The laboratory director also ensures that the review findings are used to improve the laboratory processes. The [American Society for Microbiology](https://asm.org/) provides the professional education and the guidance for the laboratory practice. The laboratory personnel should be aware of the professional standards and should follow the guidance. The review workflow is a component of the professional practice and supports the accuracy and the reproducibility of the identification results. ### The Use of the Review Workflow for the Proficiency Testing The review workflow is also used for the proficiency testing. The proficiency testing involves the analysis of the samples provided by the external organization. The laboratory analyzes the samples and reports the results. The review workflow is applied to the proficiency testing samples in the same way that it is applied to the clinical samples. The review workflow verifies that the proficiency testing samples are processed with the same procedures and the same quality controls as the clinical samples. The review workflow also verifies that the proficiency testing results are documented and the results are reported correctly. The proficiency testing results are reviewed by the laboratory director and the results are used to assess the performance of the laboratory. ### The Limitations of the Review Workflow The review workflow is a practical tool for the data management, but it has the limitations. The review workflow cannot detect the errors that are not visible in the records. The review workflow cannot detect the errors in the reference database that are not known to the laboratory. The review workflow cannot detect the errors in the sequencing instrument that are not reflected in the quality scores. The laboratory should be aware of the limitations of the review workflow. The review workflow is a component of the quality management system, but it is not a substitute for the professional judgment of the laboratory personnel. The laboratory personnel should use the review workflow in combination with the professional judgment and the knowledge of the laboratory processes. The review workflow is also limited by the resources of the laboratory. The review workflow requires the time of the personnel and the storage for the records. The laboratory should balance the review workflow with the other demands of the laboratory. The review workflow should be designed to be practical and to provide the value for the effort. ## Frequently Asked Questions ### What is the difference between FASTA and FASTQ files? FASTA files contain only the nucleotide sequence, while FASTQ files contain the sequence and a quality score for each base. FASTQ files are used for the raw data, and FASTA files are used for the processed data. ### How should I name my sequence data files? Use a consistent convention that includes the sample identifier, the run identifier, and the date. The convention should be documented and followed by all laboratory personnel. ### What is the minimum percent identity for a species-level identification? The minimum percent identity depends on the target region and the database. The laboratory should establish a policy for the minimum percent identity and the minimum sequence length. ### How often should I update my reference database? The database should be updated on a regular schedule. The update schedule should be documented and the database version should be recorded for each identification. ### What should I do if my sequence does not match any database entry? Review the sequence quality and the database selection. The organism may not be represented in the database, or the sequence may be of poor quality. ### How do I document the metadata for my sequence data? Use a structured metadata form and record the metadata at the time of sample processing. The metadata should be linked to the sequence data by the sample identifier. ### What is the role of the type strain in the identification? The type strain defines the species. The identification based on the type strain sequence is more reliable than the identification based on the non-type strain sequence. ### When should I escalate an identification result? Escalate the result when the identification is not confident, when the identification is unexpected, or when the identification has a significant impact on the patient or the public health. ## Related Diagnostic Guides - [Safety in the Microbiology Laboratory: Essential Practices and Risk Mitigation](/knowledge/diagnostics/microbiology/safety-in-the-microbiology-laboratory-essential-practices-and-risk-mitigation) - [Microbiology Case Studies: Applying Laboratory Data to Patient Care](/knowledge/diagnostics/microbiology/microbiology-case-studies-applying-laboratory-data-to-patient-care) - [Laboratory Animal Models in Veterinary Virology](/knowledge/diagnostics/microbiology/laboratory-animal-models-in-veterinary-virology) - [Clinical Microbiology: From Specimen Collection to Pathogen Identification](/knowledge/diagnostics/microbiology/clinical-microbiology-from-specimen-collection-to-pathogen-identification) ## References and Further Reading - [Biosafety in Microbiological and Biomedical Laboratories](https://www.cdc.gov/labs/bmbl/index.html). CDC and NIH. - [Microbiology Resources](https://asm.org/). American Society for Microbiology. - [Antimicrobial Resistance](https://www.who.int/health-topics/antimicrobial-resistance). World Health Organization. - [Bacteriological Analytical Manual](https://www.fda.gov/food/laboratory-methods-food/bacteriological-analytical-manual-bam). U.S. Food and Drug Administration. - [Antimicrobial Susceptibility Testing](https://clsi.org/standards/products/microbiology). Clinical and Laboratory Standards Institute. - [Culture Collections](https://www.atcc.org/). American Type Culture Collection. - [Laboratory Biosafety Manual](https://www.who.int/publications/i/item/9789240011311). World Health Organization. - [NCBI Literature Resources](https://www.ncbi.nlm.nih.gov/). National Center for Biotechnology Information. - [Respiratory microbiota imbalance in children with Mycoplasma pneumoniae pneumonia.](https://pubmed.ncbi.nlm.nih.gov/37132354). Emerging microbes & infections, 2023. - [Utility of 16S rRNA PCR performed on clinical specimens in patient management.](https://pubmed.ncbi.nlm.nih.gov/28216180). International journal of infectious diseases : IJID : official publication of the International Society for Infectious Diseases, 2017. - [CLUSTOM-CLOUD: In-Memory Data Grid-Based Software for Clustering 16S rRNA Sequence Data in the Cloud Environment.](https://pubmed.ncbi.nlm.nih.gov/26954507). PloS one, 2016. > This article is educational and does not replace validated laboratory procedures, institutional biosafety review, manufacturer instructions, or professional interpretation.