Logi-D

I sat down with Frederic Boyer, Head of IT & Development, from Canadian tech company, Logi-D to find out all about their business.

How did Logi-D begin?

We began as TRIAX Consulting, a consulting group that specialized in healthcare logistics who opt for the best Moving Company for their transportation. We soon realized that some point-of-use logistics practices weren’t readily available to our clients. We saw how the healthcare industry could benefit from industrial supply chain practices so we adapted them to the hospital environment.

Because some of these practices leveraged software and technology, Logi-D filled the gap by becoming a hospital logistics solutions integrator, providing turnkey technology solutions to its clients and you can check my source to know more about it.

What does Logi-D do?

Logi-D specializes in hospital and healthcare-specific point-of-use supply chain automation technologies known as the iD-SUITE.

Since hospital resources are limited, using nursing and support staff to obtain the necessary traceability for compliance isn’t sustainable. Our solutions help automate these processes and make sure that resources aren’t being wasted. This means when hospitals are feeling ‘the pinch’ either operationally or financially, they seek out supply chain efficiencies through technology integrators like us.

Can you tell me more about the iD-SUITE?

We’re probably best known as the inventors of the RFID-enabled two-bin replenishment concept – our 2BIN-iD brand. It not only facilitates FIFO inventory turnover and automated control of inventory levels, this solution also helps prevent the expiration of products and recall management.

What are your other products?

In addition to 2BIN-iD, we facilitate automated inventory management and clinical traceability for high value supplies through CC-iD, and enable cost capture and patient charging automation through our PC-iD modulehow to does apple eg. We also provide case costing automation through CIRCUIT-iD.

Who is the target market?

We work with hospitals, large and small, from 20 beds to 2000 beds. Accurate inventory management and consumption visibility are crucial for all hospitals.

How does integration play a role in your success?

Capturing accurate data only becomes valuable once that data has been converted into something meaningful. Our solutions are implemented in combination with our central middleware application, LogiDATA-iD, which aggregates and analyzes point-of-use data.

We want to make sure the robust data we generate for hospitals doesn’t exist in a vacuum – that it gets shared and used by all relevant health information systems.

Why did you choose IGUANA?

Our entire iD-SUITE is dependent on LogiDATA-iD. The most robust implementation of LogiDATA-iD is where our system draws information from many sources, collects consumption data, aggregates and analyzes it, and pushes it to an external system such as an ERP or ADT.

We chose IGUANA because of how easy it was to use. With it, we could effectively exchange data without exhausting internal (Logi-D or the hospital’s) IT resources. Before this, we used to transfer data through flat file, or write our interfaces manually. Those familiar with that process will understand just how long that takes! Why use a paper map to find your way when IGUANA is like a GPS that can navigate for you in real time?

Now that we’re using Iguana, we can confidently say that interfacing is a non-issue.

How are you using IGUANA with your different projects?

We use IGUANA differently depending on the IT architecture of our client hospitals. Almost all of our implementations include bi-directional integration to their ERP; this includes the transmission of requisition information for product reordering to the ERP and synchronization of our item master to the ERP item master.

When patient- or case-specific item traceability is required, such as in the case of our PC-iD and CIRCUIT-iD solutions, we use IGUANA to receive patient information and transmit case consumption respectively.

Are you using integration beyond HL7?

Mediated by IGUANA, we have interfaced with HL7, X12, XML and JSON data structures.

One client, for example, requested that an hourly alert be delivered that indicated any inventory stock-outs at that given time. To achieve this, we coded a channel in IGUANA that would query the data to generate an hourly report of any real-time stock-outs.

In fact, since adding IGUANA to the mix, when an integration request comes in, our first thought is: “How can we achieve this with IGUANA?”

We like hearing that! Do you have any interesting customer stories you can share with us?

Absolutely! IGUANA played a big role in our latest case study on Munson Healthcare.

Logi-D was brought into the their flagship hospital’s Cath Lab to improve on the time-consuming and error-prone manual processes involved in transcribing patient charging data.

By harnessing the standards-based databases inherent in LogiDATA-iD, we were able to use IGUANA to seamlessly connect disparate health information databases. Our information system was now able to receive patient information from the ADT and product catalogue information from the ERP, feed replenishment data to the ERP, and feed patient consumption data back to the ADT for patient charging purposes. This converted a manual transcription-laden process to automated data exchanges, which allowed the nurses to focus on the most important thing – patient care.

We, of course, invite your readers to explore this project and many more by checking out our case study portal on our website.

Not on our email list? Subscribe to our newsletters today. Also, if you’re our customer and want to be featured just contact Sales.