end to end security for personal
play

End-to-End Security for Personal Telehealth Asim, M., Koster, P ., - PowerPoint PPT Presentation

End-to-End Security for Personal Telehealth Asim, M., Koster, P ., Petkovic, M. Healthcare Information Management, Philips Research Europe Outline Introduction to Continua Continua E2E architecture Security in Continua 2010


  1. End-to-End Security for Personal Telehealth Asim, M., Koster, P ., Petkovic, M. Healthcare Information Management, Philips Research Europe

  2. Outline • Introduction to Continua • Continua E2E architecture • Security in Continua 2010 specifications • E2E security and privacy requirements • Consent management in the Continua architecture • Conclusions 2 Asim, M.

  3. Continua Health Alliance Interoperable personal tele-health 3 Asim, M.

  4. Continua E2E Architecture Health Record PAN Device PAN Device Application WAN Device Health Record (HRN) Device Hosting Device (HRN) Device (AHD) PAN-IF WAN-IF HRN-IF PHRs/EHRs LAN Device Disease LAN-IF care Management profs Organization (DMO) Physician EMRs 4 Asim, M.

  5. Security in Continua 2010 specification confidentiality + integrity • TLS • IHE XDM à S-MIME HR auditability • IHE ATNA Device * HRN-IF * WAN confidentiality + integrity • WS-I BSP à TLS v1.0 Device authentication • WS-I BSP à * WS-Security Header + SAML 2.0 WAN-IF auditability • IHE ATNA * Application Hosting Device confidentiality • Zigbee security * * + integrity PAN-IF LAN-IF * * PAN LAN Device Device authentication + • Bluetooth security confidentiality 5 Asim, M.

  6. E2E security and privacy requirements • Identity management – Unambiguously linking measurements to the patient – Interoperable protocols for identity linkage and cross-referencing • Integrity and data origin authentication – Measurements are being taken in an uncontrolled environment – Authenticate data sources e.g. users and devices – Prevent or detect unauthorized data modification • Consent management – Patient expectation? (Participation, accountability, specification of purpose , limits on data collection/use, transparency – Ability to specify and revoke consent preferences – Enforcement of patient consent along the care path 6 Asim, M.

  7. Design for the consent management at the HRN-IF • Specification of consent • Consent Directive as CDA document – Implementation Guide for HL7 CDA R2 Consent Directive • Semantically interoperable • Encoded using standard terminology • Successor to the IHE BPPC (Basic Patient Privacy Consent) profile 7 Asim, M.

  8. Specification of patient consent Patient- Alice Alice is presented with a default consent policy: Nurse@DMO may disclose her information to Dr. Bob for the purpose of treatment. 8 Asim, M.

  9. Consent Directive Analysis Model Consent specification - allow/disallow action - purpose of consent Medical Record Reference Privacy Policy - effective period - Patient Identification Reference - additional conditions - Medical Record Identification Action Specification - hierarchy of operations applied to information Information Sender Health Information Affected - Organization Information Receiver - Related to a diagnosis - Role - Data Sensitivity - Coverage Type - Identity - Type of information (e.g., results) 9 Asim, M.

  10. Consent Directives Reference in CDA Doc 10 Asim, M.

  11. Design for the consent management at the HRN-IF HRN Sender HRN Receiver Provide(Health Document , Patient Consent Document (optional) ) (a) Query(Patient Consent Document) Query Response (b) Retrieve(Patient Consent Document, Requestor Token) Response(Patient Consent Document ) Consent management at the HRN interface 11 Asim, M.

  12. Questions 12 Asim, M.

Recommend


More recommend