A blog about real-world solutions to common clinical lab IT issues by Brendan Hemingway.
Sunday, November 23, 2008
Cytochemistry Clinapp
The bone marrow clinapp went so well that I have whipped off another one, this one for cytochemistry interpretation. We are almost out of opportunities for this kind of automation: soon the only interpretive reports without an app will be the very low volume reports.
Wednesday, November 19, 2008
Bone Marrow Clinapp
Just completed another clinapp, this one for Bone Marrow interpretation.
It is gratifying how the basic framework continues to provide such good service, seven years after the first app was done.
Like its siblings, this app provides:
It is gratifying how the basic framework continues to provide such good service, seven years after the first app was done.
Like its siblings, this app provides:
- a work list of tech to-do (orders awaiting results)
- a work list of resident to-do (results awaiting preliminary interpretation)
- a work list of attending to-do (prelim interps awaiting review)
- same-screen access to relevant current lab results
- links to related clinapps reports for this patient
- context-sensitive access to the historical repository of lab results
- printable report PDF creation
- faxing support
- LIS interface
Monday, November 10, 2008
Tube Tracking
Our draw station software roll-out went swimmingly, but as with so much of life, it was a case of "what have you done for me...lately?"
The draw station app connects the labs and the draw stations. We had expected that the new requirement would all be on the draw station side, because we understood the lab side: we were integrating into the existing inpatient specimen handling procedure.
Except for drop-offs: the lab folks decided that they would trust the phlebotomists to handle drop-offs via our app because the phlebotomists quickly demonstrated proficiency with our app. So suddenly every draw station was a potential drop-off point.
This greatly increased the tube traffic from the draw stations. Then the issue of tracking reared its ugly head as disputes arose between the three parties:
The draw station app connects the labs and the draw stations. We had expected that the new requirement would all be on the draw station side, because we understood the lab side: we were integrating into the existing inpatient specimen handling procedure.
Except for drop-offs: the lab folks decided that they would trust the phlebotomists to handle drop-offs via our app because the phlebotomists quickly demonstrated proficiency with our app. So suddenly every draw station was a potential drop-off point.
This greatly increased the tube traffic from the draw stations. Then the issue of tracking reared its ugly head as disputes arose between the three parties:
- the draw stations (origin)
- the courier (transit)
- the lab (accepting delivery)
- the ability to batch draws into shipments (the draw station app knows how to map orders into tubes)
- the ability to create a barcoded shipping manifest
- the ability to mark a shipment as delivered
Wednesday, July 16, 2008
Phlebotomy Support
The client is a large hospital lab, recently given responsibility for Phlebotomy. Their problem is that the draw stations not only are not on the LIS, the draw stations are not computerized at all.
Their problem is compounded by the fact that their LIS is not off-the-shelf but is rather long in the tooth.
Worse, the lab is entirely focused on inpatient specimens: their processes and procedures all assume an electronic order in the LIS followed by a tube labelled with an LIS collection label.
All we can count on at the draw stations is a secure network connection.
We bridge that gap in under two months:
We provide management metrics for wait times and patient visits and a link to the Lab Man database so that the phlebotomists have up-to-date collection instructions. (More on that original Lab Man here.)
Mon Dec 1 13:35:10 EST 2008
Major release:
Major release:
Major release:
Wed Feb 23 10:11:14 EST 2011
Major release:
Their problem is compounded by the fact that their LIS is not off-the-shelf but is rather long in the tooth.
Worse, the lab is entirely focused on inpatient specimens: their processes and procedures all assume an electronic order in the LIS followed by a tube labelled with an LIS collection label.
All we can count on at the draw stations is a secure network connection.
We bridge that gap in under two months:
- custom Linux-based thin clients to provide
- dependable known web browser
- barcode label printing and report printing
- a web app to
- greet the patient, establishing a start for wait time
- identify the patient using an up-to-date patient index
- support finding and using existing electronic orders (clinics)
- support turning a paper order into an electronic order
- UI of assays
- interface to LIS to place order as if from the HIS
- print a collection label compatible with the legacy LIS
- provide history of activity by draw station or across draw stations
- support drop-offs
- support clinical trials
- support ordering synonyms to match community ordering habits
We provide management metrics for wait times and patient visits and a link to the Lab Man database so that the phlebotomists have up-to-date collection instructions. (More on that original Lab Man here.)
Mon Dec 1 13:35:10 EST 2008
Major release:
- support EKG scheduling
- support Accession Issues to link front bench and draw stations
- support for Cc physicians
- support ordering web page matching custom requisitions
Major release:
- scanned req support: barcode and tracking and viewing
- tube tracking
- support cancelled code substitution
- support lab protocol order changing automatically
Major release:
- support the new incoming LIS, SoftLab
Wed Feb 23 10:11:14 EST 2011
Major release:
- support ABNs: UI to accept the data, process to generate the forms
Monday, February 4, 2008
Custom Requisition Support
One of my colleagues provided the client with a very nice customer requisition creator:
In order to better support draw station operations, I upgraded our draw station software to accept the practice ID as part of the patient greeting process. This allows the draw station app to put up a web page which matches the paper requisition in the phlebotomist's hand.
So if they want to order the test which is the fourth box on the second row on the paper, they click on the fourth box on the second row of the screen.
Since the draw station procedure is to highlight the assays with a yellow marker as the assays are entered, to ensure entry accuracy, I mimic that on the screen: when a box is checked off, that assay has a yellow background.
The feedback was immediate and positive: the users who are not that comfortable with computers were instantly comforted by the close corelation of the physical and virtual.
- a database which holds practices and maps practices to their favourite assays;
- a UI to maintain the database;
- a formatter to put the custom information onto requistion forms
In order to better support draw station operations, I upgraded our draw station software to accept the practice ID as part of the patient greeting process. This allows the draw station app to put up a web page which matches the paper requisition in the phlebotomist's hand.
So if they want to order the test which is the fourth box on the second row on the paper, they click on the fourth box on the second row of the screen.
Since the draw station procedure is to highlight the assays with a yellow marker as the assays are entered, to ensure entry accuracy, I mimic that on the screen: when a box is checked off, that assay has a yellow background.
The feedback was immediate and positive: the users who are not that comfortable with computers were instantly comforted by the close corelation of the physical and virtual.
Subscribe to:
Posts (Atom)