Consider MySQL ‘Archive’ storage engine to store large amounts of med device structured or waveform data

I’ve been working on med device integrations for the many years now and one of the most common questions that arises when doing those integrations is “what’s the best way to save sensor waveform and analog to digital values?” Given the complexity of medical devices, there’s no single or simple answer but one approach that’s worked well for me in the past is to assume that whatever the data is, when it comes into digital format, it’s likely structured in some manner.

Most hospitals today have static (basic content) websites and many physician practices are putting up a static web presence as well. The more sophisticated health systems and practices, though, are building their sites on dynamic platforms that allow Web 2.0 functionality like social networking and online communities. IBM developerWorks recently asked me to talk about this trend so I wrote an article on how to develop content management systems for hospitals and leverage social Web 2.

We’re already familiar with the HITECH Act and how it offers money to physicians, hospitals, and multi-hospital systems to become “meaningful users” of certified electronic health records (EHR) systems. Since most hospitals and large providers who are going after stimulus money will need to install an EHR, it’s important to choose one that allows great integration so that the investment can be realized for many years to come. Because most EHR vendors are focused on their own specific certification requirements (and not your specific enterprise needs), it’s important to have a strategy for how to extend EHR systems.

My friend Tim Gee has two great posts covering a couple of very important and timely topics. If you haven’t seen them, check out the following: The Case for Regulating EMRs In this article, Tim articulated the following: In testimony at the Health and Human Services’ Health Information Technology Policy Committee, Adoption/Certification Workshop held on February 25, 2010, CDRH Director, Jeffrey Shuren, gently articulated FDA’s intent to regulate EMR applications.

These days I’m getting lots of questions about medical connectivity, health data integration, and system interfaces. There are many options for custom clinical data integration but the best is of course HL7 because it’s ubiquitous. People that aren’t experienced with health data interfaces often think that since we have HL7 interfaces we basically have a standard that we can apply equally to all problems. Given that’s not the case I asked Glenn Johnson, a 25-year veteran of the software industry with good healthcare experience and a senior vice president with Magic Software Enterprises Americas, to give us some advice about what can go wrong with HL7 interfaces and how to avoid some of the pitfalls.

With healthcare IT integration tasks finally taking off because of Meaningful Use and other care collaboration requirements, HL7 interfaces will become even more important. After being involved in dozens of interfacing efforts over the past decade or so, I have found one of the most time-consuming aspects of integration is HL7 interface documentation: nobody has time to do it and it’s almost always treated as a “nice to have”. Given my experience I was thrilled to find that someone was finally putting together some solutions to make conformance specifications easier to document.

I speak regularly (and write irregularly) about the importance of iterating through to a solid business model before you get too far with your great healthcare IT product idea. Whatever new idea you have in health IT has likely been tried before and if it failed it was likely not because the tech didn’t work but they probably didn’t understand the difference between the payer of a system, the user of a system, and a benefiter of the system (what I call my “PBU” circle).

If you haven’t had a chance to read it yet, check out Fred Trotter’s Patient Centered Health Internet article. He elegantly explains the simplicity of the Direct model vs. the the more complex (but ultimately still necessary) NHIN national model (read my article on NHIN at IBM if you’re not familiar with all these terms). There really isn’t a competition between the two models long-term because we’ll need both but the new Direct Project is coming along quickly enough that I recommend small offices and health systems really start to take a look at in 2011.

Brian Horowitz, who does some great writing over at eWeek and numerous other publications, interviewed me about what I thought the most important health IT trends will be in 2011. He published the results in his article entitled “Virtualization, EHR-Linked Devices, m-Health to Lead Health Care IT in 2011“. Brian captured what we discussed and made it even better by giving some concrete examples. Here’s some elaboration on each of the less often discussed trends we discussed:

Medigy Innovation Network

Connecting innovation decision makers to authoritative information, institutions, people and insights.

Medigy Logo

The latest News, Insights & Events

Medigy accurately delivers healthcare and technology information, news and insight from around the world.

The best products, services & solutions

Medigy surfaces the world's best crowdsourced health tech offerings with social interactions and peer reviews.


© 2023 Netspective Media LLC. All Rights Reserved.

Built on Jan 17, 2023 at 9:26am