Pete McCabe

But at the end of the day, you want to see Bob Smith's pharmacy data married up with his clinical data, married up with his genomics data, and married up with his diagnostic testing data.

What you're able to do is take this tokenization data and implant a linkable token that says Bob Smith at CVS Pharmacy is the same Bob Smith at Emory Healthcare System is the same at 23andMe.

Of course, none of this is Bob Smith.

It's hashtag 123 at CBS, it's hashtag 567 at 23andMe, and it's hashtag 91011 at Emory.

But there's a Rosetta Stone or technology that's able to say 123, 456, 8910 are the same.

And now you start to be able to create real flow.

And then there's another workflow, if you will, on identifiable data, which arguably is the most valuable.

If Pete McCabe is walking into a hospital, I like to see Pete McCabe's data, not hashtag 123's data.

But identifiable data needs to start with authorization.

And we need sophisticated processes and software to make sure that we are never putting data into the health data ecosystem without consent.

And we have different software processes to support that.

Yeah, so one of it is in the U.S.

healthcare system, covered entities have what's called TPO or treatment payment and operations authorization for the data.

So think a health plan has TPO rights to the patient's data that they serve because that will help them drive value-based care.

So in that case, you're able to get $10 million

record requests at a time from a payer.

Similarly, a life insurance company will get authorization through me when they're working on their policy.

The government will have TPO.

We move a lot of data for the Social Security Administration.

So there are mechanisms, TPO being the biggest one.