“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review August 13, 2013 Presented by: Michael Dufel and David Staggs Jericho Systems Corporation.

Slides:



Advertisements
Similar presentations
Georgia Department of Community Health
Advertisements

Cross Community (XC) Profiles Karen Witting. Outline Vision – as described in 2006 IHE White Paper on Cross Community Exchange Existing – what has been.
September, 2005What IHE Delivers 1 Karen Witting IBM Cross-Community: Peer- to-Peer sharing of healthcare information.
S&I Framework Testing HL7 V2 Lab Results Interface and RI Pilot Robert Snelick National Institute of Standards and Technology June 23 rd, 2011 Contact:
Electronic Submission of Medical Documentation (esMD) Face to Face Informational Session esMD Requirements, Priorities and Potential Workgroups – 2:00pm.
S&I Framework Provider Directories Initiative esMD Work Group October 19, 2011.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review September 17, 2013 Presented by: David Staggs and Michael Dufel Jericho Systems Corporation.
NHIN Direct Project Communications Work Group Message for State HIE/RECs August 30, 2010.
NHIN Specifications Richard Kernan, NHIN Specification Lead (Contractor), Office of the National Coordinator for Health IT Karen Witting, Contractor to.
AHCCCS/ASU Clinical Data Project March 17 th, 2009 Arizona Health Care Cost Containment Health System Medicaid Transformation Grant Program.
Query Health Business Working Group Kick-Off September 8, 2011.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
S New Security Developments in DICOM Lawrence Tarbox, Ph.D Chair, DICOM WG 14 (Security) Siemens Corporate Research.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review June 18, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review July 9, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review July 16, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
Configuration Management Issues in IHE Asuman Dogac, SRDC, METU, Turkey
1.View Description 2.Primary Presentation 3.Element Catalog Elements and Their Properties Relations and Their Properties Element Interfaces Element Behavior.
Cross-Enterprise User Assertion IHE Educational Workshop 2007 Cross-Enterprise User Assertion IHE Educational Workshop 2007 John F. Moehrke GE Healthcare.
Query Health Operations Workgroup HQMF & QRDA Query Format - Results Format February 9, :00am – 12:00am ET.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review April 9, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
VA-SAMHSA DS4P Pilot – Phase 2 HIMSS13 Sprint 4 VA Activities Pilot Project Partnership VA SAMHSA Jericho Systems MITRE HIPAAT Data Segmentation for Privacy.
S&I Public Health * We will start the meeting 3 min after the hour October 7 th, 2014.
OpenPASS Open Privacy, Access and Security Services “Quis custodiet ipsos custodes?”
Connecting for Health: Common Framework. 2 What is Connecting for Health? Broad-based, public-private coalition More than 100 collaborators –Providers.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review April 23, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Overview of IHE IT Infrastructure Patient Synchronized Applications.
Data Segmentation for Privacy Agenda All-hands Workgroup Meeting May 9, 2012.
Public Health Data Standards Consortium
“Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review April 16, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
Dynamic Document Sharing Detailed Profile Proposal for 2010 presented to the IT Infrastructure Technical Committee Karen Witting November 10, 2009.
0 Connectathon 2009 Registration Bob Yencha Webinar | August 28, 2008 enabling healthcare interoperability.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review August 27, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
Key Issues of Interoperability in eHealth Asuman Dogac, Marco Eichelberg, Tuncay Namli, Ozgur Kilic, Gokce B. Laleci IST RIDE Project.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review May 7, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review May 14, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
Data Provenance Community Meeting November 6, 2014.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
1 Healthcare Information Technology Standards Panel Care Delivery - IS01 Electronic Health Record (EHR) Laboratory Results Reporting July 6, 2007.
Ongoing/Planned Activities for Week of 4/29 Final UCR Crosswalk due COB 4/30 Hold two working sessions to complete UCR Crosswalk on 4/30 Hold working session.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review May 21, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
Health Delivery Services May 29, Eastern Massachusetts Healthcare Initiative Policy Work Group Session 2 May 29, 2009.
1 IHE ITI White Paper on Authorization Rough Cut Implementation Opportunities for BPPC Dr. Jörg Caumanns, Raik Kuhlisch, Olaf Rode Berlin,
Data Provenance Community Kick Off April 24 th, 2014.
The Patient Choice Project Project Kickoff December 14 th, 2015.
Ongoing/Planned Activities for Week of 4/22 Initial feedback on UCR Crosswalk due COB 4/23 Hold working session to continue filling out the UCR Crosswalk.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review June 25, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
Data Provenance Community Meeting May 15 th, 2014.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review June 4, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
Ongoing/Planned Activities for Week of 4/29 Final UCR Crosswalk due COB 4/30 Hold two working sessions to complete UCR Crosswalk on 4/30 Hold working session.
The Patient Choice Project Use Case Working Session January 8 th, 2016.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review May 28, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
Data Access Framework All Hands Community Meeting April 9, 2014.
Data Access Framework All Hands Community Meeting March 5, 2014.
The Patient Choice Project Use Case Working Session February 12 th, 2016.
The Patient Choice Project Use Case Working Session February 5 th, 2016.
The Patient Choice Project Use Case Working Session January 29 th, 2016.
PCOR Privacy and Security Research Scenario Initiative and Legal Analysis and Ethics Framework Development Welcome and Please Sign In »Please sign into.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review April 30, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
Health eDecisions (HeD) All Hands Meeting February 21st, 2013.
Cross Community Access Profile Karen Witting IBM Co-chair ITI technical committee.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review June 11, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review November 5, 2013 Presented by: David Staggs JD, CISSP Jericho Systems Corporation.
PCOR Privacy and Security Research Scenario Initiative and Legal Analysis and Ethics Framework Development Welcome and Please Sign In »Please sign into.
HIT Standards Committee NwHIN Power Team Dixie Baker, Chair July 20,
Structured Data Capture (SDC) FHIR SDC Pilots Template
EHR System Function and Information Model (EHR-S FIM based on EHR-S FM R2.0) CPS.9.4 Standard Report Generation aka S in EHR-S FM R1.1
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) AS.4.1 Manage Registry Communication aka S.1.1 in EHR-S FM R1.1
Overview of CRISP Connectivity Process
US Core Data for Interoperability (USCDI): Data Provenance IG
Presentation transcript:

“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review August 13, 2013 Presented by: Michael Dufel and David Staggs Jericho Systems Corporation

208/13/2013 Agenda Administrative issues Pilot scope Today’s Demonstration Pilot data flow Familiarization with the Universal Client Viewing audit records Changing PCD Demo Discussion Pilot Timeline Questions Plan of Action

308/13/2013 Pilot Administrivia This pilot is a community led pilot –Limited support provided by the ONC Zachary May (ESAC) Jeanne Burton (Security Risk Solutions) Libbie Buchele and Penelope Hughes (ONC) In conjunction with DS4P bi-weekly return of an All Hands meeting Access to DS4P Wiki, teleconference, and calendar Meeting times: Tuesdays 11AM (ET) –Dial In: Access code: URL: d= d=

408/13/2013 Scope of the Pilot 1.Define the exchange of HL7 CDA-compliant PCD between a data custodian and a PCD repository that includes a report on the outcome of the request back to the healthcare consumer. 2.Additional goal: use of identifiers that can uniquely identify the healthcare consumer and PCD repository used to report the outcome of the request back to the healthcare consumer by healthcare consumer’s provider and subsequent EHR custodians. 3.Stretch goal: mask and/or redact the clinical document based on PCD choices retrieved from the PCD repository. 4.Stretch goal: use of the PCD repository as a proxy allowing direct authentication by the healthcare consumer to the provider, subsequently reducing correlation errors.

508/13/2013 Today’s Demonstration 1.Use Universal Client to send NwHIN messages –Patient Discovery (ITI-55), Query for Documents (ITI-38), and Request Document (ITI-39). 2.Demonstrate consent based on recipient and patient consent directive (retrieved from a PCD repository) –Show result of different policies: 1 st requestor v. 2 nd requestor 3.Demonstrate PCD applied by 1 st requestor –1 st requestor retrieves document 2 nd requestor requests from 1 st requestor 4. Demonstrate consent based on purpose of use –change policy from “treatment” to “research” where request uses “research” attribute each time.

608/13/2013 Pilot Data Flow Custodian of Data being Provided at  Patient PCD Repository 2 nd Requestor 1 st Requestor   B ,  = Clinical data A,B = PCD data = audit record And Subsequent Custodian of Data being Provided at 

708/13/2013 Universal Client Orientation 1 1st Requestor starts CONNECT Universal Client

808/13/2013 Universal Client Orientation 2 1st Requestor sees local matching patients

908/13/2013 Universal Client Orientation 3 1st Requestor first time at “Patient Correlations” tab

1008/13/2013 Universal Client Orientation 4 1st Requestor completes “patient discovery” (ITI-55) (ITI-55)

1108/13/2013 Universal Client Orientation 5 1st Requestor first time at “Documents” tab

1208/13/2013 Universal Client Orientation 5 1st Requestor completes “request for documents” (ITI-38) (ITI-38)

1308/13/2013 Universal Client Orientation 5 1st Requestor retrieves document from primary custodian (ITI-39) (ITI-39)

1408/13/2013 Reviewing Audit Records

1508/13/2013 Changing PCD

Live Demo 08/13/201316

1708/13/2013 Discussion Lessons learned from current demonstration: o Communicating use of the Universal Client o Local demographic data o Patient Discovery (ITI-55), Query for Documents (ITI-38), and Request Document (ITI-39). o Communicating use of the PCD repository o Communicating use of OpenATNA Audit Message Viewer o Communicating how PCD is changed and the affects o Unexpected benefits/problems

1808/13/2013 Pilot Timeline General Timeline, conditioned on agreement of stakeholders

1908/13/2013 Questions? What do the consent directives look like? How is the PCD identifiers encoded into the clinical document? What happens if 1 st requestor has a different PCD repository for the subject of the clinical document?

20 Plan of Action Upon agreement of the participants the POA is: Identify the elements available from previous DS4P pilots Scope level of effort, decide on extended scenario Determine first draft of functional requirements Review standards available for returning information on requests Determine any gaps or extensions required in standards Stand up information holders and requestors Create XDS.b repository holding PCD Identify remaining pieces Document and update IG with results of our experience 08/13/2013

2108/13/2013 Backup Slides

DS4P Standards Material Location of DS4P Standards Inventory: Location of DS4P Standards Mapping Issues: xlsx/ /Copy%20of%20DataMappingsIssues% xlsx General Standards Source List: %20Analysis.xlsx/ /General%20SI%20Framework%20Standards%20A nalysis.xlsx Standards Crosswalk Analysis monizationhttp://wiki.siframework.org/Data+Segmentation+for+Privacy+Standards+and+Har monization (at bottom of page, exportable) Implementation Guidance 20Guidance_consensus_v1_0_4.pdf/ /Data%20Segmentation%20Impl ementation%20Guidance_consensus_v1_0_4.pdf 08/13/201322

2308/13/2013 DS4P References Use Case: ases ases Implementation Guide: nsensus nsensus Pilots Wiki Page: +Pilots+Sub-Workgroup +Pilots+Sub-Workgroup

2408/13/2013 Pilot Data Flow Custodian of Data being Provided at  Patient PCD Repository 2 nd Requestor 1 st Requestor   B ,  = Clinical data A,B = PCD data = audit record And Subsequent Custodian of Data being Provided at 

2508/13/2013 Pilot Data Flow Custodian of Data being Provided at  Patient PCD Repository 2 nd Requestor 1 st Requestor Clinical exchange #  Clinical exchange #  B ,  = Clinical data A,B = PCD data = audit record And Subsequent Custodian of Data being Provided at  Fetch PCD Send audit

2608/13/2013 Pilot Data Flow (1) Custodian of Data being Provided at  Patient PCD Repository 2 nd Requestor 1 st Requestor  ,  = Clinical data A,B = PCD data = audit record

2708/13/2013 Pilot Data Flow (2) Custodian of Data being Provided at  Patient PCD Repository 2 nd Requestor 1 st Requestor  ,  = Clinical data A,B = PCD data = audit record

2808/13/2013 Pilot Data Flow (3) Custodian of Data being Provided at  Patient PCD Repository 2 nd Requestor 1 st Requestor  B ,  = Clinical data A,B = PCD data = audit record And Subsequent Custodian of Data being Provided at 

2908/13/2013 Pilot Data Flow (4) Custodian of Data being Provided at  Patient PCD Repository 2 nd Requestor 1 st Requestor  ,  = Clinical data A,B = PCD data = audit record And Subsequent Custodian of Data being Provided at 

3008/13/2013 Pilot Data Flow (5) Custodian of Data being Provided at  Patient PCD Repository 2 nd Requestor 1 st Requestor ,  = Clinical data A,B = PCD data = audit record And Subsequent Custodian of Data being Provided at 

3108/13/2013 Pilot Data Flow (updated) Custodian of Data being Provided at  Patient PCD Repository 2 nd Requestor 1 st Requestor   B ,  = Clinical data A,B = PCD data = audit record And Subsequent Custodian of Data being Provided at 