Missed the 1/24 webinar with the GE Health Cloud's head of product? Not to worry — we recorded it for you. You can also take a look at the slides, and review some of the questions and answers below:

Q: What time and work investment will be required to migrate my app to the GE Health Cloud if I am accepted into the partnership alliance?

A: We will have to make sure you can containerize it in some shape or form. Then you will have to make sure you use the GE Health Cloud API to get access to data that’s in the Health Cloud.

You have to work with data that’s on the Health Cloud platform - not data that’s somewhere else. We will provide connectivity to bring in data from somewhere else - there’s API for that.

That said, we don’t expect it to be a heavy lift. We’ve worked with partners to make sure it’s workable and scalable. Your core app stays as is.

Q: Are there already health systems signed on, if so how many, and what is the time line for them to be on the platform?

A: The first batch of healthcare apps go live next few months; we have a lot of customers signed up, although we can’t disclose names or exact number. We’re doing a lot of testing with those customers of initial applications, we’ll start in the U.S. and expand to other parts of the world.

Q: What databases are supported on the Health Cloud? Is Oracle supported?

A: We don’t support Oracle right now — we support NoSQL, S3, Postgre, and MySQL. We can look into adding additional support based on need.

Q: How will GE’s existing provider customers come into contact with the Health Cloud? Is their use of the platform guaranteed?

A: We make it easy for customers to access apps and integrate into their existing workflows and make workflows extremely seamless. It’s the customer’s choice to use the service or not — our role is to make it easy to use and easy to adopt.

Q: How will the GE Health Cloud be differentiated from Predix?

A: Predix is built to serve all of GE’s business: oil and gas, water, healthcare, aviation, and also for asset management, operations optimization, and so on. The goal of the Health Cloud is to make it easy to build applications for healthcare — healthcare specific payloads, etc. You won’t get that on Predix directly, but the Health Cloud leverages Predix.

The Health Cloud is designed to make sure you can connect to hospitals and access the right data, then seamlessly connect back into the hospital workload.

The purpose of the Health Cloud is targeted app development for the healthcare industry, to integrate apps into healthcare workflow, and so on.

Q: Does the Health Cloud support any APIs for pushing data to the health cloud for mobile devices and vice versa?

A: At this time we have a generic API that we plan to publish; we will be adding support for getting data from mobile devices in the future. 

Q: Will the Health Cloud support IoT data streams that are deployed for healthcare uses?

A: Yes, that is one of the three use cases we target. For example, an EKG device in a hospital is streaming EKG time series data. We will offer right tools to make sure that kind of data streams into the Health Cloud.

Q: Any comments on blockchain?

A: That’s something we have been looking at very actively. We believe the distributed ledger system of blockchain will be very important going forward in the insurance market, in keeping the integrity of medical record data, etc.

Q: We’re currently working w/ a medical center for deployment of a healthcare IoT demo project which will be a clinical app. Who’s best person at GE to talk to?

A: You can contact us through the GE Healthcare website: http://landing1.gehealthcare.com/centricity-radiology-cloud-interest-contact-us.html

Q: Does the Health Cloud have any analytics services currently or planned for the future?

A: Absolutely — it’s completely a part of the platform itself. There are three parts: simple BI capabilities; analytics as a service — apply a specific algorithm on a set of data; and deep learning and machine learning.

Q: How will a typical mobile app transfer its data to the Health Cloud and get back data from the Health Cloud?

A: If you’re using our API, then your data injection and output doesn’t matter whether it’s a mobile or other app — as long as you use our connectivity API.

Q: Do GE’s customers include life sciences and pharma companies?

A: Life sciences is one of our fastest growing businesses — it’s a multimillion dollar business, and definitely part of our focus.

Q: How do I get details for the Health Cloud API?

A: The documentation is not yet public; it will be released in the next few months.

Q: Am I required to submit user testing, case studies, market data, etc.?

A: This is not required — but it is recommended as support to demonstrate how your app improves (or will improve) health outcomes. 

Q: Does the Health Cloud support MATLAB based analytics programs?

A: It will — this is definitely on our radar.

Q: For the hackathon, we have to use the API — how do we go about it?

A: Use of a particular API or SDK is not required in order for your app to be eligible for prizes.

Q: Do we have to deploy to the GE Health Cloud to be eligible for prizes?

A: No.

Q: Do we need to submit our source code?

A: No — but you do need to provide a way for us to test your app. Here are instructions for how to do that: https://gehealthcloud.devpost.com//details/faq#test

Q: How does the Health Cloud address data security for in-motion data (while data is being transferred to the cloud) as well as for at-rest data in the cloud?

A: We have high grade encryption practices for both. Very comprehensive — security is first and foremost in our minds.

Q: What differentiates the GE Health Cloud from competitors?

A: On the tech side — our APIs and services — I don’t believe there’s any cloud provider that will give so many out-of-the-box healthcare app services specifically, as well as infrastructure, security, and compliance. There’s there’s the visibility and access to all of GE’s customer base; that is a huge commercial advantage as well.