Laboratory information management system

Oh, it is an absolute alphabet soup.

CRM, ERP, APS, MES, QMS, LIMS, WMS, TMS, serialization.

I mean, it's a lot.

It can definitely look intimidating, but if we stick to your smartphone analogy, layer two is simply the apps installed on your home screen.

So he's also built in to fill a existing lab environment.

We know every lab has its own processes and system, so headOP is designed to integrate with LIS providers and other lab technologies, rather than forcing them to change how they work.

Ultimately, the goal is simple, is to give the pathology teams tools they need to work more efficiently, collaborate easily, and confidently adapt to new technologies as they feel continues to evolve to maintain the quality and consistency needed for patient care.

Fab.

Also, it was, we've done some virtual training sessions with them.

So how we would do with any customer, really.

LIS integration was pretty...

Nice.

But it's, it's a life cycle, and when it comes to systems, you know, we traditionally used to build systems around departments.

Like, hey, these are the departments that will manage the LIMS system, and these are the departments that are heavily involved in the EQMS system.

Now it's like, how do we integrate them? Because they're all working together.

How do organizations essentially think of making them one large enterprise unit or, you know, an infrastructure where multiple systems can integrate more seamlessly and data can flow seamlessly between- Each of the systems, and the processes can work more integrated with each other, whether it's an ERP or an eQMS or a LIMS or any other system.

So if somebody is working in an ERP system and there is a process where a quality person has to come in and check the work and approve, now there is a, a interface between supply chain or, uh, you know, a, a, a function within ERP and then a quality function.

So there is kind of that integration piece.

So there is a lot of those kind of integration processes where companies are now, now looking at, hey, instead of operating in silos, can we have a connected operating model where we can have the ERP, our eQMS, LIMS, MES, all of these systems work together, and the right information f- or data flows between them, and more importantly, that data is controlled.

So example, you know, recent example is, you know, I've had a company working towards...

Hi, everybody.

They're joined by their chemistry colleague, Nick Hager, who is Director of Clinical Chemistry and Lab Information Systems.

Hi.

So this group has published a recent commentary in JCM on their experience preparing their lab for how to manage a potential Ebola patient.

And, you know, automation owns it in DCS.

Quality might own it in LIMS and so forth.

And I think there's a gap in that human beings tend to kind of avoid that.

the ownership piece.

So I keep going back to proper planning, proper decision-making, proper governance, right back at the concept and basis of design of a plan so that you map your data all the way through and potentially all the way through the supply chain, or as far as you can get anyway.

And that then saves rework at the back end.

Many projects have failed because the DCS system didn't properly integrate with the MES system and the MES system didn't integrate with the LIMS system.

Again, because you're trying to do that at the back end instead of the front end.

When evidence is received by the FBI laboratory, it will first go to the Evidence Management Unit.

Within that unit, an Evidence Management Unit personnel will take a detailed inventory of the items, and they will enter those items into our Laboratory Information Management System, which gives the laboratory number as well as the item number of all of the items.

Was the evidence in this case examined by any other units at the FBI lab?

Some of the items in this case were also analyzed by the Chemistry Unit.