Health tech disruptors creating in-home monitoring and wearable technologies that collect health data may be interested to know that the FDA is getting into the business of what they call “Real World Data (RWD).” RWD is data, often collected directly from the user or patient and provides information on their health beyond a clinical encounter, like a visit to the doctor. This month the FDA awarded over $200 million to fund the next five years of their drug surveillance data program, The Sentinel Initiative.
The evolving health technology regulatory landscape can be challenging to navigate. Below, we give health tech developers a quick glance at national level efforts that are important to understand for your business strategy.
Where Health IT Stakeholders Stand (Part 2): CMS Rules on Data Interoperability, Conditions of Participation and More.
This February, draft federal rules on health data interoperability, information blocking, health IT certification, and health data exchange related to Medicare/Medicaid conditions of participation were proposed by the Centers for Medicare and Medicaid Services (CMS) and the Office of the National Coordinator for Health IT (ONC). After releasing these proposed new rules CMS and ONC opened the field to comments and questions from interested and invested parties such as health care companies, providers, and current and future patients.
Where Health IT Stakeholders Stand (Part 1): ONC Rules on API’S, Information Blocking and Data Exchange
Since this past February, many health IT companies have been reviewing, commenting on, and trying to understand the business model and production implications of the newly proposed Federal rules on health data interoperability, information blocking, health IT certification, and health data exchange related to Medicare/Medicaid conditions of participation. If your business touches the health IT sector and you haven’t been following these rules, you should be—the final versions of these rules will be game changers for the health IT sector.
It’s probably been a long time since you were knowledgeable about civic processes, but as a business owner the knowledge of how a bill becomes law can be foundational to your business’s strategic trajectory — knowing when and how to influence policy and regulation can have significant impacts on your bottom line.
By now, you’ve got a solid understanding of a health IT entrepreneur’s strategic business need to stay abreast of health data regulations as they’re developed. If you understand the connection between regulatory alignment and business growth but are wondering “When should I engage in reviewing, responding to, and influencing regulations?
So you’re all about creating the best IT-based solution to disrupt healthcare. Whether you’re a entrepreneur with a brilliant idea or a programmer bringing an idea to life, the success of your efforts will have to be aligned with the regulatory landscape of health IT legislation and regulation– and most companies need help sooner than they think.
This is a big week for those who care (or should care!) about health data tech regulation. The day before the biggest health IT conference of the year, HIMSS, the U.S. Department for Health and Human Services (HHS) dropped two highly anticipated draft rules—one outlining the seven exceptions to information blocking (i.e. when does not sharing data not count as information blocking) and the other requiring health plans to release Medicare and Medicaid claims data through openly published Health Level Seven (HL7®) Fast Healthcare Interoperability Resources (FHIR®)–based Application Programing Interfaces (APIs).
So you want to build the next best app-based telehealth solution? Great, the world needs you! But working through Washington DC’s never-ending lists of legislation and regulations to identify which will maximize return on your efforts is like unlocking a code. Incorporating national and state regulatory requirements into your prototype design can be the linchpin to the successful expansion of your company. Lucky for you, we’ve got the key!
If you haven’t yet read part one, we encourage you to go back and read about some of the reasons telehealth makes sense not only today, but for the future of healthcare. Today we want to address some practical components necessary for any health data technology to have viability, longevity, and scalability in the future landscape of telemedicine.
You might have heard of telehealth in reference to rural populations, who often must drive hours to the nearest clinic for health care. In fact, until now, telehealth has been practically synonymous with rural health as the modality used by physicians to provide care for distant populations. But it would be a mistake to think that convenience for rural populations is all that telehealth has to offer health care.