Bug Fix

We were made aware of a problem with our most recent curated rapid reporting packet, number 30. It turns out that there were 11 cases in that packet that were also in packet 29. This occurred because of a bug in the code we use to generate our balanced packets. Essentially, the code was incorrectly identifying which cases were not in use (and therefore chose cases already in packet 29). I’ve fixed this bug, removed the old packet 30 and regenerated a new packet 30 with new unique cases. Most of you won’t notice any difference but those of you who have sat packet 30 will have had your score for that packet reset.

Thanks to Zeid for pointing this out.

Image Manipulation Is Here!

By far the most requested feature for the site has been for us to add the ability for you to manipulate the images in your browser to help you better see any abnormality. I’m pleased to announce that with immediate effect we’ve added this to our rapid reporting module.

Depending on the browser you’re using, you’ll see one of the following toolbars beneath any rapid reporting image:

Desktop Safari/Chrome/FireFox:

Screen Shot 2015-01-26 at 21.32.40

 

Internet Explorer:

pic3

 

iOS:

pic2

 

 

The buttons are fairly self-explanatory. The plus and minus buttons will zoom in and zoom out respectively. The dark and light sun icons will adjust the contrast of the image and the looped arrow will reset the image to its original state. It’s also possible to zoom in and out of the image on desktop browsers simply by scrolling the mouse wheel (or two-finger scroll over the image on a Mac). Zooming can be achieved on iOS devices with pinch gestures.

Why are the buttons different on different platforms?

The zoom buttons are omitted on iOS because the pinch gesture works so well for zooming. Since the images are served to your browser at full resolution, you don’t lose any detail by using mobile Safari’s built-in zoom feature.

The main issue at the moment is with Internet Explorer. I’ve made it clear before that I loathe IE. The bottom line is that (at least for the moment – certainly until Microsoft implement CSS filters properly) you can’t adjust the contrast of an image using Internet Explorer. If you’re using a PC, I recommend FireFox over Chrome. If you’re using a Mac then this won’t be an issue.

Enjoy!

About our rapid reporting packets

A few people have asked recently how we go about selecting the cases for our rapid reporting module and how we create our exam packets. Rather than answer the same question 20 times, I thought I’d take the time to write an article about the process.

How do we choose the cases?

All cases are hand selected by one of our three founders. Generally they are stumbled upon during our day-to-day job of reporting plain films although we are occasionally offered examples of classic cases by our colleagues. The majority of the cases have been collected over a number of years.

It may be hard to believe but one of the most difficult aspects of building the rapid reporting module is finding good normal cases. We’ve had very few “complaints” overall about our images but when we do, it’s often because a tiny subtle abnormality has sneaked in under the guise of a normal film. Things like cervical ribs, excessive degenerative change, etc are common culprits. It’s for this reason that we now actively exclude normal variants from our cases.

Once we have the cases, what happens next?

Every case that is added to our database goes into a special area of our database called “quarantine”. Whilst in this area, the question is not shown to users of the site until removed. Every question is double read by a post-FRCR radiologist and many of the cases have been triple read for accuracy. If there is any doubt about the quality of the image or the diagnosis then the question is removed and you (the end user) never see the question.

How do you make your packets?

We are very proud of how we do this. Rather than simply randomise 50% normal cases and 50% abnormal cases, we use a custom algorithm that I wrote. First, the algorithm randomises how many normal and abnormal cases will be in each packet of 30 questions. Generally harder packets have more normal cases (although this is not always true). As each case is given an arbitrary difficulty rating (1 = easy, 5 = very difficult) the algorithm will then determine the ratios of discriminator images (i.e. very hard) to easy cases to include in the packet. The algorithm will also try to balance the packet in terms of body region. Finally, the order of the cases is jumbled up and released to the wild for your enjoyment.

Hopefully this gives some insight into how much effort goes into making our packets fair and balanced. We at Revise Radiology firmly believe that our packets are as balanced as possible. It’s for all of the complicated processes described above that we call them curated.

What’s next

So many exciting things are happening here at Revise Radiology. We have five packets in quarantine at present and are currently triple-checking them for accuracy. Once done, they will become available to all users free of charge. Watch this space!