Okay, Kevin, I think we can get started.
Okay, go ahead. So you want to start.
Yes.
Okay, hi, everyone welcome to this October edition of emission community webinar imaging Informatics.
And today, it's my great pleasure to have our presenters. Dr.
A spiritual Stein and.
To present on key ops com, compliant imaging archive.
Let me share my screen.
For a minute.
My slide.
Just okay, this is a picture from last, which was in person 2019. so, Joel is a project manager at this is Institute for Informatics and actively involved with development of jobs. He.
Graduated biochemistry from the University of Oregon and received his medical degree from me do research and Eva.
Um, cause he's currently professor and chair of medical imaging.
And deputy medical director at trivia, and he's a former head of nuclear medicine and watcher radiology. I didn't receive Geneva.
The universe of Geneva is head of department, local medicine information.
Vice chair report department with the increase of California, Los Angeles.
Well, he has pioneered many innovations in, um.
Pit and cardiac pit, and also many innovations in open source, medical imaging, visualization and processing in the founding member of.
Sorry explanation the president of that foundation and founder and director of the Translational literary Institute in Geneva.
I had the pleasure of meeting husband when I was graduate students were both guys, just in the late eighties and early nineties and it's been great to follow his many successes over over the years.
And it's a pleasure to have us miniature speak today. So, without further ado, I turn it over to August. Please.
I'm sharing now, thank you. And thank you very much for inviting us to share with you. The progress of our project.
It's a pleasure to meet all of you, although we don't see everybody, but we missed the meetings where we can chat and exchange ideas last time.
We had opportunity was like Kevin was showing,
but it's a pleasure to be here with you today and to get your input on some of the development that we we had undertaken as,
you know,
we've been actively putting a efforts in developing open source platform for medical imaging,
and this is our latest,
a baby,
which is a Caleb Santa present for a while some slides and Joe give you a live demonstration,
which is the best thing you can do is show you how it works.
So, let me switch to sharing my screen if I can hear PowerPoint and let me go back to the 1st screen. And can everybody see my screen? Is that okay?
I guess.
Yes, it's fine.
Okay so it's data storage and sharing is basically a platform that we desperately needed to simplify and ease the way we can collect data and
share that we all have facts and research packs and other types of trying to get community to discuss things.
Makes it complicated when we need to share images and collect them in 1 place, copy everything.
So, that took us a while until we finally decided that we will take that problem and create a platform hosting a, those imaging banks that can be shared between multiple institutions.
We want really to facilitate the open access, even for people who are not in the field of it.
So,
they can easily share cohorts of anonymize data between different institution for research,
and for developing new tools like a,
I,
and image analysis we want also to simplify the process of curating the data.
So,
creating subsets would be,
we'll call albums as you will hear from a,
from a will allows this to be easier to do and to create those curation and stratification and collection of data,
according some criteria and harmonizing the number of data that correspond to a certain research project,
we want also to create something like a social network,
sort of a cockpit where everybody can can discuss and share,
and maybe invite somebody to come and look at the images and so forth.
So, it's really in a way of interactive sharing of data as well. So that's the concept.
It started about 2 years ago,
we were able to start the project through different fundings mostly from to foundation that I'm directing the foundation,
which is a translation micro imaging Institute,
which put a quarter of 1M.
Then we had our foundation and long lasting mission to support open source. We put half a 1M. We'll put another half a 1M into the project we benefit from a European funding for about 250000.
we also have a specific local research for 1 of the pieces that I will describe, which is the gateway between clinical and research for and optimization. And we get some funding for that.
So, it started quite awhile ago, was a long process to try to go around different types of implementations and you can see different institution have contributed to the beginning. We had another weird logo.
Now,
our logo is more simplified,
but essentially there's 2 components to this is a cockpit for image navigation,
sharing,
sort of,
the Instagram of free searches and then there's all of yours and we didn't want to link really?
Or lock the viewer into the system. So, basically, you can choose the type of viewers you want, and the system is compatible with all kinds of you are the most common 1 is or if we know that we will show them off later. So essentially.
It's a server platform that allows to interface with clinical or imaging sources and I will explain the gateway carneic is a gateway that allows to anonymize data from clinical
environment to research environment.
Then it goes to the, all the API for different viewers, and essentially, it has everything 1 of the best way of getting API for 3rd party software development. The key thing about this platform is creating albums.
You just create an IBM share that with people, and these albums have some features that are really nice. Joy will show in a minute. So we also chose to have a very high security transfer of data.
We have a token system that will explain why we didn't want to go into the block chain is I was saying, and we're already for blockchain but blockchain is not ready for us.
So, we think we should stay with something more accessible, like a token, and Joel has some ideas of new technologies that are upcoming, like, and other developers as well.
So right now I'd say,
it's a token driven was audit trails and security transfer that can also trigger automatic analysis portals with what we call report provider where images can be sent to a portal having the process to come back with results
through a report on that report format we created,
as I said,
it Porter between clinical this is the most difficult part of getting data as you all know to get them out of clinical environment.
Always requires a lot of efforts with it with the security officers with, with the local regulation and so forth.
So we created a piece of software that every institution can install with basically will identify data according to the local rules.
So you have a template driven system that every institution can decide according to what kind of research,
what kind of data,
what kind of patient consent you will remove,
or rearrange data according to that template and everything goes out in the system completely anonymized and also filtered.
So, that is an important piece to make different institution, adhere to the project and have an automation of the flow of data from the clinical to the research community.
It's essentially a gateway that is Internet who should be inside the institution behind the firewall and will filter the data.
It has a relatively complex pipeline, which allows people a lot of things like, filtering, like, identifying the corresponding data.
If they comply with the was a request, and they can be rejected, who can be sorted by amendment and sorting to see why they were rejected.
And then they would go out to minimize and the identification process before they go out to a diagram storage or a cabs server.
So we do have right now, joy is full time project manager and domain developer. But we have a team behind it. 3 developers as well as equal or do we use 1 of our partner for a long time?
In many projects since there was a project, and he's now a consultant, because he's in charge of the medical it impacts at the university hospital Geneva, and he's attached now 20% to our project as well is particularly developing the current gateway.
As Kevin showed we were at was very exciting to see everybody there. And we had a lot of interesting discussions all the teams and some people are here today and remember that. We had this meeting was very exciting.
And thank you to all his team that organize some and from 2 meetings, which were very, very interesting to all of us.
We also got enough contact with Google cloud. We know Google is trying to really penetrate the market in the US. Not much in Europe.
It's not very well accepted in Europe, but we want it to be combined with the Google cloud architecture and John and his team.
And develop a, the modified version of capsule is functional and was demonstrated at the Google both at as well. So it does work with Google Cloud archive and icon storage.
We have several projects of different kinds going from looking at radiation to, uh, studying algorithms between 17 different sites in Europes. We also have a lot of works on. And what's interesting.
Now, we have more and more international registry.
These are not research product they're basically groups that needs to collect data for a long time to create registry for some rare or unusual diseases.
This is a portal system registry that's being collected between different centers in Europe and we're hosting it on our, our survey.
So we,
we also worked with different groups this is 1 example of integrating directly into an API analysis tool,
sort of an automatic analysis of features and it was done very,
simply,
we didn't even have to help them.
They just installed it cut it running.
And it integrates their analysis together, was the storage and distribution and return the results into what we call a report to the database several institution instances, have adopted camps.
Now, they install their own help server. Some of them are for clinical research.
And some of them are just basically search, and we're trying to get as the recommended platform for why does now national wide a platform for his care networks. Christmas personalize has care network.
So, we're getting quite quite popular around here for centers that don't have an. I. T department and they want to try we recently launched something called camps in a box, which is basically synergy, 40 terabytes storage, which has all the software on it.
caleb's and packs archive.
And you can just plug and play and use it in your institution, sort of a way of facilitating for small research group to have their own cups instance to use it for, for sharing images or storing images.
At this point, I will give the computer to Joe to do a demo and live demo and we'll come back with some proposals for collaboration.
The exit here.
Right, and we have to switch to from PowerPoint. You just open this up now because it's showing.
And what I want to share is.
This whole screen yes, there is a chat to you.
You're sharing your screen. All right. Can everybody see my screen.
We do, and we see now Chrome.
Chrome perfect. So in Chrome here you see.
The key ops interface this is so camped is meant to be a really simple interface with people when we, when you go home and tell her families, what we do, we're making a Dropbox for medical languages. It's kind of the idea.
So, when you log into key Ops, basically you land on an inbox, which has a bunch of com studies, and these are, are your guy come studies? So you can go in.
Look through them, you can click on them. They'll open up in, uh.
Which I imagine a lot of people are familiar with.
If you happen to have a installed.
You can go and click click on a.
And it'll open up in a Cyrus.
I should have picked a slightly small 1, but, you know, open up as soon as it's finished.
Loading it, Ah.
There we go here, it will open up opening up in a.
And where did I put Chrome? So, the end. So this is the data that I've got, I've got.
Some images I want to share, I'd like to share some, some data with with. So I'm going to say I've got this study actually don't want to share everything. I just want to share a handful.
Of of series here, and I'm going to click on send and here I'm going to send it to.
Click send.
And now, when he logs into key Ops, these 3 series will be in his inbox and you'll be able to look at them.
Send them on, et cetera so this works. Well, but we've got lots of situations where we'll have a group of data, a cohort, or some other subset of data that we want to work with.
And also we want to be able to share data with with others. Um.
Within a group, so here we've got, for example.
Album with a whole bunch of data I can if I look at my settings, I can see if this album is shared with a bunch of different users and different users will have different rights. And again we wanted to keep things. Really, really simple.
I didn't want to get a full based full on role, based access control system where you need an engineering degree to figure out what's going on. I decided I wanted to be no more difficult to use than WhatsApp.
So, here, we based the idea, kind of, on WhatsApp, you've got 2 types of users, you've got the administrators, we call the data stewards and you've got everybody else. So, in this particular album, everybody is a data store it, except for court Samir here.
And the rights that he has are limited to these permissions that are sets down here. So a non data steward user can invite other users can add remove studies, add studies removed, but not remove studies.
When they look at the album, and there's lots of situations where we want to share data with somebody, but we don't really want them to keep a copy of the data or share it or send it off further.
We don't we don't have any digital rights management on the system, but.
But as a, as a way to more indicate to users how they're meant to use the data, we've got this show download button.
So, if you don't actually want people to be downloading the data locally, we don't necessarily give them a big download button and whether or not, they can use kiosks to share the data further.
Of course, if they're if they're able to view the data, they can download the data and then they could send it to somebody else. But again, that doesn't mean we need to help them do it.
And then whether or not to they can read comments it.
Comments are feature that we've got on albums here. People can write different comments to each other.
And within this comments area, we also have notifications where you can see what actually happened.
Who who added data who move data around when somebody was added a new user was added to them.
For albums, we can also do the fun things. Here. You've got.
I've got some data and I wanted to show this because it might be interesting for the tca folks. And I think this is something we talked about with Lauren Starbucks last.
Where we've got some external system, we also have another platform called who are they also do this since everything that you've got in the interface? We actually have api's too.
We can actually build external systems that will work. So, for example, if you have a set of data here and we'll, we'll open these will again, we'll pick.
Only, the only the images, we're not going to look at the, it stops.
And say, I just want the subset. I'll click to add to an album and we'll create a new album. We'll call this album the subset.
And well hit create.
Now, now there's a new album that was created that has.
Only this data that I selected earlier and what I can do, if I want to share this with the user, I can hear I'll click on this link.
I'll create to the link I can copy this now. I'll come over here to zoom.
To the Webex squares, whereas with my Webex.
Is there a chat there we go and I'm going to paste this and now any 1 of you can go and click on that link and see this data that I just that just created.
So, this is a link that people will use.
This this link is actually based on these tokens, which is what you might call an API key in another platform. So he'll create.
Create another 1 of these new.
A token, we'll skip this token rewrite access.
I'll hit create I get this token and here for the.
For the geeks on line with us, we'll be able to I'll show you that we can do, for example, to call and look at.
Slash demo dot kiosk stuff, online, slash API, slash link.
The secrets that was given slash study.
Studies and we'll see that this is actually responds as a diagram. My vennpoint.
The fact that this is a document point might be interesting to to the engineers out there, but it's also interesting to other folks.
Because it also means that, for example, I can go to a Cyrus over here.
And say that I'm going to put a new point. So I put demo dot online API. This is.
I named it, so here, I'm not going to put the link in the there's a bunch of different ways to be able to pass this. We're gonna put it in here. See if this is the token the username is actually not used.
And once I put this in as a dot com web note in the Cyrus.
I can go and do a query on the subset.
And then this data will actually start to behaving exactly. As if it was.
As if this specific album was it packs on its own so I can go and.
Oh, double click on it and open it directly open the data directly in the sirens.
This is it's a, it's a 2 way communications so I can also I've got a.
See, what was a I've got some data here and I want to do a send. I can also send it.
Directly up to the album.
Unless if I've got in there, whoops, okay, we'll call it demo effect but.
But I gave it right access. Oh, no, I already I've already uploaded this. So anyways, that's the.
If the data's already known 2 key Ops, which is the case of the specific study, it won't let you upload it because.
Um, for it, we wouldn't want to be to give other people access rights to other images in that series.
Let's go back to Chrome.
So, you've got a tour of the general data general interface. We've got this concept of a report provider that I also wanted to show people.
This is all I'll come over here.
I'll copy the report provided here the provider is a system that allows you to.
To feed out to a completely separate Web site and have that separate website work on your data.
I've recently noticed that fire the smart app launch and fire works works. Exactly the same way. We kind of.
Have both created pretty much the same open ID based API. So here I paste a configuration for my report provider. I'll call it the report.
It's create when I look at the data in here.
When I created this new report provider, I have a new icon that shows up.
When I click on it to report, and this will go and take me to a completely separate website.
And when I go to this website website is able to do whatever it wants with this data can download all the data. But all the data's.
Only within the 1 study, and so the, this extra website will receive a token, which will allow it to queer kiosk. And when it queries kiosk kiosks will act as a Pax that only has the 1 study. The user clicked on.
And when I hear it, for example, I click on post PDF. What I'll do is, I'll download the images create.
A file and post it back to kiosks. So now when I go back into kiosks, I have this new PDF file.
When I click on it, I end up with a for a PDF file where basically just grab the data and put it in. Now, of course, this extra website could be doing much more interesting things. It could be.
We've got a system that's for menu that works like this for European project where they need to have additional data. So you go to an external website, fill out data and it's a.
Sorry, that's pushed back, but you can also have any sort of machine intelligence look at the images and create the report for you.
This is.
See, the this report provider system, not only allows you to, uh, to create these.
To create reports, but also allows you to make these what's effectively a custom viewer. So here we have launched an external viewer.
That way we use the same report provider system. This is.
An open sea dragon based Dotcom, whole slide imaging viewer.
So, here, we've got some dot com whole site imaging data that's here in key in stored in kiosk.
And we can open it with this external website. That's actually not it's its own viewer that we didn't actually built into kiosks itself.
Um, within the settings, we've got web hooks that we've added.
These are when you create a web hook, you can have them triggered when there's a new state. New series is added they just removed or new users appear.
This allows us to create some interesting workflows within the hospitals where.
If you need to have 2 key offices where you need to have 1 album, that's sinked up with another 1. we can create web hooks. That'll copy data over between different instances. For example, we've used that.
And a final feature, we've got allows us to write comments, which is.
Which we've also found to be useful for some projects where here I can say.
Um, this is my comment.
I send this not anybody who has access to this study. We'll be able to see the comment.
I can send a private comment.
I'll send to the husband and say is my.
Comments and will hit send and so this is a comment that only will be able to see on this study.
So, yeah, I think we've got done through, um, pretty much all of what the kiosks does.
And, uh, let me know if you have any questions before we go to the questions, I would like to just summarize some of the things. I have 2 slides actually, not much. Uh, basically what I think we should.
Follow up after this.
This webinar is we think we have an opportunity here to link chaos to some of the ongoing project both side the cancer imaging archive and the new CGI
project because it's relatively simple to just add this.
I would call it a cockpit or a or a portal to existing databases and have groups and users and research communities,
create their own subset of data that they can share through caleb's and add those analysis tool.
So this is something I wanted to launch as a discussion for today.
This is where the idea we discussed was showing, they said, well, what's the opportunity for us to maybe have or help you integrate into some of the existing initiatives and projects.
Hi, this alarm Starbucks. Hello, John you got that page.
Anyway, going, uh, we have a project called PRISM.
Which is looking at additional tools that that are tied into to TC, into the cancer, which are basically prism is creating a new, uh.
The platform, the technology stack, and 1 of the things that we will be doing this fall is precisely what ozbourne just suggested. We are planning on.
Creating what we call in and world a, um.
Data analysis portal, which is, which will be kiosk based where, and where people will be able to, uh.
Play with kiosks, directly accessing data in the icon.
And so that that's planned development would be a.
It's what we call what 1 might call an incubator project.
Happening this fall.
So, we may we may be reaching out to Joel.
Uh, I know you talked to Sharma, he was on our team and and so.
He did some of the early experimenting with it and.
Now, we're going to make it a reality. Excellent. Well, that's good news. We.
We're all for it now,
we'll have to set it up and if you have any features that are missing,
and I think the team here is willing to see what,
uh,
how this platform is being used outside our current projects,
and maybe enhance on some of the features,
but I think we have hooks for pretty much everything.
Yeah, so it will be.
The documentation isn't always up to snuff and we're aware of it.
But I'm impressed with what people have been able to do with what we have. Our API docs are pretty good, but our install Docs are still a bit lacking. And but I will be do everything I can to help you guys out.
Thank you so much. Totally possible. That was an excellent presentation and, and very encouraging. Thank you.
Show the live chat.
Well, so questions from others.
Hello.
Hello, this is Brandon Dallas at the FDA. I have a question. Actually I have several, but.
I'll just start with 1 and wait give someone else the chance to, um.
1 of the challenges I have encountered is, um, using images from Europe.
Gdpr law.
And I'm wondering what that means for your portal.
Well, I can answer on this because we are under the constrain of GDPR and all our countries, and the patient consent have to comply with GDPR. It doesn't mean that we cannot share images.
But the whole challenge is to have the proper consent in Switzerland. We've been having we're having a national initiative to have a generic consent form. What?
Because the general consent that will allow the patient's consent to have the data used for any research and not specifically for a given project.
And the wording, and the legal aspect for it is being worked out. I think we are now at the end of setting up a a final template for all the hospital to use.
Uh, of course, the European community is still lagging behind and defining what kind of consent can be done or not.
But, uh, yeah, it, it for a specific project, it's not a problem because what we call an informed consent is something standard across the world. So we have the same rules.
You have to inform the patient of the study, how it's gonna be used who's gonna use it what was the added value and so forth.
But if you want to have a general consent that allows us to share images and and do whatever we want with it, in terms of and of course, they have to be anonymized properly.
Uh, this requires your authorities to approve that consent form that you have the sign, the patient sign. We have 1 in Switzerland.
We have still because Switzerland is a federation and that's the problem of Federation is that every count on every state has a slightly different wording and they, their local authorities have made some different some of them.
We wanted to have 1 page consent, and some of them are about 2 pages now, but in Switzerland, we do have a general consent that we can have patient sign that can there make them donate their data for a sexual open data.
And then we can share it with you and this was 1 thing I want to clear up just in case there's any ambiguity about it.
Kiosk itself is server software,
so we have a,
a platform that we have here in Geneva that we,
we share for some of our partners over here where we have the server hardware,
et cetera,
but really what we provide is the software so that other people can set up a kiosks instance.
So there's no issue each each institution that installs their own kiosk has to deal with all kinds of rights all the issues that where the data can go, et cetera.
But it's not that there's 1 massive server over here in Geneva where we're storing everybody's data.
Thank you, I would just ask when you make some good progress on that patient consent form, please share it with this group and likewise, Julie and Kevin. If there's anything like that, that can harmonize. Uh.
What's happening in the US to be able to access or pay a similar consent form that we should be using here in the US please.
I can provide you with some examples of what has been approved by the University, the different universities in Switzerland. Some of them already trusted in English. So I can provide that to you.
It doesn't mean that your local ethical committee, or authorities will approve them. But at least it's an example of what has been approved in Switzerland and Swiss consent, they can share the images and we can share with, you.
Thank you. Awesome.
Yes, speaking speaking of multiple key instances each with their own data is is there a way in key?
Or, let's say, I have hospital a B and C.
Uh, where they can, uh, share data between the 3 key offices.
In other words, kind of, instead of a centralized archive, a distributed, but Federated archive.
Yeah, so we've got.
So, there's the simple solution is everybody stores it all in the 1 1 server and kiosk itself isn't isn't meant as a federated solution.
What we have done.
To solve these sorts of problems is that we have albums that are effectively.
Clones of each other, so you have on 1 kiosk instance.
How we end up web hooks that I showed so when data's added to this 1 album,
it triggers a web hook,
which tickles another another system that copies the data to,
from hospital E,
hospitals a caps instance from the 1 specific album to.
A specific album on hospital, these jobs.
So that that we do have in place.
It's a little bit of a hack, but it seems to work.
It also allows every hospital or every a site to have a complete set of data on their own.
In a certain item, so it's, it has to be agreed upon between the different groups. And basically it's a synchronization between albums.
So, if you don't have access to the other side, you still have a copy of all the data that has been shared.
By the group, the ones in.
Was to champion showing the chat by Tracey.
And the, the access and putting open data.
This is a different.
Same reading the message from Tracy Nolan who's asking how our sharing tokens handled sick taxes, open data using my.
So, the, the sharing tokens, the only people that are allowed to create a token, are the data stewards of the album.
And once you've released the token in the wild likely token that I pasted earlier here.
You pretty much lose control over it. You lose control of it to a certain extent. You still have the ability to disable it.
So, if I were to go back into kiosks here and go into.
Into my album and look at look at my tokens.
This sharing link is the 1 I pasted and so if I were to click on revoke.
Everybody's link would become inactive.
But otherwise, no, you don't have any good control over who's using it. You have to be careful who you share it with.
Kind of like a a link that you would use in.
Google Docs, or or something like that.
I have another question. It's Brandon. Yep.
And I understood your response about sharing images, uh, and that your caps is, uh, to be perhaps a.
Instance on other people's servers and you're not building a huge database. Um, but, uh, at the low budget, we kind of need a, a place to.
Share images so that we can start research nonpapel. You know, those images are kind of.
Share at the end of research where everything is curated and the publication is even done. So, um.
We don't have the ability to create 1 of those servers as you mentioned. So, are you accepting a down notice some images from different partners that are.
Uh, as just a parking lot sort of situation.
Why we could host some of it here in Geneva we do have 256 terabytes,
which we haven't used yet,
but,
uh,
I wouldn't open that to the whole community because that's why we cannot host that as,
you know,
Google is offering also some services that are quite attractive from a from a cost point of view,
but then it depends if you want to trustable whether or not with the data.
And the last solution we add that, which was this helps in the box doesn't cost much. I mean, you can buy 1 of those technologies servers that has 40 terabytes.
Uh, and it works pretty well. It's pretty robust. It's, uh, it's a nice and it has a redundance and it has a.
The rain technology that this 1, this goes down, it's still protected and we're pretty confident these for small groups that have there don't have the it infrastructure.
In house to buy 1 of these boxes is what less than 2000 dollars.
Yeah, it's about a grand. Yeah, my challenge is we have no ports going out like that.
That's the point I, I would suspect that 1 of the better options would be to go with Google.
Um, I would talk to your colleagues that are online on this call, I think, have had have a good.
Good relationship with Google and I think Google would probably be willing to.
To cut a deal for new projects that the I think they want to infiltrate everywhere.
And then, when it comes down to it, kiosks is just an authentication layer, or an authorization layer that sits in front of a pack.
And so,
what you end up doing is you end up having using the Google Cloud health care,
and then running on Google,
the Google cubernetti's environment to run the actual kiosk server.
I suspect that that would be a reasonable solution for you guys, if you're small. And of course, once you have to pay asking, goes up with your usage.
But again, if you want to test it, we can open a instance of camps for you in Geneva.
For a few months, and you can try to playing with it. We host a couple of terabytes easily without any problem.
Hello.
Have any questions.
I have 1, it might be kind of silly and I don't know if it's already been asked what is the data size limit or is it maybe I don't know if it's priced or not, but, you know, is it priced by some sort of amounts?
Because it does seem like users upload their images right?
Is that correct? And so again, the kiosks itself is just the software that you can install on your own on your own hardware.
So, we so far we don't have this discussion of how to.
Um, how to help fund our project by with, um.
Charging people for the server here in Geneva, but so far we've ended up just giving it as a, as a service to.
To our partners and so so, yeah, again, it's not a, since it's.
We have a kiosks here in Geneva, but it's, I suspect the key ops here in Geneva.
It's not going to be a particular interest to you guys and what will be more interesting for you would be to install it within your own institutions, or within a, with a cloud provider.
And then what you'll have to end up paying is the cloud provider for the storage, within the cloud provider.
Oh, this.
It's like, pardon? I didn't understand.
I'm just trying to make sure I understand. So I apologize. So we can just hook it up to our own data store our own pack system in a sense.
So, you'll have to kiosk itself, behaves as a pack so it's its own. It's its own data store. So you'll have to install a copy of on on a computer.
Within your institution.
Okay.
I have a question for her husband.
Or you mentioned the use of chops as a, as a player in in social network.
In that context are there any concerns about.
Users potentially sharing data with content in the content.
Let's talk about the responsibility of Ops, but somebody has to.
So the risk where the risk is to the people that put the data,
I mean,
basically somebody is the owner of the data,
and he has to make sure that the data are properly anonymize and they have the proper consent once you put it on the caps.
You're responsible of what you put in there.
We're just if it's on our server, we addressed a provider of storage when we don't have a responsibility and what's the data content is we're just a broker.
But it's still, the problem is in getting the proper consent and getting the proper identification of the data before you start sharing it on a caleb's platform with other people.
We, we certainly don't recommend people to use gaps with clinical data.
It's not meant for it's not doesn't have a degree of security that a clinical system would require. It would require some additional protection from a, to store clinical data.
We don't claim to have the degree of security right away. So I have tried really hard to have a very high degree of security and I, I believe that in practice, it's probably similar.
But, but we're not willing to make these claims. It's more of a liability issue another technique. I mean, you could use it for clinical use, but it's not meant to but it does have.
But it seems to me that chaos is a great.
Could be a great partner with image repositories because when you have a large archive, you want there's interest in sharing some.
Portion of that projects. Exactly. Chips has come up big discussions. We've had with our colleagues that.
Whether institutes in an age, like heart, lung and blood or.
Or, and I.
National, so, for infectious disease, and I ID for developing portals portals, and they've shown interest in concepts of cabs.
Well, I just wanted to relay that to, you.
Yeah, it has the advantage of being able to help some, some groups of participants to share subsets of the data.
You can have a huge edge or database, and then have some groups will just work on a subset of the data.
And share them for some research, or some project.
There's not a question from another comment from Tracy, in the chat.
He says, I think I saw in your presentation of branch of work flow where data could be analyzed at a distance and then a report could be returned to the user that would make cloud computing easier and cheaper for users.
Could you elaborate place on what's going on there? And how cubes plays a role.
Yeah, so the, I'll, I'll go back to this report provider system.
Um, so the, we've ended up using this for all kinds of different systems.
Um, the.
What ends up happening here? I'll go I'll go over it again. Is that.
You have a, and a completely separate website.
Let's see,
what would be a good people in mind since I regardless that can analyze the group and minds have a have a website where we can send the data they would do something to the data.
We'll do a report or an analysis and return some results.
And that works very well with the provider. They get the images, we do something with it, create a, a, a map or an image or a text, and return it as a, as a report to the same.
Studying so, then this outside system where it was 1 of the ideas that I had is that you would.
You would have outside providers that end up.
Offering services to analyze the images and then bring the reports back.
But getting the data to them is always kind of tricky and you end up having to send CDs or or drag and drop files into.
Into the web page or things like that things that aren't very easy to do.
So, the idea is that they could go and create 1 of these report providers.
Give users the configuration that they would that a user would enter into kiosk and then when they're in kiosk, they could load the report and it would take the user to the separate to this website. That's.
I'm off on the cloud or off on just on a different server somewhere else and this other server would then be able to access the data, analyze it and send it back.
I, I hope that.
Help to answer the question, right?
Tracy, I hope let us know in the chat if that answer.
Okay, she said, okay, so kiosk allows simple your API albums, but we still have some bio load. I was also thinking off.
And tracy's probably typing a little bit more while she is typing. I have another question for you, you mentioned documentation where would I find the documentation on.
Your website, so you click on help.
And you get the, you get the user well, if you go to caps that online, you'll find it. And if you click on the demo, you'll see that link.
This is, this is the kind of so, yeah, I was looking on the caleb's online, but I have to go into.
ketchup's demo, and then the website with Docs done jobs that online.
So suppose that you want to do okay, thank you.
And so here, you'll find the user documentation, and if you click on API documentation, it'll take you to.
So, I get have wiki where we have all of the, uh, the best resources documented.
Thank you and he has the rest of tracy's message. Okay. From the beginning allows simple albums, but we still have some output load.
I was also thinking of the ability to through an algorithm at data, rather than getting external reviewers to work with all HIV and a typical radiology.
So, yes, I think Tracy understood exactly what's going on. So it allows you to create an outside application.
That has access to the data,
et cetera,
but of course,
the is still going to be still going to be presidency this external website is going to have to download all the image data.
And then re, at the end of the of whatever process it implements.
And I'm reading tracy's comment. Perfect. Thank you. Thank you.
So, we had discussed.
Potential use of kiosks in conjunction with the imaging data comments.
Fortunately, nobody from the team is online here. I saw they've clearly for a minute, but he's on.
Todd is on start here you are here. Okay, so I'm.
Thanks, David.
I know he has the capacity to form its own cohorts but what about some tool like to for user to combine their own private collection with the corner from IDC to submit to.
Or cloud resources for started processing and analysis.
Well, certainly had a number of potential use for kiosk sharing features. It keeps it very attractive. We use Google web based. I was saying of data that's in Google buckets.
So interfacing 2 kiosks would be relatively painless. I would imagine. And we also use cases to viewer. I noticed responding, I'll have some sort of default view, or when you were navigating for.
So, there are a lot of things that we can either learn or reuse for and we will certainly be looking at that in terms of submitting data, though.
As, you know, function is primarily to provide a straightforward means, establishing cohorts to provide compute resources to apply compute resources to competing in the cloud on collections that come from established archive.
So we will have a complete mirror content. For example.
And to that end, we don't envisage sort of.
Taking submissions directly from users, unless they have been extremely well identified and curated and have come from a, sort of shall we say trusted source is of course, a trusted source.
The exception probably being that of derived data. So, to the extent that someone annotates some data and or provides.
Derived data sets that are completed in the cloud or locally.
How we will need to address the submission of that and again, we may will find that going through the original collection.
Archive, so if it's a derived data set that applies to CCA, then we don't just want it in in. We want it in as well and therefore we would have to submit or submit it to and then it would become available in IDC.
In the normal course of events. Um, so how, uh.
A tool like kiosks would serve.
To help IDC deal with submitted data maybe a moot point, given the fact that we do want to maintain.
The data in its, in its source archive, shall we say.
All right thanks, David. Well, my point was about bringing the data to call.
Combining public data to see. Yeah, that's certainly true. If they're combining their own data with data that's from or or some other similar centralized archive.
Then a tool,
like,
key Ops would be useful as would us any of the tools to provide a sort of Federated query 1 of the things you may have noticed when the demonstration was being done was the use of stuff and I put
horses the open source version of that and they can provide a federated query view so that the information could come from multiple sources or or dotcom web sources.
And so.
There's also the question of as it is related to 1, the 1 that Tracy raised, and that is, you know, to what extent does the user need a federated experience regardless of what source the data actually.
Uh, lives at, uh, both from a local computing perspective as well, as, from a, a cloud, uh, cohort definition perspective. The other thing I'd mentioned while I have 4 is, um.
Brandon had been asking about places to host data and Google had been mentioned in addition to using Google as a conventional Google cloud services,
and the Google Health cloud services,
which are specifically dotcom enabled as,
you know,
Google also has a public data set project.
So, Google is willing to host data that has public value, and they have a program for determining what constitutes that and so on.
So, even if you're not involved in the tca stream of data, which Google replicates and provides to the public, there may be other opportunities to interact with Google people and Google Health cloud.
People are also involved in that Google public dataset program.
And do not the only cloud provider that do this.
So,
there are several opportunities if there's a sort of common,
good recognized by the cloud providers,
it may be that folks like the who don't otherwise have a a straightforward means of hosting extra mural data could leverage something like that.
If the data set was was widely desirable and, and completely open.
Yeah.
Any other questions for our presenters. Okay if not, they want to thank you for great presentation and.
All the attendees for interaction and questions.
Thank you Joe, just to get an update on other activities.
Thanks.
Turn it to you.
And I hand it right back over to Justin or John for the update.
Okay.
Um, do you see in my my browser window here? Yes. Okay. So, I think John mentioned this 1, this might be where we cut off last month, but I just wanted to remind everyone.
We have a 2nd covert data set available now on and we're continuing to work with.
Both stonybrooke and on 2 additional data sets. So keep your eyes out for those in the coming months.
Then the next thing is this acronym or brain collection,
which was initially released under a limited access policy for members of the quantitative imaging network has reached its 1 year embargo and is now totally publicly available.
So, anyone that's interested in this trial can access that now. We may not be seeing this screen.
We're seeing Twitter, but not the shine is.
Yeah, we see the notifications get the wrong browser window. Maybe.
Eva.
Just do this. Okay.
Are you 3 on the Akron Tweet now?
Yes, okay. Um.
All right,
then we also had the annual virtual,
the annual CP tack meeting that was virtual this year was held earlier this month or towards the end of September I guess so we were highlighting that we are continuing to collect new CP tech
data from the various contributing sites to stay accrued new tissue samples,
and we've actually changed up the data release policy slightly to sync up with the other data types.
So, they'll only be new data added to tca when there's a accompanying data release now, rather than the calendar base monthly, quarterly thing that we were doing previously.
Then we have this new data set, the codex sell nays, which is short for neighborhoods and this used the.
Codex, which side am not familiar with, but as I guess some kind of imaging that allows imaging and 56 proteins across 140 different tissue regions.
And so it's another new pathology collection that's available.
And then, finally, we have a workshop that we're doing together with the imaging data comments group, where we'll be walking through, and kind of a hands on format teaching people how to use both systems.
And then summarizing some of the, the similarities and differences between the 2.
2 archives,
and then the other thing I should mention,
that's not in the feed here,
but we're also again involved in the Mikhail brats brain tumor segmentation competition with data from the cancer imaging archive once again being utilized to facilitate that.
So that's another interesting thing to check out. Make sure.
I think that's it.
Thanks.
I think that leaves only me and the announcements. Kevin do you want to speak a little bit about Chuck that Justin just mentioned and what's coming up for the imaging data comments?
Sure. Let me see if I can bring up that announcements.
Or I'll bring it up. No, I mean, I have it now and share it. Okay.
Okay, you said, yes.
Books, so a lot of people are excited about going to leave approval next week, but unfortunately.
So, anyway is just the mission.
Uh, there will be a tutorial on.
Probably can't see missing data repositories, which basically introducing.
Uh, and sort of the collaboration between the 2 groups.
And, um, to essentially filter as users with how to access data sets and navigate.
The platforms and download in the case of, or in the case of, like, the.
Cohorts for the processing.
Unfortunately, we decided not to have hands on demonstrations because.
During that on line, it's sort of 2 issues.
Technical issues, so they're gonna be a sort of 1 day 9 active demos of the of the platforms.
Um, and, uh, this would be on on Thursday.
And the content will be available online for for year until like, this, the next.
In 2021, as far as IDC to update, is that.
The hard launch of the, I didn't see the official launch is expected to be on.
20 of this month and, uh, it's likely that the soft launch before that day. Possibly later this week.
And so maybe portsmen in this.
Tutorial would be able to access to the website.
So, um, so.
It's my hope that in the next version of this webinar, we will have.
Updates from legacy as well as to.
That's all Thank you. Thank you came on. I do have 1 more thing. So given that we are thinking about scheduling and potentially an additional.
I'm coming to our session.
Uh, in month of November to feature, I didn't see.
We couldn't plan to say head because of the uncertainty about the exact date that I can see.
So, we have a couple of presentations lined up for the next couple months that I think we mentioned and, um.
And we're considering having the extra session to have IDC introduced to you. So.
I'm sure we will send out notices about that. That's that's plan.
Thank you. Thank you. Keep on. Yes, I will do this. And the next scheduled is November. 2nd.
And will have presentation about money I.
The following is December 7th, we will hear a presentation about the portal.
We will try to schedule and imaging data comments, introductory between these 2.
And we'll updated the recordings from the webinar can be found on the wiki.
Information about upcoming calls are also and that's all I had for today on the call.
Thank you Lisa. Did you talk about the next 2?
Presentations November in December. Okay. I was reading from the chat content.
Well, thanks everybody. Um, this was a great session, and it was a, it was a pleasure for me to future husband and.
And hopefully you found the presentation interesting and we'll actually have a have a great day and see you next month.
Thank you thank you.