The good news, I guess, is that we survived another CFS Advisory Committee meeting. The bad news is that much of what happened made no sense to me. Some excellent summaries of the meeting are available, including this very detailed recap from Phoenix Rising. I would like to tackle a few of the topics that had me shaking my head, or asking myself if my experience of reality is so at odds with the Committee’s. This post is long, and I apologize for that. Here’s my report card on these head-scratcher issues:
Meeting Mechanics
I know how difficult it is to prepare for and moderate two full days of contentious meetings, and I imagine it is more difficult to do so when the meeting will be held in public. However, I was struck by how poorly some of the administrative aspects of this meeting were conducted. For example, the procedure for meeting and comment registration is unnecessarily complicated for a patient population that struggles with multiple forms of cognitive dysfunction. I hope this can be simplified.
On the first day of the meeting, Dr. Gailen Marshall said that members would be limited to three minutes for comments during discussion. He did not enforce this limit evenly, including on himself. More than one observer noted how long his own comments were, and how he sometimes monopolized discussion. I happen to think that a Chairman needs leeway to cover certain topics, but sometimes this seemed excessive. Participation by other Committee members is very uneven: Eileen Holderman, Dr. Mary Ann Fletcher and Steve Krafchick speak most frequently; Dr. Jordan Dimitrikoff and Dr. Susan Levine fall somewhere in the middle; Dr. Adrian Casillas, Dr. Lisa Corbin, Dr. Dane Cook, and Rebecca Collier rarely if ever spoke. It did seem like the non-voting liaisons were integrated into the discussion, and had opportunities to ask questions and offer feedback.
I was very frustrated by the evident lack of preparation for even simple agenda items. For example, when approving the list of ME/CFS organizations for linking on the Office of Women’s Health website, the Committee did not have a list in front of them and they approved the criteria on Day 2, after approving the list on Day 1. One of the criteria was that organizations would consent to being linked, but on Day 1 Dr. Lee said that was not checked, so the criteria list on Day 2 had to be amended. It was a mess, and hard to follow. A similar lack of preparation was evident in the discussion of the High Priority List, as we’ll see. There is simply no good reason for the lack of preparation. Why didn’t a staff member type up the list of criteria and list of organizations, provide it to the Committee and post as a slide, so everyone knew what they were voting on? The disorganization and confusion wastes time, at the expense of other issues.
One mechanic that worked fairly well, in my opinion, was the audience Question & Answer. The audience questions led to some very significant discussion, especially regarding CDC. Some people feel that Dr. Marshall should not curate these questions, and I thought that the “answer” discussion tended towards domination by the Committee instead of actual answers to the questions. However, I think the value of this kind of interaction was very clear and I hope this will continue.
High Priority Recommendations
From a procedural perspective, we scored a small victory here. Dr. Marshall acknowledged that the list was not handled correctly last year. I pressed the Committee to devote an appropriate amount of time to discussion of the list, and I was shocked when they agreed. I don’t know what happened at lunch, or who said what, but apparently there was enough concern expressed that Dr. Marshall said they would move the discussion to Day 2. They discussed the list and how to use it going forward, and voted on it in public as required by FACA. Procedurally, they handled the issue correctly.
But the substance of their decision is perplexing, at best. No list was posted, and it did not seem like the committee members had a single piece of paper in front of them with the full list. Items were added – but without reading some of the additions into the record – and a process for removing items was discussed but not used. Dr. Marshall downplayed the fact that several recommendations had been altered from the original form, saying that “the spirit is there.” Dr. Lee said that the old recommendations chart would now be a historical document, and the High Priority list would be the working list. Dr. Marshall said that of the eight recommendations the Committee made last year, three were complete and the other five would be added to the list. But he did not specify which recommendations he considered complete, and no one asked him to be specific. I can make a pretty good guess, but we won’t know for certain until the final list is posted.
And amid all this back and forth, Dr. Marshall said that the list was never intended to prioritize one recommendation over another within the list. Everything on the list is of equal importance. No one questioned or objected to this. This may not seem like a big deal, but it is. By acquiescing to this equal priority description, the Committee created a situation where holding a disability workshop is of the same priority and importance as holding a case definition workshop. I don’t think most members would agree with that statement, but now they’re stuck with it.
So what did they select as the high priority recommendations? The Committee combined the original seven recommendations on the January 2012 list, five of the eight recommendations made in 2012, and two recommendations added by Eileen Holderman. These items are listed in chronological order. New recommendations will be added to the list automatically, and the Committee will have to vote to remove an item once they are satisfied with the response from the Assistant Secretary. I’ve drafted my best guess at the specific recommendations they approved (given the lack of precision on the 2012 recommendations), and I’ll post the official version when it becomes available. Is this list ever going to matter? Technically, I think it matters a great deal but I’m not sure the Committee shares that view.
Invisible Information
One of the things I said we should watch for at the meeting was any mention of the Ad Hoc Workgroup. Guess what? They never mentioned it once. This is one of the things that has me questioning if my reality is different from the Committee’s. Dr. Lee made such a point of talking about the Workgroup in 2012, and their report was published in March. But at this meeting? Total silence. It’s as if the Workgroup doesn’t exist. And not a single Committee member brought it up or asked a question. Why? What is the status of this group? What did the Committee think about the report? Did they even READ the report? Am I the only person who thinks this is strange?
The other thing that received almost no attention is the response from the Assistant Secretary to the Committee’s October 2012 recommendations. This was posted to the CSFAC website shortly before the meeting (pdf link). Again, I don’t understand why the Committee doesn’t simply review these at the outset. Instead, the only discussion was when Steve Krafchick objected that the response to the recommendation to hold a case definition workshop was not actually responsive (see the discussion on case definition below for more details).
The risk of ignoring or glossing over the official responses to CFSAC recommendations is that we miss opportunities to understand the basis for those responses. For example, buried on page 3 of the response is this statement: “To date, CDC has not been able to confirm the occurrence of outbreaks of CFS.” This leaves me wondering how in the world CDC characterizes the outbreaks at Incline Village and Lyndonville. But because the Committee does not discuss the responses, these questions don’t get raised. If I write to CDC or submit a question for the next PCOCA call, I will probably be ignored. But a CFSAC member could ask these questions and get answers on the record. Instead, this information – and the opportunity to learn even more – is effectively invisible, and it has no apparent effect on Committee members and discussion.
Oh CDC, You So Crazy
The CDC’s report of activities was ho-hum, dry, and devoid of much of interest. It was not until the Q&A sessions that we actually learned anything important.
The very first question was whether CDC would use the two-day cardiopulmonary exercise testing in phase 2 of its multisite study. Dr. Unger said that the clinicians in the multi-site study felt a two-day exercise test was “not advisable.” She elaborated that patients travel some distance to get to the physicians involved in the study and that a two-day test was not feasible. It was not clear to me whether the concern was the time required or the physical impact on the patients. I was very surprised that the clinicians (Natelson, Klimas, Peterson, Kogelnik, Bateman, Lapp, Podell) were the ones who advised against using the test because most (if not all of them) have used two day testing for some of their patients. Steve Krafchick pressed Dr. Unger, stating the importance of two day protocols for exercise and neuropsych testing in order to objectively capture the effects of post-exertional malaise. Dr. Unger said they would rely on questionnaires for functional outcomes and the clinicians’ observations of clinical course. Krafchick said it was a mistake to eliminate the testing, and asked if Dr. Unger had talked to Dr. Chris Snell. Dr. Unger said, “No.” My jaw hit the floor. How could it be that Unger has never talked to Snell about CPET? They’ve been at meetings together, including the recent FDA meeting where Snell gave a presentation on two-day CPET. I still can’t wrap my brain around this. Two day CPET provides objective evidence of metabolic dysfunction, post-exertional malaise and estimate of disability. CDC, how could you refuse to use this test?!
Another great question for CDC was whether the website would include a highlighted warning that exercise can be dangerous for ME/CFS patients. Dr. Belay answered that the website states exercise can exacerbate the illness, and Dr. Marshall asked about the equivalent of a black box warning. Dr. Belay said they could consider it. Dr. Fletcher followed up with a reminder that the Toolkit recommends exercise as a therapy, and Dr. Belay said CDC has revised the Toolkit and it is going through clearance. My jaw hit the floor again. Why didn’t Dr. Belay think to mention that in his routine report? It’s obviously of interest to the Committee since they recommended last year that the Toolkit be removed from the website. I guess Belay was planning to wait until the revision was complete, because when Steve Krafchick asked if Committee members could see it for review or comments Dr. Belay responded, “Why?” and “we don’t do that.” Seriously? Dr. Marshall pointed out comments could be useful, and Dr. Lee said they could send informational copies to interested members for feedback.
The Committee discussed a review of the CDC website, including the photos which portray people yawning at work, going for slow walks, etc. Several committee members (and many patients) feel the photos are misleading because they do not portray the seriousness of the illness. Dr. Unger responded that they want to portray a “positive” side. Seriously? To be frank, it is conversations like this one that make patients wonder what planet CDC lives on that they think there is a positive or lighthearted side to ME/CFS. The discussion moved into case definition because the CDC website and medical education material lists multiple criteria, including the maligned Oxford definition, even though CDC says it endorses and uses Fukuda. There was more discussion of the 2-day CPET, whether the Canadian Consensus Criteria is difficult to use, and whether there was enough information to endorse the Canadian Criteria immediately as many advocates insist. Unfortunately, and typically, there was no resolution on any of these issues and case definition raised its ugly head again and again.
A Rose By Any Other Name . . . .
So we come to case definition. In October 2012, the CFSAC recommended that the Secretary:
promptly convene (by 12/31/12 or as soon as possible thereafter) at least one stakeholders’ (Myalgic Encephalomyelitis (ME)/Chronic Fatigue Syndrome (CFS)experts, patients, advocates) workshop in consultation with CFSAC members to reach a consensus for a case definition useful for research, diagnosis and treatment of ME/CFS beginning with the 2003 Canadian Consensus Definition for discussion purposes.
And the Assistant Secretary responded in writing on May 1, 2013:
The National Institutes of Health (NIH) is convening an Evidence-based Methodology Workshop process . . . to address the issue of case definitions appropriate for ME/CFS research. However, it will not cover in detail a clinical case definition. The Office of the Assistant Secretary for Health, Department of Health and Human Services, is actively pursuing options for a separate effort that would work in coordination with the NIH process, but result in a case definition useful for clinicians who see patients with symptoms that may be ME/CFS. . . . .
The EbMW consists of a thorough, unbiased evidence review of the literature related to clinical research outcomes compared across case definitions and culminating in a workshop composed of experts and patients. The workshop participants and panel members will use the evidence review to evaluate the strength of evidence for case definitions with the goal of identifying the most consistent outcomes. . . . The first organizational meeting for the EbMW on ME/CFS was held on February 19,2013. A timeline for the process is being developed.
The wording of the response is very important: the EbMW will address the issue of case definitions appropriate for ME/CFS research. That does not say they will identify the correct or new research definition – just that the issue of appropriate research definitions will be addressed.
These two paragraphs from Assistant Secretary Koh’s response translate as follows: 1) No, we will not have a stakeholders’ workshop as you recommended in October 2012. 2) We will have an EbMW to address definition issues related to research. 3) We are “actively pursuing options for a separate effort” on a clinical case definition.
Understandably, several CFSAC members were upset that the answer was No-but-we’ll-do-something-else. This is what led to the fireworks at the end of Day 2. Several members reacted strongly to Dr. Susan Maier’s report that the unidentified people who attended the meeting on February 9th submitted a list of 35 to 40 potential candidates for the EbMW’s organizational committee to the Office of Disease Prevention for vetting and selection. Dr. Maier could not identify that list of candidates, although she did say that there were CFSAC members and advocates on the list. We have no timeline for publication of this list, either. Dr. Fletcher was particularly vocal about the secrecy and long timeline
I have to say that I am not surprised that the answer was “no, but . . . ” and I’m not knocking the EbMW. Dr. Beth Collins-Sharp from the Agency for Healthcare Research and Quality gave a detailed explanation of the methodology used for evidence reviews, and it is quite robust (and includes a patient viewpoint). I suspect that this is the same kind of evidence review that was requested by the CFSAC years ago in order to have a State of the Science Workshop, and which was never completed. The State of the Knowledge meeting in April 2011 was basically a State of the Science-Light kind of meeting. AHRQ’s last review on CFS was completed in 2002, so it is certainly time for an update.
The problem here is that we don’t have enough information to judge the EbMW process, since we don’t know who is on the organizing committee. We can’t judge the case definition process, since we have absolutely NO information about it whatsoever. And this leads to the real problem: THIS IS TOO SLOW.
As Dr. Wanda Jones reminded us in her welcoming remarks on Day 1, government moves slowly. It does indeed, and this creates extraordinary frustration for every patient and advocate involved. It seems unlikely (at this point, anyway) that the Canadian Consensus Criteria will be adopted as an interim measure, and none of the other case definition processes will bear fruit within the next six months. The government apparently expects us to wait patiently and calmly as this process unfolds at a bureaucratic pace. We don’t have a choice about the waiting part, but I don’t think the expectation that we will be patient and calm is realistic at all. This issue is too huge, too important, too divisive, and too slow. People are angry and will continue to be so, unless the government can demonstrate urgency.
If anyone from HHS is reading this post, may I suggest that you improve the way you communicate around this issue as a first step? The FDA communicated openly with us, and also produced a great meeting. Look to FDA for ways to productively and positively engage the patient advocate community. If you don’t, we are likely to see fireworks of one kind or another at every CFSAC meeting going forward.
Precision Is Required
Post updated June 28, 2013. See end of post for additional information from FDA.
Five ME/CFS advocates recently sent a letter to DHHS, FDA and select members of Congress requesting that FDA convene a second meeting with ME/CFS patients “to develop a clear regulatory pathway” for drugs to help us. This letter has been followed by a call for patients to email FDA in support of such a meeting. However, both the letter and the email template contain multiple statements that are inaccurate or imprecise. I am concerned that these errors are significant enough to potentially undermine the effectiveness of the letter with the very people it is meant to influence.
Part of my role as an FDA Patient Representative is to bring the ME/CFS perspective to FDA discussions. But another part of my role is to bring accurate information about FDA to the ME/CFS community. It is in that spirit that I point out a few of the errors in this letter and email campaign. I am not trying to micro-edit or nitpick. Rather, I believe that precision and careful crafting of requests can make us all more effective advocates.
The rules should not apply
The email template includes this statement:
No, FDA cannot do this. FDA is one of the most highly regulated agencies in order to make it very clear what FDA can and cannot do. The products that FDA monitors and regulates account for a huge part of our economy. FDA has an extraordinary amount of power, but the regulations exist to constrain that power. FDA cannot look at a situation, wave a wand and say the traditional regulations do not apply. There are alternatives to “traditional regulations,” but those alternatives are themselves defined by more regulations.
No regulatory pathway
The letter sent to FDA and select Congressmen states, “The FDA must create such a regulatory pathway for ME/CFS.” I’m seeing this phrase – regulatory pathway – pop up in multiple places now. While the letter does not say so, I frequently see the phrase used in comparison to AIDS, tuberculosis and Alzheimer’s. To paraphrase the argument: those diseases have special regulatory pathways so we need one too.
But this is not correct. TB and Alzheimer’s do not have their own regulatory pathways. To my knowledge, there are no disease-specific or individualized pathways. There are special programs to accelerate review, and these were discussed at the FDA meeting by Melissa Robb beginning at page 74 of the meeting transcript. These programs include Accelerated Approval, Fast Track, Priority Review, and Breakthrough Therapy. These programs are all defined by regulations, but they do not lower the standard for safety and effectiveness nor are they specific to a single disease.
Where FDA does get disease-specific is in issuing Guidance to Industry. Guidance documents are intended to give FDA’s perspective on a specific issue or disease. For example, the draft guidance to industry on developing drugs for early-stage Alzheimer’s provides FDA’s thinking on the design of clinical trials for this purpose, including selection of patients, selection of endpoints, and ways to demonstrate disease modification. Guidance documents go through substantial processes of development, including a period of public comment. The documents also do not establish legal or regulatory requirements; the guidance is a non-binding recommendation from FDA to industry.
Guidance to industry on ME/CFS was proposed at the April meeting by several people, including Ms. Jody Roth from Eli Lilly. Dr. Theresa Michele, Clinical Team Leader in FDA’s Division of Pulmonary, Allergy and Rheumatology Products – where all ME/CFS drug applications are reviewed – said:
The advocates’ letter was dismissive of the prospect of a report, saying: “A report of any kind, but particularly one that has no specific deadline, is a very poor outcome for the amount of work that was put forth by the FDA, the experts and, most importantly, this debilitated population of patients.” But there is a significant difference between a summary report of the meeting and a Guidance to Industry document. FDA can’t force drug developers to come into the area of ME/CFS. But FDA can encourage it, and can provide industry with the guidance it needs to design good clinical trials. From what I heard on and off the record at the meeting, FDA is ready and willing to do exactly that. A Guidance report would be an outstanding and much needed outcome from the meeting.
Precision is so important, especially in communicating with FDA. Claiming that other diseases have individual regulatory pathways is inaccurate. I think I know what the advocates mean here: that FDA should clearly state what endpoints and outcome measures should be used in clinical trials, and then shepherd review of products through the various pathways for accelerated approval. But that is not what the letter says, and therefore there is a risk that FDA will not understand that this is what they mean.
May I Have Another?
The fundamental request of the call to action is for FDA to hold a “true” stakeholders’ meeting by the end of the year to define a regulatory pathway for ME/CFS treatments. But why would FDA agree to hold another meeting when we’re only sixty days out from the first, especially when the meeting comment docket has not closed yet? While the letter cites numerous criticisms of the April meeting, it seems to ignore that requesting a second meeting so soon after the first and in this fiscal climate is extraordinary, and therefore a compelling case must be made in support of that request. I fear that the errors and imprecision in this letter and email campaign undermine the attempt to make a sufficiently compelling case.
Effective communication requires understanding the context and language of the audience. If we are imprecise or inaccurate, the audience will get distracted by our mistakes and lose sight of what we are actually trying to say. In turn, this can lead to the failure of the overall communication through misunderstanding or even outright dismissal. FDA’s language is based on statute, regulation and science. The errors I discussed are potential signals to FDA that we do not actually understand what the agency can do or the best ways FDA can help us.
ME/CFS advocates require the same of others. How do we react when someone says “chronic fatigue” instead of “chronic fatigue syndrome”? Or “CSF” instead of “CFS”? We expect clinicians, researchers and agency representatives to know our issues and our language. We all know the difference between the Oxford definition and the Canadian Consensus Criteria, and we justifiably react negatively if someone tries to tell us those definitions are basically the same thing. To communicate effectively with us, an agency representative would do well to be precise and accurate. Otherwise, we end up reacting to the mistakes in the message and the actual message gets lost.
To be effective advocates, we must also be precise and accurate and we undercut our own position if we fail to do so – even if the failure is accidental. I know the advocates who have called for this action, and have worked with them in the past on other efforts. Each of them is deeply committed to advancing the cause of ME/CFS patients. But as advocates, we have a responsibility to communicate as clearly and effectively as possible. It is worth the time and energy invested to craft a specific, accurate and strategic request that speaks to the context of the audience. Such a carefully crafted request focuses discussion on the substantive issue, rather than accidentally diverting attention with misstatements.
We owe it to each other and the ME/CFS patient community to get things right. We must speak with precision and clarity about complex topics, while also presenting a strong case for what ME/CFS patients need. It is not an easy thing to do, but it is essential to our collective and ultimate success.
Update June 28, 2013: After some discussion in the comments, I asked FDA whether the April meeting was sufficient to begin the Guidance to Industry process, and whether FDA would be pursuing it. Dr. Theresa Michele replied via email to me, in part: