If there ever was an opportunity for citizen journalism to ever actually “own” a story unlike the mainstream media, the current swine flu epidemic could definitely be it.
In short: by tracking trends of people complaining of having flu symptoms or reporting localized outbreaks on Twitter and other social networks, the “hive mind” of these social networks may quickly be able to spread word of where outbreaks are occurring long before state or local health agencies are able to pull together a press conference.
More importantly, any sort of spreading virus creates a demand for hyperlocalized information which is best covered by those on the ground who can collect and broadcast information to the people around them.
Keep in mind, though, to differentiate “confirmed” outbreaks and infections from official sources and reported or suspected cases from citizens or doctors.
Some resources and tips on collecting news and tips of the swine flu outbreak:
Using Twitter: Be sure to follow @breakingnews (which is doing exhaustive coverage of the epidemic intenationally) and @cdcemergency (the Centers for Disease Control), but also find and follow local paper, news radio, or TV stations for their breaking news feeds and Twitter accounts. By searching the Local Tweeps directory you can also find other Twitter users in your area who may be the first to report on news or rumors of infections near them. Send out an occasional tweet asking subscribers if they’ve heard of local infections or preparations, and to contact you if they hear anything new.
Pick up the phone, or send an email: Contact your doctor, school nurse, or nearby medical facilities to find out if they’ve handled any potential cases of swine flu, and how they’re prepared to handle a potential pandemic. Whether or not they have a straight answer will be worth reporting on.
Additional resources: A Google map of reported swine flu infections in the US and Mexico, Mashable’s Guide to Tracking the Swine Flu online, and the Centers for Disease Control Emergency Preparedness and Response page.
{ 0 comments }