Dave Dyell is SVP of product development of NantHealth of Culver City, CA.
NantHealth exhibited at the HIMSS conference, but nobody I talked to could figure out exactly what the company is selling even after talking to the people in the booth. What is being sold today?
The solutions fall primarily into two sections today. One of those is connectivity, the older iSirona set of products, but taking them beyond the traditional “in the house” variety that iSirona has focused on. Focusing primarily more on telehealth.
There were other assets that were available as part of NantHealth that we’ve brought to that connectivity suite. Medication adherence — it’s a solution called the GlowCap and the GlowPack that we can place into a home that allows to track whether or not a patient is actually taking their medication when they’re supposed to. That is live today in multiple organizations.
We currently also have a product we call the HBox, which is just going GA right now, which is allowed to go into the home and be able to communicate to virtually any medical device that a patient may have in the home. This could be an off-the-shelf glucometer, your scale, blood pressure cuff, things of that nature that would bring that data back and send it to the cloud.
The second part of the solution set is what we call interoperability. This is the ability to go in and partner with an ACO organization to provide the technology platform. That is our Clinical Operating System that we launched at HIMSS, which allows us to then connect to all of those systems that a particular physician’s practice may be running. The ACO is going to be needing to be able to interact with the data about that patient, obviously connecting to the hospital systems.
Any typical hospital can have 80 to 100 different systems. We can pull data from all of those silos, as well as then the insurance companies, and bring in all the historical claims data and other information from maybe even pharma. Any of the claims data that would be related to any of the healthcare around that patient.
I wasn’t clear when the announcement was made about the Clinical Operating System. I understand that there’s like 80 acquisitions involved and suddenly declaring those to be a Clinical Operating System seems like a bit of a stretch from an interoperability standpoint.
The Clinical Operating System actually came from a single organization previously known as Net.Orange. It was built from the ground up to be a Clinical Operating System. That was the original vision that that team had for that particular product.
You’re looking at seven-plus years of development that’s gone into that particular platform, building each and every one of those individual connectors over time. All of them tied to an implementation. That’s the key –going into an organization and actually performing that integration rather than just building an off-the-shelf connector to it.
I must have missed that point with the announcement. Tell me again, what exactly is the Clinical Operating System and what is its heritage?
It was designed from the ground up to be based on bringing supply chain principles to healthcare. Dr. Rangadass and his team came from the old i2 space in supply chain management. Obviously i2 had a breadth into healthcare as well. One of the things that frustrated them was the waste that happens in healthcare.
When they started looking at building the next generation of platforms, they wanted to build something that could literally sit on top of all these different systems, gather the data, and then bring it to the front. In the case of applications, that would look at things that we call Value Monitor, which would help you see how you’re comparing to your peers.
A lot of the typical trending applications that we’ve all seen in healthcare and worked around for a while — their real goal was to see, can we build a data model and a set of services that essentially, if you wanted to build any healthcare application on, we would have those basic services. That’s what they set out to do. That’s why we call it an operating system, because they’ve literally built a service that can do just about anything you would possibly want to do in healthcare if you were trying to build a clinical application.
There are customers live on this now?
There are. US Oncology is one of those customers that’s been using the platform for 5+ years. They’ve got all of their physicians on it.
But they’re not really a hospital and you’re targeting this to hospitals. Are there hospitals live?
St. John’s Health System in Los Angeles.
That’s the only one?
It is, yes.
When you’re describing this to a hospital that might be a prospect, what is it that you tell them they could do and what capabilities they need to run this on top of their existing systems?
The biggest traction we’re getting right now in the conversations with hospitals is of course around population health management. Everybody’s trying to figure out what is population health management. There’s a lot of buzz, a lot of noise. But one thing is for certain – everyone is trying to identify that platform that they’re going to use to pull all of this data together.
They all understand they need the data. They know there’s data locked in their EMR. They know there’s data locked in their other independent systems. They know there’s data locked in the multiple physician EMRs that are out there. How do they bring all data together into a single platform, that if they’re going to form some type of accountable fee structure, that they can use that data to care for that population? That’s normally where the conversation starts.
Once everybody understands the full depth and breadth of the Clinical Operating System, they immediately see the value. They immediately see where this is different than anything they’ve seen before. Where we can bring together that data unlike anything else that’s ever been done before. Then you add to it the rest of the things that belong in the NantHealth family. You start talking about genomic data, you start talking about proteomic data, and you bring that science in and add that to that clinical component. It’s not like any platform you’ll ever find out there.
Are all these acquired companies still operating independently under their own names or is the plan to roll them all up into a super-product?
Unknown to the market is that this didn’t start like a light switch on January 1. Dr. Soon-Shiong has been an investor in iSirona for over five years. He’s been an investor in many of these companies for years. This has always been something we talked about. It’s always been something that we started to plan for and operationalize around, even from a perspective of technology choices we’ve made in our applications.
We’ve had most of our things interoperable over the years to be prepared for this. I personally spent most of 2013 and parts of 2012 taking other assets that he had invested in that were no longer surviving as a market go-forward company and bringing those in and integrating them into iSirona in the background, being ready to launch on January 1. The launch of NanthHealth was January 1.
As of January 1, we are a single operating company. We are going to market with a single sales force, single message, single company. There won’t be an iSirona any more. There won’t be in Net.Orange. There won’t be any of these individual companies any more. They will only be NantHealth. The market is going to sit back and wait to see whether we can pull off or not but it has already actually been in place for a large number of years.
What’s the effort required and what are the steps that are required to turn a bunch of piecemeal investments into something integrated?
We’re a little over 350 employees right now as a company. We have 280+ hospitals that are using some aspect of our technology. Most of that is the iSirona stuff, but still, there are others that are using different pieces of the rest of the portfolio.
We’ve got over 50 percent of the different US Oncology practices that are currently using our decision support engine. That came in from a company called Eviti that’s a part of the portfolio. There are a very large number of practices and companies and revenue that are coming in the door today.
As far as putting it all together and making it that single cohesive story, again, we believe we did that in preparation for the launch at HIMSS. We are out in the market with that single message.
You had 180 or so employees at iSirona. I didn’t appreciate what a big chunk it is of NantHealth.
We are, yes.
Dr. Soon-Shiong has a far-reaching vision on personalized medicine and genomics. What are the steps required to take NantHealth to meet that vision?
We already have the genomic, the proteomic technology. What needs to be done now is taking that data and being able to map it in a meaningful way into the rest of the care process.
If you’re a case manager who’s looking at a care plan and walking your way through that on a member of your population that you’re trying to manage, and all of a sudden a physician orders a gene mapping and you get those results back, what do you do with that data? How do you map that wisdom that’s going to come back from the science into the overall decision support workflows that are going to be around traditional population health management to make it different?
We like to say it this way within NantHealth. What’s that one piece of data, that if we could get in front of a caregiver, would make for a significantly better outcome? That’s really what drives us all — trying to find that one piece of data, that one other piece of data that I could put in front of a physician, put in front of a caregiver, put in front of a scientist for that matter, that would give that patient a much better outcome.
BlackBerry seems to be on its last legs. Why did it suddenly get interested in healthcare and what will it co-develop with NantHealth?
That’s an interesting perspective, because one of the largest portions of the market that BlackBerry owned was healthcare. I don’t think I’ve walked into a hospital in 15 years that hadn’t had some form of BlackBerry technology there. The BlackBerry enterprise server is installed in hundreds of hospitals, if not thousands across the country, because of its secure messaging and because of HIPAA concerns and those things. People have been using BlackBerry for years.
They use BlackBerry devices, but this is actually developing healthcare-specific technologies and not just saying they’re going to park BlackBerry in a hospital.
It is, but that’s to me why it’s a natural foray for them. They’ve already go this large infrastructure. They’ve got a large customer base that’s already in healthcare that’s using one of their devices.
What they saw obviously with NantHealth is on our connectivity side again. Connectivity everywhere, regardless of where you are. We think the smartphone is another logical place to provide some of that connectivity. Not everybody’s going to want an Hbox in their home. A lot of us that are more tech-savvy are going to want our smartphone to be that.
Having the Nantoid with BlackBerry is going to be a really interesting play for us to be able to provide a device that’s optimized for that connectivity, optimized for image display, those types of things.
The NantHealth offering isn’t exclusive to BlackBerry, right?
No, of course not.
So their contribution is just to optimize it for BlackBerry?
What are the milestones the market will see in the next few years from NantHealth?
I think what you’re going to see over the next few years is some significant growth within the telehealth side of the business as we continue to expand the connectivity-everywhere approach. You’re also going to see on the interoperability side us expand much more heavily into population health. We have some releases and stuff that will be coming out soon and new customers on that end where the Clinical Operating System is being used as the basis for multiple population health deals. These are again primarily focused around ACOs at this particular point.
Wearing your iSirona hat, what did you think of the FDA’s report and the topic of medical device integration with EHRs?
What’s interesting is if you look at the majority of the market, at least for the more mature companies, everybody’s already there anyway. Cerner produces medical devices. Siemens produces medical devices. GE produces medical devices. Maybe an Epic on the outside, but they’re got laboratory systems, many of which are already regulated.
I’m not sure why any of them would be concerned about this from an overall ruling perspective. Most of them already have some type of quality management system and build their software under that ruling anyway. I was a little bit shocked that the FDA didn’t take it a little bit further than they did considering that reality.
I think there’s this misperception in the market that somehow software vendors don’t follow quality processes. But for the most part, they do, especially if you’re going to be an international company. For the rest of the world, if you’re not building your clinical software especially under a quality management system of some sort, whether you’re fully ISO certified or not, just having a quality management system is so important in trying to market to the rest of the world. If you’re going to be an international company at all, you have to be able to show that you do actually use quality within your development practices.
What about the status of alerting and alarming? What’s being worked on to try to make that smarter?
We obviously follow that space pretty closely because of the fact that we connect to so many medical devices now. A lot of those vendors in that space look to us for the data. We got our own alerting and alarming package cleared last year that we call Magellan. We started to bring that to market around HIMSS as well. We’ve launched that and we should be seeing some press releases on that coming out soon. It’s a space that we believe in, obviously, and one that we’re going to continue to invest in.
Do you see a point where there won’t be a third-party product in between the medical devices and the EMRs to help negotiate the conversation so that it makes sense to the clinicians?
I really don’t. You’re right – HL7 and other types of integration standards that have tried to standardize the industry, what we found is is that until customers demand that interoperability, there always ends up being somebody in the middle.
I’ve been in healthcare long enough to remember when HL7 was in its infancy and when products like Cloverleaf and at that time DataGate and the old Healthlink product were all just coming to market. Every one of them, everybody thought would last a few years and then HL7 would have that broad market adoption and nobody would need integration tools any more. EAI was going to be a short-term thing. Those engines are still going strong today.
In the mean time, companies like Orion, companies like InterSystems have come out and completely stolen market share away as those products have died in some cases, especially in the case of the eGate thing after they sold it off to Sun and Oracle. You really see that everybody believes these integration technologies will only be around for a little while, but they end up staying because even once the standard’s adopted, the standard doesn’t necessarily always fit every situation. So no, I don’t see middleware, if you would, going away any time soon to help broker that conversation.