Healthcare Application Development | Vicert
Read about ideas that untangle
the complexity of Digital Health

Tech Team

Recent Posts

The five W's and an H of Microservices in Healthcare

Posted by Tech Team on Jan 31, 2018

1. What are Microservices?

Microservices is almost a philosophy, as it is used to develop applications not piece by piece but by building all the pieces simultaneously by different teams. It is a special implementation approach for service-oriented architectures (SOA) used to build flexible, independently deployable software systems. Shortening the time to market, but also allowing for the system to be constantly improved and in theory much more scalable. 

Read More

Topics: healthcare, Microservices, Service Oriented Architecture (SOA)

How to use a HAPI-FHIR library and SMART Health IT #FirstEncounter

Posted by Tech Team on Nov 30, 2017

FHIR (pronounced "Fire") is a standard for interoperable exchange of healthcare data developed under the HL7 organization. FHIR includes all features present in HL7 V2, HL7 V3, and CDA.

For more information on FHIR and benefits for providers, payers, clinicians, etc. - check out latest white paper:

Read More

Topics: Java, FHIR

The Role of Angular in Building Digital Health Web Apps

Posted by Tech Team on Jul 31, 2017

1,429 new jobs on Indeed.com are aimed at AngularJS developers, we added one more keyword “healthcare” and it fell down to 74. It is an interesting debate whether or not that number should be higher, but it is certain that the advantages of using AngularJS when building web apps in healthcare is present.
 
Last week, during our regular tech R&D sessions, our devs were exploring the trends around AngularJS and later versions (Angular 2+ versions, Angular 4). One of the questions that was raised was, “How common is the use of angular in healthcare?” It is known to be a popular programming language used for mobile app development, but exactly how populated is it and how well is it known to healthcare execs and among the health tech startups were some of the other questions that came up in our discussion.
Read More

Topics: digital health, HIPAA, Apps, Angular

Summer in the Health Cloud: AWS Lambda Slack Bot

Posted by Tech Team on Jun 30, 2017

Summer is famous for its flings , and our R&D department (basically our devs having fun with new tech) chose their first week of summer crush – AWS Lambda (before another one catches their eye next week - IBM Bluemix OpenWhisk).  

In just a couple of hours in a relaxed summer atmosphere (courtesy of our HR department for providing these amazing lounge chairs) our devs were able to test AWS Lambda by making a Slack Bot. The idea was to check how we could automize and build a development environment for a healthcare client - meaning it needed to be HIPAA compliant (whence AWS Lambda and Slack).

Read More

Topics: CLOUD, Chatbots, AWS

DevOps @ Vicert – Lessons Learned

Posted by Tech Team on Aug 1, 2016

Through many years spent developing various applications, using various technologies and working with different clients, we have tried a number of diverse development methodologies and techniques, in search of the most optimal development process. But first, we had to define what optimal means for us.

Some would argue that the optimal process is the one that produces the required output (working functionality) the fastest. While that might be the case for small, simple projects, we find that on a large enterprise scale, the fastest output does not usually produce an optimal result.

Read More

Topics: Devops, HealthIT

How to integrate multiple Wellness devices using Human API

Posted by Tech Team on Jul 21, 2016

In a recent project for one of our clients, we came across a need to gather data from multiple wellness devices. We were faced with a choice between creating a custom connector for each device’s API, or using a service that gathers data in one place.

Read More

Safe Texting a New Worry for Health Care Leaders

Posted by Tech Team on Jan 29, 2016

Just like the rest of America, health care workers are becoming increasingly dependent on their mobile devices, and finding that texting is a convenience they’d rather not leave behind when they go to work. That’s despite the potential privacy concerns associated with unsecured texting apps.

Read More

Topics: HIPAA, Provider

User Driven Design: Three Steps to Breakthrough Digital Health Care Solutions

Posted by Tech Team on Dec 30, 2015

Kent Lawson is the Health Care Practice Lead at IA Collaborative, a preferred partner company.

Together with IA Collaborative we offer our clients in the digital health space a full service solution development process, from research, design and deployment of applications to consultancy and domain specific problem solving.

Throughout the year we will invite our trusted partners to guest blog to introduce new perspectives and angles on digital health.

The key to innovation—any innovation—is seizing latent opportunities and solving real problems for real users. At IA Collaborative, we call it user driven design.

User driven design includes three course of action and reaction, all focused on taking insight to action:

  1. Design Research- Researching real users and key stakeholders, in-context.

  2. The Journey- Understanding the current journey of any user or any product, the gaps that exist today, and most importantly the potential to fill or capitalize on those gaps.

  3. Design & Develop- Designing and developing the ideal future state, collaboratively with a multi-disciplinary team, including all key stakeholders.

Read More

Topics: healthcare

#2 Spring: Manipulating Salesforce objects

Posted by Tech Team on Apr 9, 2013

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.

Read More

Topics: Spring/Hibernate, Tech

#1 Spring Web application: Authentication

Posted by Tech Team on Apr 8, 2013

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).

Read More

Topics: Spring/Hibernate, Tech