1 / 74

Mobile Blood Donation Registration Service: Security and Privacy Issues

Mobile Blood Donation Registration Service: Security and Privacy Issues. Presented by Patrick C. K. Hung Faculty of Business and IT University of Ontario Institute of Technology (UOIT) Canada. Salute. Prof. Ho-Fung Leung (CUHK, Hong Kong)

kadeem
Download Presentation

Mobile Blood Donation Registration Service: Security and Privacy Issues

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Mobile Blood Donation Registration Service: Security and Privacy Issues Presented by Patrick C. K. Hung Faculty of Business and IT University of Ontario Institute of Technology (UOIT) Canada

  2. Salute • Prof. Ho-Fung Leung (CUHK, Hong Kong) • Dr. C. K. Lee (Hong Kong Blood Transfusion Service, Hong Kong) • Prof. Jay Tashiro (UOIT, Canada and Wolfsongs Informatics, USA) • Prof. Wendy Hui (University of Nottingham Ningbo, Ningbo) • Prof. Michael Chau (HKU, Hong Kong) • Dr. Lalita Narupiyakul (UOIT, Canada) • Mr. Frenco Cheung (CUHK, Hong Kong) • Mr. Mars Yim (CUHK, Hong Kong) • Mr. Matthias Farwick (University of Innsbruck, Austria) • Mr. Kai-kin Chan (Baptist U, Hong Kong) • Mr. Thomas Trojer (University of Innsbruck, Austria) • Ms. Michelle Watson (UOIT, Canada) • Ms. Stephanie Chow (UOIT, Canada) • Mr. Ryan Bishop (UOIT, Canada)

  3. Outline • Blood Donation Registration • XML Technology • Security and Privacy Issues • Our System • Pilot Tests • Demonstration • Future Work • Q&A

  4. Blood Donation Registration Blood Donation Procedure Objective Blood Donation Form Electronic Blood Donation Form

  5. Blood Donation Procedures • Personal data • Health history enquiry • Haemoglobin test and blood pressure checking • Interviewed by nurse • Blood donation

  6. Objective • Minimize drop out blood donors • Maximize return blood donors • Reduce time and human error • Keep contact with blood donors • Promote blood donation events • Provide visualize education about blood donation • Maximize blood donation services

  7. Blood Donation Form

  8. Blood Donation Form (cont’d)

  9. Electronic Blood Donation Form

  10. Electronic Blood Donation Form (cont’d)

  11. XML Technology XML XML Schema Extensible Stylesheet Language Web Service Web Service Description Language Simple Object Access Protocol Service Oriented Architecture Semantic Web – OWL, SWRL

  12. XML: eXtensible Markup Language • A general-purpose specification for creating custom markup languages. • Allow users to define their own elements. • Facilitate the sharing of structured data across different information systems • Used to encode documents and to serialize data XML <Staff> <Name> <FirstName> Adam </FirstName> <LastName> Smith </LastName> </Name> <Login> asmith </Login> <Ext> 1765 </Ext> </Staff> Traditional Database or Spreadsheet Adam, Smith, asmith, 1765, John, Smith, jsmith, 1234, ...

  13. XML Example

  14. XML Schema • A description of a type of XML document • Express in terms of constraints on the structure and content of documents • Example of XML schema

  15. Extensible Stylesheet Language(XSL) • A family of transformation languages • XSL Transformations, XSL Formatting Objects and XML Path Language • XSL Transformations (XSLT): an XML language for transforming XML documents • Describe how to format or transform files encoded in the XML standard

  16. XSLT Example

  17. Web Service W3C Definition of a Web Service • has a unique Uniform Resource Identifier (URI) http://en.wikipedia.org/wiki/Uniform_Resource_Identifier • can be defined, described, and discovered using XML • supports exchange of XML messages via Internet-based protocols Supported by all major computing companies, e.g., IBM, Microsoft, Sun Java, and etc.

  18. Web Service Description Language Web Services Description Language (WSDL) describes the Web service’s interface: • what operations the Web service supports • what protocols to use • how the data exchanged should be packed The WSDL document is a contract between the service requestor and provider.

  19. Simple Object Access Protocol Simple Object Access Protocol (SOAP) is an XML-based messaging protocol. SOAP is independent of the underlying transport protocol: • HTTP • SMTP • FTP.

  20. Service Oriented Architecture Optional BUSI 2501U E-Business Tech. - Winter 2008

  21. Semantic Web – OWL, SWRL • The Semantic Web is a web that is able to describe things in a way that computer applications can understand • Ontology Web Lanuage (OWL) is a language for defining and instantiating Web ontology • Ontology refers to the science of describing the kinds of entities in the world and how they are related • Semantic Web Rule Language (SWRL) is a language for defining the relationship between instances on OWL

  22. Health Level 7 (HL7) • Formed in the United States in 1987 • One of several American National Standards Institute (ANSI) • "Level Seven" • Refer to the highest level of the International Organization for Standardization (ISO) communications model for Open Systems Interconnection (OSI) • Application level • Who needs HL7 • Hospitals, doctors, nurses and health care practitioners • Require the ability to send and receive healthcare data • Ex. patients information, lab reports and test results www.hl7.org

  23. Clinical Document Architecture (CDA) • HL7 is in the XML platform • Version 3.0 • Provide XML schema as standard • Clinical Document Architecture (CDA)‏ • Version 2.0 • Standard for the clinical document • Schemas for recording clinical events in documents • Composed of 2 main parts • Header: Patient information, Document information, Confidential level, Time stamp • Body: Medical background, Physical examination, Image, Video

  24. Security and Privacy Issues Literature Review Privacy Access Control Threat Modeling

  25. Literature Review Adapted from Blobel, B. and F. Roger-France. (2001). A systematic approach for analysis and design of secure health information systems. International Journal of Medical Informatics, Volume 62, Number 1, pp. 51-78.

  26. Literature Review (cont.) Adapted from Blobel, B. and F. Roger-France. (2001). A systematic approach for analysis and design of secure health information systems. International Journal of Medical Informatics, Volume 62, Number 1, pp. 51-78.

  27. Literature Review (cont.) • “Preserve donor privacy by restricting access to donor data to authorized Red Cross personnel” • “Protect the integrity of donor data” • “Protect the integrity of usage data” Integrity Confidentiality Availability • “Maintain availability of communication paths” • “Maintain availability of web service server”

  28. Privacy • “Privacy is the ability of an individual or group to stopinformation about themselves from becoming known to people other than those they choose to give the information to.” • http://en.wikipedia.org/wiki/Privacy • “All persons have a fundamental right to privacy, and hence to have control over the collection, storage, access, communication, manipulation and disposition of data about themselves.” • International Medical Informatics Association (IMIA)

  29. Access Control Role Based Access Control (RBAC) American National Standard 359-2004 is the Information Technology industry consensus standard for RBAC Adapted from: David F. Ferraiolo, Ravi Sandhu, Serban Gavrila, D. Richard Kuhn and RamaswamyChandramouli, “Proposed NIST Standard for Role-Based Access Control, ACM Transactions on Information and Systems Security (TISSEC),” Volume 4, Number 3, August 2001.

  30. Access Control (cont.) • eXtensible Access Control Markup Language (XACML) • Allow administrators to define the access control requirements for their application resources • Support data types, functions, and combining logic • Allow complex (or simple) rules to be defined • XACML privacy profile • Includes an access decision language • used to represent the runtime request for a resource • When a policy is located which protects a resource • The functions compare attributes in the request against attributes contained in the policy rules ultimately yielding a permit or deny decision

  31. Access Control (cont.)

  32. Access Control (cont.) • GEO-Privacy • Extend GEO-Privacy with complex constraints like „Two Eyes Principle“, or role-location conflicts • Create a prototypical implementation using XACML and the IPhone‘s location API UsersU RPOS Rs Obligations Purposes SessionUsers UserRole Instance Assignment SES Ri OPS Obj Session roles SPATIAL ROLES Enabled Session Roles Conditions Retentions

  33. Threat Modeling

  34. Threat Modeling (cont.) Man-in-the-middle

  35. Threat Modeling (cont.)

  36. Our system Overview of the System Architecture of the System User Interface - JavaServer Face Web Service-based SOA

  37. Overview of the System Privacy & Security User Interface Network Linux • Connectivity • Private Wireless Network • LAN • GUI • JSF • XML Security • Apache Rampart • Open Source • Tomcat 6 • Axis2 • WASA • eXist

  38. Overview of the System (cond’t)

  39. Overview of the System (cond’t)

  40. Overview of the System (cond’t)

  41. Architecture of the System

  42. User Interface - JavaServer Face • J2EE Model View Controller Pattern (MVC) for the Web • Integrated validation of user input • Integrated dynamic page flow support • Ajax add-ons for dynamic behavior (i.e. progress bars, dynamic highlighting, etc)‏ • Server-side Java classes make integration with Web Services easily

  43. Web Service-based SOA • Software-Oriented Architecture • Used for businesses to communicate with each other • Allow organizations to communicate data without intimate knowledge of each other's IT systems behind the firewall

  44. Pilot Test The Hong Kong Red Cross Blood Donation Center

  45. Blood Donation Station Set-up • Server – Lenovo Laptop(OS: Linux) • Client side (Mobile Devices) – Asus EeePC • Red Cross side – our own notebook

  46. November 28, 2009 – King’s Park

  47. Result and Feedback • 1st pilot test (on 9th August): • Fail to send the finished form from client to server • Unsatisfied reaction time for the interface • 2nd pilot test (on 6th November): • Connection failure between the mobile devices and the server • Input interrupted • A non-styled e-form occurred • 3rd pilot test (on 26th November): • Everything running smoothly

  48. Result and Feedback (cont.) • 4th pilot test (on 15th December): • Testing the Tablet PC with touch screen • General feedback from the users: • Satisfactory on learning how to use the system • Prefer to use the paper form (but this may depend on the age groups of the users and other reasons) • Agree that this system can help in shortening the waiting time for blood donation • Prefer to use the touch screen

  49. Demonstration Video Demonstrations

  50. Client Side

More Related