Smart Cities Aren't Just Smarter, They're Healthier

February 06, 2018
smart cities are healthier

If it’s healthy to bike, why doesn’t biking reduce my healthcare insurance costs?

My thought process on this one was interesting. I don’t quite remember when I started thinking about this, but it recently came together in my head.

The benefits of exercise

Just 20 minutes of exercise delivers health benefits. Depending on your malady — you can improve depression, diabetes, weight, and more with a small amount of exercise.

Biking is exercise.

I’ve been using Citi Bike for just that reason. I have a weak knee. My alternatives are surgery or 20 minutes of biking a few times a week. For those who don’t believe this, I’ve avoided surgery for about 22 years because I happened to find a doctor who was ahead of his time back then and treated with exercise first.

Who benefits if people are healthier?

Aside from the people, insurance companies benefit.

If an insurance company can improve their financial metrics, why wouldn’t they?

So, why wouldn’t an insurance company subsidize a Citi Bike membership?

There’s an ROI calculation right there.

Is the health benefit greater than the cost of a Citi Bike membership (assuming the health benefit is the only one for the moment)?

Simple, right? Maybe. So why don’t they?

Let’s have a look at how this would work to understand where the barriers are. In short, the barriers are not technical, they’re procedural in how companies think about their offerings and how they deliver technology products to the market.

What if?

Here’s how I’d imagine that working. Not all of the technology is in place for this today, though I believe all of it is possible.

  1. I have agreed with my insurance company that if I stick to their exercise plan they will cover my Citi Bike membership, otherwise I will. I will share data about my rides with my insurance company, and we will decide each week if I have met my goals for coverage. The insurance company will pay for my Citi Bike up front and each week that I don’t meet my goals, they will automatically withdraw 1/52nd of my membership from my bank (or Apple Pay, or whatever). It’s seamless, and if I miss a whole week of riding it’s a penalty I can live with — this is the customer experience part, and an important part of the implementation to consider.
  2. I walk up to a Citi Bike with my iPhone and Apple Watch.
  3. I swipe my phone or watch to unlock the bike. By using my phone/watch instead of a FOB, I can incorporate sophisticated identity authentication, so that I know with great certainty who it is that has unlocked a bike. There’s also no manual intervention to the process of making sure all rides are tracked.
  4. If I have an Apple Watch, Gymkit is used to automatically start a workout and collect extra health data with that workout (like heart rate).
  5. At the end of my ride I swipe my phone/watch again. This is different than today, where putting the bike in the rack ends my session. Swiping again allows the identity authenticated via the phone to verify that I was the person riding the bike (because I was at both the start and finish points of the ride).
  6. After the ride, data from the bike and from my devices about the workout are sent via a HIPPA-compliant app using a FHIR API back to the patient data record system used by the insurance company to track this program. The insurance company can even offer a service to patients/doctors to share this work out information with the patient and their doctor so that they can better discuss health outcomes.

All in, some things to consider closely but not terribly difficult of a technical challenge. I think today one could use Bluetooth LE on the iPhone (but not NFC) so that would require different technology on the bike racks (which might change their fundamental economics that would impact the ROI). Also, in order to ensure that people swipe before their bike is locked at the end of the ride would take some user retraining and reworking of the bike dock software.

The key thing here is changing some of our assumptions around how authentication is used. We can use biometrics and Device DNA to make sure it’s me, and tie that right into the application flow so that we get beyond trusting someone that they’re working out according to plan. That same identity would be used to govern the HIPPA implementation requirements. There would be no manual intervention to the overall process.

By the way, today many corporate healthcare programs include gym membership discounts, but have no way to track if people are actually using them. The discount costs someone something, but there’s no governance. What’s amazing about smart cities and these bikes is that we can govern the behavior we are trying to encourage.

It seems like a win-win, except we’ll infuse this with faulty assumptions that make it impossible to get to an ROI metric or deliver something simple. Complexity is the devil for simple use cases like this, at least until they’re proven to be valuable use cases.

Stop with the bad assumptions

In my head, I hear people saying things like:

  1. My city has something other than Citi Bike, we can’t do this until we can support all cities.
  2. I walk, I don’t like to bike, we have to do this for people who bike AND walk or it’s not fair.
  3. Whatever we do has to work for iOS and Android users, or we can’t do it.

The answer to all of these is, "not really."

I think insurance companies need to start somewhere. Who knows if something like this will even be successful. Start small, manageable. Then grow. It’s easy enough to add other cities once we know how it works. It’s actually harder to solve for modularity and expansion until you understand the core integration problem and what kind of modularity you need. NY would certainly give a lot of data it being the largest shared bike implementation in the US.

Also, with the right API abstraction and capabilities to deliver security and privacy policy in the infrastructure (rather than as part of the app integration silo), it becomes relatively easy to expand to new bike systems.

If you walk and don’t bike, you have the exact same insurance offering you have today. If you want to take up biking, you have some motivation. If you don’t, well, other people will benefit and maybe on the next project, you will. (PS it’s quite obvious how once this is in place, the same could be done for walking should the benefits be able to be quantified so that an ROI could be done).

As for iOS and Android, think again. It’s faulty to assume that something has to be done on all platforms or none (see Aetna and Apple Watch). Tight integration is necessary to maximize the focus on customer experience and to make sure that an ROI can be achieved. Trying to support too many platforms dilutes the capabilities that can be supported, and increases the friction for users because they will be presented with things that make sense on other platforms, but not their platform of choice.

That doesn’t mean there shouldn’t be an Android solution. It means that even an Android solution needs to be vertically integrated to maximize the experience.

When you make assumptions like these, you introduce complexity. The complexity makes it harder to get the project started, and harder to keep the customer in mind. Focused on one’s own process, this seems like an awful lot of work just to give a customer a discount. There’s not really a penalty for companies to keep doing what they’re doing today instead of trying something totally new. So nothing happens, at least in this specific use case, for now.

If you think this is crazy, you’re not paying attention. This makes perfect sense in a connected city and is a great use of technology to demonstrate the benefit of being connected. For example, in China if you don’t follow the rules on trains it impacts your credit score:

David Bressler is VP Vertical Solutions (Focused on IoT these days), API Management at CA Technologies where he helps tie together business drivers to technology solutions. His newest book is "The Elephant in the Room has a Paycheck."

Overlay Init

Curated By Logo