Jerry Fahrni

Author: Jerry Fahrni

  • First Impressions – Lenovo T410s Laptop

    There’s a new Lenovo T410s laptop in the house. It’s technically not mine because it has a giant company asset tag on it, but it’s mine for the duration of my employment and it’s one incredible machine.

    The configuration is as follows:

    • Windows 7 Professional (64-bit)
    • Intel Core i5-M560 Processor
    • 160GB Intel Solid State Drive
    • 8GB RAM
    • 14.1-inch WXGA touchscreen…yes, that’s right, it is a touchscreen
    • 6 Cell Li-ion battery
    • 3-cell ultrabay battery that fits in the DVD slot when I need additional battery
    • And all the typical stuff that goes with most laptops, i.e. camera, Bluetooth, wireless (no 3G), etc

      • (more…)

  • Quick hit: approaches for standardized healthcare data

    When my brother, Rob and I get together it often brings our wives to tears with boredom as we often get deeply engrossed in long conversations about computers, software and technology in general. Super Bowl weekend was no different. Rob and I started talking about strategies for connecting various pharmacy systems to other hospital systems and the issue of a lack of standardized information in healthcare came up. I mean we have standards, right? Of course we do. There’s SNOMED-CT, RxNorm, ICD-9, ICD-10, LOINC, GLNs, GTINs, NDC, bar-code “standards”, HL7, NCPDP SCRIPT standards and so on and so forth ad infinitum. I realize the list above includes a hodge-podge of standards that don’t really belong in the same category, but I did it to illustrate my point. And that point is that we have too many stinking standards. Trying to figure out which standard to use is an exercise in futility. Standards typically make sense to the people that invent them or study them, few others. And someone always has an idea for a better standard, hence the plethora of standards.

    As healthcare inches forward interoperability of systems will hold a key role in the success of the government’s plan for electronic health records. So as Rob and I discussed how to integrate various services and products we pondered how one goes about creating a standard that everyone can live with. Well, how does one create a standard that everyone will use? Heck if I know, but we decided that there are basically two approaches. The first is to create a standard and try to cram that standard down everyone’s throat. Microsoft has been fairly successful with this approach. With that said, few people have the resources that Microsoft has to throw at a problem. The second approach is to offer the standard as part of a free solution that comes with your product; this way people can use your product and use your free, open-source solution to tie the systems together. I assume this is the smart approach for companies that have limited resources; kind of a grassroots approach. Of course it would be wise to build this free, open-source solution on top of an existing standard that’s prominent in the market, otherwise you’re trying to re-invent the wheel. And we all know what happens when someone re-invents the wheel. Uh, you get a wheel. We don’t really need any more of those. Both approaches have pros and cons.

    Now the question becomes which standard makes sense as you design your solution. If only I had a crystal ball. We’re at least a decade away from having a truly inter-operable healthcare system; optimistic, I know.  Ultimately, the standard of choice won’t be driven by what makes sense, but rather will be driven by adoption rates. Things often become a standard without even trying.

  • Monday evening quarterback

    What a great weekend. The Super Bowl wasn’t a blowout and turned out to be quite exciting in the end. The commercials weren’t extravagant, but were surprisingly entertaining. The one downside was the absolutely embarrassing rendition of the National Anthem sung by Christina Aguilera. For all those would be National Anthem singers out there, please don’t add to or take away from the National Anthem. When you do, you’re doing nothing more than punching this great country of ours in the face.

    Anyway, here’s some other stuff I’ve found interesting over the weekend:
    (more…)

  • “What’d I miss?” – Week of January 30, 2011

    As usual there were a lot of things that happened over the past week, and not all of it was related to pharmacy automation and technology. Here are some of the things I found interesting.
    (more…)

  • Do smaller hospitals get the shaft when it comes to automation and technology?

    I’ve worked in several acute care hospitals during my career, from the small one horse operation that did little more than care for minor inconveniences, to larger, multi-pharmacy facilities that handled everything from pneumonia to severe trauma. As I’ve mentioned elsewhere on this blog each one of those pharmacies offered a slightly different way of doing things. Granted, some were variations on a similar approach, but they were all different.

    However, one trend I’ve discovered across the range of facilities is that the smaller the hospital, the less automation and technology the pharmacy has. Why? It’s quite simple. Automation and technology is expensive. It’s also time consuming to plan for, implement and maintain. Of course another argument is that smaller hospitals - and therefore smaller pharmacies – need fewer technological advances. That doesn’t make much sense to me. I agree that a small 50 bed hospital pharmacy may not need a giant robot to fill their med carts, but they can certainly benefit from clinical decision support, pharmacy surveillance software, bar code medication administration (BCMA), computerized provider order entry (CPOE), automated dispensing cabinets (ADCs), smartpumps, mobile devices, so on and so forth. The problem is that much of this technology is expensive and takes a sizable chunk out of smaller budgets.
    (more…)

  • Time to accept pharmacy robotics as our friend and ally

    As the word “robot” passes its 90th birthday1 – introduced by Karel Capek in his play R.U.R. (Tossums’s Universal Robots) in January 1921 – it’s become obvious that robotics has not only captured the imagination of geeks everywhere, but has become a point of interest in many industries including healthcare.

    Late last year ASHP began pushing the idea of a new pharmacy practice model, PPMI. The movement was a hot topic for a while, but seems to have lost a lot of steam recently – “Hence the name: movement. It moves a certain distance, then it stops, you see? A revolution gets its name by always coming back around in your face” (Tommy Lee Jones in Under Siege 1992) – Anyway, when the PPMI movement was still going strong many important people in the pharmacy world struggled with the best way to approach a new pharmacy practice model. Many believe, and rightly so, that the best way for pharmacists to reinvent themselves is to become the cornerstone of a more robust patient care model. After careful consideration I believe the best hope for developing such as model will be to rely heavily on pharmacy robotics to handle much of the repetitive dispensing duties now handled by pharmacist on a day to day bases. You know, free up the pharmacists. It’s not a new concept, but one that seems to escape us.

    Obviously it will take some time to develop robotics to the point where it will be effective in such a system, and it certainly won’t be cheap, and pharmacists will have to fight with state boards of  pharmacy to accept it, and pharmacy administrators will have to work closely with their hospitals to develop such a systems, and someone’s going to have to be brave enough to step up to the plate and get stated, and so on and so forth. In other words it’s going to be hard and it won’t happen overnight.

    Who’s up for a little project? For now let’s just take a quick look at some of the things that lead me to believe robotics is worth another look as a potential solution.

    (more…)

  • Cool Technology for Pharmacy – Sharp SX Bagger

    Some items in a pharmacy are simply difficult to bar-code. Perhaps they’re too small, have an awkward shape or their surface won’t accommodate ink or an adhesive. The problem creates some interesting workarounds, and not always for the better.

    One solution is to individually package each item and place the drug information and a bar-code on the outside of the packaging material; overwrapping, if you will. I’ve never been a big fan of overwrapping items because it can be time consuming and cumbersome. Today I ran across a machine that I think offers a genuine option for medications that are difficult to bar-code.
    (more…)

  • The next big thing in pharmacy informatics? Hint: IDK

    RxInformatics: “The following was a list serv question from Monica Puebla, PharmD, MBA, BCPS for a HIS course. Here is my response to the Question. I would add State Boards of Pharmacy to the list of those to present this as well.

    “If you were given the opportunity to present to your DOP, VP and CFO a project that you deem would have the greatest impact on the pharmacy department as well as the health-system in general from any point of view, clinical, financial, operational, without regards to costs, what would it be?””

    John’s response was to “Study under what circumstances pharmacist order review (perfection) could be taken over by automated clinical decision support while increasing quality and safety” in addition to including a nice list of references related to ‘perfection’ (listed at the bottom of this post). I highly recommend looking at the references John provides because they’re informative and enlightening. You can also read more about the ‘perfection’ idea at one of John’s older posts here. It’s amazing that this discussion has been going on for well over a year and to the best of my knowledge has yet to make much headway.
    (more…)

  • Going cartless

    I spent some time recently speaking with the director of pharmacy (DOP) from a large acute care facility about operations and various dispensing models. In this particular instance, the hospital utilizes a cartfill model, decentralized pharmacists in satellites to handle first doses, batched IV’s and automated dispensing cabinets for pain meds and other “PRN” medications.

    At one point the conversation drifted toward a discussion of using a cartless dispensing model. The DOP wasn’t a fan. The reason cited was a fear that utilizing automated dispensing cabinets in a cartless model would create a workflow logjam in the pharmacy as the entire day would be dedicated to “massive ADC [automated dispensing cabinet] fills”. I understand the thought process, but have found through experience that this simply isn’t true. In a well-constructed workflow a cartless model is quite efficient.
    (more…)

  • “What’d I miss?” – Week of January 9, 2011

    As usual there were a lot of things that happened during the week, and not all of it was pharmacy or technology related. Here’s a quick look at some of the stuff I found interesting.
    (more…)