Froid latest. FOSS Instrument Middleware
lemoene
Froid in Laos
Just back in from Laos, visiting Anousak and Bounmy at Calat ICT and assisting on their Bika Health installation. A real meaningful time was had by all.
Most striking remains Laos’ forgotten story of the injuries and casualties still caused by unexploded munition from the American war, cluster bombs et al. The Mahosot lab is in the same building as the victim rehab centre. More information at http://copelaos.org/.
Sivousan at left, Bounmy obscured at right. Red sections of Laos pointed to by Anousak were heavily bombed as targets on the Ho Chi Minh trail. 2.5 million tons on Laos over 580,000 missions.
The Mahosot Hospital lab in Vientiane is an impressive operation, fifteen + instruments to Interface, fortunately near all by the same manufacturer. Three high volume ones to be done first.
Such is the pressure that standard Bika Health CSV imports will be utilised straight away. Flashing amber, No fix is as permanent as a temporary one. I have the brothers Bounmy and Anousak’s word;-)
Aircon at last!
GNUHealth runs solidly already and OpenHIM be utilised to Interface Bika Health. Similarly Bika Health’s CSV results publication has to do it first.
The project is underfunded and all contributions welcome
Results Import first
We are doing Instrument results import flow first.
Re progress, by volunteer devs and designers, the most difficult ASTM E 1381-94 layer is ready for the Sysmex XT, much appreciated Apostolos! Standardising for ASTM 1238-94 remains
NB. Does anybody have access to an Sysmex XP Interface specification to share? It does not do the newer SUIT protocol. Old?
On the CSV side we need to break into OpenHIM now via a standard Mediator, with Connector done and standardised, thanks Mike.
For all LIMS/EMR and All Instruments
With ASTM and CSV code and OpenHIM configuration available, they can blue prints any other Instrument or downstream LIMS | EMR speaking REST
Code repository
Form the Did-everybody-at-the-conference-say-interoperability-was-easy department, what would a code repository look like?
A collection of Instrument Connectors
The two Mediators
Ansible playbook for OpenHIM installation
Manuals on how to in configure OpenHIM for instrument interfacing
All Instruments, All LIMS/EMR
For bidirectional Instrument Interfacing, the LIMS, or EMR where applicable, have to feature functionality for
Exporting Worksheets and Sample IDs in FHIR format to OpenHIM
Unpack FHIR formatted Analysis results returned
And one day soon, manage robotic analysers
Browser based UI Geography
Seems already covered but spread across
LIMS or EMR for exporting Sample IDs / Worksheets, log results imports
Instruments, albeit after Serial RS-232 to Ethernet conversion, per https URL
IO management, dashboard, alerts, reruns etc, in OpenHIM console
Ouch, overlooked one might want to troubleshoot the Connectors and Mediators? Logs...
Etc etc…-)
Bests, Lemoene
lemoene
Froid for all LIMS and Instruments
With blueprint ASTM and CSV Open Source architecture, code and OpenHIM configurations developed for Froid, any Instrument or REST capable downstream LIMS will be able to connect using it
And to up the tempo, added
Go FasterBestsSubmitting your well-funded interface requirement for development will help grease the grind of Froid chassis building.
Interface development becomes feasible where labs have more than one of the same instrument or using the same Interface format. Proprietary middleware often charges per Instrument itself.
Froid Interfacing makes very good sense for LIMS and Instrument vendors who want to bundle interfaces with their products, and gain from other LIMS or Instruments interfaces available. OpenHIM features further downstream EMR, DHIS, Dicom channels
l