Of course, none of this is as simple as conservatives claim.

In fact, the bill Carter is so angry about is almost entirely irrelevant to HIV prevention; the mandatory newborn testing Carter favors is useless for telling us if newborns are HIV positive, is overly controlling of mothers, and will do almost nothing for preventing HIV transmission; and virtually all the effective policies for reducing mother-to-child HIV transmission involve improving the effectiveness and availability of prenatal care.

1) The omnibus bill Carter is angry about has almost nothing to do with HIV prevention.

The specific legislation that set Joe Carter and the FRC off is an omnibus legislation intended to eliminate dozens of so-called “earmark” programs. In order to prevent the anti-earmark bill from having dozens of anti-anti-earmarks hanging off of it, the Democrats decided to accept no amendments at all, on any subject, to the anti-earmark bill. The no-amendments provision doesn’t seem like an unreasonable approach to an anti-earmark bill, and it certainly has nothing to do with the Democrats being against AIDS prevention funding.

(For further discussion of this aspect, read Kevin Keith’s arguments in the comments of Evangelical Outpost.^a )

2) Mandatory newborn testing can’t tell us if newborns have HIV. It can only tell us if mothers have HIV.

It’s important to understand that HIV-testing a newborn doesn’t tell us if the newborn is HIV positive. For the first 18 months of life, infants who aren’t infected with HIV will nonetheless test as HIV-positive if their mother was HIV positive while she was pregnant. (This happens because anti-HIV antibodies, which is what the standard test looks for, are transmitted from mother to child in the womb. Source.). 75% to 85% of infants who “test positive” for HIV do not have HIV.

There is a newer test which tests for HIV virus in the baby, rather than just testing for antibodies. However, this test is only 33% accurate on a newborn; it’s not until a baby is two months old that this test becomes 90% accurate, and not until six months that it’s 95% accurate. (Source).

So there’s no effective way of finding out if a newborn baby has HIV. What testing the babies actually provides is a way of finding out if the mother has HIV. “Newborn” testing avoids the sometimes uncomfortable and slow work of getting a mother’s informed consent for HIV testing — by testing for the mother’s HIV status indirectly. It’s about avoiding the need for the mother’s consent. As Senator Tom Coburn, the leading proponent of mandatory newborn testing, say: “If they didn’t want to be tested, their baby was tested.”

Labor, childbirth and the hours immediately after birth is the time when a mother has the least choice about being in the hospital, and about submitting herself and her baby to medical tests; it is therefore the time that conservatives have been most eager to test women for drugs and for HIV. With a mandatory newborn testing law, there’s no need to muck about with counseling and informed consent and all that; you just do the test, wam bam no need for thanking you ma’am.

3) Mandatory newborn testing is mostly worthless for preventing HIV transmission.

The FRC’s Joe Carter asks “what could possibly be more important than preventing babies form contracting HIV/AIDS?” But the only controversial part of the Ryan White Early Diagnosis Grant Program is mandatory newborn testing — and mandatory newborn testing is mostly worthless for preventing mother to child transmission.

Consider this real-life story from The Body, an advocacy group for people with HIV and AIDS. Rosa, a 27-year-old mother, lives in New York. (New York’s mandatory newborn testing program is often cited by advocates as a success story). When Rosa found out she was pregnant with her second child, she went for prenatal care and counseling, and was counseled about the importance of breastfeeding. But at no point was she counseled about HIV or advised to get tested. Six weeks after giving birth to her daughter, the hospital called Rosa.

A phone call summoned her to the mental health division of the hospital. There, during a meeting that lasted less than fifteen minutes, she learned that her daughter had been tested under New York State’s mandatory newborn HIV testing program and that her results were positive.

No one had informed Rosa ahead of time that her daughter would be tested. No one informed Rosa now what the results of the test meant. It was only later, through her own research efforts, that Rosa learned that the temporary presence of the mother’s viral antibodies in a newborn’s blood means that all infants of HIV-positive women will test HIV-positive at birth. It was only later that she learned that only 15 to 25 percent of these newborns will themselves be infected by the virus. It was only later that she learned that screening newborns for HIV antibodies reveals the HIV status of the mother, not that of the infant.

Rosa immediately told her boyfriend about the test results. A few weeks later, however, a visiting nurse who came to the apartment when Rosa was not at home implied to the boyfriend that Rosa had known her status before her daughter’s birth but hadn’t told him. When Rosa got home, her boyfriend beat her up, forcing her and her children to leave her apartment and stay in a shelter for several days.

“I definitely would have tested prenatally if anyone had asked,” says Rosa. “If I had known earlier, I would have planned. I probably would have taken AZT because I would have wanted to increase the chances that my child would not have the virus. I would never have breastfed.”

Does anyone believe that New York’s mandatory testing program did a good job of reducing Rosa’s odds of transmitting HIV to her daughter?

By definition, testing newborns happens too late to prevent most mother to child transmissions. Serious efforts to prevent mother to child HIV transmission have to be prenatal, before the virus is transmitted. And that requires working with mothers, not bulldozing over them. The good news is, prenatal testing and treatment have already been successful at vastly reducing mother to child HIV transmission nationwide. So why do we want to take $30 million dollars away from existing programs (which are already critically underfunded) and give it instead to programs that include mandatory newborn testing — a “prevention” effort that’s guaranteed not to be very effective?

Supporters of mandatory newborn testing often claim that such programs have worked miracles preventing HIV transmission, usually citing New York as an example. But there have been enormous improvements nationwide, not just in New York and other states with mandatory newborn testing. According to a CDC factsheet on mother-to-child HIV transmission, “Over the course of the epidemic, the number of perinatally transmitted AIDS cases has decreased dramatically. The number of infants infected with HIV through mother-to-child transmission decreased from an estimated peak of 1,750 HIV-infected infants born each year during the early to mid-1990s to 280–370 infants in 2000 (CDC, unpublished data, 2000). This decrease is largely due to the use of antiretroviral therapy during pregnancy and labor.” (Emphasis added).

4) What we should be fighting for.

• Prenatal care for all pregnant women.
• Information and counseling on prenatal HIV testing for all pregnant women, and on pregnancy, childrearing and HIV for HIV positive pregnant women. These should be available in a variety of languages and designed for a variety of cultural backgrounds.
• Free anti-HIV drugs for all HIV positive pregnant women (and all HIV positive people, but that’s a topic for a different post, I suppose). Being treated for HIV drastically reduces the chances of a mother transmitting HIV to a child in the womb or during childbirth – from around 20% to less than 2%. (For those who are interested, here (pdf link) is a detailed discussion of the medical issues.)
• Attention to the economic and other issues that often prevents women, especially non-white, immigrant, or low-income women, from getting adequate prenatal care. This is too large a topic for this post, but issues to be considered include low-cost transportation, language and cultural barriers, how difficult it is to get prenatal care outside of regular working hours, childcare for mothers expecting new children, and the impact of abuse. This may sound like a grab-bag of irrelevant issues, but in fact it’s a central issue: Readily available prenatal care is the number one way we can prevent mother-to-child HIV transmission.
• A model of medical care that assumes that all women — including women with HIV — need to give informed consent for all medical treatment and tests.

Sources/ Further reading:

HIV Infection in Infants and Children
Whose Virus Is It Anyway?, from The Body
Routine Testing Must Include Informed Consent
Mother-To-Child (Perinatal) HIV Transmission And Prevention (CDC factsheet)
Striking A Balance: HIV Testing For Pregnant Women And Newborns

1. From one of Kevin’s comments:

   HJRes20 is the omnibus “anti-earmark” bill. As many people have noted, getting rid of “earmarks” is harder than it looks, because there is no legal distinction between an “earmark” for “pork-barrel spending” and an ordinary appropriation for an ordinary program. But both parties have declared they are going to do something about “earmarks”.

   The approach they have taken is to submit a huge bill that comprehensively strikes out hundreds – possibly thousands, there were too many for me to count – of targeted allocations for named programs. The same bill stipulates specific levels of funding for different departments, and in some cases specifies that that funding should be used in certain ways.

   …The bill is an attempt to clear the decks of the thousands of small allocations for individual projects, in order to start a systematic attempt to decide what should or should not be funded. Along the way, a huge number of specific funding initiatives – most of them probably reasonable – have been undone. (Note that this does not mean that these programs will not get funded, or that the money will “just sit there”. It means that all those funding decisions will have to be revisited, hopefully with greater oversight. Every single one of the rescinded “earmarks” could be funded if Congress chooses to do so, even after passing this bill.)

   So what’s up with the Baby AIDS program? It is one of the hundreds of line items that is being taken out of the budget.

   Why are the Democrats holding it up? They’re not. A Republican member attempted to re-insert a specific earmark for that program in the bill designed to eliminate earmarks. Reid has said he will not allow specific programs to be exempted. I don’t think Reid has said anything about the Baby AIDS program – just that he wants the entire earmark bill dealt with at once, and not a bunch of earmarks on the earmark bill.

Also, I’ve added a “subscribe to comments” feature.

Like these add-ons? Hate them? Let me know, please.

UPDATE: “Fancy Archives” had to be deactivated – apparently the sucker was a real CPU hog. Oh, well.

What happened was a server load problem – a problem which has plagued this blog. But now I think we finally know what the problem is – on a blog that gets as many page views as “Alas” does, you just can’t have a 20-post-long “recently commented” list. As Robert wrote me via email:

Diagnosing your problem: It’s your most-recent-comment plugin.

That query is extremely computationally expensive. (Expense means how much disk and CPU activity it needs in order to run) You’re saying “give me every field in this big honkin, table, and also figure out which record has the latest date, from this huge ass database and with a bunch of logic to process for every row…oh, and run this on two big-tables in conjunction with each other…and then when you’re done with that look at the whole damn result set and put it in order and then subgroup each row by this index field.”

I’m tired just reading it; your plugin is probably asking for this every time someone loads any page on your system. I ran into a similar problem on BNN: the architecture was very programmatically attractive (this is a nice query) but it didn’t scale up well. This query is fantastic for a blog with 2 posts a day and 10 comments apiece but it will put a bullet in the brain of a machine asked to do it 8000 times a day on posts with 300+ comments. (Particularly because inexpensive web hosting computers tend to be cheap POS rack boxes that don’t have a ton of hardware because 99% of the sites don’t need any real processing power to deliver their trickle of hits.)

Easy fix: kill the plugin. Hard fix: Learn or hire WordPress expertise and have someone write you an efficient plugin for big comment sites.

For now, I’ve taken Robert’s “easy fix,” because it was the quickest way to get “Alas” back online.

Here’s a letter I sent to DreamHost support, explaining my future plans:

Hi! I’m working on solving my recent server load problems, which led DreamHost Support to turn my WordPress database off yesterday.

The problem was, I believe, caused by my blog’s “recently commented posts” list. A WordPress expert I talked to suggested to me that such a list, when loaded on every single page view on a popular blog, could cause problems if it calls for more than 10 posts to be listed. My “recently commented posts” list was set to list the 20 posts that comments had recently been left on.

Because my blog emphasizes reader comments and discussion (the blog sometimes get hundreds of reader comments a day), the “recently commented posts” list is essential – without it, posts that still have active discussions will “fall off” the front page and be too hard for readers to find. What I’d like to do is experiment a little, to find a way to restore the “recently commented posts” list that won’t cause an unfair strain on DreamHost’s server load.

My proposal is to restore the “recently commented posts” list on the sidebar – but this time with only 7 posts listed, rather than 20. That should reduce the server load enormously, hopefully eliminating the problem. I’ll also create a separate page with a larger, more detailed listing – but since it’s a separate page, I expect it’ll only be loaded by the relatively small number of very dedicated readers who follow the discussions very closely.

What I’d like is your help in making it possible for me to run this experiment. I could start this at any time that works for you (I suggest 9am pacific time Thursday). What I’d like from DreamHost Support is, if the server load gets too high (and I don’t think it will), rather than shutting me off, email me letting me know there’s a problem. I’ll make sure to monitor my email frequently. Once emailed, I’ll turn the offending plugin off immediately and use the new information to figure out the next step.

This will allow me to try to find a solution without fear of having my blog suddenly turned off by the host; and it will provide you with assurance that if there is a server load issue caused by the plugin, it will be turned off quickly.

The other thing I’d like, if things go wrong and I have to shut the plugin off, is a detailed report from the database regarding server load. This will help my consulting expert figure out what is wrong and how to run my blog while avoiding the problem in the future.

I hope that we can work together to let my blog have the functionality it needs, without causing server load problems. I’ll look forward to your response.

So that’s the plan; I should hear back from DreamHost Support by sometime tomorrow. Let me know what y’all think.

On another subject, I have no idea why the comment preview stopped working once I’d moved to DreamHost. If anyone has a clue, please enlighten me.

The alternative arrangements we were making have fallen through, so we need to find a new server for “theennead.com” and also for “amptoons.com.”

Until that happens, it’s possible”Alas” will be down for several days.

If anyone would like to recommend a good not-too-expensive server, or to let me know what the heck the computerese stuff below the fold is about, feel free.

From: “Lunarpages Helpdesk”
To: [censored]
Date: Mon, 28 Feb 2005 02:11:41 +0000 (GMT)
Subject: Account suspended and moved to Quantz [4842-ETPK-4878] [052db701] Question Created
==== Enter your reply ABOVE this line ====
Dear Elkins,

The following ticket has been created by a member of our staff for you

Your question’s details:

============== Title: ==============
Account suspended and moved to Quantz

============== Message: ==============
Hello,

we suspended and moved your account to “Quantz” server because of the
following reasons.

Too many php processes and mysql connections caused Europa to hang.
Here are the log files from Europa:

Processes running while server had load issues:
————————————————————————————-
freedo15 9616 0.0 0.1 14940 5728 ? S Feb24 0:01
/usr/bin/php
theenn2 29054 2.3 0.1 14556 7156 ? S 17:09 0:00
/usr/bin/php
theenn2 29062 7.8 0.2 15128 7800 ? S 17:09 0:00
/usr/bin/php
theenn2 29134 3.0 0.1 14408 7080 ? S 17:09 0:00
/usr/bin/php
theenn2 29191 3.5 0.1 14420 7080 ? S 17:09 0:00
/usr/bin/php
root 29266 1.0 0.1 12796 4576 pts/2 S 17:09 0:00
/usr/local/bin/php -q /etc/lunarscripts/menu/shell_runp
theenn2 29289 15.5 0.1 14904 7500 ? S 17:09 0:00
/usr/bin/php
theenn2 29301 8.0 0.1 14520 7068 ? S 17:09 0:00
/usr/bin/php
theenn2 29325 15.0 0.1 14420 7076 ? S 17:09 0:00
/usr/bin/php
theenn2 29466 2.2 0.1 14540 7152 ? S 17:09 0:00
/usr/bin/php
theenn2 29534 11.0 0.2 15132 7748 ? S 17:09 0:00
/usr/bin/php
theenn2 29537 12.3 0.2 15128 7748 ? S 17:09 0:00
/usr/bin/php
theenn2 29542 3.3 0.1 14416 7080 ? S 17:09 0:00
/usr/bin/php
theenn2 29644 0.0 0.1 14424 7080 ? S 17:09 0:00
/usr/bin/php
——————————————————————————–

MYSQL log:
——————————————————————————–
———————————–+
| 2073 | theenn2_amptoons | localhost | theenn2_MT | Query |
4 | Copying to tmp table | SELECT alas_posts.*,
MAX(comment_date) AS max_comment_date FROM alas_comments,
alas_posts WHERE alas |
| 2078 | theenn2_amptoons | localhost | theenn2_MT | Query |
4 | Copying to tmp table | SELECT alas_posts.*,
MAX(comment_date) AS max_comment_date FROM alas_comments,
alas_posts WHERE alas |
| 2079 | theenn2_amptoons | localhost | theenn2_MT | Query |
2 | Copying to tmp table | SELECT alas_posts.*,
MAX(comment_date) AS max_comment_date FROM alas_comments,
alas_posts WHERE alas |
| 2083 | theenn2_amptoons | localhost | theenn2_MT | Sleep |
|
| 2084 | theenn2_amptoons | localhost | theenn2_MT | Query |
2 | Copying to tmp table | SELECT alas_posts.*,
MAX(comment_date) AS max_comment_date FROM alas_comments,
alas_posts WHERE alas |
| 2607 | theenn2_amptoons | localhost | theenn2_MT
Query | 6 | Copying to tmp table | SELECT alas_posts.*,
MAX(comment_date) AS max_comment_date FROM alas_comments,
alas_posts WHERE alas || 2608 | theenn2_amptoons | localhost | theenn2_MT
|
Query | 6 | Copying to tmp table | SELECT alas_posts.*,
MAX(comment_date) AS max_comment_date FROM alas_comments,
alas_posts WHERE alas || 2610 | theenn2_amptoons | localhost | theenn2_MT
|
Query | 5 | Copying to tmp table | SELECT alas_posts.*,
MAX(comment_date) AS max_comment_date FROM alas_comments,
alas_posts WHERE alas |
| 2612 | theenn2_amptoons | localhost | theenn2_MT
Query | 5 | Copying to tmp table | SELECT alas_posts.*,
MAX(comment_date) AS max_comment_date FROM alas_comments,
alas_posts WHERE alas |
| 2613 | theenn2_amptoons | localhost | theenn2_MT
Query | 3 | Copying to tmp table | SELECT alas_posts.*
MAX(comment_date) AS max_comment_date FROM alas_comments,
alas_posts WHERE alas |………….
——————————————————————————————

Your account’s STATS before we suspended your account:

theenn2 theennead.com
Average cpu usage : 6.66%
Average memory usage:1.63%
Average Mysql Usgae : 0.6
Top Process%CPU 72.0/usr/bin/php
Top Process%CPU 63.0/usr/bin/php
Top Process%CPU 50.0/usr/bin/php

Hence we moved you to Quantz first to solve the issue of the degraded service
on Europa and second as a courtesy in order to prevent any downtime on your
site to allow you time to rectify the situation. Currently, your site is not
suitable for a shared hosting environment.

Quantz is not a production server and is not guaranteed to run in the same
manner as your old server nor will it support all functions you may have.
This is a transitional server only and is not intended to be a permanent
placement. Please make a decision on how you would like to proceed within
seven (7) days. After seven (7) days, your account will be suspended if no
other arrangements are made.

You have the following options:

1.You may take steps to correct the problem. This must be done before the
seven (7) days are up. You will need to let the technician know the steps you
took to correct the issue and get approval before being returned to a
production server.

2.You may look for a dedicated server or other hosting solution. Please
remember that propagation takes up to seventy two (72) hours so if you decide
on changing hosts you should allow enough time for propagation.

Thank you for your cooperation in this matter. We value you as a customer and
want to work with you toward a solution that is mutually beneficial. Please
let us know as quickly as possible how you would like to proceed.

Please Let us know, If you have any issues!
We are at your service and Our mission is to serve you better!

Regards,
Ramarajan.V,
JRSA, Support team.