I read a fantastic article in Nature magazine (vol 459, pp931-939 (18 June 2009)) that summarizes not only the current state of novel H1N1 (aka Swine Flu) understanding, but also a compares H1N1 against other flu strains. In particular, it discusses in-depth how the pathogenic components — i.e., the stuff that kills you — compare against each other.
The Influenza virus is quite fascinating. Allow me to ramble on…
Comparison to Computer Viruses
How many bits does it take to kill a human?
The H1N1 virus has been comprehensively disassembled (sequenced) and logged into the NCBI Influenza Virus Resource database. For example, an instance of influenza known as A/Italy/49/2009(H1N1) isolated from the nose of a 26-year old female homo sapiens returning from the USA to Italy (I love the specificity of these database records), has its entire sequence posted at the NCBI website. It’s amazing — here’s the first 120 bits of the sequence.
atgaaggcaa tactagtagt tctgctatat acatttgcaa ccgcaaatgc agacacatta
Remember, each symbol represents 2 bits of information. This is alternatively represented as an amino acid sequence, through a translation lookup table, of the following peptides:
In this case, each symbol represents an amino acid which is the equivalent of 6 bits (3 DNA-equivalent codons per amino acid). M is methionine, K is Lysine, A is Alanine, etc. (you can find the translation table here).
For those not familiar with molecular biology, DNA is information-equivalent to RNA on a 1 to 1 mapping; DNA is like a program stored on disk, and RNA is like a program loaded into RAM. Upon loading DNA, a transcription occurs where “T” bases are replaced with “U” bases. Remember, each base pair specifies one of four possible symbols (A [T/U] G C), so a single base pair corresponds to 2 bits of information.
Proteins are the output of running an RNA program. Proteins are synthesized according to the instructions in RNA on a 3 to 1 mapping. You can think of proteins a bit like pixels in a frame buffer. A complete protein is like an image on the screen; each amino acid on a protein is like a pixel; each pixel has a depth of 6 bits (3 to 1 mapping of a medium that stores 2 bits per base pair); and each pixel has to go through a color palette (the codon translation table) to transform the raw data into a final rendered color. Unlike a computer frame buffer, different biological proteins vary in amino acid count (pixel count).
To ground this in a specific example, six bits stored as “ATG” on your hard drive (DNA) is loaded into RAM (RNA) as “AUG” (remember the T->U transcription). When the RNA program in RAM is executed, “AUG” is translated to a pixel (amino acid) of color “M”, or methionine (which is incidentally the biological “start” codon, the first instruction in every valid RNA program). As a short-hand, since DNA and RNA are 1:1 equivalent, bioinformaticists represent gene sequences in DNA format, even if the biological mechanism is in RNA format (as is the case for Influenza–more on the significance of that later!).
OK, back to the main point of this post. The particular RNA subroutine mentioned above codes for the HA gene which produces the Hemagglutinin protein: in particular, an H1 variety. This is the “H1” in the H1N1 designation.
If you thought of organisms as computers with IP addresses, each functional group of cells in the organism would be listening to the environment through its own active port. So, as port 25 maps specifically to SMTP services on a computer, port H1 maps specifically to the windpipe region on a human. Interestingly, the same port H1 maps to the intestinal tract on a bird. Thus, the same H1N1 virus will attack the respiratory system of a human, and the gut of a bird. In contrast, H5 — the variety found in H5N1, or the deadly “avian flu” — specifies the port for your inner lungs. As a result, H5N1 is much more deadly because it attacks your inner lung tissue, causing severe pneumonia. H1N1 is not as deadly because it is attacking a much more benign port that just causes you to blow your nose a lot and cough up loogies, instead of ceasing to breathe.
Researchers are still discovering more about the H5 port; the Nature article indicates that perhaps certain human mutants have lungs that do not listen on the H5 port. So, those of us with the mutation that causes lungs to ignore the H5 port would have a better chance of surviving an Avian flu infection, whereas as those of us that open port H5 on the lungs have no chance to survive make your time / all your base pairs are belong to H5N1.
So how many bits are in this instance of H1N1? The raw number of bits, by my count, is 26,022; the actual number of coding bits approximately 25,054 — I say approximately because the virus does the equivalent of self-modifying code to create two proteins out of a single gene in some places (pretty interesting stuff actually), so it’s hard to say what counts as code and what counts as incidental non-executing NOP sleds that are required for self-modifying code.
So it takes about 25 kilobits — 3.2 kbytes — of data to code for a virus that has a non-trivial chance of killing a human. This is more efficient than a computer virus, such as MyDoom, which rings in at around 22 kbytes.
It’s humbling that I could be killed by 3.2kbytes of genetic data. Then again, with 850 Mbytes of data in my genome, there’s bound to be an exploit or two.
Hacking Swine Flu
One interesting consequence of reading this Nature article, and having access to the virus sequence, is that I now know how to modify the virus sequence to probably make it more deadly.
The Nature article notes, for example, that variants of the PB2 Influenza gene with Glutamic acid at position 627 in the sequence has a low pathogenicity (not very deadly). However, PB2 variants with Lysine at the same position is more deadly. Well, let’s see the sequence of PB2 for H1N1. Going back to our NCBI database:
601 QQMRDVLGTFDTVQIIKLLP 621 FAAAPPEQSRMQFSSLTVNV 641 RGSGLRILVRGNSPVFNYNK
As you can see from the above annotation, position 627 has “E” in it, which is the code for Glutamic acid. Thankfully, it’s the less-deadly version; perhaps this is why not as many people have died from contracting H1N1 as the press releases might have scared you into thinking. Let’s reverse this back to the DNA code:
621 F A A A P P E Q S R 1861 tttgctgctg ctccaccaga acagagtagg
As you can see, we have “GAA” coding for “E” (Glutamic acid). To modify this genome to be more deadly, we simply need to replace “GAA” with one of the codes for Lysine (“K”), which is either of “AAA” or “AAG”. Thus, the more deadly variant of H1N1 would have its coding sequence read like this:
621 F A A A P P K Q S R 1861 tttgctgctg ctccaccaaa acagagtagg ^ changed
There. A single base-pair change, flipping two bits, is perhaps all you need to turn the current less-deadly H1N1 swine flu virus into a more deadly variant.
Theoretically, I could apply a long series of well-known biological procedures to synthesize this and actually implement this deadly variant; as a first step, I can go to any number of DNA synthesis websites (such as the cutely-named “Mr. Gene”) and order the modified sequence to get my deadly little project going for a little over $1,000. Note that Mr. Gene implements a screening procedure against DNA sequences that could be used to implement biohazardous products. I don’t know if they specifically screen against HA variants such as this modified H1 gene. Even if they do, there are well-known protocols for site-directed mutagenesis that can possibly be used to modify a single base of RNA from material extracted from normal H1N1.
[Just noticed this citation from the Nature article: Neumann, G. et al Generation of influenza A viruses entirely from cloned cDNA. Proc. Natl Acad. Sci. USA 96, 9345-9350 (1999). This paper tells you how to DIY an Influenza A. Good read.].
OK, before we get our hackles up about this little hack, let’s give Influenza some credit: after all, it packs a deadly punch in 3.2kbytes and despite our best efforts we can’t eradicate it. Could Influenza figure this out on its own?
The short answer is yes.
In fact, the Influenza virus is evolved to allow for these adaptations. Normally, when DNA is copied, an error-checking protein runs over the copied genome to verify that no mistakes were made. This keeps the error rate quite low. But remember, Influenza uses an RNA architecture. It therefore needs a different mechanism from DNA for copying.
It turns out that Influenza packs inside its virus capsule a protein complex (RNA-dependent RNA polymerase) that is customized for its style of RNA copying. Significantly, it omits the error checking protein. The result is that there is about one error made in copying every 10,000 base pairs. How long is the Influenza genome? About 13,000 base pairs. Thus, on average, every copy of an Influenza virus has one random mutation in it.
Some of these mutations make no difference; others render the virus harmless; and quite possibly, some render the virus much more dangerous. Since viruses are replicated and distributed in astronomical quantities, the chance that this little hack could end up occurring naturally is in fact quite high. This is part of the reason, I think, why the health officials are so worried about H1N1: we have no resistance to it, and even though it’s not quite so deadly today, it’s probably just a couple mutations away from being a much bigger health problem.
In fact, if anything, perhaps I should be trying to catch the strain of H1N1 going around today because its pathogenicity is currently in-line with normal flu variants — as of this article’s writing, the CDC has recorded 87 deaths out of 21,449 confirmed cases, or a 0.4% mortality rate (to contrast, “normal” flu is <0.1%, while the dreaded Spanish flu of 1918 was around 2.5%; H5N1, or avian flu, is over 50%(!), but thankfully it has trouble spreading between humans). By getting H1N1 today, I would get the added bonus of developing a natural immunity to H1N1, so after it mutates and comes back again I stand a better chance of fighting it. What doesn’t kill you makes you stronger!…or on second thought maybe I’ll just wait until they develop a vaccine for it.
There is one other important subtlety to the RNA architecture of the influenza virus, aside from the well-adjusted mutation rate that it guarantees. The subtlety is that the genetic information is stored inside the virus as 8 separate snippets of RNA, instead of as a single unbroken strand (as it is in many other viruses and in living cells). Why is this important?
Consider what happens when a host is infected by two types of Influenza at the same time. If the genes were stored as a single piece of DNA, there would be little opportunity for the genes between the two types to shuffle. However, because Influenza stores its genes as 8 separate snippets, the snippets mix freely inside the infected cell, and are randomly shuffled into virus packets as they emerge. Thus, if you are unlucky enough to get two types of flus at once, the result is a potentially novel strain of flu, as RNA strands are copied, mixed and picked out of the metaphorical hat and then packed into virus particles. This process is elegant in that the same mechanism allows for mixing of an arbitrary number of strains in a single host: if you can infect a cell with three or four types of influenza at once, the result is an even wilder variation of flu particles.
This is part of the reason why the novel H1N1 is called a “triple-reassortant” virus: through either a series of dual-infections, or perhaps a single calamitous infection of multiple flu varieties, the novel H1N1 acquired a mix of RNA snippets that has bestowed upon it high transmission rates along with no innate human immunity to the virus, i.e., the perfect storm for a pandemic.
I haven’t been tracking the latest efforts on the part of computer virus writers, but if there was a computer analogy to this RNA-shuffling model, it would be a virus that distributes itself in the form of unlinked object code files plus a small helper program that, upon infection in a host, would first re-link its files in a random order before copying and redistributing itself. In addition to doing this, it would search for similar viruses that may already be infecting that computer, and it would on occasion link in object code with matching function templates from the other viruses. This re-arrangement and novel re-linking of the code itself would work to foil certain classes of anti-virus software that searches for virus signatures based on fixed code patterns. It would also cause a proliferation of a diverse set of viruses in the wild, with less predictable properties.
Thus, the Influenza virus is remarkable in its method for achieving a multi-level adaptation mechanism, consisting of both a slowly evolving point mutation mechanism, as well as a mechanism for drastically altering the virus’ properties in a single generation through gene-level mixing with other viruses (it’s not quite like sex but probably just as good, if not better). It’s also remarkable that these two important properties of the virus arise as a consequence of using RNA instead of DNA as the genetic storage medium.
Well, that’s it for me tonight — and if you made it this far through the post, I appreciate your attention; I do tend to ramble in my “Ponderings” posts. There’s actually a lot more fascinating stuff about Influenza A inside the aforementioned Nature article. If you want to know more, I highly recommend the read.