13th European Conference on eGovernment – ECEG 2013 1 | Page 163

Giuseppe Ciaccio, Antonio Pastorino and Marina Ribaudo
medical history without resorting to any paper document and, perhaps more importantly, without missing any of Alice ' s medical records.
Challenges. Alice might not want to show all of her medical records to the doctor. Some illnesses, like HIV infection for instance, pose serious privacy concerns and might not be significant for the specific disease Alice is asking advice for. Scopes in OAuth 2.0 allow to specify which fields in a generic record can be accessed and which cannot, but they are not able to discriminate among distinct instances of the same field in distinct records. A workaround might be to have a specific field for privacy‐sensitive information and letting the user decide whether to authorize disclosure of those sensitive fields or not.
In a different scenario, Alice might not be able to give authorization, perhaps because she is unconscious, due for example to a car accident. In this case, there must be another entity which has enough privileges to give authorization without being the data owner. This entity might be the head physician or a close relative of Alice ' s, and currently this scenario is not explicitly covered by OAuth 2.0, which contemplates a single owner for each data item.
In the medical context it is also very important to have access to aggregated and anonymized datasets for different purposes, for instance to perform statistical analysis for a given disease or to compare the performance of different hospitals. This release of large anonymized datasets is not covered by the current OAuth 2.0 flows which indeed grant access to specific records of an individual user. We will briefly discuss these points in Section 5.
4.2 Tax payment
Scenario. Bob needs to fill in his annual tax return. As usual, he visits his business accountant bringing lots of pieces of paper: his annual salary, medical expenses, documents concerning his properties, other expenses he can deduct from his income, and so on. The other possibility is to use a web application provided by the government and fill in an online form by manually copying all the data printed into the various paper documents.
How OAuth 2.0 could help. Figure 4 shows Bob in front of an innovative online service. He still has access to a web application to fill in the online form for his annual tax payment. This year, however, most of Bob ' s income information comes directly from various remote databases where it is scattered, upon a simple online authorization by Bob himself. Filling in the form is simpler, quicker and less prone to mistakes.
Figure 4: Tax payment via OAuth 2.0
Bob is the owner of the data. He applies for the authorization grant( arrows 1 and 2) so that the web application he is connected to can directly access his restricted access resources stored in different databases( the Employer Registry, the Estate Registry, the Medical Expenses Registry shown in the figure). He then fills in the form adding only data that could not be obtained via online third parties.
141