<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns="http://purl.org/rss/1.0/"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:cc="http://web.resource.org/cc/"
 >
<!--
	This ontology document is licensed under the Creative Commons
	Attribution License. To view a copy of this license, visit
	http://creativecommons.org/licenses/by/2.0/ or send a letter to
	Creative Commons, 559 Nathan Abbott Way, Stanford, California
	94305, USA.
-->
 <channel rdf:about="http://ebiquity.umbc.edu//tags/html/?t=ontology%3B+cloud+computing">
  <cc:license rdf:resource="http://creativecommons.org/licenses/by/2.0/" />
  <title><![CDATA[UMBC ebiquity RSS Tag Search]]></title>
  <link><![CDATA[http://ebiquity.umbc.edu//tags/html/?t=ontology%3B+cloud+computing]]></link>
  <description><![CDATA[UMBC ebiquity RSS Tag Search for ontology; cloud computing]]></description>
  <items>
    <rdf:Seq>
      <rdf:li resource="http://ebiquity.umbc.edu/paper/html/id/852/Delegated-Authorization-Framework-for-EHR-Services-using-Attribute-Based-Encryption"/>
    </rdf:Seq>
  </items>
 </channel>
 <item rdf:about="http://ebiquity.umbc.edu/paper/html/id/852/Delegated-Authorization-Framework-for-EHR-Services-using-Attribute-Based-Encryption">
  <title><![CDATA[Delegated Authorization Framework for EHR Services using Attribute Based Encryption]]></title>
  <link>http://ebiquity.umbc.edu/paper/html/id/852/Delegated-Authorization-Framework-for-EHR-Services-using-Attribute-Based-Encryption</link>
  <description><![CDATA[Medical organizations find it challenging to adopt cloud-based Electronic Health Records (EHR) services due to the risk of data breaches and the resulting compromise of patient data. Existing authorization models follow a patient-centric approach for EHR management, where the responsibility of authorizing data access is handled at the patient's end. This creates a significant overhead for the patient who must authorize every access of their health record. This is not practical given that mult...]]></description>
  <dc:date>2021-11-01</dc:date>
 </item>
</rdf:RDF>
