The ONC has announced its punitive action plan to deal with non-compliant Health IT developers. EHRs failing compliance will undergo Direct Review, have to submit a Corrective Action Plan (CAP) and will be placed under a Certification Ban till they become compliant. Integrating with (g)(10) pre-certified BlueButtonPRO is an easy solution.

With the Cures Act deadlines around the corner, the focus has been on “how” to meet the requirements, and not “why”. Let’s not forget that each one of us will be a patient at some point in our lives. When we are the patient, we want Health IT to work for us. We need access to our health data for that and Cures Act makes it possible. This personal experience will make that evident.

More than any other stakeholder it is patients who stand to gain the most from FHIR enabled semantic interoperability. In this blog, we outline the major benefits that patients can expect to gain from increased interoperability.

Healthcare payers stand to benefit from increased interoperability.. We explore why proposed rule CMS-9115 could mean a lot for payers in 2020.

Let's take a look at the history, and future, of compliance and interoperability in healthcare, and what to expect out of patient focused semantic interoperability. Will 2020 finally be the year that healthcare changes put the patient first?

While Apple’s Health App is a great initiative to get healthcare consumer directly involved with FHIR®, there are some serious limitations in this approach. Read how we have used Microsoft® FHIR Server and Azure Cosmos DB in our BlueButtonPRO App to address these limitations while trying to achieve the same end goal i.e. empowering healthcare consumer with access to their healthcare data with Personal FHIR Record.

In our recent blog, we discussed how Microsoft has taken a radically different approach as compared to Amazon and Google for their FHIR® offerings. Yesterday Microsoft announced Azure API for FHIR that adds to it’s open-source project for FHIR. We gave it a try.