Newer
Older
Digital_Repository / Misc / Mass downloads / UTas / 782.html
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  2. "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  3. <html>
  4. <head>
  5. <title>UTas ePrints - Professional Access Control</title>
  6. <script type="text/javascript" src="http://eprints.utas.edu.au/javascript/auto.js"><!-- padder --></script>
  7. <style type="text/css" media="screen">@import url(http://eprints.utas.edu.au/style/auto.css);</style>
  8. <style type="text/css" media="print">@import url(http://eprints.utas.edu.au/style/print.css);</style>
  9. <link rel="icon" href="/images/eprints/favicon.ico" type="image/x-icon" />
  10. <link rel="shortcut icon" href="/images/eprints/favicon.ico" type="image/x-icon" />
  11. <link rel="Top" href="http://eprints.utas.edu.au/" />
  12. <link rel="Search" href="http://eprints.utas.edu.au/cgi/search" />
  13. <meta content="de la Motte, Leigh" name="eprints.creators_name" />
  14. <meta content="Hartnett, Jacky" name="eprints.creators_name" />
  15. <meta content="lhdela@utas.edu.au" name="eprints.creators_id" />
  16. <meta content="j.hartnett@utas.edu.au" name="eprints.creators_id" />
  17. <meta content="conference_item" name="eprints.type" />
  18. <meta content="2007-02-19" name="eprints.datestamp" />
  19. <meta content="2008-01-08 15:30:00" name="eprints.lastmod" />
  20. <meta content="show" name="eprints.metadata_visibility" />
  21. <meta content="Professional Access Control" name="eprints.title" />
  22. <meta content="pub" name="eprints.ispublished" />
  23. <meta content="280103" name="eprints.subjects" />
  24. <meta content="public" name="eprints.full_text_status" />
  25. <meta content="paper" name="eprints.pres_type" />
  26. <meta content="Health Informatics, Access Control, Computer Security, Roles, Medical Records" name="eprints.keywords" />
  27. <meta content="Topic area and paper objectives:
  28. This paper investigates the hypotheses that it is possible to build a practical access control system
  29. for patient records within a hospital domain that ensures access to all those who are at any one time
  30. part of a particular patient's treating team yet at the same time provides appropriate barriers to
  31. access for those not currently part of this team. A caveat for this hypothesis is that at no time
  32. should a clinician be barred from access to a particular record, but that means should exist to ensure
  33. that appropriate access is accepted and inappropriate access reported upon. Central to this idea is
  34. that it should be possible to use standards of professional ethics and normal workflow to enable the
  35. model.
  36. Background and concise literature review:
  37. Traditional models of access control do not cope well with the problem of how to define access
  38. permissions for a team that is dynamic in nature (as is a treating team) and where the access is to
  39. objects (patient records) only in the loosest 'owned' by those who have a need to access such
  40. objects. In these models either the system administrator has to define permitted access in advance
  41. (mandatory access control) or the owner of the data can define the permitted accesses (discretionary
  42. access control) (Pfleeger 2000). Extensions to Role Based Access Control (RBAC) and Team
  43. Based Access Control (TMAC) have provided the most useful solutions to date but still require a
  44. system administrator or surrogate to define appropriate access in advance. (Ferraiolo &amp; Kuhn 1992)
  45. (Ramaswamy &amp; Sandhu 1998) (NIST 2004) (Thomas 1997) (Georgiadis et al 2001) (Georgiadis
  46. 2002) However, work by Thomas &amp; Sandhu (1997) and Alotaiby &amp; Chen (2004) has shown that it
  47. is possible to incorporate changes to access privileges as part of normal workflow.
  48. Methods:
  49. As a result of observing and discussing normal and unusual workflow patterns within the
  50. Tasmanian hospital environment a set of scenarios were developed each of which characterised a
  51. unique instance of change to whom should be able to access a patient record. The method used by
  52. current access control models to handle each scenario was then analysed. A new definition of a
  53. team in a hospital environment was then used to develop the Professional Access control (PAC)
  54. model that was implemented and tested in Oracle. Testing was carried out using each scenario in a
  55. simulated hospital of 3 wards, 20 staff and 20 patients.
  56. Results and discussions:
  57. Clinicians at a hospital were defined as either being Members: part of a patient's treating team,
  58. Colleagues: having the same role and belonging to the same unit as the patient or Associates: part of
  59. the hospital but not currently related to the patient. Being a team Member can be adjusted as part of
  60. the normal hospital admission and referral processes. Emergency access is provided subject to
  61. retrospective approval and auditing procedures. The model has been developed as an Oracle
  62. implementation for a simulated hospital environment and tested against the 24 scenarios defined.
  63. The Professional Access Control model allows for dynamic definition of the treating team and
  64. facilitates guaranteed availability to clinicians appropriate to their relationship to a patient. This is
  65. made possible by relying upon the professional ethics of clinicians rather than those of system
  66. administrators. It relieves the burden of predefining access control from system administrators
  67. without endowing clinicians with unnecessary system administration privileges." name="eprints.abstract" />
  68. <meta content="2005-08" name="eprints.date" />
  69. <meta content="published" name="eprints.date_type" />
  70. <meta content="8" name="eprints.pages" />
  71. <meta content="13th Health Informatics Conference HIC2005" name="eprints.event_title" />
  72. <meta content="Melbourne, Australia" name="eprints.event_location" />
  73. <meta content="31 Jul - 02 Aug 2005" name="eprints.event_dates" />
  74. <meta content="conference" name="eprints.event_type" />
  75. <meta content="UNSPECIFIED" name="eprints.thesis_type" />
  76. <meta content="TRUE" name="eprints.refereed" />
  77. <meta content="Alotaiby, F. T. and Chen, J. X. 2004, 'A Model for Team-based Access Control (TMAC 2004)', International
  78. Conference on Information Technology: Coding and Computing (ITCC'04), IEEE, Las Vegas, Nevada, USA
  79. de la Motte, L. H. and Hartnett, J. 2005, 'Trusted Access Control', submitted to Australasian Conference on
  80. Information Security and Privacy (ACISP'05), Brisbane, Australia
  81. Ferraiolo, D. and Kuhn, R. 1992, 'Role-Based Access Control', 15th National Computer Security Conference
  82. Georgiadis, C. K., Mavridis, I., Pangalos, G. and Thomas, R. K. 2001, 'Flexible Team-Based Access Control
  83. Using Contexts', SACMAT '01, ACM, Chantilly, Virginia, USA, pp. 21-27
  84. Georgiadis, C. K., Mavridis, I. K. and Pangalos, G. I. 2002, 'Programming a view-based active access-control
  85. system for healthcare environments.' Health Informatics Journal (2002): 191-198.
  86. Hartnett, J. 2002, Research into the Implementation of Electronic Consent for the use of Patient Identifiable
  87. Health Data, University of Tasmania - School of Computing.
  88. Kalam, A. A. E., Baida, R. E., Balbiani, P., Benferhat, S., Cuppens, F., Deswarte, Y., Miege, A., Saurel, C. and
  89. Trouessin, G. 2003, 'Organisation based access control', 4th International IEEE Workshop on Policies for Distributed
  90. Systems and Networks, IEEE, Lake Como, Italy, pp. 120-131
  91. Kudo, M. 2002, 'PBAC: Provision-based access control model.' International Journal of Information Security
  92. 12: 116-130.
  93. NIST 2004, Role Based Access Control. viewed 6th October, 2004, <http://csrc.nist.gov/rbac/>
  94. Pfleeger, C. P. 2000, Security in Computing, Prentice Hall PTR, Upper Saddle River, New Jersey.
  95. Ramaswamy, C. and Sandhu, R. 1998, 'Role-Based Access Control Features in Commercial Database
  96. Management Systems', 21st National Information Systems Security Conference, Crystal City, Virginia, USA
  97. Schneier, B. 2000, Secrets and Lies, John Wiley &amp; Sons, Inc., New York.
  98. Thomas, R. K. 1997, 'Team-based Access Control (TMAC): A Primitive for Applying Role-based Access
  99. Controls in Collaborative Environments', RBAC '97, ACM, Fairfax Va USA, pp. 13-19
  100. Thomas, R. K. and Sandhu, R. S. 1997, 'Task-based Authorisation Controls (TBAC): A Family of Models for
  101. Active and Enterprise-oriented Authorisation Management', IFIP WG11.3 Workshop on Database Security, Chapman
  102. &amp; Hall, Lake Tahoe, California, USA
  103. Woodcock, D. and Gillies, I. 2003, 'Generic middleware as a new paradigm for providing a single user interface
  104. to multiple disparate web-based clinical applications', HIC 2003 RACGP 12CC Combined Conferences, Darling
  105. Harbour, Sydney Australia" name="eprints.referencetext" />
  106. <meta content="de la Motte, Leigh and Hartnett, Jacky (2005) Professional Access Control. In: 13th Health Informatics Conference HIC2005, 31 Jul - 02 Aug 2005, Melbourne, Australia." name="eprints.citation" />
  107. <meta content="http://eprints.utas.edu.au/782/1/PAC.pdf" name="eprints.document_url" />
  108. <link rel="schema.DC" href="http://purl.org/DC/elements/1.0/" />
  109. <meta content="Professional Access Control" name="DC.title" />
  110. <meta content="de la Motte, Leigh" name="DC.creator" />
  111. <meta content="Hartnett, Jacky" name="DC.creator" />
  112. <meta content="280103 Information Storage, Retrieval and Management" name="DC.subject" />
  113. <meta content="Topic area and paper objectives:
  114. This paper investigates the hypotheses that it is possible to build a practical access control system
  115. for patient records within a hospital domain that ensures access to all those who are at any one time
  116. part of a particular patient's treating team yet at the same time provides appropriate barriers to
  117. access for those not currently part of this team. A caveat for this hypothesis is that at no time
  118. should a clinician be barred from access to a particular record, but that means should exist to ensure
  119. that appropriate access is accepted and inappropriate access reported upon. Central to this idea is
  120. that it should be possible to use standards of professional ethics and normal workflow to enable the
  121. model.
  122. Background and concise literature review:
  123. Traditional models of access control do not cope well with the problem of how to define access
  124. permissions for a team that is dynamic in nature (as is a treating team) and where the access is to
  125. objects (patient records) only in the loosest 'owned' by those who have a need to access such
  126. objects. In these models either the system administrator has to define permitted access in advance
  127. (mandatory access control) or the owner of the data can define the permitted accesses (discretionary
  128. access control) (Pfleeger 2000). Extensions to Role Based Access Control (RBAC) and Team
  129. Based Access Control (TMAC) have provided the most useful solutions to date but still require a
  130. system administrator or surrogate to define appropriate access in advance. (Ferraiolo &amp; Kuhn 1992)
  131. (Ramaswamy &amp; Sandhu 1998) (NIST 2004) (Thomas 1997) (Georgiadis et al 2001) (Georgiadis
  132. 2002) However, work by Thomas &amp; Sandhu (1997) and Alotaiby &amp; Chen (2004) has shown that it
  133. is possible to incorporate changes to access privileges as part of normal workflow.
  134. Methods:
  135. As a result of observing and discussing normal and unusual workflow patterns within the
  136. Tasmanian hospital environment a set of scenarios were developed each of which characterised a
  137. unique instance of change to whom should be able to access a patient record. The method used by
  138. current access control models to handle each scenario was then analysed. A new definition of a
  139. team in a hospital environment was then used to develop the Professional Access control (PAC)
  140. model that was implemented and tested in Oracle. Testing was carried out using each scenario in a
  141. simulated hospital of 3 wards, 20 staff and 20 patients.
  142. Results and discussions:
  143. Clinicians at a hospital were defined as either being Members: part of a patient's treating team,
  144. Colleagues: having the same role and belonging to the same unit as the patient or Associates: part of
  145. the hospital but not currently related to the patient. Being a team Member can be adjusted as part of
  146. the normal hospital admission and referral processes. Emergency access is provided subject to
  147. retrospective approval and auditing procedures. The model has been developed as an Oracle
  148. implementation for a simulated hospital environment and tested against the 24 scenarios defined.
  149. The Professional Access Control model allows for dynamic definition of the treating team and
  150. facilitates guaranteed availability to clinicians appropriate to their relationship to a patient. This is
  151. made possible by relying upon the professional ethics of clinicians rather than those of system
  152. administrators. It relieves the burden of predefining access control from system administrators
  153. without endowing clinicians with unnecessary system administration privileges." name="DC.description" />
  154. <meta content="2005-08" name="DC.date" />
  155. <meta content="Conference or Workshop Item" name="DC.type" />
  156. <meta content="PeerReviewed" name="DC.type" />
  157. <meta content="application/pdf" name="DC.format" />
  158. <meta content="http://eprints.utas.edu.au/782/1/PAC.pdf" name="DC.identifier" />
  159. <meta content="de la Motte, Leigh and Hartnett, Jacky (2005) Professional Access Control. In: 13th Health Informatics Conference HIC2005, 31 Jul - 02 Aug 2005, Melbourne, Australia." name="DC.identifier" />
  160. <meta content="http://eprints.utas.edu.au/782/" name="DC.relation" />
  161. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/BibTeX/epprod-eprint-782.bib" title="BibTeX" type="text/plain" />
  162. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/ContextObject/epprod-eprint-782.xml" title="OpenURL ContextObject" type="text/xml" />
  163. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/ContextObject::Dissertation/epprod-eprint-782.xml" title="OpenURL Dissertation" type="text/xml" />
  164. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/ContextObject::Journal/epprod-eprint-782.xml" title="OpenURL Journal" type="text/xml" />
  165. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/DC/epprod-eprint-782.txt" title="Dublin Core" type="text/plain" />
  166. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/DIDL/epprod-eprint-782.xml" title="DIDL" type="text/xml" />
  167. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/EndNote/epprod-eprint-782.enw" title="EndNote" type="text/plain" />
  168. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/HTML/epprod-eprint-782.html" title="HTML Citation" type="text/html; charset=utf-8" />
  169. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/METS/epprod-eprint-782.xml" title="METS" type="text/xml" />
  170. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/MODS/epprod-eprint-782.xml" title="MODS" type="text/xml" />
  171. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/RIS/epprod-eprint-782.ris" title="Reference Manager" type="text/plain" />
  172. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/Refer/epprod-eprint-782.refer" title="Refer" type="text/plain" />
  173. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/Simple/epprod-eprint-782text" title="Simple Metadata" type="text/plain" />
  174. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/Text/epprod-eprint-782.txt" title="ASCII Citation" type="text/plain; charset=utf-8" />
  175. <link rel="alternate" href="http://eprints.utas.edu.au/cgi/export/782/XML/epprod-eprint-782.xml" title="EP3 XML" type="text/xml" />
  176.  
  177. </head>
  178. <body bgcolor="#ffffff" text="#000000" onLoad="loadRoutine(); MM_preloadImages('images/eprints/ePrints_banner_r5_c5_f2.gif','images/eprints/ePrints_banner_r5_c7_f2.gif','images/eprints/ePrints_banner_r5_c8_f2.gif','images/eprints/ePrints_banner_r5_c9_f2.gif','images/eprints/ePrints_banner_r5_c10_f2.gif','images/eprints/ePrints_banner_r5_c11_f2.gif','images/eprints/ePrints_banner_r6_c4_f2.gif')">
  179. <div class="ep_noprint"><noscript><style type="text/css">@import url(http://eprints.utas.edu.au/style/nojs.css);</style></noscript></div>
  180.  
  181.  
  182.  
  183.  
  184. <table width="795" border="0" cellspacing="0" cellpadding="0">
  185. <tr>
  186. <td><script language="JavaScript1.2">mmLoadMenus();</script>
  187. <table border="0" cellpadding="0" cellspacing="0" width="795">
  188. <!-- fwtable fwsrc="eprints_banner_final2.png" fwbase="ePrints_banner.gif" fwstyle="Dreamweaver" fwdocid = "1249563342" fwnested="0" -->
  189. <tr>
  190. <td><img src="/images/eprints/spacer.gif" width="32" height="1" border="0" alt="" /></td>
  191. <td><img src="/images/eprints/spacer.gif" width="104" height="1" border="0" alt="" /></td>
  192. <td><img src="/images/eprints/spacer.gif" width="44" height="1" border="0" alt="" /></td>
  193. <td><img src="/images/eprints/spacer.gif" width="105" height="1" border="0" alt="" /></td>
  194. <td><img src="/images/eprints/spacer.gif" width="41" height="1" border="0" alt="" /></td>
  195. <td><img src="/images/eprints/spacer.gif" width="16" height="1" border="0" alt="" /></td>
  196. <td><img src="/images/eprints/spacer.gif" width="68" height="1" border="0" alt="" /></td>
  197. <td><img src="/images/eprints/spacer.gif" width="68" height="1" border="0" alt="" /></td>
  198. <td><img src="/images/eprints/spacer.gif" width="68" height="1" border="0" alt="" /></td>
  199. <td><img src="/images/eprints/spacer.gif" width="82" height="1" border="0" alt="" /></td>
  200. <td><img src="/images/eprints/spacer.gif" width="69" height="1" border="0" alt="" /></td>
  201. <td><img src="/images/eprints/spacer.gif" width="98" height="1" border="0" alt="" /></td>
  202. <td><img src="/images/eprints/spacer.gif" width="1" height="1" border="0" alt="" /></td>
  203. </tr>
  204. <tr>
  205. <td colspan="12"><img name="ePrints_banner_r1_c1" src="/images/eprints/ePrints_banner_r1_c1.gif" width="795" height="10" border="0" alt="" /></td>
  206. <td><img src="/images/eprints/spacer.gif" width="1" height="10" border="0" alt="" /></td>
  207. </tr>
  208. <tr>
  209. <td rowspan="6"><img name="ePrints_banner_r2_c1" src="/images/eprints/ePrints_banner_r2_c1.gif" width="32" height="118" border="0" alt="" /></td>
  210. <td rowspan="5"><a href="http://www.utas.edu.au/"><img name="ePrints_banner_r2_c2" src="/images/eprints/ePrints_banner_r2_c2.gif" width="104" height="103" border="0" alt="" /></a></td>
  211. <td colspan="10"><img name="ePrints_banner_r2_c3" src="/images/eprints/ePrints_banner_r2_c3.gif" width="659" height="41" border="0" alt="" /></td>
  212. <td><img src="/images/eprints/spacer.gif" width="1" height="41" border="0" alt="" /></td>
  213. </tr>
  214. <tr>
  215. <td colspan="3"><a href="http://eprints.utas.edu.au/"><img name="ePrints_banner_r3_c3" src="/images/eprints/ePrints_banner_r3_c3.gif" width="190" height="31" border="0" alt="" /></a></td>
  216. <td rowspan="2" colspan="7"><img name="ePrints_banner_r3_c6" src="/images/eprints/ePrints_banner_r3_c6.gif" width="469" height="37" border="0" alt="" /></td>
  217. <td><img src="/images/eprints/spacer.gif" width="1" height="31" border="0" alt="" /></td>
  218. </tr>
  219. <tr>
  220. <td colspan="3"><img name="ePrints_banner_r4_c3" src="/images/eprints/ePrints_banner_r4_c3.gif" width="190" height="6" border="0" alt="" /></td>
  221. <td><img src="/images/eprints/spacer.gif" width="1" height="6" border="0" alt="" /></td>
  222. </tr>
  223. <tr>
  224. <td colspan="2"><img name="ePrints_banner_r5_c3" src="/images/eprints/ePrints_banner_r5_c3.gif" width="149" height="1" border="0" alt="" /></td>
  225. <td rowspan="2" colspan="2"><a href="/information.html" onMouseOut="MM_swapImgRestore();MM_startTimeout()" onMouseOver="MM_showMenu(window.mm_menu_0821132634_0,0,25,null,'ePrints_banner_r5_c5');MM_swapImage('ePrints_banner_r5_c5','','/images/eprints/ePrints_banner_r5_c5_f2.gif',1);"><img name="ePrints_banner_r5_c5" src="/images/eprints/ePrints_banner_r5_c5.gif" width="57" height="25" border="0" alt="About" /></a></td>
  226. <td rowspan="2"><a href="/view/" onMouseOut="MM_swapImgRestore();MM_startTimeout()" onMouseOver="MM_showMenu(window.mm_menu_0821133021_1,0,25,null,'ePrints_banner_r5_c7');MM_swapImage('ePrints_banner_r5_c7','','/images/eprints/ePrints_banner_r5_c7_f2.gif',1);"><img name="ePrints_banner_r5_c7" src="/images/eprints/ePrints_banner_r5_c7.gif" width="68" height="25" border="0" alt="Browse" /></a></td>
  227. <td rowspan="2"><a href="/perl/search/simple" onMouseOut="MM_swapImgRestore();MM_startTimeout()" onMouseOver="MM_showMenu(window.mm_menu_0821133201_2,0,25,null,'ePrints_banner_r5_c8');MM_swapImage('ePrints_banner_r5_c8','','/images/eprints/ePrints_banner_r5_c8_f2.gif',1);"><img name="ePrints_banner_r5_c8" src="/images/eprints/ePrints_banner_r5_c8.gif" width="68" height="25" border="0" alt="Search" /></a></td>
  228. <td rowspan="2"><a href="/perl/register" onMouseOut="MM_swapImgRestore();MM_startTimeout();" onMouseOver="MM_showMenu(window.mm_menu_1018171924_3,0,25,null,'ePrints_banner_r5_c9');MM_swapImage('ePrints_banner_r5_c9','','/images/eprints/ePrints_banner_r5_c9_f2.gif',1);"><img name="ePrints_banner_r5_c9" src="/images/eprints/ePrints_banner_r5_c9.gif" width="68" height="25" border="0" alt="register" /></a></td>
  229. <td rowspan="2"><a href="/perl/users/home" onMouseOut="MM_swapImgRestore();MM_startTimeout()" onMouseOver="MM_showMenu(window.mm_menu_0821133422_4,0,25,null,'ePrints_banner_r5_c10');MM_swapImage('ePrints_banner_r5_c10','','/images/eprints/ePrints_banner_r5_c10_f2.gif',1);"><img name="ePrints_banner_r5_c10" src="/images/eprints/ePrints_banner_r5_c10.gif" width="82" height="25" border="0" alt="user area" /></a></td>
  230. <td rowspan="2"><a href="/help/" onMouseOut="MM_swapImgRestore();MM_startTimeout()" onMouseOver="MM_showMenu(window.mm_menu_0821133514_5,0,25,null,'ePrints_banner_r5_c11');MM_swapImage('ePrints_banner_r5_c11','','/images/eprints/ePrints_banner_r5_c11_f2.gif',1);"><img name="ePrints_banner_r5_c11" src="/images/eprints/ePrints_banner_r5_c11.gif" width="69" height="25" border="0" alt="Help" /></a></td>
  231. <td rowspan="3" colspan="4"><img name="ePrints_banner_r5_c12" src="/images/eprints/ePrints_banner_r5_c12.gif" width="98" height="40" border="0" alt="" /></td>
  232. <td><img src="/images/eprints/spacer.gif" width="1" height="1" border="0" alt="" /></td>
  233. </tr>
  234. <tr>
  235. <td rowspan="2"><img name="ePrints_banner_r6_c3" src="/images/eprints/ePrints_banner_r6_c3.gif" width="44" height="39" border="0" alt="ePrints home" /></td>
  236. <td><a href="/" onMouseOut="MM_swapImgRestore()" onMouseOver="MM_swapImage('ePrints_banner_r6_c4','','/images/eprints/ePrints_banner_r6_c4_f2.gif',1);"><img name="ePrints_banner_r6_c4" src="/images/eprints/ePrints_banner_r6_c4.gif" width="105" height="24" border="0" alt="ePrints home" /></a></td>
  237. <td><img src="/images/eprints/spacer.gif" width="1" height="24" border="0" alt="" /></td>
  238. </tr>
  239. <tr>
  240. <td><img name="ePrints_banner_r7_c2" src="/images/eprints/ePrints_banner_r7_c2.gif" width="104" height="15" border="0" alt="" /></td>
  241. <td colspan="8"><img name="ePrints_banner_r7_c4" src="/images/eprints/ePrints_banner_r7_c4.gif" width="517" height="15" border="0" alt="" /></td>
  242. <td><img src="/images/eprints/spacer.gif" width="1" height="15" border="0" alt="" /></td>
  243. </tr>
  244. </table></td>
  245. </tr>
  246. <tr><td><table width="100%" style="font-size: 90%; border: solid 1px #ccc; padding: 3px"><tr>
  247. <td align="left"><a href="http://eprints.utas.edu.au/cgi/users/home">Login</a> | <a href="http://eprints.utas.edu.au/cgi/register">Create Account</a></td>
  248. <td align="right" style="white-space: nowrap">
  249. <form method="get" accept-charset="utf-8" action="http://eprints.utas.edu.au/cgi/search" style="display:inline">
  250. <input class="ep_tm_searchbarbox" size="20" type="text" name="q" />
  251. <input class="ep_tm_searchbarbutton" value="Search" type="submit" name="_action_search" />
  252. <input type="hidden" name="_order" value="bytitle" />
  253. <input type="hidden" name="basic_srchtype" value="ALL" />
  254. <input type="hidden" name="_satisfyall" value="ALL" />
  255. </form>
  256. </td>
  257. </tr></table></td></tr>
  258. <tr>
  259. <td class="toplinks"><!-- InstanceBeginEditable name="content" -->
  260.  
  261.  
  262. <div align="center">
  263. <table width="720" class="ep_tm_main"><tr><td align="left">
  264. <h1 class="ep_tm_pagetitle">Professional Access Control</h1>
  265. <p style="margin-bottom: 1em" class="not_ep_block"><span class="person_name">de la Motte, Leigh</span> and <span class="person_name">Hartnett, Jacky</span> (2005) <xhtml:em>Professional Access Control.</xhtml:em> In: 13th Health Informatics Conference HIC2005, 31 Jul - 02 Aug 2005, Melbourne, Australia.</p><p style="margin-bottom: 1em" class="not_ep_block"></p><table style="margin-bottom: 1em" class="not_ep_block"><tr><td valign="top" style="text-align:center"><a onmouseover="EPJS_ShowPreview( event, 'doc_preview_790' );" href="http://eprints.utas.edu.au/782/1/PAC.pdf" onmouseout="EPJS_HidePreview( event, 'doc_preview_790' );"><img alt="[img]" src="http://eprints.utas.edu.au/style/images/fileicons/application_pdf.png" class="ep_doc_icon" border="0" /></a><div class="ep_preview" id="doc_preview_790"><table><tr><td><img alt="" src="http://eprints.utas.edu.au/782/thumbnails/1/preview.png" class="ep_preview_image" border="0" /><div class="ep_preview_title">Preview</div></td></tr></table></div></td><td valign="top"><a href="http://eprints.utas.edu.au/782/1/PAC.pdf"><span class="ep_document_citation">PDF</span></a> - Requires a PDF viewer<br />462Kb</td></tr></table><div class="not_ep_block"><h2>Abstract</h2><p style="padding-bottom: 16px; text-align: left; margin: 1em auto 0em auto">Topic area and paper objectives:
  266. This paper investigates the hypotheses that it is possible to build a practical access control system
  267. for patient records within a hospital domain that ensures access to all those who are at any one time
  268. part of a particular patient's treating team yet at the same time provides appropriate barriers to
  269. access for those not currently part of this team. A caveat for this hypothesis is that at no time
  270. should a clinician be barred from access to a particular record, but that means should exist to ensure
  271. that appropriate access is accepted and inappropriate access reported upon. Central to this idea is
  272. that it should be possible to use standards of professional ethics and normal workflow to enable the
  273. model.
  274. Background and concise literature review:
  275. Traditional models of access control do not cope well with the problem of how to define access
  276. permissions for a team that is dynamic in nature (as is a treating team) and where the access is to
  277. objects (patient records) only in the loosest 'owned' by those who have a need to access such
  278. objects. In these models either the system administrator has to define permitted access in advance
  279. (mandatory access control) or the owner of the data can define the permitted accesses (discretionary
  280. access control) (Pfleeger 2000). Extensions to Role Based Access Control (RBAC) and Team
  281. Based Access Control (TMAC) have provided the most useful solutions to date but still require a
  282. system administrator or surrogate to define appropriate access in advance. (Ferraiolo &amp; Kuhn 1992)
  283. (Ramaswamy &amp; Sandhu 1998) (NIST 2004) (Thomas 1997) (Georgiadis et al 2001) (Georgiadis
  284. 2002) However, work by Thomas &amp; Sandhu (1997) and Alotaiby &amp; Chen (2004) has shown that it
  285. is possible to incorporate changes to access privileges as part of normal workflow.
  286. Methods:
  287. As a result of observing and discussing normal and unusual workflow patterns within the
  288. Tasmanian hospital environment a set of scenarios were developed each of which characterised a
  289. unique instance of change to whom should be able to access a patient record. The method used by
  290. current access control models to handle each scenario was then analysed. A new definition of a
  291. team in a hospital environment was then used to develop the Professional Access control (PAC)
  292. model that was implemented and tested in Oracle. Testing was carried out using each scenario in a
  293. simulated hospital of 3 wards, 20 staff and 20 patients.
  294. Results and discussions:
  295. Clinicians at a hospital were defined as either being Members: part of a patient's treating team,
  296. Colleagues: having the same role and belonging to the same unit as the patient or Associates: part of
  297. the hospital but not currently related to the patient. Being a team Member can be adjusted as part of
  298. the normal hospital admission and referral processes. Emergency access is provided subject to
  299. retrospective approval and auditing procedures. The model has been developed as an Oracle
  300. implementation for a simulated hospital environment and tested against the 24 scenarios defined.
  301. The Professional Access Control model allows for dynamic definition of the treating team and
  302. facilitates guaranteed availability to clinicians appropriate to their relationship to a patient. This is
  303. made possible by relying upon the professional ethics of clinicians rather than those of system
  304. administrators. It relieves the burden of predefining access control from system administrators
  305. without endowing clinicians with unnecessary system administration privileges.</p></div><table style="margin-bottom: 1em" cellpadding="3" class="not_ep_block" border="0"><tr><th valign="top" class="ep_row">Item Type:</th><td valign="top" class="ep_row">Conference or Workshop Item (Paper)</td></tr><tr><th valign="top" class="ep_row">Keywords:</th><td valign="top" class="ep_row">Health Informatics, Access Control, Computer Security, Roles, Medical Records</td></tr><tr><th valign="top" class="ep_row">Subjects:</th><td valign="top" class="ep_row"><a href="http://eprints.utas.edu.au/view/subjects/280103.html">280000 Information, Computing and Communication Sciences &gt; 280100 Information Systems &gt; 280103 Information Storage, Retrieval and Management</a></td></tr><tr><th valign="top" class="ep_row">ID Code:</th><td valign="top" class="ep_row">782</td></tr><tr><th valign="top" class="ep_row">Deposited By:</th><td valign="top" class="ep_row"><span class="ep_name_citation"><span class="person_name">Mr Leigh de la Motte</span></span></td></tr><tr><th valign="top" class="ep_row">Deposited On:</th><td valign="top" class="ep_row">19 Feb 2007</td></tr><tr><th valign="top" class="ep_row">Last Modified:</th><td valign="top" class="ep_row">09 Jan 2008 02:30</td></tr><tr><th valign="top" class="ep_row">ePrint Statistics:</th><td valign="top" class="ep_row"><a target="ePrintStats" href="/es/index.php?action=show_detail_eprint;id=782;">View statistics for this ePrint</a></td></tr></table><p align="right">Repository Staff Only: <a href="http://eprints.utas.edu.au/cgi/users/home?screen=EPrint::View&amp;eprintid=782">item control page</a></p>
  306. </td></tr></table>
  307. </div>
  308.  
  309.  
  310.  
  311. <!-- InstanceEndEditable --></td>
  312. </tr>
  313. <tr>
  314. <td><!-- #BeginLibraryItem "/Library/footer_eprints.lbi" -->
  315. <table width="795" border="0" align="left" cellpadding="0" class="footer">
  316. <tr valign="top">
  317. <td colspan="2"><div align="center"><a href="http://www.utas.edu.au">UTAS home</a> | <a href="http://www.utas.edu.au/library/">Library home</a> | <a href="/">ePrints home</a> | <a href="/contact.html">contact</a> | <a href="/information.html">about</a> | <a href="/view/">browse</a> | <a href="/perl/search/simple">search</a> | <a href="/perl/register">register</a> | <a href="/perl/users/home">user area</a> | <a href="/help/">help</a></div><br /></td>
  318. </tr>
  319. <tr><td colspan="2"><p><img src="/images/eprints/footerline.gif" width="100%" height="4" /></p></td></tr>
  320. <tr valign="top">
  321. <td width="68%" class="footer">Authorised by the University Librarian<br />
  322. © University of Tasmania ABN 30 764 374 782<br />
  323. <a href="http://www.utas.edu.au/cricos/">CRICOS Provider Code 00586B</a> | <a href="http://www.utas.edu.au/copyright/copyright_disclaimers.html">Copyright &amp; Disclaimers</a> | <a href="http://www.utas.edu.au/accessibility/index.html">Accessibility</a> | <a href="http://eprints.utas.edu.au/feedback/">Site Feedback</a>  </td>
  324. <td width="32%"><div align="right">
  325. <p align="right" class="NoPrint"><a href="http://www.utas.edu.au/"><img src="http://www.utas.edu.au/shared/logos/unioftasstrip.gif" alt="University of Tasmania Home Page" width="260" height="16" border="0" align="right" /></a></p>
  326. <p align="right" class="NoPrint"><a href="http://www.utas.edu.au/"><br />
  327. </a></p>
  328. </div></td>
  329. </tr>
  330. <tr valign="top">
  331. <td><p>  </p></td>
  332. <td><div align="right"><span class="NoPrint"><a href="http://www.eprints.org/software/"><img src="/images/eprintslogo.gif" alt="ePrints logo" width="77" height="29" border="0" align="bottom" /></a></span></div></td>
  333. </tr>
  334. </table>
  335. <!-- #EndLibraryItem -->
  336. <div align="center"></div></td>
  337. </tr>
  338. </table>
  339.  
  340. </body>
  341. </html>