As we move from (a)(9) Clinical Decision Support (CDS) to (b)(11) Decision Support Interventions (DSI) under the HTI-1 Final Rule, the differences between these two criteria are substantial, driving significant improvements in how decision support is delivered within healthcare systems. Read more.

The EHR landscape is experiencing a shift from EHR adoption driven by Meaningful Use incentives to the organic evolution of headless EHRs. This is great news, but it raises some questions about the effectiveness of the incentives and sustainability of the innovation. Read on to explore some of these questions and join us for a panel discussion for more in-depth analysis.

Darena Solutions launches a timely (b)(11) DSI compliance solution for EHRs to meet the new HTI-1 mandates before December 31, 2024.

ONC has updated the (g)(10) requirements, as detailed in the HTI-1 final rule. As per these updates, EHRs must publish and maintain their service base URLs in FHIR format, and complete compliance checks by December 31, 2024. Learn more about all (g)(10) related tasks and possible compliance paths available to EHRs in this blog.

Consumer-mediated exchange allows patients to directly share their health data with providers, payers, and researchers, enhancing data accessibility and addressing interoperability issues. This blog examines the mechanics, challenges, and solutions for implementing consumer-mediated exchange of health information.

It’s ONC Bingo time! Today’s number is B11. Before you reach for your daubers, let's talk about something even more exciting than marking off squares: What will B11 add to your EHR? How to fully comply with the B11 requirements to safely enable Decision Support Intervention (DSI) within your EHR?

This blog takes you through the highlights of the HTI-1 program and how ONC will be enforcing the (g)(10) FHIR API requirement. It focuses on requirements EHRs and certified health IT modules must meet by the Dec 31, 2024 deadline. We’ve also included an HTI-1 readiness checklist for convenience.

ONC’s Health Data, Technology, and Interoperability (HTI-1) final rule was enacted on March 11, 2024, and since then has been the front and center of all news in healthcare IT.  A particular section of the HTI-1 rule, Decision Support Intervention (DSI), has been the primary focus. In this blog, we will unpack what DSI is and what it means for EHRs and AI App Developers.

In a significant move to address the growing demand for Artificial Intelligence (AI) in healthcare, Darena Solutions, in collaboration with Leidos and SLI Compliance, today unveiled a new industry-leading initiative: a robust verification process tailored for AI applications built using Substitutable Medical Applications and Reusable Technologies (SMART) on Fast Healthcare Interoperability Resources (FHIR).

Darena Solutions, a leader in healthcare clinical, analytics, and regulatory solutions, today announced the launch of MeldRx™, a platform to simplify the development, testing, and deployment of apps based on the SMART specification.

Read about the launch of a unique FHIR Client Certification program by our partner, the Drummond Group.

Are you looking to fast-track your transition to 170.315 (b)(10) certification? Let us simplify your journey to quick (b)(10) compliance and CHPL listing updates.

With the introduction of the HL7® FHIR® standard, accessing patient health records has become easier than ever before. When FHIR is combined with the power of artificial intelligence language models such as ChatGPT, the results are nothing short of amazing. In this blog, we explore the possibilities of interpreting patient FHIR records with the MeldRx Chat powered by ChatGPT. In the accompanying video, we showcase how patients can receive real-time assistance in understanding complex medical terminologies, test results, and treatment options. We believe that collaboration is the key to driving innovation and advancing healthcare. Join us in the movement towards a more connected and patient-centric healthcare system with ChatGPT and FHIR.

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.

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.

Tune in to the message the ONC is broadcasting through their recent blogs/media to reinforce the need for (g)(10) FHIR® API and Information Blocking compliance, whom these apply to, and how the mandates will be enforced. Let’s turn up the volume on the latest hits from ONC.

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.

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.

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.

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?