Thursday, March 18, 2010

Having issues with adding values in drop down when adding options via AJAX in IE only?

Well, in my case this happened because IE and FF/Safari/Chrome treat the option object's constructor [option(arguement-1)] differently.
IE's interpretation = The name of the option is what was passed in arguement-1. The value is null.
FF/Safari/Chrome interpretation = The name of the option is what was in arguement-1. The value is also arguument-1.
So, make sure you pay special attention to this. Since IE does not set the value if 2nd parameter is not passed in, make sure to pass it! It can save you hours!

Friday, January 29, 2010

Windows mobile marketplace main memory filled?

I started using Windows Mobile Marketplace about a month ago on my HTC diamond phone. Initially, I thought ... *finally* an app store from Microsoft, awesome! .. but it didn't take me long till I filled my main memory. I figured no problem, I will just tell the cool-tiny-little Marketplace app to install it on my internal storage.

Oh no .. there is no such option. Once again, I fail to understand why Microsoft leaves stuff in a limbo ...
  • Was it too hard to give some configuration options?
  • What purpose did it serve to lock down a user to only allow him/her to install on main memory?
These are questions that sadly will never be answered from Microsoft even though, they have read them again and again on numerous forums online. Alas! the world of Microsoft.

However, fear no evil, there are a couple options to retro this scenario ...
  • Our friends at XDA have developed a hack that will allow you to install applications on the internal storage card
  • The other option is to use Pocket Mechanic that will allow you to move applications from one place to other.

Tuesday, April 29, 2008

Integerating Muse (GE) and Epic EMR (Epic Systems)

Although, I am roughly about six months late in posting this article, but I wanted to talk about my experience with integrating Muse and Epic EMR together with an ADT, Orders and Results interfaces.

Overall, I was really pleased with the overall improvement in ROI that was observed with the integrating these two applications. Some key elements are

  • Availability of ECG exams in one centralized place for all inpatient/outpatient medical providers
  • Excellent automatic ECG result notification for individual outpatient medical providers.
  • Complete history of preliminary, final and edited results in the primary EMR application.
  • Viewing of complete ECG strips on a single click of a button.
From a technical standpoint, following is the list of items that were performed,

  • Configure order transmittal (Epic component) to send ECG orders to an HL7 outbound interface.
  • Design/build mapping documents for ORM/O01 and ORU/R01 messages between Epic and MUSE. The Epic interfaces that were used were the generic outbound 'orders interface' and inbound 'radiology results' interface into Epic. (The inbound radiology results interface is capable of handling both ORM and ORU messages)
  • Since the MUSE web server which hosted the EKG strips in a PDF format, was protected under the standard IIS basic authentication security model, we had to write a small wrapper script that would allow automated logins when the EKG strip links were clicked in Epic EMR.
  • Epic EMR in basket routing was adjusted per organizations clinical care settings.

Overall, it was a great project and the end result was absolutely an improvement in patient care.

Tuesday, October 09, 2007

Implementing a Paceart HL7 results interface to Epic

Okay, this post has nothing to do with the Medtronic recall that just occurred, but with all honesty, the paceart application that Medtronic offers, sucks. Yep, Sorry, but it really does. In trying to integrate the paceart application with Epic, it was really sad and unfortunate to see the limitations that paceart has in place with the way they have implemented their interfaces, but not only this, the highly unhelpful staff they provided us for support purposes, sucked as much.

Here are some things that I think Medtronic needs to accommodate in order for their application to succeed

- Provide an accession number that is unique per study, and will remain the same even if the study is edited/deleted/merged, etc.
- Accept critical fields like an external systems account number/accession number
- Accommodate more characters for provider numbers
- Accept a real-time orders interface, this means the ability to handle O01, O02 messages
- Fix the abnormal results message that consists of multiple OBR segments, even though, they are part of the same order

That is at the least they should provide along with better support so that HIT folks can successfully integrate EMRs with paceart.

Wednesday, July 12, 2006

Interface Talker (Java program)
  1. Basic functionalty
    1. Manage communication on multiple ports. Communication can be incoming or outgoing.
    2. Means to create log files of all communication that gets carried over different ports.
    3. Ability to add/remove/configure ports/message types/activities.
  2. GUI
    1. Each communication should have its own tab.