Please to read the entire article.
Marked as spam
Jenish, your best bet is to not try and develop the interface but use middleware. A good middleware choice is from Data Innovations. They have drivers for most every clinical instrument you can think of: http://www.datainnovations.com/
Marked as spam
John, Thank you for your reply. Would you be able to tell me what is LIS and how is it different from LIMS. Also, what is these communication protocol CSLI1 bidirectional and unidirectional protocols LIS2-A2 (record formats) and LIS01-A2 (low level protocol).
A good explanation between LIS and LIMS is covered on the limswiki knowledgebase: https://www.limswiki.org/index.php/Laboratory_information_management_system
and this about LIS: https://www.limswiki.org/index.php/Laboratory_information_system
You will find that LIS is a subset of LIMS. LIMS can do what LIS do but LIS cannot do what LIMS do.
With respect to the protocols, CLSI has developed a set of communications standards that clinical instruments work against. There is a wide degree of variability between all the instruments despite having these standards you have referenced. The instrument drivers from Data Innovations are developed to those standards and more. When you use those drivers they have all the coding built around those standards. The other standards you will find are ASTM which are deprecated but they are heavily used by most clinical instrument manufacturers.
John, I reached out to Data Innovations and they were helpful but it was not feasible on the business side. And at this point I am running out of options. Would you be able to clarify on how can I develop a interface?
I am sorry Jenish, I cannot tell you that as it is a never ending discussion that would take up way more time than I can afford. If you cannot buy a solution, then you have to code one and if you have to code one then you have to get on with it and you will not find an answer to writing code in a discussion forum. You will have to start looking for open source bits and pieces in Github.
Please Sign-in to post a discussion or comment.