1 / 9

Enforceable Specification of Privacy

Enforceable Specification of Privacy. Peter Mork Jean Stanford. CEM IR&D. Problem. Growing need for Health Information Exchange Continuity of care Decreased costs Public health reporting Facilitate clinical research Health Information Exchange requires patient consent: Paper-based

chanel
Download Presentation

Enforceable Specification of Privacy

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. Enforceable Specification of Privacy Peter MorkJean Stanford CEM IR&D

  2. Problem • Growing need for Health Information Exchange • Continuity of care • Decreased costs • Public health reporting • Facilitate clinical research • Health Information Exchange requires patient consent: • Paper-based • One form per transaction • Non-transferrable • Signed with limited time to think

  3. Background DoD VA Paper consent forms prevent seamless health information exchange

  4. Objective • Support Meaningful & Granular Patient Consent • Globally Accessible by: • Patients and • Record Holders • Platform Adaptable • Modular Design adapts to: • Technology Changes • Legal Changes

  5. Activities • Developed rules language for consent: • Basic constructs = purpose, topics, datatypes, time, etc. • Two forms of negation • Terminological hierarchies • Reusable knowledge components • Policy reasoner: • Input = Patient preferences + request • Output = Minimized rule tree • Policy enforcement: • Conversion to XACML • Prototype of EHR with XACML engine

  6. Highlight Request Server (e.g., hData) Browser Record Holder Server Consent Server EHR Policy Enforcer Consent DB Policy Reasoner

  7. Demonstration Dr. Walsh: Purpose = Treatment (Medications or Allergies) and not Mental Health

  8. Impacts • Sponsor Engagements: • Office of the National Coordinator • Substance Abuse and Mental Health Services Administration • Department of Veteran’s Affairs • Other Engagements: • Healthcare Information and Management Systems Society • GE Healthcare • United Health • Open Source: • https://sourceforge.net/projects/kaironconsents/

  9. Future Plans High Integrate with State Mandates Automated Enforcement Intelligent Redaction Eliciting Patient Preferences Integrate Care Relationships Implemented Technical Complexity Under Development Patient Review & Approve Grand Challenges Credential Matching Preemptory Access Audit Low Accepted Practices Policy Maturity Inchoate

More Related