Cdc wonder api
Covid-19 vaccine safety & effectiveness & how to address
“Write a package” had been on my to-do list for a while, so I took the plunge this summer. I decided to start with something seemingly straightforward, such as writing a few functions to query an API and parse the results. With the aim of making federal health data more available, I decided to tackle the CDC Wonder API. I concentrated on writing code to set up the database requests and process the responses since Bob Rudis had already developed a feature to make CDC Wonder API query requests–wondr::make query(). As is often the case, the mission proved to be more difficult than I had expected.
1. Any question must contain a long list of parameters, but the CDC Wonder API documentation does not define what those parameters are, other than giving two examples for one of several databases (Ex. 1, Ex. 2).
3. The most important aspect of the xml answer is a nested table, which can be difficult to parse due to a variety of quirks in the tables, such as rows of different numbers of cells, as in this example:
The overall solution was to put in a lot of effort behind the scenes to find out how to set up a query, and then store relevant data in two places: internal lookup tables in R/sysdata.rda for use by package functions, and codebook vignettes for the user. The script for generating all of the data files can be found here.
Lockdown talanoa with dr api talemaitoga – “we are still at the
The Mortality – Infant Deaths (from Linked Birth / Infant Death Records) online databases at the Centers for Disease Control and Prevention (CDC WONDER) provide counts and rates for deaths of children under the age of one year that occurred in the United States to U.S. citizens. The data from death certificates has been matched with the data from birth certificates. Data is available by maternal race and ethnicity, maternal age, maternal education, and marital status, as well as by child’s age, underlying cause of death, gender, birth weight, birth plurality, birth order, gestational age at birth, time of prenatal care, gestational age at birth, gestational age at birth, gestational age at birth, gestational age at birth, gestational age at birth, gestational age at birth, gestational age at birth, gestational Since 1995, data has been available. The National Center for Health Statistics is the source of the information.
The recent Ebola outbreaks highlight the importance of having up-to-date and reliable health information. The federal information source for Ebola and other infectious diseases, as well as other public health statistics, is the Centers for Disease Control and Prevention (CDC). Data.CDC.gov has 48 datasets and views ranging from smoking statistics to infectious disease statistics. The Socrata Open Data API allows developers to integrate JSON data into their applications.
The CDC provides a way to integrate health data into blogs, websites, and social media for those who aren’t developers. Users may embed a microsite into their website or app using Tools.CDC.gov. A microsite is a standalone Web page or collection of pages that can be embedded into another Web page. Microsites are one way to bundle and repurpose federal government material, also known as “content syndication.”
A consumer might want to use the CDC’s microsite “What’s New | Ebola Hemorrhagic Fever” as an example. The user will then select the “Get Embed Code” tab and copy the code to his or her website. The material will be transmitted to the Web page if you refresh the page. The CDC handles all updating and code updates, while the data is automatically pushed to the user’s Web page. The CDC also provides documentation about how to customize the microsite so that it matches the design and functionality of the user’s Web page. [Please note that Ebola data is currently unavailable on Data.CDC.gov.]
Covid-19 town hall videos and materials: opening remarks
It’s difficult to get government data directly from the source. If you’ve done it, or at least attempted it, you’re familiar with the frustrations of oddly formatted files, ineffective searches, and annotations that reveal nothing about the data in front of you.
The most aggravating aspect of the process is realizing how valuable the data could be if it were exchanged more easily. Unfortunately, usability is seldom the case, and we we spend more time encoding and checking data than we do actually using it. Isn’t it supposed to be the other way around?
Perhaps the people in charge of these pages just have no idea what’s going on. Or maybe they’re frustrated by suck and don’t know where to begin. Or they’ve been afflicted by the that’s-how-we’ve-always-done-it virus without realizing it.
I’m going to use the Centers for Disease Control and Prevention as a test case, but much of what I’m going to cover should apply to other government websites as well (and non-government ones too). And I choose the CDC not because they’re the worst, but because they publish a lot of data that the general public can use right away.