[Automatic captions by Autotekst using OpenAI Whisper V3. May contain recognition errors.] Welcome to the next part of Data at UiO.
I'm going to start by going through our consensus solution, so that we can show how it works properly.
I have a demo at the end, which I have worked a little with to play in the foreground, because it runs out my birth number in the bowels and edges when you have to deal with these consensus.
So, what is the consensus solution we now have?
I got a question from OSR saying, yes, we are the supplier of digital partnerships for Oslo University Hospital.
We have entered a separate agreement for it, and we are a approved general supplier.
Our partnership solution received an enormous boost during Corona, when Arne Sørore collected 200,000 digitally signed partnerships in the course of a short period of time, as stated in Dagsrevyen with his study.
It was useful that we managed to collect a digital consensus on the level he needed, which was that you consensus on the delivery of journal data from different companies.
It has been tested several times, and we have seen that we have also obtained journal data from other health companies based on those consensus.
We have documented the validity and quality of our consensus.
Men det er mange nivåer av samtycke, og dette med å kjøre krypterte nøkkel, med de pdf-ene og det som jeg skal vise nå etterpå, det er det de færreste som trenger.
In the beginning, there were a lot of people who used it, and then we started to send calculations on it.
It's fine with 10-20 of them, but now you have 200,000 opinions, and if we factor in 650 plus mums per, then Arne Søro's coffee got a little in the throat.
But it was corona, so the money was a little looser for research, fortunately.
I'll show it to you, but we at UiO often just use a network scheme with a fade-in login.
We are very sure to trust who the people are when they log in with a fade-in.
If you agree that we film you at our IT conference and that we upload it, then you don't have to see it in a portal.
We just have to have documentation that it was given consent.
If you want it back, then you can contact us and discuss it.
Don't make it too difficult either.
Our requirements for documentation are far beyond that.
Many can manage with digital consent, where you just log in with the ID-port.
So, when you're going to make a copy, you go into NetSkjema and pick it up from Mal.
Here we have a copy with a signature, and then we have a copy without a signature.
The biggest difference is that it's much easier without a signature, and it's free.
So there are two big arguments.
The disadvantage is that it's worse to say that it's okay that you have consent to the issuance of journal data.
But if it's a research project where you give away health data, for example, then it can in many cases be good enough to just have an ID-porting signature.
It will still appear in our portal when you use these schemes.
The latest consensus scheme is made for Oslo University Hospital to be used against their system MedInsight.
There is also a solution where we automatically export the consensus into the OS infrastructure to MedInsight.
To activate and control a consensus scheme, you do it now from NetSchema.
As you can see here in this TSD file, you can control the consent scheme.
And then you, as the person who has given the consent, can log in to a portal on the Internet called TSD Consent Portal.
It looks like this.
I'll just run through it, because they have a full process afterwards.
Researchers can log in to TSD and look at their data in the portal or in File Explorer.
I will also show this in my demo that starts now.
Here I go into a diagram to create a consensus diagram.
It is a similar diagram as all the others, the same type of questions, and it looks exactly the same, it's just that we handle it a little differently.
So here I just make a name for the diagram and go and choose to get the diagram from Mal.
So you have to have that type of diagram.
You can change the type of diagram afterwards if you want to, also after you have put your data in the diagram.
You click on the questions many know about from NetSchema, and you can set up the diagram itself.
You see here that it has put some questions.
You can just edit them however you want, but it's in the picture.
And that's just something we've put.
There it's just put that I agree, I disagree, no.
I think I have to do some tricks here, I found out when I was working on this movie.
I put my birth number completely down so I can hide it in the demo.
I made a silly text here.
Otherwise it would be so stupid.
But you have to have birth number questions, because that's when we can pick it up and put it in this portal that is out on the internet.
The respondent can log in with bank ID to see metadata about that scheme.
I just check the code book here, go to the TSD EduCloud farm, and choose to connect the schematics.
This is the same for all schematics that will deliver data to TSD and EduCloud, but here I chose signage.
And choose to send this to TSD.
You can send it to EduCloud, but it will not be exported to the public portal.
So it's not that fun.
I log in with my TSD user, and connect the diagram to it.
And when we connect this diagram, a database is created in TSD that can receive the data.
We also see here that I get the opportunity to see the rights and control who will be allowed to see the consent within TSD.
This is a functionality we have for all diagrams.
You can control these rights from the net diagram.
Then I open up a schedule to collect the data and go to the website that looks like this.
I log in with my usual bank ID, do some tricks, and then I have logged in.
I have hidden my birth mother completely down here, so that we don't go out with this on the internet.
We see that some questions are automatically answered.
We pick them up from the contact and reservation register, and fill out the name and birth certificate number.
Below it does not say deliver, it says sign.
And we have to send to the post its signage service, which we have a collaboration agreement with, which is the one who also invoices us money per consent, which means that we must have that high price.
This is a subcontractor of ours.
But here it is put on keys that document that the PDF has not been changed.
If someone manages to change the PDF, Acrobat Reader will give error messages, because it checks against a checksum that the post has taken care of for us.
Now I go to my consent portal, tst.usu.no, and log in with me as the respondent's birth number via BankID.
And here we see that this consent scheme that I just talked about is located with metadata in this portal.
And all the consent I have given, I will be able to see here with a set of metadata.
In addition, this is a link to a network scheme, where this project in the example, which I now recommend, has the fact that you have to sign a new agreement where you say no as you withdraw your agreement.
Now I take on my researcher hat and go into my TSD project, which may look like this.
When you start a browser, a net reader in TSD, everyone gets this website up.
I put links to this, as Leon showed, Tables, which is a portal where you can publish files on the net on a given birth number.
In addition, we have the data portal to the network, where all the data from the network is located.
I go into the data portal to find the data and the consent that has now been delivered to my project.
Log in here without two-factor, because it is not possible to use two-factor in TSD, because it is not internet.
Here you see that there is a diagram called consent with data at UiO, as well as a number of other diagrams.
Then I can go into that diagram and look at the consent that has been given.
You can see there's a sign here that says signed document, where there is a PDF.
It may take a few minutes for it to arrive, because there is a delay in the generation of the PDF, now that it has been sent after the data from the net diagram has been sent.
You also find the same PDF in File Explorer, in this area, durable.
There are good attachments and CSV files with all the contents.
And you can see the PDF that I showed here in the start.
There is a PDF that has been made now.
So there I went through the entire flow of how our consensus solution works.
This means that if someone withdraws a consensus, you will actually get a new consensus.
You have to handle that yourself, but you get it collected in TSD in the way we showed here in the data portal.
We know that this is a consensus, since it is included in the PDF that is delivered in a slightly different way.
So we will make some changes relatively soon within TSD, so that we get some more features around the data that is delivered as a consensus.
So you can just follow along with what happens, but it's a little less changes than it has done now.
If we had done the same with just the birth number, then it would have been logged into the portal, and then it would have been logged as data in the data portal, but without the PDF.
This can, as I said, work quite well in many projects.
That was the consent solution.