REM lab machines - 2 way communication

Hello again everyone,

This time I have a question,

How many of you guys use or would consider using REM in house lab machines if they had 2 way communication with OpenVPMS? 

To be more specific, this development would allow us to generate an in house investigation and have the patient details appear in a queue on the machine. Once the tests were run, a copy of them would be automatically attached to the investigation in the patient record. They are using a small computer that sits in between the machines and OpenVPMS they have called a Fuse. They are selling the Fuse for more then four figures.

This development would allow OpenVPMS to talk this Fuse machine.

I'll start out by saying Boronia Vet Clinic want this and we are going to pay to have the code developed for us all. So no spruiking for dollars. But what we are interested in is how many users this will help and who would look at this option for their clinic.

I am not going to link REM in the forums. It's just too close to promotion for mine. Feel free to google their machines though. We use them becuase of their cost of consumables. 

Thanks everyone

Matt

 

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: REM lab machines - 2 way communication

We use one of their machines at the moment and are thinking of getting more.  It is a bit of a chore to get the data off. I have some of it scripted but not all.  So this idea is a definite plus.  Especially since there would be no more batching of data downloads.

This would use the ASTM protocol?

Simon Slater

Registered Linux User #463789 @ http://linuxcounter.net

Re: REM lab machines - 2 way communication

Hey Simon,

Not sure as to the exact protocols the system uses. 

The Fuse box sits on the network and what ever test devices you have sit on the network too.

The devices are configured to talk to the Fuse box via Restful requests.

 

We have a Fuse box in the clinic now and our current methodology is;

a) Patient Entry

Navigate to Fuse using web browser and start a new test with a new patient details.

b) Results transfer

After test is complete, navigate back to Fuse webpage and download the results as pdf and attach manually. You could configure docloader to autoattach these docs to an investigation/act but at this stage we do it manually.

We had the window based software that spoke to the machines through serial-usb connections but it was just too flaky. It sounds like the above methodology may not contribute much for you but the proposed two-way communication would.

 

Cheers,

Matt C

Re: REM lab machines - 2 way communication

Hey Tim (Anderson),

Is adding two-way communication to the Investigations something that could be feasibly scheduled for Version 2.0? 

Cheers,

Matt Costa

Re: REM lab machines - 2 way communication

I shouldn't think so. At this stage, the last scheduled feature is Patient Insurance, which is currently likely to push the final 2.0 release out to early next year.

Re: REM lab machines - 2 way communication

Tim,

Attached is a file on how 1 of the the REM Systems machines, the VS2 biochem analyser, uses the ASTM protocol.  I had an extract of the manual for the comms chapter, but it wouldn't attach.

Basically there are 4 choices: None; ASCII text; ASTM; XML.  The text and XML are over serial (USB) or use ASTM over the network.

For the serial comms, you need to connect with minicom or similar.  Just like the old days of accessing remote data-loggers over a 9600 baud connection.  Interfacing with the network would be much smoother, but one look at the specs and I realized it was out of my league.

AttachmentSize
vs2-astm.txt 5.65 KB

Simon Slater

Registered Linux User #463789 @ http://linuxcounter.net

Re: REM lab machines - 2 way communication

We would be looking to provide a laboratory order API that allows different vendors to plug in their own implementations.

This is the approach we are using for the insurance project, as it allows us to interface with vendors that don't provide a public API.

Re: REM lab machines - 2 way communication

Sounds like you guys have been busy!

Let me know how new projects are created now and how funding allocated. We are keen on this, suffice to say :-)

Ta

Matt

Re: REM lab machines - 2 way communication

Hey Simon,

Did you find the Serial communication a massive pain to deal with? I did!!!

The existing API for the communication between the new Fuse box and OpenVPMS uses RESTful requests over network connections. 

OpenVPMS has the API documentation from REM systems so hopefully the final solution should be quite functional. 

Cheers,

Matt

Re: REM lab machines - 2 way communication

Matt,

The hardest part was finding the VS2 as a USB device since it was not auto recognized.  As for the rest of the process, I spent many years with data-loggers, so it was a bit like riding a bike - it took a while to get the hang of it again, but I don't mind that sort of thing.

Then a script using sed to strip headers, awk to split the date and change the month format, extract the requisition ID and put it all together as separate files with date and ID as the filename, so OP finds them.

Simon Slater

Registered Linux User #463789 @ http://linuxcounter.net

Syndicate content