The ONC recently shared updates clarifying the app registration requirements for health IT developers certified to § 170.315(g)(10). Read on to find out what must the Certified API developers do to conform to these updates.

The Information Blocking Rule ensures efficient sharing of electronic health information (EHI), prohibiting unnecessary restrictions unless legally justified. Compliance is critical for healthcare providers, EHRs, and HIE networks to avoid penalties. Learn simple steps to avoid information blocking.

Staying compliant with information blocking regulations is essential, not only to avoid penalties but to protect patient trust. With the ONC's rules tightening and hefty fines at stake, it's more critical than ever for EHRs and healthcare providers to understand and adhere to these guidelines, ensuring transparency, data-accessibility, and data-sharing that empowers patients.

ONC warns healthcare providers and developers to keep data access open as directed in HTI-1 and the Cures Act. Hidden information blocking could result in a bone-chilling visit from regulators this Halloween.

This week, Micky Tripathy, the ASTP/ONC Acting Chief AI Officer, published a blog post addressing significant gaps in the implementation of the 21st Century Cures Act and brought the focus back to FHIR APIs. This blog captures the 5 key points he made to warn and to enforce the mandates. Join the conversation.

January 1, 2023, is not just the beginning of a new year, it is also the beginning of the enforcement period for the Information Blocking portion of the Cures Act. The EHRs must provide FHIR APIs for all their users, and Providers must ensure that their FHIR API endpoints are publicly available.

Do you have a game plan ready to have a (g)(10) FHIR-based API in place for the fast-approaching December 31st, 2022 deadline? We have assembled a comprehensive checklist of items you should consider for making an informed decision.

The misinformation floating around combined with an incomplete understanding of the (g)(10) FHIR API and other Cures Act requirements can be detrimental to the EHR developers and the providers. In this blog, we bust these myths, shatter misconceptions, and guide you to ask the right questions.

EHRs are feeling the heat of Cures Act requirements as the deadlines draw closer. Read on to find answers to burning questions that EHR developers and providers are faced with as they are trying to understand the implementation details of the (g)(10) FHIR API and its implications.

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.

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.

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.

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

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.

Read how to implement a clinical registry solution based on Microsoft Azure API for FHIR that accepts data directly from patients in a very secure yet simple way. Before a patient can share data, they need to have access to the data themselves and be able to control it. Find out how we address this issue.