Finding Your Ideal Healthcare IT Partner

In our previous article, we discussed the expectation gap that forms when an organization like yours engages a healthcare IT outsourcing firm to help with a software development project. To put it simply, the gap between the expertise you expect and the expertise they actually provide can derail your entire plan, leading to missed deadlines, budget overruns, and unhappy clients.

As we promised, we’re now going to take a look at what happens when you choose the wrong partner, and how you can avoid these headaches on your next project.

Continue reading “Finding Your Ideal Healthcare IT Partner”

Bridging the Expectation Gap in Health IT Outsourcing

Shouldn’t healthcare IT outsourcing make your job easier, not harder? Aren’t IT partners supposed to help you deliver software on time, on budget, and in line with client expectations?

Yes, and yes—in theory. In practice, it’s a different story.

Whether you’re an IT manager or a leader at an independent software vendor (ISV), you’ve probably struggled with the reality of IT outsourcing partners that didn’t deliver on the expectations you had when you went into the project.

It’s not that they misrepresented themselves. It’s not that they cheated you. It’s not that they were incompetent. But the fact remains, they didn’t meet expectations.

Continue reading “Bridging the Expectation Gap in Health IT Outsourcing”

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”