I think we'll probably still have some more people coming in, but it's a little after 8:30 A.M. now, so we'll probably get started for everyone. So first, welcome everybody in person. It's nice to see all of you in person. We have a bunch of folks that are online too, on Zoom. So welcome to all of you that are remote. So first of all, this is the first time for us that we've got a good contingency of our management team actually in Australia. So I have David Madaffri with me, our COO, and Dyan O'Herne, our CFO, with me here for the week. So what a great way to kick off the week. I will ask that, as we go through the presentation, if you all wouldn't mind holding questions until the end, and then we'll go through any questions that we have in person first, and then we'll get to all those of you that are online and your questions online at the end. We'll get through this. There we go. Hey, first, I know most of you have heard the story before, so I won't spend a whole lot of time on this, but, you know, one of the things that is unique about Mach7 is if you—if our tagline of independence through innovation. What makes Mach7 unique is the fact that we have separate modules that we sell, that can service customers across the spectrum of enterprise imaging. What we don't do is make our customers buy our entire ecosystem in order to take advantage of our technology. So, so what that means is, as an enterprise-first company, we really like to have our, our customers focused on consolidating imaging, bringing in images from across the whole hospital system, not just radiology, and then being able to serve those images back out to the whole hospital community in a meaningful way. So the two major components of the system that allow us to do that are our VNA and our enterprise viewer. There are other components in here as well, and there's other use cases that we'll discuss, which are really important to our customers. But the idea that you don't need to buy our whole ecosystem to find an advantage and to find an ROI with our software is really important and sort of central to who we are. So kind of a new slide for those of you who've seen some of our decks before. I just put this together for everyone just to get an idea of Mach7. I sort of usually ignore the seven to 10 range. I don't talk a lot about that. But in 2016, Mach7 did become a public entity on the ASX through a reverse merger with a company called 3D Medical. That's how we ended up here in Australia. And then in 2018, we signed our most significant contract at the time, the Hospital Authority of Hong Kong, which was really an anchor for us with our APAC region, a very, very central region for us and where our founder is located in Singapore. And then, of course, one of the most important things for us is our acquisition of Client Outlook. That took place in June of 2020. I think it finalized in July of 2020. That was a transformational acquisition for us. And we had this wonderful back end from an enterprise imaging perspective, but we partnered with Client Outlook to provide the front end, and the front end is really what radiologists fall in love with, right? The radiologists and other users, they like front ends. So, when we, when we acquired Client Outlook, that really made a more complete solution for us and allowed us to, to quadruple the size of our, of our funnel and our opportunities. So, so transformational for us, for sure. You know, as we started today, we got more traction in the market. We got recognized by KLAS, we got better KLAS rankings. You know, and sort of started to get a bit of this network effect within the U.S., especially within the U.S. And, you know, and that sort of has led us to where we are today, most recently with our, with our NTP contract in the VA, with a lot of contracts in between. So a couple of things that I'll mention here, just because I think they're important topics for you to understand sort of our take on things, because these are topics that come up constantly in all of our conversations, right? The first one around AI. You know, look, for us, you know, AI means a lot of things to a lot of people, and we hear a lot about it, but we're generally hearing a lot of more news around, you know, bigger data models, natural language models, generative AI, things like that, right? Our take on this is that for us, we know medical imaging is going to be a big consumer of AI products into the future in a lot of different ways, both clinically, operationally, and also from the perspective of efficiencies with, with doctors. It could be anything from from voice recognition and how they're transcribing their findings to to how they're coming up with their initial clinical findings. We also know, though, that there's some things that are kind of in the way of AI right now in medical imaging. M&A activity is taking place, it seems like weekly, it's probably monthly, but it seems like it's a, it's a big part of, of, of that market where companies that are coming up with an algorithm today-... Either become obsolete in six months or they're acquired. So there's a lot of movement in the market right now, and on top of that, at least in the U.S., there's complications around reimbursement. The good news is reimbursement is starting. But it's slow. It's gonna take some time, but it's starting. So the more reimbursement hits the, you know, the U.S. system, the more likely it will be that facilities will look at AI models, and how they can use them clinically. You know, the other piece that I mentioned here is a lack of evidence, and what I really mean by that is, first, evidence that it is more efficient for the radiologists and that they can move through more studies, more images, with higher quality at a faster rate. They need evidence that's the case before they invest money, is one part. The second part is evidence that they're clinically appropriate. I was just recently at a KLAS symposium where a speaker was talking about any risks around AI models clinically. And part of that was, you know, who's gonna be the first hospital in the U.S. that is sued because an inappropriate clinical finding was found? How is that case going to be prepared and presented? What kind of an impact will that have on the market? We don't know yet, right? I think the first case is being heard in California, actually, this month, around this. We'll see how this evolves, but regardless, we know that it's something that's going to be into the future of medical imaging anyways. From a Mach7 perspective, again, we're not investing in bringing in the imaging scientists to develop new algorithms to provide clinical features and functions for radiologists or for other users. What we're concentrating on is making sure all this data that's being centrally located in our archive is available for our customers to be able to use themselves for AI initiatives that they themselves have. Many of them are initiatives that they are bringing in internal. They have their own scientists that are developing their own algorithms. They want to use their own data to develop these algorithms. Other parts of it is they need data that they can easily segregate so that they can, they can do their own testing against commercial models, right? In those ways, we can really help. We give some facts here just around, you know, the number of type of information that we have, number of images that we have in our solution, just to give some context for how that data can be used internally by our customers. I would emphasize, though, that this isn't data that we intend to monetize, right? This isn't data that we own, that we intend to monetize. This is data that we help our customers monetize, right? Make sure we're really clear on that. The other piece on this is. I mentioned Client Outlook being a transformational acquisition. I just wanted to, and many of you have seen this slide before, but I just wanted to just spend a second just to really emphasize how important that really was. It showed us that as a company, there is growth opportunity through acquisition. We believe that today, just as we believed it when we acquired Client Outlook. However, given the current market conditions, we are a little cautious. We would want to find an acquisition opportunity that we thought could create the same sort of transformational business model that Client Outlook did for Mach7 when we made that acquisition. So if we do see that right opportunity, we certainly wouldn't shy from it, but at the same time, it would have to be the perfect opportunity, just like I think Client Outlook was the perfect opportunity for us. And, you know, we always keep our eyes and ears open for those opportunities. This sort of gives you a little bit of information. That bottom slide in FY 2023, the way to interpret that is we had 17 deals that were for Viewer only. We had seven deals that were for VNA only. We had seven deals where the customer bought both products from us at the same time, and we had six deals of either a Viewer client buying the VNA or a VNA client buying the Viewer from us, right? Just to show that we do have some cross-selling opportunities in there, right? Clearly, for us, the value is when people buy both products. That's the ideal solution. Dave will talk about that when he talks about how we sell our product and the value propositions. So just a snapshot from FY 2023. As a reminder, our FY 2023 results came out, right? We did have some conversations about this already, but we have not released our Q1 FY 2024 numbers yet. Those will be released at the end of October. So just know that they're coming but haven't been released yet. I won't spend a lot of time on this. I think everybody's probably quite familiar with this. But I think one of the important parts here really has to do with recurring revenue. The CARR and ARR number, I think is really important. I think we're seeing our business model, where we've had a large percentage of deals that are capital contracts. I think we're seeing some transition there, where two years ago, we saw we were around 50/50. The last couple of years, we've been around 60/40, 60% being subscription, 40% being capital. And I can see as the future progresses, that that number is gonna continue to shift over time, more and more towards subscription, right? That has an impact on our business. On the one side, it's really good quality, recurring revenue, right? On the other side, you know, if it happens too quickly, then we have a situation where, you know, our revenue from the capital deals isn't coming in in a current year, right? So the idea is to really try to curate that transition as effectively as we can and not jump too fast to a full subscription model. I get asked all of the time, "Why not just, you know, say just subscription only?" Well, it's easier said than done. It'd be great if we were just starting, but we're several years into this business model, so it's a little bit more complicated than that. So just as an ending note, before we hand this over to Dave, fragmented opportunities. We have a lot of our longstanding vendors, the IBMs, GEs, Philips of the worlds that are losing market share right now. Vendors are moving further and further away from those single ecosystem solutions. We know they're losing market share. It's leaving market share open to all the rest of us that are trying to gain some market share. We're also seeing volume transition from the what we call the acute care space, the hospital space, to the ambulatory space, the outpatient space. But not just in the U.S., but all over the globe, we're seeing that happen. That leaves... There's several vendors out there that can do a great job in the acute care space. They can do a great job in the ambulatory space, but they can't do a great job across the spectrum. Feel like that's an advantage of Mach7, where we can effectively use our software across the breadth of these opportunities. You know, from a complexity perspective, we're oftentimes asked, like, what works out better for us, the acute care space or the ambulatory space? Where do we concentrate? Look, we concentrate on complex. The more complex the workflow is, the more, the more return on investment you get out of a solution like ours. You're not gonna find a single hospital with ordinary workflow, who's doing 100,000 procedures a year. There's a lot of solutions for that, for that type of customer. But to find an ambulatory site with 50 imaging centers and reading services for teleradiology that work out of 10 hospitals, or hospital systems that have multiple hospitals, multiple JVs with other outpatients, teleradiology services, things like that, all the, all the complexity there, that's where we can thrive. So it's not a matter of what market we thrive in, it's a matter of, you know, the more complex, the better for us. Of course, and everyone has seen our renewal opportunities. We have a lot of opportunity in renewals in FY 2024. Look, we hope that always is the case, right? We want our existing customers to continue to renew with us. We generally sign five-year term agreements. We want them to be 10-, 15-, 20-year agreements, but they're at five years at a time. We have a low attrition rate with our customers, so, you know, we should get these renewals on a pretty regular basis, right? And I'll let Dave talk a bit about sales, and you'll understand more from him, but, you know, we expect good things out of sales this year. We expect our sales orders to grow by 20%. You know, we've stated revenue growth and then, of course, a lower OpEx growth than we see on the revenue side. Essentially, what I'm trying to say there is, if we start to see a transition in revenue, closer and closer to that subscription model, right, our OpEx has some variation to it, right? So, we'll work really hard to maintain margin, right? That's one of the, a focus of ours is to try to maintain margin. We wanna grow the company, though. So the focus is on sales orders, the focus is on revenue, the focus is on OpEx, and all things are in relation to one another. I think with that, I am going to hand it over to Dave, who's going to talk to you all about sort of the value propositions and sales of our product. Thank you. Thanks, Mike. Reminds me a lot of Southern California. I lived there for a number of years. Beautiful water. So yesterday at lunch, when I was having lunch with Mike, he told me he's buying boots before he leaves here. I didn't know boots were a thing in Australia, but being from Texas, I think that makes us have something in common. We have a lot of boots in Texas, as you know. We also have big hats. I think the other thing that, that we have in common is our accents. So as you'll notice, I have a, a strong Southern drawl. Later, you'll be meeting Kristi and Jeff. They'll be doing a demo of the product. They're also from Texas, so we're gonna try to enunciate all of our words slowly, for you guys, so it makes sense. I guess, the only thing we don't have in common is football. So hopefully, I will learn more about your football while I'm here this week. How many Australian football fans? A lot. Any American football fans? Just one. Two. All right, awesome. So I was excited because this morning I woke up at 2:30 A.M., and I'm going through the channels in the hotel room, and I caught the Buffalo Bills, Jacksonville Jaguars live in Australia, 2:30 A.M., being broadcast from Wimbledon in England. So obviously I was really excited, nearly called in sick, today, but Mike, I thought I should probably come in. So with that, I'm really here to talk about my second love, which is medical imaging. And so fortunately for Mach7, medical imaging is booming right now. So all of you are aware, traditionally, medical imaging typically is in radiology and cardiology. All of you probably had a CAT scan or an MRI, or you know people who've had ultrasounds. But with the advent of this device that most of you are handing in your pockets right now, this is the newest medical image capture device. So if you're out for instance, playing rugby and you gash your kneecap, when you go into the ED, more than likely the ED physician is going to take a snapshot of your wound for historical purposes. If you go to dermatology with a skin lesion, again, dermatology is now using iPhones to take pictures of those skin lesions and store them. We now have tiny cameras everywhere in the hospital taking videos. So we have tiny cameras that go in through your throat to take pictures of polyps in your stomach. We have pictures of surgery when you're having surgeries done. And then all of you are familiar with going into the dentist, getting dental X-rays. Pathologists are now starting to digitize their slides. And so what Mach7 does for its customers is we take all of those images, regardless of where they're taken in the enterprise, and we consolidate them into a single image repository, which is on your right. So we also call it our vendor-neutral archive. And so by doing that for our customers, we help them eliminate the silos of data throughout their enterprise. Why customers like the Mach7 solution is we are a software-only provider, which allows our customers to use their own infrastructure and more importantly, their own security to protect their data and also their own data storage mechanism. With the Mach7 solution, our customers can store it on-prem in their own data center. They can store those studies in the cloud with Azure or AWS or Google. Some of our customers are even doing hybrid, meaning they would store a copy on-prem, and then they might store their disaster recovery copy offline in Azure or AWS for cost-saving purposes. Once we have all of those images consolidated at the enterprise level, the next thing we need to do is provide access to clinicians. The access that we provide through our zero footprint viewer has to be scalable because we're sharing those images with thousands of users across the enterprise. And remember, the enterprise could encompass not only an individual facility or multiple facilities, physicians, offices, mobility devices. So all that data has to be available to those clinicians anywhere, anytime, on demand. And by the way, it has to be fast, because if you think through it, if you have a vendor-neutral archive here in Sydney and a physician in Melbourne wants to pull up a study and look at it, we have to ensure that we deliver that image to Melbourne very quickly. Not only to that user, but potentially the thousands of users calling images from different locations at the same time. So that is why people love the Mach7 solution. Centralized repository, very fast, easy to use, intuitive viewer that can deliver images anytime, on demand. Within the viewing system, we also have to have specialized tool for different users. So the tools that your dentist uses when he looks at your dental exam is very different than the tool sets that a radiologist might use. A radiologist might need to do 3D imaging. Your radiologist also might need to perform mammography studies, which is very complicated and requires very sophisticated tools to interpret them. So with the Mach7 solution, we have a very customized approach, delivering different tools to different users throughout the entire enterprise. This also becomes very important as we move into the academic institutions, because not only do we want to deliver those images quickly and efficiently, but we also want to segment them for certain types of users. Meaning, if I'm doing a research study that requires some level of anonymization, I want to make sure that I can put those images in a segment in the vendor-neutral archive that's only accessible to certain users, keeping that data confidential from other types of users. And then finally, all of this information has to be not only available through your devices, but most physicians also want to see them, available through their electronic medical record. So that when I'm in looking at other types of data, such as your EKG or some of those other clinical areas of your history, I can launch and view all those images directly from Mach7. So the last box, workflow orchestration, is what I really consider to be the secret sauce and what makes us different. If you talk to many of my competitors in the market, most of them will tell you they have a vendor-neutral archive and a zero-footprint viewer. I would argue that theirs isn't as good, of course, but what really makes us different and what my competitors don't have is workflow orchestration. So I'll give you a few examples. So as I talked about earlier, we, let's say that we have a system here in Sydney, that has a set of modalities, let's say CT and MRI, and they acquire another hospital in Melbourne that has different CTs and MRIs, but we're all sending all that data to one common location. Within the Mach7 solution, I normalize all of that data as it comes in to make sure that I can then deliver that data to the right clinician at the right time in the workflow. It's very important for making all of this massive amounts of data work together. Think about, like, your own computer, how you have your own file structure, and it's easy to find things. We're doing that at massive scales with massive amounts of data, and that is the secret sauce of the Mach7 solution. Also included in that is DICOM routing. Okay, so DICOM routing is important. I'll talk about something that's buzzy right now in the market. A lot of you people are talking about, AI, adaptive intelligence. So the real important thing about adaptive intelligence is the workflow, to make it work. And if you can imagine, if you're a clinical system that's using 13 or 14 different algorithms from a vendor, we have to make sure when those images come in to our solution, whether we send the whole study or certain images from that study to the right algorithm at the right time, to make sure the algorithm can do its job and send back the results to the clinician prior to the clinician providing the diagnostic interpretation. Without that key elements of workflow, AI would be doomed to fail. So we think as the AI market continues to grow, Mach7 is gonna have a great foothold in helping our customers develop workflows, complex workflows, around AI. And then lastly, for workflow is lifecycle management. Unfortunately, most clinicians in the States, I'm not sure of here in Australia, but, you know, clinicians tend to keep all studies forever which is very costly from a customer perspective, because you're storing studies that are eight, 10, 12 years old. And so, although customers haven't adopted true lifecycle management, which we give them the ability to do, which is essentially deleting studies, instead, they can use our lifecycle management tools to get creative. Maybe instead of deleting that studies, I can take studies older than, say, seven years old, I can compress them and send them to a cheaper storage alternative. So it allows me to decrease my costs from a storage capacity while maintaining the record for the life of the patient. Does that make sense? All right, moving on. This is... I always like to highlight this, when talking about our Mach7 solutions, because it is unique in the industry. So the tools you see here, if you think traditionally back about imaging, remember, it started in radiology. All these tools here, radiology have been using these tools for years, because it was important to make the radiology departments work. What Mach7 has done, we've taken all those tools that are traditionally only available in radiology, and we make them available to all the users across the enterprise. So if you go back to my examples earlier, if I'm that doctor doing wound care images, or I'm a dermatologist, or I'm a, a pathologist, I need to have on the left there, quality control. I need to be able to make sure that the image I just captured in my iPhone is correct; it's got the correct labels. It's got the correct clinical information, so that when I send it back to the vendor neutral archive, I know that it's accurate. Traditionally, until Mach7 made those tools available in the enterprise, those customers didn't have the capabilities of doing that. In the middle, worklist. Typically, radiologists have been using worklist for years. We now have taken that idea and spread it to all the users on the enterprise. A couple of use cases for that are: if I'm now a clinician and I'm on the floor making rounds and I'm seeing all my patients, I now have a custom work list of every patient I'm going to see that day, and more importantly, I can launch and see that patient's clinical imaging records from one location and see all those images, regardless of where they were taken, at the bedside while I'm talking to my patient. I also like to use work lists for tumor boards. If we're going in and we're collaborating with a group of clinicians about tumors, I can have all of those on my work list. I can pull out my iPad, I can launch them, I can display them on the screen, and we can collaborate with all the physicians, regarding those cases, live and on demand. And then, we talked a lot about the images, the importance of them being fast, being able to collaborate with other clinicians wherever I'm at. We have tons of stories where physicians are out at dinners. He may be the only physician capable of reading a particular type of study. He can pull out his iPad at the dinner table, get a call from another clinician in-house, and collaborate real-time using the Mach7 solution, on his tablet, which is phenomenal, I think. All right, I'd like to use this slide, to talk about scalability and flexibility of the solution. So this is a few of our customers. We have 165. So let's start with scalability. If you look at this list, which is pretty extensive, we're able to accommodate very small customers like, Wake Radiology. Wake Radiology is a small customer in the U.S., that is using us for a very small use case, up to the Hospital Authority of Hong Kong, which is a country. So we also have small community hospitals. We have large IDNs, we have radiology reading groups. And so our solutions at Mach7 are customizable and scalable based on the size of the organization. They're also very flexible. So if you look at, for instance, Penn Medicine, Penn Medicine uses Mach7 for the vendor neutral archive, so they're storing all their studies on us. They're using us for an enterprise viewer, so all the clinicians in the enterprise look at images on the Mach7 viewer, but in the department, they use Visage for radiology. So conversely, if you go to a place like Stanford Healthcare, Stanford Healthcare is using Sectra in radiology. They're using Sectra for archiving, but they're using Mach7 as their enterprise viewer for the speed and performance that we can deliver. And then finally, we have customers like Adventist Health there in the top left, which is a large IDN in the West Coast that uses our full stack. So not only are they using us for the enterprise archive, they're using us for enterprise viewing, they're also using us for departmental viewing, which means all their radiologists are using this every day to read studies. So it's a very scalable, flexible solution, which makes us, I think, very opportunistic around opportunities, because we can provide our customers exactly what they're looking for. The next slide really is about our customers and partners. So in addition to being scalable and flexible for our customers, we're also scalable and flexible with our partners. So here you see a variety of partners, some big names, some I'm sure you recognize. These partners use us in a variety of ways. So if we start with someone like, is Nuance on here? Nuance, there in the center. Nuance has a PowerShare solution that they market, so that allows all of the Nuance customers to share images across their enterprise. Within their solution, anytime a customer pulls up an image from their PowerShare solution, they're actually utilizing the eUnity viewer. So they've embedded their software around the Mach7 solution to provide the speed and performance for their customers that they need. We have other customers that are resellers that sell our whole stack, like Nuvodia, and then we have other customers have wrapped software around the Mach7 solution to develop their own solution. So Lucid Health is a great example. It's a group of radiologists out of the Midwest, I think Indianapolis, to be specific, and they have built a custom worklist. So they go out and sell this custom worklist to radiology reading groups that provide them a lot of efficiency, and when a customer of theirs launches their worklist, they are actually launching the eUnity viewer. So there's a lot of use cases, as you can see here. I'm not gonna go into them all, but we've been very successful, and this market continues to grow for us. I probably get two to three calls a week from vendors that wanna work with Mach7 in a variety of ways. We're really excited about that and the opportunities in front of us in that arena. This shows you a little bit of that flexibility. In the middle is the eUnity viewer from Mach7, and if you go straight up, that's our own work list. When I talked about Adventist Health earlier, Adventist Health is using our work list, launching our viewer and reading studies. However, if a physician likes the experience of the eUnity viewer, but he has a different preference for workflow, using different work lists, what you're seeing around the outside are all the vendors that we can be launched from. So with Clario, which is an Intelerad product, which is quite popular here in Australia, the Clario worklist actually is live in several locations where they launch the eUnity viewer. Same with RadAssist, which is Lucid. DocPanel has built their own worklist, which is a reading group out of New York that's really growing rapidly. And then in the bottom left, which we're really excited about, Nuance has built their own worklist. I'm sure all of you saw our announcement regarding the National Teleradiology Project, where we're going to be providing teleradiology for the federal government, which is a, a big deal for us in the States. We did that in collaboration with Nuance and Microsoft. So in that particular instance, Nuance will be driving the workflow, eUnity will be the viewer and the archive, and our archive will be hosted in Microsoft Azure. So that's a really exciting project. It's kicked off, going well. We are scheduled to go live with that sometime in the June timeframe of next year. All right, KLAS, I know that you guys have—Mike briefed me. It's something I think you talk about a lot. We continue to do well in KLAS. We absolutely always have room for improvement, and it's difficult. This is a very time-consuming thing for a vendor to do well in KLAS. The key to KLAS is making sure that our customers fill out the surveys. So we've done really well in eUnity. For the last several years, we're always in the top. We expect to be in the top three again this year. That'll be announced roughly right after RSNA, which is the January timeframe. In the vendor neutral archive, we have some work to do, and the reason we have work to do in the vendor neutral archive space is because we have a lot of legacy customers. Customers who have been using us for a long time. So again, we, as the vendor, have to make sure that those customers take the time to send in their surveys to make sure we get the results to move us up on the KLAS surveys. So we're gonna continue working on the vendor neutral archive this year. We're rolling out a new version of the product called V12. That's in production in a customer site.... So that's on track, but, we're very excited about V12 and the impact that'll have on our VNA—on our KLAS rankings. So I'll end with this slide. You know, a few wins, that you're probably aware of. St. Paul's was a net new win in Hong Kong. It was part of the Teresa Catholic Health System there. Nuvodia is a customer I've known since my days at Philips, so I dealt with, Nuvodia for a long time when I was at Philips Healthcare. When I joined Mach7, they were happy, and I was happy they decided to move over and join us here at Mach7. They're a reseller, an interesting reseller group in the sense that they're actually a radiology group. A group of professional radiologists who started their own IT managed service business, and they've chosen to use the Mach7 solutions to sell to all of their customers. They presently have about 150 customers on Philips, and over time, they'll start moving all those customers to the Mach7 solution. And then, late last year, huge win for us. We signed Akumin, which is a large, imaging center chain in, 48 states, primarily in the south, spreading out towards the southwest, I guess. But very large contract for us. Lots of users. They had an insane amount of radiologists reading for them. I just saw the number. I want to say it was, like, 328 radiologists in that group reading. So we're just, are in install now. I think the VNA came live. We're starting migration of studies, and we expect all of those imaging centers to be live sometime by late next year. It's a great, exciting project for us. And then finally, this last quarter, I guess these are public now. There's the NTP. Huge opportunity. So not only... The reason the NTP was so exciting for us is the National Teleradiology Project is a reading platform on top of all the VA hospitals within the United States. So there's hundreds of VA hospitals in the United States, and so what happens when they get busy, or they need specialty readings, they forward studies from those hospitals to the National Teleradiology Project. That's going to be read on the solution I detailed earlier. That's phase one. But the more exciting part for us is they also said that in later phases, when those individual VA hospitals come up for their renewal with their departmental PACS solutions, they have the option, instead of going out to bid, which is very painful with the U.S. government, they would have the option to just move that study volume to the NTP in what they're calling NextGen Fed PACS. So we'll see where that goes. Still early, but we're excited about that project. And then two other wins. We signed DIA, which was an existing customer. We actually moved them into a subscription contract, and they're expanding the use of eUnity. Previously, they'd only used us for mammography. Now they'll be using us for all of their studies. And then lastly, I think in a you know, a display of you know, their satisfaction, the Hospital Authority of Hong Kong renewed their service agreement with us, which also included professional services. So I think that's it. Hopefully, I didn't take too long, and I spoke slowly enough and enunciated all my words for you guys. But next, I think the more exciting thing, two great presenters are actually going to spend a few minutes showing you guys the actual product. That's not something we've done before. We thought you guys might enjoy seeing what we actually do. So, I'm going to start by handing it over to Jeff Hastings. Jeff, are you there? I am here. Hello, everyone. Good to, good to see you. Let me go ahead and share my screen. I wanted to start, kind of where Dave left off in terms of building. Is the screen share actually coming through? I don't see it behind you yet. Hey, Jeff. Yeah, we're not getting it yet. Okay. It says I'm sharing it, so I don't know if we need to just stop sharing on your end in order to free up the screen. Hold one. Okay. All right. You're up. You're up. Okay, excellent. So I thought I would go ahead and just build on some of the examples that Dave gave as it relates to how facilities are using the VNA. I'm going to start with the VNA side, and then I'll pass it over to Kristi for the viewer side. But our focus is really going to be on the differentiators, what makes Mach7 unique, and how those directly translate into benefits to the health system. So I'm just starting on the VNA. As Dave said, storing DICOM images is fairly run-of-the-mill. Everyone should be able to do that. But one of the key things in the Mach7 solution is the ability to take that study in, so just think of this as a top-down workflow. We're taking the studies in, we're doing any data normalization that may be needed, modifying the patient medical record number, things of that nature, series descriptions, et cetera. Bringing that in, normalizing it, and then placing it into the appropriate logical archive segments. So as Dave said, this is a software-only solution. We're allowing the health system to choose their server infrastructure, their storage infrastructure... But then we break that up into logical segments in order to place radiology in the appropriate segment, cardiology, dermatology, et cetera. And the way we do that is by utilizing the DICOM header information. So it could be as simple as just the department name, or it could be any of a number of different filter criteria or identifiers that are contained within the study. So it gives us a lot of flexibility in creating rules that say, "This study should go into this segment." Okay, why is that important? What this allows us to do is two things. The first is to provide an enterprise access to all the studies across all of the segments based on their user credentials. So should they be able to see into the dental segment or the dermatology segment? The other thing that it allows us to do is to create individualized lifecycle management rules. So for dermatology, they may have a different image retention policy than your cardiology or radiology department. So by breaking up the studies into logical segments, that allows you to create that granular control for both user access as well as the, the life cycle management, like I mentioned. The other item I wanted to hit on was the research piece. So very frequently, whenever you're doing research studies, you want... You may want to store those, but in addition to storing them in their own segment, is doing things like anonymizing based on a template that's put in place, or maybe even saving it based on a specific transfer syntax. So within the medical imaging world, there's many different transfer syntaxes or different types of how the image is encoded. Maybe that's a better way to think of it. And so not only can Mach7 do the normalization on the patient identifier level, but even if it's converting it from maybe an old way of scanning that the machine is generating and modifying that, putting it in a newer transfer syntax or a specific syntax that the research department may need. So you could think of that as the, the data normalization on the, the encoding layer as well. So a tremendous amount of flexibility there. I want to go into teleradiology next, 'cause it's very similar flow in terms of top-down workflow, but specifically with teleradiology, many times the scanning sequence or what they're calling it, the, the type of study may not match up with what the other, you know, what they've decided the standard should be on the hospital. So the ability to use a compare/replace matrix in order to normalize how they're calling or what they're calling or naming that study. The same thing, is true also for adding a prefix to the information on an identifier, like imaging center number one, et cetera, so it doesn't cause any data conflicts, or it can be easily identified, within the solution when the radiologist is reading it. So you bring the study in, do that data normalization, like I mentioned, but in this example, I'm not archiving it long term. I just want to put it in a teleradiology cache that I've sized for six months, a year, two years, whatever I would like to have, and then at some point, that study just falls off. It hits the high water mark and falls off the cache. So the key thing to remember on this teleradiology workflow is that we have the ability to both normalize the data as well as treat it appropriately as it relates to image retention, for studies that are coming in from the outside. I'm going to switch over to the... I'm going to stay with that teleradiology topic, but switch over to the workflow engine to highlight, another component, as far as the benefits of the Mach7 solution. So frequently, frequently within a teleradiology workflow, the technologist at the scanning site is just pushing the study into the hospital. The hospital may or may not know that that study is coming. Quite frequently, they're not getting any order or any type of information in advance. All they know is that the study has just been sent to them, and that's it. Frequently, historically, they're also relying on that technologist to send them the comparison studies. "This is a new CT. I want to look at the last three CTs for that patient in order to check the progression of the disease or what's going on with their health." So they're relying on the technologist to properly select the study and then send it to them before the patient can... Or that study can be read by the radiologist. That can be quite time-consuming and prone to errors. So what Mach7 can do is actually build out automated rules that allow all of that workflow to occur automatically. So the technologist is just sending the study to the hospital. We're using an internal archive event of archives. So I've received the study, and that's what's going to trigger the workflow for the teleradiology rule that I've built out. So I receive the study. I can query the source that's sent to me, sent the study to me. I can go in and automatically query their archive, in this case, an MR of the brain. I'm looking back four years, and I'm pulling the three most recent priors. But if this was a different type of study, maybe a mammography exam, there's different rules or different guidelines for comparing historical studies, so I'm going to look further back in the archive. I'm going to go back 10 years, and I'm going to pull the eight most recent priors. In addition to that, I'm going to look in maybe a separate archive and have a rule that says, for anything at all, I want to go back three years and pull five most recent priors. So each of these individual boxes, this is all just automated workflow that is kicked off immediately. But if you turn this into time required for the technologist or staff at that same facility, this can be minutes or sometimes an hour worth of time for them looking, finding the older exam, and then sending it to the radiologist. All of that time delay, what that means is that the radiologist is not able to read the new study until all of that has occurred. So by having these automated rules, it saves time for the remote hospital, it saves time for the staff at the hospital itself, as well as being able to allow the radiologist to read sooner. In addition to that, so these are all just DICOM transfer pulling the images, if you will. HL7 is another integration methodology that's usually used for billing, lab work, those types of things. You could set it up where you send a message, an HL7 message back to the hospital saying, "We've got the study, the reading is in progress," as well as maybe perhaps creating an order. Since an order was never sent, you could use simply the receipt of the study to generate the order and appropriate billing on the hospital side as well. So tremendous workflow advantages for the staff by creating these types of rules. Another one that I wanted to mention was the non-DICOM or this even could be DICOM workflow, like point of care ultrasound. Many times those pictures they take with their phone for dermatology or a quick ultrasound that they're doing in the emergency room, those are not captured in terms of the image record, made part of the larger longitudinal record, and they also may not be billed for simply because they're just a quick look, and there's no actual order that's been generated. So Mach7 can also be used in that situation, where we're receiving the study, either non-DICOM or DICOM, but then create an HL7 message, that actually generates that outbound order, so it can be billed for properly, and also so it can be put in the appropriate context within the patient's record. So again, all this ties back to improving the patient care and enabling enterprise access for the, for the images that have been acquired. The next one I wanted to hit on was the actual DICOM routing. And David mentioned this, and Mike also mentioned it in relation to the AI workflow, and so I want to give you a quick example on that. So within AI, as was discussed previously, you have many algorithms that are customized to do very specific things. So it only may be... It might be a CT of the brain. That is the only type of study that needs to be sent to a particular algorithm, and something else may be used for a CT of the chest. So a facility may have multiple algorithms, and there's two ways to accomplish getting the studies to the algorithm. The first is by sending it directly from the modality or having someone send it from the radiology PACS. That can be time-consuming and fairly complex as well. If they forget to send it, then that algorithm never processes the data, so you're missing out on the advantages of the AI. The other option is to create an automated rule, and that's where Mach7 comes into play. So in this case, we'd be bringing the study in, same type of top-down workflow, bringing the study in, but then based on the criteria that you've established, either the protocol name, the type of study, et cetera, you use that as the trigger to say, "There's a match. I want to route it to this AI destination." And so all of that would occur automatically, again, with the goal of improving the turnaround time for that AI result to come back and be ready for the radiologist to use during the reading. In addition to that, you can have times where you're wanting to evaluate an AI algorithm. Either I want to test something I've built on my own or maybe a new algorithm that I'm considering, but I haven't purchased yet. So you could narrow it down and say, for a particular study description, but all the way down to the individual machine name. This, this station AE title, that's the unique name of an individual scanner in the hospital. So you could have a rule that, that only applies to a specific type of study performed on a specific scanner within the hospital. That's the one you're evaluating, so if that's a match, I'm going to send it to two different AI algorithms in order to see which one might be better suited for, for my patients, et cetera. And the same thing can be put in place as far as doing any type of anonymization or data normalization on the output side as well. So I've just barely scratched the surface in terms of the functionality that the VNA provides, but I wanted to keep it focused on a few specific use cases that really benefit the health systems that are using our solution. So with that, I'm going to stop sharing, and I will pass it over to Kristi, who's going to cover the viewer side of it. ... Jeff, let me know when you can see my screen. I can see it. Mike, others in the room, can you see it on your side? Yep, come up. Yep. Perfect. Okay, great. So, as Jeff has shared with you guys, we have a pretty powerful VNA that's going to drive our solutions. What I'm gonna share with you is eUnity. It's the viewing side of the application that's gonna allow us to see the images and some of the different workflows that we've talked about. So we are a HTML5 viewing solution, so zero footprint download. When you come in and you start looking at the images, any type of device that can hit an HTML5 browser can open up and look at the images, which is really great. PCs, tablets, phones, like we've talked about. Zero, zero footprint download too, also means we're not adding patient information and leaving that behind on the customer's devices. So that makes it really nice as far as security goes, as people are moving around with their personal devices. We're gonna start out by showing you the application in a direct launch. But most of our enterprise viewers are probably gonna go in through an EMR. On a direct, on a direct login, what you're gonna see here is I keep everything very simplistic, because we have a lot of people on the enterprise that we're gonna need to be able to go through and train. So as we look at that, we've kept this very simplistic to be able to go in and just immediately access the images that we need to look at. What you'll see here is I quickly opened up Mr. Killarney's jacket. For anyone in the room, if you've had more than one set of images, this might be what some of these, X-ray jacket used to look like. It's just now presented in a list. You'll see from the newest all the way to the oldest, nice, quick, and easy. So with this direct launch, it's really easy to identify what images I may wanna go in and open up and look at. But when I'm doing this, I'm gonna go ahead with you guys, and I'm gonna start with the oldest set of images. When I open this up, I'm gonna really unrealistically take this through nice, fast, and easy. So you guys can see very quickly how I could go through if this was a trauma case. What you can see down here is I just went through 17 images nice, fast, and easy. What I didn't start with is the way that we have our viewing environment set up. I'm actually in the Texas area, and multiple, multiple states away from me is where my servers and my images are being hosted. So, we're out of Virginia. We're able to now pull these open, and I'm on a very standard connection to my house. We don't even have fiber into my house right now. So, that just is gonna give you kind of an idea of how quickly, when we talk about how quickly someone could come in and use these diagnostic quality images, how quickly they could display them. And when we talk about that, how are we doing that? What really makes us different? So when we look at all these images, one of the things that you'll note here is I'm going to open up really quickly, this one particular image. This is a 14 by 17 image when we used to take it on film. It's a 2K image if you start thinking about that more, computer-based. When we look at this, I'm on just a standard laptop, so no fancy graphics cards or anything are driving what I'm pulling for you. So what we're doing is, even with this full resolution image, we're looking at how the users are interacting with the data. What kind of display ports are we using? How are each one of the individual viewports configured? And lots of other things in the background. And then we are customizing how we share that information with the client so that we can be very fast. And what you'll notice here is there's an easy zoom factor that allows me to see on this lower resolution monitor, how am I displaying that? But instantaneously, I can go in and grab that 100% to look at the spine and very quickly see that at diagnostic quality where I am. So it makes it something that is very easy for the users to gravitate and want to use. In our past life, in radiology, we used to always know that if they got less of an image, you could actually misdiagnose somebody. So this is very powerful for us to be able to share that these are full resolution, and we can give them everything that they need regardless of where they are. When we look at this, the other things I always look at, in clinical care, it's not usually just one set of images that are gonna be necessary to take care of you or to take care of your family member. What they're really gonna be looking at is what's going on in your entire history. So the nice thing is, when we talk about that history, it was great on a direct login that we could see that. But if somebody's coming in through the EMR, they're launching directly to these images, and they can still get to it. So as the doctor is taking care of this patient, he can go back to the oldest set of images provided and then follow what has actually gone on in this patient's history. You can see here, this patient has gone through lots of X-rays and different, different types of studies after they had their trauma. And you can also see even when those datasets get a little bit more complex, we can divide those out and hang them with some automation that is gonna allow anyone, so the surgeons, not just the radiologists, actually have tools activated and make their life simplified, less clicks, more efficient. So you'll see here I have nice little lines that are showing me where I am on the spine, but we also build in a lot of tools. They've done a really great job identifying some intelligence in the tools and things that somebody might need as they're looking at this. So if I was the surgeon, not the radiologist, I want easy ways to figure out where I am in all these diced up images. So you can see if I start here, we have five lumbar. So if I start on three, so here's five, four, three, and I place that marker. It goes ahead and moves all the rest of the images where they need to be, but nice and easy, we can do that on any image. So if I'm up here, I don't have to move my eyes away, or if I'm over here and I want to start identifying down here where I am, I can quickly continue to label as I'm looking at the data set. So it makes it something, again, that's very easy for the users to gravitate and use, which gets adoption by a lot of the enterprise users that did not gravitate to using these images and relied heavily on the radiologist's reports. We're going to continue as we look at this patient's record, though, and find out where did they end up? So we can see as they go through, they may have gone all the way through into the surgical environment. Maybe this instead was a broken hip. So as you can see, as we look through the data set, now we're seeing different types of information that being, may be necessary to take care of the patient. So what you see here is I have a hip, but the surgeon may have needed to add some additional post-processing to that, maybe something that we don't, don't do inherently. That's okay, because if they have applications that send us that information, you can see how we were able to add that into the patient's record and display it. Because we have a really powerful way to integrate, they could add that into this menu and actually launch directly into that application if they needed to use it where they are. It's very powerful to be able to go in and continue to take care of that patient, regardless of what types of additional information that you may need to add into their records. Adding into what Dave had talked about and what Jeff has shared with you, when it comes to the enterprise side of things, we need to be able to really address all the different ways and things that people want to see, and then be able to narrow those down if it's not something that's important to what they do. So based on my user access rights, when this patient left us after surgery, you can see they came back in, chest pain. They had their EKG, and this is a really sticky subject. Some people don't want 15 EKGs listed in a patient's record, but your cardiologists, your nurses, they need to say it, to see it. So based on the way we can segment that archive, we have the way now to be able to go in and say, these people are presented with it, other people who don't need to see it, it can be in the background. And then for those who do need to see it, now I have that EKG here, but I have the chest X-ray that actually goes along with that diagnosis, so I can look and see what's going on in the heart, nice and clear. But with a lot of cases, what we see when we've gone through that heart, we find out it's really not anything going on with the heart, but instead, it might be instead that they've got something actually going on with the GI system. Quite common for that to be misleading when they come into the ER. So you can see here now we've added additional information from the endoscope, endoscopic views, making it a true enterprise view. Then we can have those same things that go next to that CT scan that they may need it, they may have needed. So it can continue to build on the patient's progression in the entire enterprise, the different departments that may be necessary to care for this patient. So we're going to take it into the last two things of this patient's record. Two of the last places they, they came to visit us was they were having some pain, maybe in that wrist. So what you'll see here is typically, lots of places will make the doctors go back and forth. Well, this, turning it into something that's visual is easy for the radiologist, but not necessarily always very clear for someone outside of radiology. So we want to make sure that they have tools at their fingertips that are going to allow them to use it, again, more effectively, to actually see things that they need to see to take care of the patient. And what you'll see here is advanced information that would allow me to say, you know what? No matter where I am, I need to be able to quickly drop that in to a volumetric. I need to be able to see all three of the planes nice and clear, to maybe look at what's going on in this hardware. But even more so, now I have this overall picture that we were talking about, being able to take those slices and images and quickly look at that hardware nice and easy. So this allows us to see there's really not anything going on with the hardware itself, but you can see maybe what actually was occurring is pain. Pain that was actually coming up from a rash in this patient. So here's the dermatology that now gets added into that patient's record, making all of the clinical decisions more clear and more effective. So when we see this, it makes our enterprise discussions very broad. We like to take everyone into a lot of have you thought of? Because our product offers a lot of abilities to go in and say, have you really thought of every department in your environment? So maybe instead it is the sleep study. A lot of times we find these are hidden in office buildings, not necessarily mixed in with that chest X-ray, but because it goes so much along with what they would need to see in a heart that's potentially a lot enlarging from sleep apnea. Wouldn't it be great to put it into that patient's record? And we can also, from what we've talked about before, look at some of the different divisions. So a lot of times on some of the more complex workflows, places are gonna have things like a dental that goes into the surgery. But we don't wanna just be able to see these. We've actually started adding functionality in to be able to support it as well. So your dentist might want to come in and be able to say, we can not only just support the display of the images and the way they might like to see it, but we can actually measure that root for them and actually save that into the patient's record itself. And you'd be surprised, a lot of dental units out there who need to do 3D. Take that CT scan that they're doing of the jaw to be able to see what's going on in that patient's record, and I mean, on that patient's jawline, what's going on with that tooth and segment those out. We have the capability to support that. The last set of images I'll pull for you on the enterprise discussion might be something like your ophthalmology review. On this type of a study, it's really great because when you go in and you start looking, we can see here that as we're looking at all these different types of images, so you can see how we can add the motion to them. But we also, again, don't just think about displaying them. We want to start adding in common features that allow us to navigate them more effectively. So for example, here you can see a red free filter that allows you to see the retina nice and clear. I'm going to take us now from just the enterprise view and quickly go into some of the other workflows on this modular solution. So let me log in, and let us go in and talk through some of the workflows maybe that have been positioned. It's really amazing to be part of this platform where you can go in and start diving into what are the pain points in a facility? How can we help augment or change those pain points? So I have some really great examples for you, that are built into the platform and different ways that customers have actually added us into what they're doing. So I'm logged in as an administrator, and I like to be able to talk through a lot of these, so I keep them at my fingertips. Some of the things that you're going to note, we've got customers who have already paid for a PACS solution, for example, but they don't have a really good downtime scenario. They need to be able to see things like what's going on in the stroke unit. A lot of people do not think about breast imaging, mammography, when their systems go down. People are reading 100-200 studies a day, and there might be four or five or 10 readers. How far behind are you going to get if you miss eight hours? We want to be able, of course, address ED stat reads. So we do have people today who are using us for that type of workflow. As well, you have very image intensifier and image-intensive users. Dave mentioned orthopedics is one that is very common. They can go in through the EMRs, and they can build some small lists, but most of the time, that's not quite as effective as they would like it to be. So instead, I could, by group or by user, go in and to build out some workflows that are going to allow them to see the studies that have been done, maybe that are coming through today, including maybe the reports that have been generated by the radiologist. I could also see what were the last seven days of the inpatients that are here, or who's coming in with things that I've ordered for today that I need to be able to make sure that I'm ready for. So it gives them some high-powered workflow as well, with all of the automated features that a radiologist would typically look at. Because I don't know about in Australia, but I know my orthopedic surgeon friend here, he sees a minimum of 110 patients in a day. That's a lot of patients to look at, and almost every one of them is going to have images. The last couple of things we can talk through, quick touch QC, like Dave was talking about, being able to go in and address the different workflows to fix the different types of studies and then into the radiologist reading. So for me, when we look at the flexibility of what we can provide, what we can provide on these worklists, you have a lot of opportunity to talk to different scenarios on our platform. When we look at this, I'm going to go through some really quick images just to kind of show you how we tie together that exact same viewing environment. But because of the automation, we're going to launch a lot of additional functionality. So you're going to see here, I'm going to just do something very basic and easy. Something like chest X-rays mixed with, maybe some very high-powered volumetric review that's necessary for trauma. And then we may go in and quickly say, you know what? There is a lot going on in mammography environment, especially with the attrition of the readers. This is a very specialized, high-demand area that a lot of people have been really honed in on one or two specific vendors who support it, but we want to give them some flexibility outside of radiology. So we're going to talk about how some of this works. We're going to load these in, and what you're going to see normally in this environment, you're going to see that I would have multiple monitors set up. So you're going to see, you're going to see a couple of flashes on your screen, and this is going to launch you to the second and third monitor. This is usually where the radiologist would be living, but I'm going to shrink it down for just a quick few seconds. This is the information that we're sharing with them. The piece of paper from a long time ago, handing them. This is the orders. This is that full patient history down here. This is the queue that we just built out that we're going to read and any information that might be shared, whether that's coming from the technologist or other people that might need to be able to have that functionality available. Then we're going to take you back to the images. We're going to say how quick and easy that we can look at these. Here's my current and my prior, and I want to go from my single view to my second view. So that's considered an anterior posterior to a quick lateral view. And then what you're going to see down here, I'm going to open this up so you can kind of see what those images look like. But as we do this, I want to go next, next, next. How many priors do I want to compare to see what has gone on as this patient has come from having a port prior, he did not. So now I can go back in and nice, quick, and easy, verify what's going on with this. Now, my radiologist may keep this open, and they may place it in different locations, so they may want it at the top of the screen, more accustomed to where some of the other vendors may place it, where they trained, or you may see it at the side of the screen. But we want to make sure that they're comfortable, and we support where they need to see that information. As well, we want to make sure, again, those tools are nice, fast, and easy. So I'm quickly going to go in and do some things with my hot keys to go in, shortcut keys to go in and make the quick ratio measurements that they would typically make. Now I can move on and diagnose, or if I got interrupted, I can quickly come over here and go, "Yes, I know. We've got this, trauma case up that's ready to go." I'm now taking that telephone call, so I'm going to quickly go through and I'm going to look. You guys can see they only sent me one image. I can't turn things around, but I see there's other stuff going on up here. Can I quickly, even in a lower bandwidth area, open this up? This has got a lot of pathology to it. It's over 900 images, and look how fast we were able to load that up and move it around and see the displacement going on in the, in the pelvis here that was so hard to see on the other images. Nice, fast, and easy review of something like that. Even more so, as I'm in here, I explained I got interrupted. So who am I on the phone with that might need to actually take a look at these? So I'm going to go ahead and share my screen. Nice, fast, and easy. As we begin to look at this, I'm going to have Jeff join me very quickly so that he can see the displacement that I was looking at. And you can see Jeff's cursor. He is live. He is now rolling those images. My hands are away from my, from my keyboard, but that's going to allow us to truly go. Now, if I hit the keyboard and I go, "You know what? How about here? Do you think we need to place screws there?" Jeff might come in and go, "You know what? I think we actually need to do some stabilization here. You can see how fast and easy it is for us to actually have true collaborative, not, well, it's image 222, and I think if you look at that, we need to move. You can see that true collaboration in effect. We have seen this in great distributions. For example, a veterinarian world, where we were able to see 17, 18 students remotely joining in to learn about how to diagnose animals. Very flexible. I'm going to take us back very quickly. We can go even bigger into this on the volumetric side. We provide a lot of different functionality, being able to see this in two different planes or to place it into what we call a MIP, Maximum Intensity Projection, that really highlights the vasculature in the lungs. We have all of those capabilities built in for quick, fast, and easy review. I'm going to take us now instead, though, into mammography, because we haven't really touched on what we can do in that environment. Many people have been really associated to one or two vendors here, and the thing is, even remote, these are... Sorry, these are about 18 images. They are true tomo images. For anyone in the audience who knows, these are quite large datasets. You can see how fast and easy it was. We can immediately display everything. We have one, two, three, four, five, six, seven, eight, nine, 10, 11, 12, just in the current. It's nice, fast, and easy for us to see that we have all of those 12 images immediately displayed. And then we're going to provide them some really fast workflow with some amazing hanging protocol functionality that now goes across the board for everybody. But it was really generated by those who need to read mammography because of the requirements to see the different views. So you can see here as I go through and I look at any of these images, these are requirements for how we look at the datasets, but there are some things in here that are quite unique to us. The ability to say, and we could hotkey this to make it really fast and place it on any kind of peripheral device. But if I see something and I go, "You know what? I want to mark this for the surgeon."... I don't have to type in a separate or mark it and then measure it and then type something in. We have functionality that is built in to meet that specific need. Nice, easy ways for us to see, again, prior. In this, they don't, if they read multimodality and mammo, they don't have to learn different tool sets because it's all the same viewing tools. So I can come in now and basically go next, prior, next, prior, next, prior, on all my mammo images. Nice, fast and easy. Oops, I passed one. Let's go back to here. These are tomosynthesis images. Being able to stack those images and go through them quick and easy. As well, at any point, we can go back and forth. These are things that other vendors struggle with, but we can do that effectively to keep the mammographer constantly in the same pattern. We can do this because we can do this where they are in that same effective pattern, whether they are screenings, whether they are diagnostics, whether it's 2D, 2D CAD markers or 3D CAD markers, we can support all of that workflow. And that doesn't just have to be within the facility walls. It is cost-effective for us to be able to roll that out outside to support reading remotely. So some of the facilities who can't get mammography readers can get support through our platform. Any additional types of datasets that we want to be able to open and share might be things like, we might be looking at AI. We can generate and put that into the workflow. We can segregate that out. So all of those are things that we're able to go in and address for the customers, and we can do it very modularly based on where they are in their IT solution strategy. Mike, I think from here I'm going to hand it back to you. Thanks, Kristi. Appreciate that. So hopefully this is the first time we've really spent time showing our products to the investment community. Hopefully, we showed you the appropriate amount of detail, trying to give you a flavor for our two most popular products and to start to visualize what we talk about when we're speaking about workflow. So I think with that, we'll open it up to questions in the room first, and then we'll move on to questions that we may have remotely. We will have a microphone that's brought around for questions, simply because those that are on the Zoom will be able to hear those questions better with the microphone. So if anyone has any questions, feel free to raise your hand, and we'll... Jules Cooper from Shaw and Partners. Thanks for that presentation, guys. I really appreciate the, you know, the look in terms of, in terms of the products. Just on the data normalization, secret source, David, that you sort of mentioned there. I guess being an independent VNA probably helps, you know, in terms of being able to deliver those benefits to the customer. Could you maybe just elaborate a little bit around how, you know, Mach7 would be executing that data normalization versus other independent VNAs? Yeah. And then also, if you are sort of utilizing technology from a vendor, right, you know, thinking being tied to a particular piece of hardware, just how they, they navigate, you know, some of that data normalization from, you know, sort of a vendor-specific solution. Yeah, happy to. You know, it's interesting. I've been in imaging my entire career, worked at numerous vendors. Every vendor I've ever worked at has claimed to have a vendor-neutral archive, which is very misleading. The main difference is most vendors, vendor-neutral archive that they refer to is really just a DICOM repository. The only thing they're doing for their customers is collecting all the data and storing it in a common location. Even if they can do some of the things that we said today, such as data normalization, DICOM routing, lifecycle management, typically the only way their customers can get that type of thing done is to call the vendor, place a service call, and when the vendor gets around to it, they'll write those rules that you saw Jeff doing, et cetera. Our moniker at Mach7 is we want to put our customers in charge of their own data. So it's anything that I can do to the solution at Mach7, through my services team, we provide the customer themselves the training and the flexibility and the access to do all of that activity themselves. And so it makes it very fast and efficient, and that's why customers buy us for their VNA. This one might be for Mike. So earlier on, you were talking about acquisitions, and obviously, eUnity was a very important one. How would you kind of think about now that you've got the front end and the back end? I mean, where are the kind of gaps where there is potential to have an impactful acquisition? ... Yeah, sure. You know, we're, we're always evaluating that, and that, that answer is, but I think as I look at the market right now, it's really around more workflow orchestration, it's around optimizations, it's around, the ability to provide good analytics, good, good, data science capabilities with all this data. As we start to gather that, I think that over time, there's gonna be a lot of different uses there. And, you know, so I, I would say it's, you know, it's analytics, it's workflow orchestration, it's those type of capabilities. If, if there is one, I wouldn't say that we've got a gap in our, technology stack right now. I think we're, we're where we wanna be from a back end and a front end perspective across the enterprise. I think that we don't want to create a Frankenstein approach, and I think it's really difficult to try to buy specific pieces of technology. If you're trying to buy an advanced visualization tool and add it to a viewer, that becomes quite difficult, and you don't want your product to sort of have that stitched together feel. So I think some of that stuff is better to build organically. But things around analytics and optimization or workflow, I think are opportunities. Sorry. So just going back to the VNA, I just wanted to ask a question in regards to rolling out the V12, and obviously you mentioned there are some issues, and just wondering, you know, the feedback from customers that use the VNA, and if there's anything missing there, and if there's, you know, that V12 is gonna sort of solve some of those issues, or what's the plan there? So the main reason we rolled out V12 to replace some of the legacy Microsoft products included in it. So the initial customer that took the first version of V12 went extremely well, really no issues whatsoever. And we continue to monitor that. I'm not aware of any problems we've had. Yeah, no, the big thing for people wanting to take V12 beyond the new functionality that we've built in is the fact that we've replaced the Silverlight technology. Silverlight was a part of Internet Explorer that has had some security gaps in the past. It's end of life, so you had to create a whole new GUI to accommodate for that. So that's really- Well, it's really also, It's being on the same path with the IT organizations in regards to doing something like that, right? If they're still on Explorer, and if they're still using Silverlight and other applications, it may not be quite as important to them as for others, so it's just a priority for our customers. One other one, just around... You also spoke, Mike, at the beginning, around the more complexity in an enterprise, the better it is for you guys. I mean, there's a lot of M&A happening in the U.S. healthcare space and around the place. What's your view? I mean, do you think M&A makes for a simpler enterprise or a more complex one? And, I mean, how do you think that kind of breaks down? Are you getting, yeah, more customers or less, and your thoughts, yeah. Yeah. Good, good, good question. And different answers, depending on acute care or ambulatory care. On the acute care space, it can work to our advantage. On the other hand, if a hospital group is using someone else's technology, you know, there's risk associated to that, right? Where depending on which vendor they have a preference towards. I would say in the world of M&A, it does seem like, you know, it doesn't really matter if you're the buyer or the seller right now. That just because you're the buyer, doesn't mean you're gonna keep the technology you have. You may be doing a buy because you like the technology that the seller has, right? So there's no guarantees there. On the ambulatory side, it's typically making a more and more complex situation, more and more complex, and that usually works to our advantage. Thanks. Thanks. This is Wei from Jefferies. Just a question on the KLAS ratings, which we brought up before. So I'd be keen to understand, you know, how important these are when we go marketing and Mm-hmm. You know, how much it comes up in conversations and helps us win contracts. Also, just in regards to the different types of, I guess, categories that they have for KLAS. You know, we're ranked very well on the universal viewer side, but is the vendor-neutral archive your only kind of target going forward? I don't really understand how these things work, just like in terms of PACS or like above and three, you know, the large PACS viewers and lower PACS viewers, is that an area that we could be targeting too? Thanks. Sure. So KLAS is a little complicated, without a doubt. So we, we are ranked with KLAS in the two sectors, right? The, the universal viewer, which, you know, I think KLAS might be redefining the definition of, of a universal viewer actually soon. Because what, what exactly is that? You'll find that they have a new category in there. I can't remember what the acronym is, but essentially, it's a, this is part of an ecosystem. You can't buy the product independently. So they're starting to label products like that in KLAS, so you can know this could be ranked high, but you can't buy it without buying the PACS solution. So KLAS is starting to get a little smarter about that. You know, for us, you know, the two segments, are, are important. It's just the, the... What would be missing for us to classify ourselves as a PACS solution is the simple fact that we will sell either of our components independently. Any of the people that are listed as a PACS provider will not sell their components individually. It is a combined ecosystem that they are selling as a PACS solution. You'll find other vendors that are not included in PACS, right? That you would traditionally think could be, and that's generally because they don't have a complete back end. They may have large caches, but they're dependent on other back ends. So, so not everybody's listed in the PACS sections. Most PACS companies are broken down between what size customer that they'll sign. Most PACS companies are not gonna do an academic center and an imaging center. Most are gonna do one or the other, right? But, you know, from a VNA perspective, I'm starting to see more acronyms there from KLAS too with the fact that here's the VNA, but it's not, it's not independently purchasable, right? The VNA section, you'll notice, is starting to become very bifurcated in the sense that a whole chunk of us right now are in unlimited data. It's not just us. There's a number of VNA customers, because it's a back-end product, right? So you're talking about IT resources, and they've got to respond to surveys, and some will, some won't. It's just, it's getting their attention to do it for all of us, not just us, that, that become the difficult part of managing KLAS. In regards to how important is it? Look, it's important to us from a marketing perspective, just, you know, because I do think that, clients look at that to decide who they want to invite to an RFP process, as an example. Is it the end all be all, though? It's not, right. It's one data point, one data point among many. But it, but, you know, it's, it's an objective data point that you can point towards, right? Jules here from Shaw and Partners again. Just, I've got two, maybe one for Kristi. Thanks for that fly-through on the viewer. Helpful. I'd just be interested to understand, lots of functionality and sort of integration capability that you demonstrated there, particularly on the enterprise side. How much of that, you know, functionality or IT resides in the viewer itself versus being powered potentially by the VNA? Is the experience, if you were sort of using the viewer separately to, you know, Mach7's VNA, for example, would it be widely different? That's the first question. The second question is just on that DICOM routing. David, I wondered if you might be able to... You know, you talked about sort of the secret sauce in the data normalization, but is there some secret sauce potentially of benefit to the independent VNA around the DICOM routing side as we sort of move further into the AI space? Kristi, you can go first. Are we able to unmute her? Hi. Oh, there we go. Can you hear me? Yep. Yep, we got you. So as far as the functionality goes for the volumetrics, those are part of our platform for the enterprise as well as for if we're launching it from the VNA. The VNA is just gonna add in some relevancy rules, so some things that allow us to see currents and priors and some workflow in that direction. So as far as the viewing environment goes, you get the standard tools across the board. I think the other thing that I could add in, as far as adding in additional applications, so you just have to have the viewing environment to be able to do that. But we can also do that through the VNA. So it's very modular on how we're able to position that, whether they're using just the enterprise or they're going to go ahead and go with the VNA and the enterprise viewer. I hope that answered the question. Thank you, Kristi. Thank you. And then, then in regards to DICOM routing, it's really the same story as data normalization. Typically with our competitors, especially PACS vendors, through PACS vendors, their customers have to tend to buy third-party DICOM routing solutions that they integrate to. And so there are DICOM routing solutions in the market that you can buy to make PACS better. Very few vendors in the market have all of those tools embedded in their solution like Mach7 does. When I say very few, less than four vendors. Mike, just a question on the switch between kind of like the capital model and the subscription model. Is there any, I guess, ties for the different models on a geographical basis? And does that speak anything towards, you know, a shift in terms of geographical weighting? Or is it more so that, you know, across different geographies, we're really just trying to switch over to the subscription model? Yeah, yeah, good point, actually. For sure, the U.S., I think, as an industry, is heading further and further towards subscription. But outside of the U.S., particularly in the APAC environment, it's heavily capital-oriented. Not only that, but it's heavily capital perpetual license-oriented in the APAC and Middle East, which is entirely different than what you see in the U.S. and in other OUS markets. And I'll just ask two other quick ones. Just in terms of our systems and from a technical perspective, are you able to speak a bit on the latency and bandwidth requirements that we expect? So that's one. And the other one is just asking on the unit economics, when we're talking about, you know, having the resellers or the wraparounds, how that works. Thanks. Yeah. You know, from a bandwidth perspective, you know, we're a low bandwidth system, right? We don't have specific network requirements that we're providing to our customers. I mean, the fact of the matter is, you know, any customer that's got a modern network architecture, our system is going to work fine. Modern wide area network connections are fine, but we don't build our solution with the need to have complicated architecture, either from a network perspective or from an infrastructure perspective. You know, as Dave alluded to, from an infrastructure perspective, we're agnostic. We don't care what vendor people use from a hardware perspective, nor do we care if it's an on-prem or a private cloud or a public cloud. We have S3 storage. We don't care. We're completely agnostic to that. We don't get involved in that. We are a software-only provider. We provide zero hardware. Zero hardware. We are nothing more than services and software. Okay. Yeah, yep, sorry. So typically our resellers of our product, we're providing them pricing, right? They're buying from us, and they're generally buying maybe a slight discount. However they want to resell that product and whatever percentage uplift they want to put on that product, that's on them. That's not part of it to us. When we don't do revenue sharing models or things like that, we're selling the licenses to the reseller. The reseller is uplifting that and selling that. This is one more around early on, maybe for Dyan or Mike. You were talking about FY 2024 and what you've kind of sold in the last year. Sorry, FY 2023. You were talking about cross-sell opportunities. I mean, how much of your current customer base would you say are using other vendors? Then, I guess, just to get a sense for the opportunity for the cross-sell across you. Well, I would say almost all of our customers are using somebody else's technology. Whether it's a radiology PACS solution, cardiology PACS solution, enterprise viewers, VNAs, like, there's multiple different variations there. You know, largely we integrate with other radiology PACS solutions. I think that has become something that's relatively new for us over the last couple of years, where we're starting to provide more of the radiology PACS solution. Again, we're kind of born out of the enterprise. Yeah. So because of that, we typically, any of our older clients would have already had a radiology solution in place. Mm-hmm. Right? And then, you know, they, they're evolving off of them from time to time. But, but I... And I would also say that it's, it's more frequent that we would find a VNA client that would have an opportunity to sell them the viewer- Yeah. -than it would be the viewer to have the opportunity to sell them the VNA. It's a little bit more predominant from VNA to viewer. You kind of see the opportunity being, particularly for your VNA clients, to become more of their one-stop-shop, appreciating that it's never a one? Yeah. Yeah. Yeah, I see that. I see that as a higher likelihood, yeah. Then the other way. Yeah. Yeah. Just with what you mentioned there, Mike, in regards to the fact that you've probably become more radiology PACS rather than that enterprise viewer. Clearly, the viewer has maybe done better with radiologists than you might have presumed earlier on. I just wondered how that then changes, and maybe even Kristi or Dave, you can speak to this as well, you know, I guess the sales strategy and then thinking about whether you have the, you know, enough of the right people. Jef and Kristi are clearly very experienced in, you know, the product knowledge and can run through it really well. I assume that radiologists are gonna want sort of that really technical side of the product. You know, is that something that's been developed over the last...? Look at it like this: You know, we still... Our primary market is still around the value from an enterprise perspective, okay? So that's still where the bulk of our clients are coming from. Radiology, we look at radiology like it's a use case, and so which of our clients have a use case for radiology? So when we're selling the solution, even if it's our complete stack, we're selling a solution. We're going into the hospital, and we're asking them: What are your use cases? What do you need this for? And if radiology is one of those use cases, then we will sell on that use case. We have the people already to do it, and the buyer is gonna be a little bit different, right? The buyer that's looking at us for that radiology use case is not looking at us because that's their only use case. They're looking at us because they have 10 use cases, right? If what the hospital is doing is really looking for a purpose-built, single department, radiology PACS solution, and the radiologist is the buyer, we might pass on that deal. We might not, but we might, depending on whether or not we think there's a good or a high likelihood of winning it. Because that's useful, but it's not as useful as having a whole enterprise, you know, concept. So it's not necessarily the focus. You know, if I had to be faced with whether I want to build an advanced visualization tool for radiologists, or whether I wanted to build an advanced visualization tool that everybody else could use, it's everybody else that I'm most concerned about... Although we still know that we have to have those tools for the radiologists. We want to provide the right tool set for the radiologists. It's just a, it's an economics thing, right? Where the CIO is looking at us because they're looking to buy a solution across the enterprise, right? And solve multiple problems with one acquisition rather than just that radiology part. We've got the right people for it. We've got the right focus from an R&D perspective. I don't think we need to do anything different from it, from it. I don't think it's something that we're necessarily trying to market towards. I think we're still sticking to our story, and we're still sticking to our market. It just so happens that as we pick up traction, more and more people are interested in that radiology use case. Hi, I've got a question for Jeff, if I could, please. It's just going back to that part where you described the creation of rules to support the workflow. It said there's an endless level of customization there. My question was, is that done largely by the customer, you know, by them, or is that something that your team does as a service? And then a follow-up, I can imagine that you'll find through that process, some routines that might be generally useful. And I wondered about your ability then to make that available to other customers, please. Thanks. Yeah, both are, both are true. So typically, what we'll do during an implementation, we have a full library of different tools, workflow plugin adapters, so to speak, that have been created over time. Many of those are common across from one customer to the next. So we might implement those as a training process when we're doing the implementation. But the goal is to make the customer, the IT department, self-sufficient. So we may train them in the beginning, but the goal is for them to be able to have the tools and be able to do future customizations, new rules, modifying the rules, et cetera, completely on their own. We're always there to help them, but we want to first and foremost, teach them how to do it and be there to support them, as needed based on how they'd like to engage with us. Yeah, I'll add to that. I feel like we're seeing our clients have smaller and smaller IT teams. When that happens, they tend to reach out to their vendors for help on everything. I think it's really important that our customers are self-sufficient, just as Jeff says, that's what we're shooting for, right? I don't want to have to build out a support staff of 100 people to support customers, right? Self-sufficiency is number one. If they absolutely need to, we have Professional Services that can be purchased. Yeah, Jules from Shaw and Partners again. Mike, just picking up on that concept of, you know, value from, from an enterprise perspective, and that being the focus of the business. We've seen, you know, Mach7 increasingly successful in the teleradiology space. Does that mean that when you look at some of those recent wins, that, those customers are seeing sort of value beyond just the, the radiology use case there in, in, in those wins? Or, or is it, you know, that not an example, I suppose, of what you were talking about there, about the broader enterprise view? Yeah, teleradiology is a great example of an economics gain, right? You run a teleradiology company. Teleradiology companies have small margin, and they're always looking for ways to try to maximize that margin. They're also not reading the most complex exams all of the time, where they're a little different than a research facility. They're trying to chug through a lot of studies. They want to be efficient, they want a cost-effective solution, and oftentimes it's coming out of their pocket, right? That's not a corporation that's buying a billion-dollar system, right? It's the radiologists. These are the owners, and they want a solution that will work for them. Maybe it doesn't give them all of the bells and whistles that they want, but allows them to get their jobs done efficiently, effectively, and in a cost advantageous way for them. That's why, you know, I think we start to see more ambulatory business. Hi, Anthony from Shaw and Partners. In the KLAS PDF, there was a stat there that you were number one as of the fourth of August. twoas that changed since then, or is that just you can only see live data on certain dates? You see live data all the time. I think it actually updates on a monthly basis, based off of when they put their most recent findings in. It's, you know... It's a hard thing. Watching your class rankings is like watching your stock portfolio every day, right? It goes up, and it goes down. It's nerve-wracking, and you don't really necessarily know the whys. So watching live data can be very tough. But, I'm not sure where we stand right now, actually, on the live data. I've sort of tried to take a break from looking at all the live data because it drives me crazy. We'll probably be looking at it again just before RSNA, so we know where we stand. I can tell you for the last two years, in the live data, we ranked number one for universal viewer, right up until January, when they did best in class, and they put last-minute things in, and two years in a row, we ended up taking a number two slot. I don't know. It is what it is. I think I could share one additional thing. We just recently, within, in fact, the last two weeks, I did an aggressive email campaign to all of our customers, from our account management team, to really make sure that they're aware of the importance of those surveys, and that they're helping us respond to those in a timely manner. Because it's like anything else, what we found is when a customer is happy, they're less likely to respond to a survey, just like all of us in our everyday lives. So we're really putting a lot of focus on that leading up to RSNA, and I'm confident we're gonna have some good results from that. Françoise, do we have a lot of questions online? Yeah, we've got some questions online, so we'll start off with a couple from Scott Power at Morgans. Hi, Mike. You mentioned that the older legacy providers are losing market share. Is there a sign that they are looking to improve their offerings? From a legacy perspective, they generally don't move too fast. You know, I would say, in a way, Philips is an example of a competitor that has tried to adjust to the market and to losing market share. They did that through acquisition with Carestream. I can't speak to whether or not that helped them or not, but I think that was their, that was their goal, so certainly they're making an investment to do that. Other vendors have their own take on how they're going to try to adjust and move into the new world. At the end of the day, though, many of these programs were built 20 years ago, and they've made incremental changes, but it is built off of older technology. To fundamentally change your core software offering is a huge undertaking for a vendor. Are they trying to do it? You know, I'm not sure. Are we seeing evidence of it in the marketplace? We're seeing evidence that they're still losing market share. I can only base that off of what we see, not based off of what we think that they're trying to do. Thanks, Mike. Our second question from Scott Power: How price sensitive are you finding your customers? Is it becoming more about solving a solution? And if you can solve that solution, the customer is happy to pay. I guess I'll answer, but you might have a different take than me. Dave's dealing with us on an every day basis. I think customers are price sensitive. I think there's some that aren't. I think that there's... But I think overall, the market is shifting to... And I've listened to a lot of hospitals speak at conferences recently, where they're really trying to figure out how to stretch their IT dollars. And honestly, it's not investing in imaging all the time. They've got other fundamental solutions that they need to solve. So they know that they need a good quality imaging solution. They know that they're gonna have to pay for it, but whether or not they can continue to afford to pay a premium or whether or not it's becoming more and more price sensitive, I think everyone at some point is price sensitive. I don't know what you're saying. I would address it a little differently. You know, first and foremost, we are a solution sales team, so we embark on the journey with the customer to sell the solution. We are trying to find ways that our solution not only solves their problems, but also eliminates costs that they have. So we're, you know, very efficient and I think aggressive at proving that the price that they would pay Mach7 would result in significant savings in other areas of their spend. You know, specifically, one area I talked about early today is the consolidation of data. You know, right now, a lot of hospitals have multiple silos of imaging data that they have to pay to maintain, support. We're able to eliminate that entire infrastructure, if they move to our vendor neutral archive. We have a question from John Peterson: Thank you for the excellent update and product demo. There was some concern when Mach7 announced our Q4 results due to a timing issue with receipts. While we appreciate your Q1 results will be announced later this month, can you confirm your FY 2024 guidance of 20% sales order growth and 15%-25% revenue growth remains? Nothing has changed from our guidance. We maintain our guidance that we provided to the market. Thank you, Mike. Now we have a question from Dominic Pham: Great presentations provided. A question if Mach7 has integrated the universal viewer with various EMR vendors, as globally Epic, Cerner, Meditech, Allscripts, which have the dominant market share, and there are potentially many more vendors, and these require bespoke development efforts for Mach7. Yes. All the, all the ones mentioned, we have active integrations with. It's very common. So many, many customers of each of those. I'd take it a step further and say Allscripts is a partner. Yeah. Allscripts actually can resell eUnity as well, and has resold it to some of their customers. That's all the questions we have online. We can hand back to the floor for final questions. One more? Just back to the contract win. So the Veterans Health, we've won the phase one. Just in terms of the phase two and the description of that before, is that more of a slow burn rather than something where there could be a kind of like large contract win? Yeah. It's very difficult for us to know. It could be. We could get a phone call in the next month to have some facilities begin a phase two approach. We could wait until after phase one is complete in June of 2024. It's difficult for us to know right now. It's because it's based off of really when these hospitals are going to sort of have to renew on their existing agreements. Since we don't have insight right now to the install base and when they're going to be renewing with their existing clients, it's hard for us to know. What I will say, that what we're focused on right now in regards to phase two, is educating all of these VA facilities on the fact that they have a new contractual vehicle that they can work with as they start to look at renewals. So really, it's an educational component for us to start with right now. We'll go from there. All right. Well, look, I'll just thank everyone for attending. I know this was a long meeting for everyone. I appreciate the attention for all of you that showed up in person. To all of you that attended via Zoom, thank you so very much. Hopefully, we were able to to give you some additional information about Mach7, and I look forward to being able to speak to you all again soon. Thank you, all. Thanks, Jeff and Kristi. Thanks. See you. Thank you. It's nice to meet everyone.