But as you say, it's incredible how until recently user interfaces were just like, you kind of had to have a degree in mastering the user interface, didn't you? And as you're going into health districts, et cetera, and just socially, how do you deal with the fact that some people might say, oh, well, Harrison's coming in to remove jobs? Because I suspect that might be something some people think about.

Yeah, certainly this, like, I get the question from my colleagues a lot.

I would probably say to them that Harrison will enable more scans to be done.

And as a result, will probably actually increase the demand for radiologists.

Sort of similar to, perhaps the phrase has been used a lot, but Giron's paradox probably comes to mind.

Radiology is not by itself an end product.

It's not like coke, where there is a certain amount of coke that can be drunk every day by the 8 billion people on the planet, and that's the maximum amount of coke you ever need to produce.

Aside from the range of scanning products that you sell to hospitals and doctors and clinics, how do you use AI internally at Harrison for workflows? Is it as embedded as one might imagine, given how AI-ish your product is? Yeah.