Looking for the Next Big Digital Health Disruptors

Every new healthcare app or fledgling technology is like a sunny window into the future: Could virtual reality replace opioids for pain relief, as proposed by startup DeepStream VR? Might smart contact lenses, under development by Verily (aka Google) and Novartis, soon measure blood sugar levels in tears, eliminating painful finger pricks for people with diabetes?

This optimistic focus on innovation is what makes the upcoming Health 2.0 conference a driving force in an industry dogged by numerous problems—from a lack of care coordination and wasteful practices to a lack of IT interoperability and workforce shortages. Every year, the conference offers some of the tech industry’s best ideas for solving these problems—or making them disappear altogether.  

Continue reading “Looking for the Next Big Digital Health Disruptors”

Exchanges 3.0? How health insurance marketplaces are evolving

Consumers are buying health insurance in new ways these days, while still turning to in-person help for making a choice — even in the age of the online economy.

The end of January brought the end of open enrollment for the third year of the exchanges, a key part of the Affordable Care Act. It’s been a rocky trip for all involved, especially consumers, many of whom were digital-savvy purchasers of all kinds of goods and services before the ACA.

HiRes-1.jpg

Continue reading “Exchanges 3.0? How health insurance marketplaces are evolving”

Where Is Disruption In #HealthIT?

7 truly innovative technologies in healthcare!

blog2

In 2000, Harvard Business Review ran an article about the threats to existing business models and entrenchment that often prevented innovation and disruption in healthcare.  In it Clayton Christensen, et al described real disruptive technologies being those that “enable less expensive professionals to do progressively more sophisticated things in less expensive settings.”  Since then, the Accountable Care Act was passed and it may one day prove to be the enabler of insurers, regulators, hospitals and health professionals  working together to facilitate disruption instead of uniting to prevent it.

Continue reading “Where Is Disruption In #HealthIT?”

Does Documentation Still Matter?

It’s a great time to be a healthcare software developer. You’ve finally broken free from the traditional software development process. You can now use iterative or Agile development approaches to deliver high-quality software in a fraction of the time.

And the best part of it is that you no longer have to deliver all that painstaking documentation with your applications, right?
Wrong. Dead wrong.

Too many Health IT solution providers are falling into the trap of thinking that streamlined development and faster processes have somehow eliminated the need for good documentation. They figure, “Since everything is moving so fast now, surely the top priority is to start cranking out code as soon as possible.” Continue reading “Does Documentation Still Matter?”

Vicert @ “Berlin API DAYS 2014”

In May 2014, Berlin was the host of API Days convention, and this time it was pretty much developer oriented. Naturally, Vicert has sent one of its team members to attend. Here are the impressions.

Are Web APIs that big of a deal?

Yes, yes they are.

Web APIs are gaining in importance as a way of providing software, but also as an integral part of the web site. Developing and owning Web APIs can be very profitable (Google Maps comes to mind) so it is no surprise that there are more and more startups with Web API as their product.

Continue reading “Vicert @ “Berlin API DAYS 2014””

#2 Spring: Manipulating Salesforce objects

In Part 1 of this topic, we saw how to do OAuth authentication with Salesforce  using Spring. In this part, we’ll see how to fetch and update records  and upload documents to Salesforce using Force.com REST API.

Using Force.com REST API from Spring Web application – Part 2: Manipulating Salesforce objects

Force.com  REST API Resources are used to manipulate objects, execute queries,  display API information etc. Each resource is tied with a specific resource URI which is used to read, create or update record. All URIs  have common base URI: “http://domain/services/data”. Domain is usually instance URL retrieved during authentication, or a domain pointing to some Salesforce instance.

Continue reading “#2 Spring: Manipulating Salesforce objects”

#1 Spring Web application: Authentication

Force.com  REST API provides a simple and powerful way of communicating with  Force.com. It is a great way for a secure programmatic access and  interaction with Force.com from a Web or mobile application using REST-based web services.

Using Force.com REST API from Spring Web application – Part 1: Authentication

The API is based on using Force.com REST Resources. REST resource can be a single data record or a collection of records,  like Salesforce objects or custom objects. Each resource is identified  by a named URI, and is accessed using standard HTTP methods (HEAD, GET,  POST, PATCH, DELETE).

Continue reading “#1 Spring Web application: Authentication”

Spring: ServletContext attributes

Sometimes  you need to expose some Spring bean or property for parts of  application unaware of Spring. This can be easily achieved if the Spring  unaware code is aware of servlet API. Spring provides a way to expose  beans as ServletContext attributes using ServletContextAttributeExporter.

Implementation

Let’s cut right to the chase.
Assume we have a properties file named config.properties containing name-value pairs which we want to expose to some Spring unaware code. We can create java.util.Properties bean using Springs <util:properties> tag. First, we must define util namespace in spring beans configuration file:

Continue reading “Spring: ServletContext attributes”