{"id":23973,"date":"2013-02-01T11:40:43","date_gmt":"2013-02-01T10:40:43","guid":{"rendered":"https:\/\/blogs.bmj.com\/bmj\/?p=23973"},"modified":"2013-03-14T12:00:08","modified_gmt":"2013-03-14T11:00:08","slug":"readers-editor-what-do-us-physicians-think-of-the-bmj","status":"publish","type":"post","link":"https:\/\/blogs.bmj.com\/bmj\/2013\/02\/01\/readers-editor-what-do-us-physicians-think-of-the-bmj\/","title":{"rendered":"Readers’ editor: What do US physicians think of the BMJ?"},"content":{"rendered":"

This blog is the first in a series about you, our readers. Fiona Godlee, the BMJ’s<\/em> editor in chief, suggested I write a regular blog explaining some of our policies and procedures. Many of them have been in place for decades, but our readership of practising physicians and academic researchers may not be aware of many of them. I’ll aim to choose topics based on recent questions from readers around the world who see the journal in print, online, and on the iPad.<\/p>\n

But firstly, why me? I edit bmj.com<\/a>, and over the last five years I’ve written a number of\u00a0articles<\/a> about digital developments and future priorities at the BMJ<\/em>. Secondly, a big part of that role is fielding reader queries. I and my colleagues in the web team get asked all sorts of questions.<\/p>\n

\"injury\"<\/a>Yesterday, for instance, a US sports physician from Concord, North Carolina, wanted to know how to cite a BMJ<\/em> article about first rib fractures, published in 1869. Readers like him were on our minds last week, when we held a BMJ<\/em> editorial strategy session in Baltimore. I and some of my colleagues discussed what the hot issues are in US healthcare and how we should cover them in the journal.<\/p>\n

The BMJ<\/em> is the first international medical journal to launch an online US edition. We now have 20 US employees, including a US news and features editor based in New York, and two research editors (one based in Washington, the other in Boston), plus a growing stable of freelance journalists and columnists working across the US.<\/p>\n

One of the issues we considered in advance of the launch was how to accommodate US spelling and punctuation into BMJ<\/em> house style. We resolved this by deciding that house style is to reflect the reader, not the author. This means that articles about the US that display online in the US edition should be in US English.<\/p>\n

Laboratory values may be expressed using either conventional or Syst\u00e8me international d’unit\u00e9s (SI) units, depending on what the author uses, with conversion factor expressed secondarily (in parentheses) only at the first mention.<\/p>\n

Articles that contain numerous conversion factors may list them together in a box. In tables and figures, conversion factors may be presented in the footnote or legend. The metric system is preferred for the expression of length, area, mass, and volume. Conversion factors can be obtained via the Units of Measure table in the the AMA manual of style<\/a>.<\/p>\n

Our US edition launched in September 2012, so we now have some analytics data to help us decide what kind of articles are popular. This helps us to decide our editorial priorities for the coming year. Unsurprisingly, US readers have similar tastes to readers elsewhere. Investigations, research, and education articles get lots of traffic, along with Christmas BMJ<\/em> articles .<\/p>\n

But surprisingly, the most read article in the US in 2012 (34,231 US page views and counting) was a Finnish cohort study<\/a> published on November 30. It explores the extent to which muscular strength in adolescence is associated with all cause and cause specific premature mortality.<\/p>\n

So far the study has not been cited and has only had two responses, but it did attract lots of US press coverage, 1000 Facebook likes, and 128 tweets. The top five most read include Brian Deer’s January 2011 series on Andrew Wakefield and the impact of his 1997 Lancet<\/em> paper false linking the MMR vaccine with autism. Here’s the top five articles read in the US in full.<\/p>\n