The final implementation phase of the most stringent requirements of the Cures Act has already begun and everyone in Healthcare IT can feel the heat of FHIR® rising. No more delays are likely in the enforcement of the ONC and the CMS rule. If you're trying to find the quickest and shortest path to meeting the Cures Act requirements let us show you SMART® approach and how to leverage the power of FHIR.

As the Cures Act deadlines draw closer, many EHRs find themselves in the ring of FHIR, whether it be Information Blocking, Real World Testing, or the (g)(10) FHIR API certification. Continue to read to learn about different elements of Cures Update and how you can jump through them successfully.

As the clock ticks away, some of the Cures Act milestones have been realized (Information Blocking, USCDI V1, RWT), while others are approaching fast including the (g)(10) FHIR API. Would you be able to get (g) (10) certified by the Dec 31, 2022, deadline? Discover a Better Way for Your EHR’s 2015 Cures Update Certification Maintenance with Darena Solutions.

Is your EHR concerned about the fast-approaching Cures Act Conditions and Maintenance of Certification deadlines and the timelines for your team to complete internal development, QA testing, Test Wave prep, and deployment to production/users? Darena Solutions can help your EHR dev team answer the classic build vs buy question.

The latest Condition of Certification to maintain 2015 Edition EHR Certification is approaching fast. The EHRs will need to have an APPROVED Real World Test-plan (RWT) in place by the ONC deadline of Dec 15, 2021. The ACB deadlines are sooner. This blog highlights the specific challenges in meeting the requirements for RWT compliance and possible solutions.

The 21st Century Cures Act set out the mandates of compliance for all 2015 Edition Certified EHRs. Real World Testing (RWT) is among one of these mandates with a fast-approaching deadline. This blog highlights an efficient path to RWT compliance for EHRs to maintain the 2015 Edition certified status.

The market for FHIR solutions is quickly heating up. While every solution may have its pros and cons, we have recently seen many announcements and promotions that we felt are misguided representations of FHIR solution's actual capabilities related to meeting regulatory requirements. In this blog, I would like to bring to light some facts, to enable you to make an informed decision.

Over the last decade, billions of American taxpayer 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. Is FHIR® the answer to the interoperability conundrum?

As 2020 comes to a close, it is time to reflect back at the year. The COVID challenge we are faced with and drawing upon the lessons learned from it to remind everyone that regardless of the role you play in the healthcare ecosystem (patients, providers, payers, and Health IT vendors), come 2021, you need to start playing with FHIR.

After the 21st Century Cures Act Final Rule was announced, the healthcare IT marketplace has been inundated with solutions, all claiming to be able to meet or even exceed the compliance requirements. Unfortunately, there is no magic mirror available that can tell you which FHIR solution is the fairest choice for your organization. So, let’s start with some facts and follow a logical path to help you find a solution that not only meets your current needs, but aligns with your future requirements as well.

Updating the CCDAs might be the easiest way to share USCDI data and avoid the $1,000,000 penalty under information blocking regulation. However, it might not be the best way as Cures Act ultimately requires you to make the same data available through a FHIR® API. In this blog, we will drill a little deeper on how making this data available through a FHIR® API is a better long-term strategy than simply sharing an updated CCDA.

On October 29th, 2020, ONC announced an Interim Final Rule to extend compliance for some of the provisions including Information Blocking due to the COVID-19 pandemic. In this blog, we discuss what changed in the Interim Final Rule, how it impacts providers and EHR vendors, and solutions for meeting the Information Blocking requirements.

Darena Solutions announced a new integration between their BlueButtonPRO™ solution and Microsoft® Azure API for FHIR. BlueButtonPRO is an end-to-end FHIR-based patient engagement platform to connect providers, payers, research organizations, registries and patients.

BlueButtonPRO™ by Darena Solutions becomes the nation’s first ONC certified solution for meeting 21st Century Cures Act requirements for EHR Vendors and Payers. BlueButtonPRO™ can be integrated with any EHR to meet the Cures Act requirements mandated by ONC for all EHR Vendors. It also meets and exceeds the CMS Interoperability and Patient Access final rule requirements for payers.

It can be hard to explain how a Personal FHIR® Record differs from a Personal Health Record. But in reality there is a key difference in the interoperability of the two record types. That difference is what makes a PFR special, and why every patient should have a PFR.

There is a lot of confusion on what exactly the 21st Century Cures Act requires and includes. We help break down the law and demonstrate how we are helping our clients meet the requirements using Azure API for FHIR®.

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.

There is a lot of buzz surrounding the concept of interoperability and FHIR®, but what do healthcare providers get out of it? We delve into a variety of benefits that providers organizations (big and small) can expect to see when they decide to adopt FHIR®.

Last year at HIMSS, ONC announced a proposed rule pertaining to some provisions of the 21st Century Cure’s Act, which included some new certification criteria that all EHR vendors will need to support going forward. Yesterday evening, CNBC released an article sharing that Epic’s CEO, Judy Faulkner is urging hospital executives to oppose this rule. Epic has confirmed this and that they have sent an email to HHS Secretary Alex Azar, which has been signed by other “healthcare CEOs.” This is a very disappointing action by Epic, trying to misrepresent the proposed rule. Let’s winnow the fiction from the facts to understand what is going on here.

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