Cross-posted on the Google for Work blog.

Japan faces a critical shortage of radiologists. Although major hospitals are well equipped to conduct scans, the scarcity of experts to read them and give patients their diagnoses means that people, especially those in rural areas, often have to wait a long time to discover their results. This can have tragic consequences for people with serious conditions.

To address this shortage and help people get accurate diagnoses faster, Medical Network Systems Inc. (MNES) in Hiroshima started running a remote diagnosis service in 2000. Rather than waiting for patients to come to hospitals, we bring the radiology equipment to them. This teleradiology service has helped combat the challenge of getting scanning technology to people in remote areas; however, we are still short on specialists that can read the scans, and we wanted to find ways to give access to patients in areas without specialists.

Last year, our team started using Google Cloud Platform to power our remote-diagnosis systems. Patients used to be given a hard copy of their scan to take to a doctor or specialist. Moving the process to the cloud speeds everything up. All of our buses are equipped with CT scanning machines, so our technicians upload images and scans right from the bus. Specialists can then log into the system from wherever they’re working and see the scans and diagnose the patient remotely.

Reading scans is a very specialized process. Radiologists must examine lots of images and scans in a very particular sequence, and it’s important that this process isn’t laggy or slow. One of the benefits of using Google’s services is that they can handle massive volumes of information. Google App Engine processes the images and data in the right sequence and enables us to cross reference patient inputs with existing radiographic and pathological information.

Instead of waiting for a few days or a week for a diagnosis, which was the usual turnaround for our teleradiology service, patients get their results within a few hours. And it’s not just our patients benefiting from remote diagnosis; enabling our radiologists to work from anywhere has meant that many of our female specialists are able to stay in the workforce — diagnosing scans while working from home and taking care of their kids. With so few radiologists in Japan, this flexibility helps us keep skilled technicians in the workforce.

We’re optimistic about the potential for cloud-based technology to enrich our understanding of pathological issues and believe it signals a new chapter for the healthcare industry by removing geographical barriers between patients and doctors.

- Posted by Dr. Naoyuki Kitamura, CEO, Japan’s Medical Network Systems Inc.

We know that developers don’t want to spend time managing their billing information so we’ve added a couple of useful features to make managing your billing easier and less time consuming.

First, you’re now able to consolidate multiple projects and pay for them under a single billing account. This means you no longer have to manage and maintain billing information in multiple places. It also lets you quickly and easily set up new projects without having to re-enter your billing details.

Consolidate multiple projects into a single billing account

Second, we know that sometimes you want another person (e.g. your accountant) to have access to your billing information but don’t want to grant them ownership permissions on your projects. You can now invite additional billing administrators from the Developers Console who can view and manage your billing details but are not automatically project owners.

Add additional billing administrators

With these two changes, you can spend time less on billing and more time doing the work you care about.

-Posted by Dan Stokeley, Product Manager

Israel is a country in which life is rarely dull. Many Israelis read or listen to the news several times a day, often from leading broadcaster Channel 2 News. Channel 2 has responded with the development of a mobile app, to which it continuously streams its news broadcasts. In November 2012, events in Israel led to a peak in app usage. This led to availability issues, which persisted despite servers being added during the crisis.

To cope with such unexpected peaks in traffic, Channel 2 News decided to migrate the infrastructure for its mobile app to Google Cloud Platform. To find out more about the process and the results of the migration, read the case study here.

-Posted by Ori Weinroth, Product Marketing Manager

At the first Google Cloud Platform Live, developers told us that they were inspired to be surrounded by hundreds of their peers using Cloud Platform technology to turn their ideas into reality. They had the opportunity to meet Googlers who designed and built the products they use and hear, firsthand, about our vision for cloud computing. On November 4, Brian Stevens, who recently joined as Vice President of Product Management for Cloud Platform, and I will outline our next steps for Cloud at the second Google Cloud Platform Live.

We’ll share how Docker and Kubernetes can complement VMs as well as how our flexible PaaS solution provides workload portability and ease of use. We will give a sneak peek at the future of our mobile services, making it easier than ever for you to build a Cloud-backed mobile app. We’ll also be talking about how you can get useful insights from ever growing data.

For those who get to join us in person, we will have a Partner Sandbox, featuring MongoDB, Datastax, Fastly, RedHat, SaltStack, Tableau and Bitnami where you can see first hand the work they are doing with Google. And, just announced, an after-party to celebrate the day’s events.

Finally, we just released a new list of speakers, including the engineers, product managers, and developer advocates who build the products you know and love. You can see the full list of speakers at - and come back to see updates between now and the event.

Click here to register. See you on November 4!

- Posted by Greg Demichillie, Director

mCASH, a payment provider located in Norway, relies on Google App Engine to build a resilient payment system for users that can handle the incredible rate of growth of mobile transactions.

As more consumers switch from cards to mobile, mCASH anticipates large-scale volume to their virtual bank, where a customer can send and receive money instantly, pay bills, view transactions, and even obtain instant credit.

“With App Engine, we can go from ten transactions a second to thousands a second without a hiccup. Expanding across borders into new markets becomes vastly more tractable. It scales beautifully,” notes founder and CEO Daniel Döderlein.

To learn more about their use of Google Cloud Platform and subsequent results for their business, read the case study here.

-Posted by Ori Weinroth, Product Marketing Manager

In an effort to add transparency, speed and simplicity to our release process, Google Cloud Platform will align our own release definitions and process with how our developers manage their projects. We are eliminating the confusing (and Google-specific) “trusted tester,” “limited preview” and “preview” phases and replacing them with simple Alpha and Beta releases. These align more closely with standard software practices for pre-release products.

Going forward, all products will be pre-released in Alpha format for testing by a select group of customers, and after passing this phase, will be released to Beta testing. Beta products are available publicly to all customers but will not have SLAs and full support until cleared to General Availability. Timing for each phase varies by product and will be announced accordingly.

Some more precise definitions:

Alpha is a limited availability test for releases before they are cleared for widespread use. By alpha, all significant design issues are resolved and we are simply verifying functionality. For Alpha, customers need to apply for access, agree to applicable terms and get their projects whitelisted. Alpha releases don’t have to be feature complete, no SLAs are provided and there are no technical support obligations, but they will be far enough along that customers can actually use them in test environments or for limited-use tests -- just like they would in normal production cases.

You will mostly only hear about products when they’re released in Beta stage. This means you can now use it openly without access controls. However, beta products will not have an SLA or technical support obligations. Charges may be waived in some cases. Products will be complete from a feature perspective, but may have some open outstanding issues. Beta releases are suitable for limited production use cases, though customers should be aware that this is pre-release software and full, SLA-bound use is not encouraged until General Availability (GA).

Along with the introduction of Alpha and Beta, we are renaming the “Trusted Tester” program, which is designed to give a small group of customers tight integration to our design process during early stages of development, the “Early Access Program" (or EAP). Most products won’t go through this phase, but for certain programs where complexity and breadth of design are significant, we will continue to seek tight integration and feedback from a select group of customers.

These new program names roll out immediately -- we look forward to your participation and your help in making Google Cloud Platform better with each new release!

--Posted by Tom Kershaw, Product Management Director

Today’s guest bloggers are Brian Peterson and John Rector, co-founders of Switch Communications, a San Francisco-based voice communications startup. Learn more about how they use Google Apps for Work here.

At Switch Communications, we fundamentally believe that technology should empower people to work faster. That was the driving principle behind, a cloud-based business phone system we launched yesterday enables you to make and take calls from anywhere, on any device, so you can be as productive on your smart phone at the local coffee shop as you are on your desk phone at the office. With, calls ring on all connected devices, so you don’t miss any calls, and it’s easy to switch seamlessly between each of those devices without having to hang up and call back.

Of course, we apply the same principle of speed to our company, too: technology should help our employees be more efficient, flexible and agile. That’s why we built on Google Cloud Platform — because we believe startup founders should spend time on products, not on backend architecture.

John Rector and Brian Peterson, co-founders of Switch Communications

Selecting the cloud service for your underlying architecture is a key decision for any startup. We evaluated a number of platforms, but quickly determined that Google’s Cloud Platform was by far the best fit. We knew we were dealing with a complex system with our telephony infrastructure, and given the viral nature of our initial conferencing product, UberConference, we also knew we needed solid scalability and flexibility. Google Cloud Platform ticked off all the right boxes.

Google App Engine made rapid development of possible. In fact, we built on App Engine in under a year, which would have been unheard of just a few years ago given’s sophisticated infrastructure. Since all of the core routing and smart business logic takes place in App Engine, we’ve eliminated the need to perform administrative tasks or carry pagers around to deal with maintenance issues.

In addition to App Engine, we’re heavy users of Cloud Datastore, which makes it easy to upload all of our data into a simple, searchable database. For example, we’re able to provide search functionality across a user’s entire history of messages in real-time by just typing in a few letters. This setup required just one engineer and was completed in about a month -- a MySQL database couldn’t have enabled a similar result.

Beyond building on Google Cloud Platform, we utilize the set of rich Google Apps APIs to integrate with Google Apps for Work. When you call someone from, you get useful context by seeing recent Gmail messages, shared Google Docs, and upcoming Calendar invites. You can even launch a Hangout directly from a conversation.

With Google Cloud Platform, we can prioritize building dynamic features instead of bailing out water repairing databases and networks. It helps us focus on what we really care about: improving the product to create a great experience for our users and, like Google, making work easier.

-Contributed by Brian Peterson and John Rector, co-founders of Switch Communications