Healthcare IT

Article – The 8 RIS innovations you need now

dondennison Healthcare IT , , , ,

Here is a summary (note: may need to register with site to access) of some RIS (Radiology Information System) innovations that providers should be looking for.

Sneak peek…

  1. Digital dashboards
  2. Electronic medical record aggregation
  3. Clinical decision support
  4. Critical results reporting
  5. Customer service
  6. Technologist feedback
  7. Peer review
  8. Data mining, surveillance, and outcomes

I am working on an article on how (and why) RIS and PACS will be deconstructed and will not exist (as we know them today) in the future. Stay tuned for that.

Article – ARRS: Facial photos curb wrong patient errors

dondennison Healthcare IT ,

This is an interesting study.

Providing patient pictures were found to significantly improve the Radiologist’s ability to detect that images had been associated with the incorrect patient.

I have heard of the idea of using pictures to ensure the correct patient is involved in a procedure or treatment (when the patient is actually in front of you), but not in the diagnostic image review process. It would probably make sense to ensure that the patient picture was available in the EMR, and that the EMR was available (in context of the patient) at the PACS client—that way, even non-PACS users would benefit.

Article – CHIME presses HHS for HIE certification

dondennison Healthcare IT , , ,

This makes sense.

If we are going to certify EMR technology, HIE should be held to the same standard. Especially as more physicians turn to their HIE to provide basic EMR-like access to patient records (mostly because the HIE interface is better than their own EMR’s, the collaboration tools are better, and there is more of their patient’s data from more sources in the HIE).

Article – Enterprise Imaging: Beyond Cloud-based Image Sharing

dondennison Healthcare IT , , , , , ,

Read this, seriously.

Some thoughts…

  • I agree with most of what the article covers. I believe that Radiologists will be more consultant than owner of the Enterprise Imaging (EI) platform.
  • One topic that is not covered is the informatics around the metadata to collect at the time of capture. DICOM and IHE provide guidance as to what metadata we want to capture and include when doing a CT exam, but what needs to be captured when a clinical images are captured and stored is far less defined (though this will evolve as EI is adopted). Hopefully, we can start defining this by using some standard lexicons and codes (like SNOMED CT), as these are more mature now than when we started defining metadata values for traditional radiology modalities.
  • There needs to be close attention paid to the indexing of metadata in the EMR and the EI platform; more than is traditionally done when doing a basic EMR and PACS viewer integration. If an HIE is in place or planned, this also needs to be considered. Not all systems will be capable of managing all the desired metadata (including unique identifiers).
  • The EI platform should be considered a component of the EMR and managed as such–don’t put EI in your radiology PACS; just don’t.
  • We need to develop EI professionals through education and shared experiences, if we want to succeed. I may be biased, but I believe that SIIM is one of the organizations well-positioned to provide this. Check out my two-part blog post (part 1, part 2) on the SIIM web site.

UK study: Telehealth not cost effective

dondennison Healthcare IT , , ,

UK study: Telehealth not cost effective …I have two thoughts on this.

One, telehealth is not only about cost reduction—it is also providing patients access to scarce resources, such as a cardiac specialist. Patients with chronic disease in rural or otherwise under served areas can use telehealth to get services where they otherwise would go without. In this case, telehealth costs equal to, or even a premium above, standard costs may be warranted (or, at least, a comparison to average costs is unfair considering the inflated costs to provide equal services in an area where resources would need to travel to the patient).

Two, costs will come down. And, an 80% reduction in costs (as cited in the article) is not that difficult to achieve if one compares dedicated enterprise solutions to consumer solutions (e.g. smartphone apps). The cost of a widely shared set of web services in the cloud accessed by off-the-shelf, multipurpose consumer devices, like smartphones and tablets, is much lower than deploying and maintaining dedicated vendor-proprietary solutions.

Open mHealth vs. HL7 FHIR

dondennison Healthcare IT , , ,

OK, so check this out. I signed up to the mailing list for Open mHealth, an initiative that promotes the use of designs and technologies that I believe in, like REST APIs and JSON. They have started to post some documentation and specs, and have even have published some early implementation code. They have some discussion going on in a Google Group.

But what I am trying to figure out is how this relates to HL7’s FHIR. They seem to be using the same tools with similar missions.

It will be interesting to see which one gets traction:

  • the open initiative (seemingly) driven by the user community (doctors and people working in hospitals), or;
  • the standard from the well-established and accepted healthcare standards body

It reminds me of MINT (open community) and DICOM Working Group 27‘s (standards body) output (but in this case it was many of the same people involved in both).

In general, the open community moves faster, drives rapid innovation, and gets lots of attention, but the established healthcare IT vendor community often waits for the responsible standards body committee to provide a formal, consensus-driven specification (with design controls and governance around it to prevent unexpected changes), before implementing the API. Also, initiatives like IHE will typically only reference final standards in their integration profiles.

Articles on Mobile Health Applications and FDA Regulation

dondennison Healthcare IT , ,

Check these out…

Dear FDA: Qualcomm’s Robert Jarrin lists his wishes for FDA regulatory action

Where is the ‘fine line’ between safety and free rein for mobile development?

Some thoughts…

  • At risk of ending up on some government list of subversives, I question how often FDA (or equivalent agency in other countries) regulations actually result in protecting patients when they are applied to health IT products. Yes, good design, development, and validation practices are necessary for quality products. And, yes, health IT products are managing very important, not to mention legally protected, information that—when misused or when a defect affects its operation—can result in improper actions being taken …sometimes with adverse effects. But, for those that have worked for a registered medical device manufacturer, we spend more time with our eyes on paperwork than we should be. Time we could be spending on better design, or additional testing before launch. Too much of the paperwork is about evidence creation, and not about actual quality. Many process and method innovations developed in general IT product development are often difficult to adapt to the expected models in the FDA’s so called good manufacturing practices (GMP), and therefore do not achieve the same benefits/results.
  • If the U.S. government is generating revenue from the new medical device excise tax, is it possible that the FDA may be motivated to determine that more, not fewer, mobile apps are medical devices, and therefore subject to taxation? OK, I may have crossed the line into full-fledged conspiracy theory there. Sorry about that.

 

Article – Healthcare analytics market to exceed $10bn by 2017

dondennison Healthcare IT ,

Healthcare analytics market to exceed $10bn by 2017

…digitize, codify, manage/secure, consolidate/exchange and analyze.

Article – EHR Adoption Report: The Latest Trends

dondennison Healthcare IT

EHR Adoption Report: The Latest Trends

Some interesting tidbits…

The Office of the National Coordinator (ONC) for Health Information Technology’s most recent data briefs, reporting hospital adoption of EHR technology based on American Hospital Association (AHA) data, indicated the number of nonfederal acute-care hospitals with EHR systems–also known as electronic medical record (EMR) systems–has more than tripled since 2009, increasing from 12.2 percent to 44.4 percent.

Use of electronic active medication lists and clinical decision support rules increased to 87 percent, from 62 percent and 66 percent, respectively. The percentage of hospitals using computerized provider order entry (CPOE) jumped 167 percent, from 27 percent in 2008 to 72 percent in 2012.

The ACP/AmericanEHR study showed user satisfaction fell 12 percent from 2010 to 2012, with the percentage of very dissatisfied clinicians increasing by 10 percent. Thirty-nine percent of physicians would not recommend their EHR to a colleague. The numbers were similar for physicians in a variety of practice settings.

…physicians do not like being forced to use electronic technologies and that EHRs do not measure up to what they are used to in their day-to-day lives, which include iPad apps and smartphones, saying that record systems are fairly rigid with a flat interface.

Article – mHIMSS executives say FDA regulation won’t hold back app innovation

dondennison Healthcare IT , ,

This short Q&A article discusses the role and impact of FDA regulation, as well as the new medical device excise tax.

Some thoughts…

  • Someone explain to me how applications accessed on a tablet or smartphone are so much different than a desktop app being accessed on a netbook on Wifi. A tablet is a computer, typically without a keyboard and mouse. The user input method varies slightly and we have a whole new class of device? I don’t get it. If an application is collecting clinical data (e.g. dermatology photo), it should be subjected to appropriate regulations regardless if the user is using a mobile computer or a full desktop to run the application. This seems to me like a lack of understanding of computing by policy makers.
  • I believe the driving issue are mobile app developers getting into healthcare rather than registered medical device manufacturers getting into building mobile apps. Those familiar FDA regulations (and similar ones in other jurisdictions) generally know the rules. It is the mobile app developers unaware of the FDA regulations that are likely facing the greater challenge (mostly learning the requirements of being a medical device manufacturer). Providing the right guidance to the app developer community could be a growing opportunity for experienced regulatory affairs contractors/consultants.