How to get versioned Protein Accession Number for a Refseq Accession Number?

I have some versioned RefSeq Accession numbers and I would like to know their corresponding Protein Accession Numbers.

According to the RefSeqFAQ http://www.ncbi.nlm.nih.gov/books/NBK50679/#RefSeqFAQ.what_causes_the_version_number there is not a 1-to-1 mapping between these numbers.

Also, nucleotide (NM_, XM_) and protein (NP_, XP) records for the same transcript may not have the same version number after an update. For example, an update to the 5’ UTR of a RefSeq nucleotide record would cause a version number change for the updated nucleotide record but not for the corresponding protein record. Conversely, a change in the annotated start site of the coding sequence without a change in the underlying nucleotide sequence would cause a version number update for the NP_ but not for the NM_.

I have tried this, but it gives me a huge

>>> from Bio import Entrez
>>> Entrez.email='[email protected]'
>>> f = file('entrez_NM_005529.5.txt', 'w')
>>> print >>f,  Entrez.efetch(
...     db="protein",id="NM_005529.5", rettype="native", retmode="xml").read()

The XML results contain the Protein Acc No, <Textseq-id_accession>NP_005520</Textseq-id_accession> but there is no version specified. Is there a simple way to get obtain the matching protein transcript version?

  • $\begingroup$ Are you always dealing with the latest nt version, or do you need to get previous ones? $\endgroup$
    – terdon
    Commented Mar 2, 2016 at 12:08

1 Answer 1


There is another simple way for human sequences.

Go to RefSeq FTP and download the LRG_RefSeqGene file. This file contains updated mappings between the gene, mRNA and protein sequences (latest versions).


    Tab-delimited file reporting, for each Gene, the accession.version
      of the genomic and RNA and protein RefSeqs the RefSeqGene/LRG 
      project treats as reference standards.  

    The columns are:
      NCBI taxonomy id (all 9606)
      Symbol of the gene (official from HGNC when available)
      Accession.version of the standard RefSeq
      Term describing the RefSeq 
         RefSeqGene              genomic sequence
         Ref Std, nucleotide     RNA sequence
         Ref Std, protein        protein sequence

      The LRG equivalent of the RefSeq standard
         LRG:                    genomic sequence
         t1                      locations for transcript 1
         p1                      CDS from transcript 1

         NOTE: t values can be > 1 ,  the integer assigned to t
               is matched by the integer assigned to p

Some few lines from the file:

9606    3329    HSPD1   NG_008915.1     NM_199440.1     NP_955472.1     reference standard
9606    3329    HSPD1   NG_008915.1     NM_002156.4     NP_002147.2     aligned: Selected
9606    3336    HSPE1   NG_008914.1     NM_002157.2     NP_002148.1     reference standard
9606    3339    HSPG2   NG_016740.1     NM_005529.6     NP_005520.4     reference standard

It is not that easy for other organisms. For them, you should either parse the mRNA page to find the RefSeq protein id or go to their specific designated databases (such as FlyBase for Drosophila) and obtain information on the gene to protein mapping.

For obtaining RefSeq records from NCBI using parsing you should first obtain the GI accession number corresponding to the mRNA.

Example: NM_007393 (mouse beta-actin)


which would give the GI accession number: 930945786.

Then fetch the protein GI using this accession number:


which gives the GI accession number: 6671509

Finally get the RefSeq id (if available) corresponding to this GI accession. You can download the feature table and look for the RefSeq i.d:


For more information on how to use Entrez E-Utilities see here.

  • $\begingroup$ Thanks for a very comprehensive answer. Fortunately I'm only dealing with humans, but this will serve as a very useful explanation for others. $\endgroup$
    – ChrisGuest
    Commented Mar 3, 2016 at 4:11

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .