Radiology

 Today is our third and final post in deference to Stroke and Trauma Awareness Month:

As I mentioned in my last post, May is both Trauma and Stroke Awareness month. vRad serves hundreds of trauma and stroke centers across the U.S.  The intention of this blog series is to provide a behind-the-scenes look into our process for triaging stroke and trauma studies and relaying critical findings. 

Today in the vRad technology quest we set forth to understand Dev (or test) Environments.

Let’s jump right in.

You don’t have to work in the information security industry to know the challenge virtually all organizations face.

May is both Stoke and Trauma awareness month.  In recognition of this, we will be publishing a series of 3 posts covering:

1. Stroke information and our impact;
2. Trauma information and our impact;
3. Critical relay times and the future of stroke and trauma treatment.

Welcome back to the vRad Technology Quest.

At vRad, we value our ability to deliver frequent, regular, and minimally interruptive releases and today I’ll provide an overview of the development pipeline we utilize to achieve those releases.

Welcome back to the vRad Technology Quest. Today we’ll cover our development approach to maintaining vRad’s radiology platform.

At vRad, our development team uses the Agile Methodology, with most teams adhering more or less to Scrum.

If you aren’t familiar with software development, don’t fret; understanding how vRad develops software doesn’t require in-depth knowledge of various methodologies.

At vRad, we have a passion for connecting – with each other, with clients, and with patients. In technology, we strive to break down the language barrier between geek-speak and common users to share our tools and processes.