Added another clinapp today, this one for Special Coagulation reports.
It has been a few years since the first clinapp, the one for flow cytometry, and I really have this down to a science: it took about 4 hours of work to set up and launch this one.
I wonder if and when rich data environments will be come standard in the basic LIS?
A blog about real-world solutions to common clinical lab IT issues by Brendan Hemingway.
Thursday, July 29, 2004
Friday, July 16, 2004
Molecular DX Clinapp
Oh, joy, another clinapp, this one for Molecular Diagnostics.
The underlying topic is interesting. The duplicate of previous work is not.
At least the users (techs, residents and attendings) are all quite enthusiastic. Cutting down turn-around-time by 50% and all that.
The underlying topic is interesting. The duplicate of previous work is not.
At least the users (techs, residents and attendings) are all quite enthusiastic. Cutting down turn-around-time by 50% and all that.
Wednesday, May 12, 2004
Sysmex CA-500 Automated Analyzer Interface
Today I start another instrument interface. Now the novelty has worn off. I just want to get this puppy up and running.
Still loving the client's homegrown interface framework, but the requirements for these interfaces are pretty strict and the instruments are not very featureful in the output department. These interfaces are a bit of a grind, although it is gratifying to work with users who know exactly what they need and who test so thoroughly. It is also gratifying to be filling such a concrete need.
Still loving the client's homegrown interface framework, but the requirements for these interfaces are pretty strict and the instruments are not very featureful in the output department. These interfaces are a bit of a grind, although it is gratifying to work with users who know exactly what they need and who test so thoroughly. It is also gratifying to be filling such a concrete need.
Friday, March 19, 2004
IFE Clinapp
Banged out another clinapp today, this one for IFE's. Victim of my own success: the client keeps finding new tasks well-suited to this code base. Satisfying to be providing value, but not the most exciting way to make a living: endlessly repeating oneself.
Thursday, February 19, 2004
Cell-Dyn 4000 Automated Analyzer Interface
Today I started work on another automated analyzer interface, this time for the CD4000. I expected that instruments in the same series would be similar, but I was wrong: much like consumer electronics, the individual instruments seem to differ greatly from model to model.
I am still using the same protocol and still using the same very good framework from the client. But this time I will be adding a feature entirely my own: an automated Audit module to support the new-to-the-client feature of....autoverification! Rather behind the industry curve, the client has decided to adopt autoverification but they want strict monitoring and tight control, which is OK by me.
I am still using the same protocol and still using the same very good framework from the client. But this time I will be adding a feature entirely my own: an automated Audit module to support the new-to-the-client feature of....autoverification! Rather behind the industry curve, the client has decided to adopt autoverification but they want strict monitoring and tight control, which is OK by me.
Friday, August 22, 2003
Cell-Dyn 3200 Automated Analyzer Interface
Today I started work on an instrument interface for Abbott's Cell-Dyn 3200 automated analyzer. Most of the work was done for me by the client, whose staff have developed a very solid framework in which to build instrument interfaces.
Automated analyzers are weird: they are sophisticated in every way but the way in which they handle I/O. This has been an introduction to some concepts for me:
Automated analyzers are weird: they are sophisticated in every way but the way in which they handle I/O. This has been an introduction to some concepts for me:
- ASTM E1381/95 a rather outdated, clearly serial protocol rather reminiscent of MS-DOS block-based communication protocols of yesteryear.
- Worklists for analyzers which are derived from LIS orders
- Analyzer flags and how to present them
- Verification UIs
Monday, November 26, 2001
Flow Cytometry Reporting
Starting a new and interesting project: provide a web-based rich data environment to support clinicians making clinical impressions of flow cytometry results.
Flow cytometry is a new and exciting technology for analyzing cells along a number of dimensions, but that is not my area. My area is providing an environment in which the raw flow cytometry results, which are precise but not clear, can be interpreted.
In practice, this means providing the following functionality:
Flow cytometry is a new and exciting technology for analyzing cells along a number of dimensions, but that is not my area. My area is providing an environment in which the raw flow cytometry results, which are precise but not clear, can be interpreted.
In practice, this means providing the following functionality:
- a worklist for the section
- orders as they arrive (tech to-do)
- cases to be interpreted as they are run (clinician to-do)
- up-to-date patient demographics
- access to any previous reports on this patient
- access to related and support current lab results
- macros for impressions
- push-button creation of a printable clinical report as a PDF
- publishing verified impressions:
- automatic interfacing of impressions to the LIS
- automatic faxing of reports to the ordering clinician
- tech--can enter and edit results
- resident--can enter impressions, not results and cannot sign a report
- attending--can enter impressions, not results and can sign a report
Subscribe to:
Posts (Atom)