Table 4. Validation status codes summarize the available validation data in assay reports and refSNP clusters.
| Validation evidence | Description | Code in database for ss# | Code in FTP dumps for ss# | Code in database for rs# | Code in FTP dumps for rs# |
|---|---|---|---|---|---|
| Not validated | For ss#, no batch update or validation data, no frequency data (or frequency is 0 or 1). rs# status code is OR'd from the ss# codes. | 0 | Not present | 0a | Not present |
| Multiple reporting | Status = 1 for an rs# with at least two ss# numbers; having at least one ss# is validated by a non-computational method. For a ss#, status = 1 if the method is non-computational. | 1 | 1b | 1,0b | 1 |
| With frequency | Frequency data is present with a value between 0 and 1. | 2 | 2 | 2 | 2 |
| Both frequency | For ss#, the method is non-computational and frequency data is present. If the ss# is a single cluster member, then the rs# code is set to 2. | 3 | 3 | 3/2 | 3 |
| Submitter validation | Submission of a batch update or validation section that reports a second validation method on the assay. | 4 | 4 | 4 | 4 |
If the rs# has a single ss# with code 1, then rs# is set to code 0.
For a single member rs where the ss# validation status = 1, the rs# validation status is set to 0.
From: Chapter 5, The Single Nucleotide Polymorphism Database (dbSNP) of Nucleotide Sequence Variation
NCBI Bookshelf. A service of the National Library of Medicine, National Institutes of Health.