In our last blog we discussed how Apple, Google, Microsoft and Amazon are planning to leverage the HL7® FHIR® standard. This discussion would be incomplete without the mention of probably the largest FHIR solution in the country today managed by a (non-tech) organization. I am talking about Blue Button 2.0 by Centers for Medicare and Medicaid Services (CMS).
A recent blog post by ONC in 2018 highlighted some amazing analysis around the adoption of FHIR® in the US. The post briefly mentioned how Apple, Google, Microsoft and Amazon are planning to leverage the HL7® FHIR® standard. This blog discusses how some of these big companies are approaching FHIR.
In our last blog, we had discussed about the MIPS 2017 performance feedback reports that became available on June 29, 2018. These reports provide the final MIPS score and the corresponding final payment adjustment that will be applied to 2019 Part B payments. For most people, the final scores were what they expected. However, many are crying foul over the payment adjustments.
Over the last decade, billions of American tax payer dollars have been spent to achieve “interoperability” in healthcare. Has it worked? The answer depends on who you ask. However, everyone agrees that we have a long way to go. Can FHIR® might be the answer to the interoperability conundrum?
The key differentiator of FHIR from any previous standards used in the healthcare is the portability of FHIR “resources”. This granular approach to storing and consuming healthcare data opens up many more new opportunities as compared to the traditional document-based methods. However, this approach also presents some challenges. Can Azure Cosmos DB be the perfect solution to those challenges?
FHIR has gained a lot of momentum in a very short time. Learn with the help of a a simple scenario to demonstrate how FHIR could drastically reduce data entry burden for reporting the Quality Performance Category.