SLIDE 1
Asim, M.
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
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 ., - - 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
SLIDE 2
SLIDE 3
Asim, M.
3
Continua Health Alliance
Interoperable personal tele-health
SLIDE 4
Asim, M.
4
Continua E2E Architecture
Application Hosting Device (AHD)
PAN Device
LAN Device WAN Device
Health Record (HRN) Device
PAN-IF LAN-IF WAN-IF Disease Management Organization (DMO) PHRs/EHRs HRN-IF Physician EMRs
care profs
Health Record (HRN) Device PAN Device
SLIDE 5
Asim, M.
5
- TLS
- IHE XDM à S-MIME
- IHE ATNA
- WS-I BSP à TLS v1.0
- WS-I BSP à
WS-Security Header + SAML 2.0
- IHE ATNA
- Zigbee security
- Bluetooth security
Security in Continua 2010 specification
WAN-IF Application Hosting Device PAN Device PAN-IF LAN Device LAN-IF HRN-IF WAN Device HR Device
* * * * * * * *
confidentiality + integrity auditability confidentiality + integrity authentication auditability confidentiality + integrity authentication + confidentiality
SLIDE 6
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
- n data collection/use, transparency
– Ability to specify and revoke consent preferences – Enforcement of patient consent along the care path
SLIDE 7
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
SLIDE 8
Asim, M.
8
Alice is presented with a default consent policy: Nurse@DMO may disclose her information to Dr. Bob for the purpose of treatment.
Specification of patient consent
Patient- Alice
SLIDE 9
Asim, M.
9
Privacy Policy Reference Consent specification
- allow/disallow action
- purpose of consent
- effective period
- additional conditions
Information Sender
- Organization
Information Receiver
- Role
- Identity
Health Information Affected
- Related to a diagnosis
- Data Sensitivity
- Coverage Type
- Type of information (e.g., results)
Medical Record Reference
- Patient Identification
- Medical Record Identification
Action Specification
- hierarchy of operations applied to information
Consent Directive Analysis Model
SLIDE 10
Asim, M. 10
Consent Directives Reference in CDA Doc
SLIDE 11
Asim, M.
Design for the consent management at the HRN-IF
11
Provide(Health Document , Patient Consent Document (optional) ) HRN Sender HRN Receiver Retrieve(Patient Consent Document, Requestor Token) Query(Patient Consent Document) Response(Patient Consent Document ) Query Response
(a) (b) Consent management at the HRN interface
SLIDE 12
Asim, M.
12