Less than two weeks into the New Year, a group of us from the NaviNet Open Product Research team had the opportunity to attend the HL7 FHIR Connectathon in Orlando, FL. The Connectathon was a prelude to the HL7 Working Group Meeting and Payer Summit, and it brought together developers and integrators from many different organizations with a goal to get connected using FHIR. As part of NantHealth, our NaviNet Open team sees FHIR as an important advancement to help stitch together clinical and administrative workflows, and the HL7 Connectathon was a great chance for our team to create something useful using FHIR. Needless to say, I jumped at the chance to roll up my sleeves and write code, which is something I don’t get to do often in my role as a Solutions Architect. Here’s a few of my key observations from the experience.
A few weeks ago I wrote a post on Web Components, specifically the technologies that make them up. In this post, I’ll focus on Polymer and I recommend you read my previous post first if you aren't familiar with some of the concepts Web Components tries to introduce. This will help give you a sense of what Polymer can provide over standard Web Components. Now, back to Polymer, which I was recently able to get my hands dirty with when I was asked to develop the user interface (UI) for a Task Management System we were developing for NaviNet’s 2015 Customer Forum. This event is a great opportunity for our engineering team to show customers and prospects where we want to take NaviNet Open. It was also a great chance for me to test the water with the latest and greatest technologies like Polymer.
There has been a lot of brouhaha in the software development community about Web Components and the huge potential applications with the modern web. At NaviNet, we have kept a very close eye on Web Components as we continuously evolve our user interface (UI). Both our UI and Research team have had hands on experience with Web Components and in particular the Polymer library , so we would like to share some of our experiences. In this first post of our two-part series on Web Components, we’ll cover: