737. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 6/9/2017 3:46:04 PM Eastern Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.

737.1 Files compared

# Location File Last Modified
1 eHealth_Exch (eHealth Exchange Enhancements) Build 3 docs & code_May_2017.zip\eHXE_Build3_2017-05-04.zip\NHIN_adapter\Docs Purpose Of Use Analysis-Adapter.xlsx Mon Feb 13 21:09:32 2017 UTC
2 eHealth_Exch (eHealth Exchange Enhancements) Build 3 docs & code_May_2017.zip\eHXE_Build3_2017-05-04.zip\NHIN_adapter\Docs Purpose Of Use Analysis-Adapter.xlsx Mon Jun 5 03:02:08 2017 UTC

737.2 Comparison summary

Description Between
Files 1 and 2
Text Blocks Lines
Unchanged 1 226
Changed 0 0
Inserted 0 0
Removed 0 0

737.3 Comparison options

Whitespace
Character case Differences in character case are significant
Line endings Differences in line endings (CR and LF characters) are ignored
CR/LF characters Not shown in the comparison detail

737.4 Active regular expressions

No regular expressions were active.

737.5 Comparison detail

  1   SHEET: She et1
  2   Date : 201 5/02/13,
  3   Process Na me,Directi on,VAP Pol icy Check? ,Purpose O f Use Bein g sent to  VAP during  Policy Ch eck?,Audit ing?,Purpo se Of Use  Audited?,A dapter Cha nges?,Comm ents,Audit  Record co lumns,
  4   Patient Di scovery,In bound,Yes, Yes( if pr esent in t he request  assertion ),Y( Check Policy cal l Audits i t),Yes( if  present i n the requ est assert ion),N,Aud iting happ ens under  the action  'CheckPol icy',Actio n
  5   AuditTime
  6   PatientID
  7   PatienLast NAme
  8   PatientGiv enName
  9   PatientSSN
  10   PatientFac ilityNumbe r
  11   PatientFac ilityName
  12   UserId
  13   UserRole
  14   PurposeOfU Se
  15   UserFacili tyNumber
  16   UserFacili tyName
  17   UserName
  18   Organizati onId
  19   RemoteOrga nizationId
  20   Details,
  21   Doc Query, Inbound,Ye s,Yes( if  present in  the reque st asserti on),N,May  be needed  for auditi ng. Busine ss Needs t o clarify,
  22   Doc Query( Called by  internal A pplication s),Inbound ,No,N,N,N, May be nee ded for au diting. Bu siness Nee ds to clar ify,
  23   Doc Retrie ve,Inbound ,Yes,Yes(  if present  in the re quest asse rtion),Y(  Only in ca se of happ y path),Ye s( if pres ent in the  request a ssertion), N,Action
  24   AuditTime
  25   DocumentId
  26   PatientID
  27   PatienLast NAme
  28   PatientGiv enName
  29   PatientSSN
  30   PatientFac ilityNumbe r
  31   PatientFac ilityName
  32   Organizati onId
  33   PurposeOfU Se
  34   UserId
  35   UserRole
  36   UserFacili tyNumber
  37   UserFacili tyName
  38   UserName
  39   DocSpecTyp e
  40   ,
  41   Doc Query, Outbound,Y es,Policy  check is d one at Two  Levels. 
  42   1. First,  Policy on  the User(U serInfo in  SAML asse rtion) req uesting ou tbound is  done. Purp ose of use  is not se nt during  this check .
  43   2. Second,  before ma king an ou tbound req uest to th e partner,  policy ch eck is don e. Purpose  of use is  sent to V AP during  this call( if present  in reques t Assertio n).
  44   ,N,N,May b e needed f or auditin g. Busines s Needs to  clarify,L ogging for  individua l request  to remote  partner is  done. Req uest LOG i s stored i n REQUEST_ LOG table,
  45   Doc Retrie ve,Outboun d,Yes,Poli cy check i s done at  Two Levels
  46   1. First,  Policy on  the User(U serInfo in  SAML asse rtion) req uesting ou tbound is  done. Purp ose of use  is not se nt during  this check .
  47   2. Second,  before ma king an ou tbound req uest to th e partner,  policy ch eck is don e. Purpose  of use is  sent to V AP during  this call( if present  in reques t Assertio n).
  48   ,Y ( Audit ing for in dividual r equest to  remote par tner is do ne in happ y path . I n case of  errors/exc eptions Au diting is  not done.  Audit is s tored in A UDIT table  ),Yes( if  present i n the requ est assert ion),N,Act ion
  49   AuditTime
  50   DocumentId
  51   RemoteDocu mentId
  52   RemoteDocu mentReposi toryId
  53   RemoteOrga nizationId
  54   UserId
  55   UserRole
  56   UserFacili tyNumber
  57   UserFacili tyName
  58   UserName
  59   PurposeOfU Se
  60   Organizati onId
  61   PatientID
  62   PatienLast NAme
  63   PatientGiv enName
  64   PatientSSN
  65   PatientFac ilityNumbe r
  66   PatientFac ilityName
  67   DocSpecTyp e
  68   ,
  69   Announce/P atient Dis covery,Out bound,Yes, Policy che ck is done  before ou tbound req uest to th e partner  is being s ent for PD . Purpose  of use is  sent to VA P during t his call(i f present  in request  Assertion ).
  70   ,Y(Auditin g is only  done by An nounce). C heck Polic y call fro m PD also  does an Au dit.,Yes,A nnounce Pa tient does n’t have a  way to ge t Purpose  of use fro m the call er/request er. So whe n it creat es the req uest for P D outbound , it defau lts Purpos e Of Use t o ‘TREATME NT’. Busin ess Needs  to clarify ,Announce  Stores : 
  71   Action
  72   PatientID
  73   PatienLast NAme
  74   PatientGiv enName
  75   PatientSSN
  76   PatientFac ilityNumbe r
  77   PatientFac ilityName
  78   UserId
  79   UserRole
  80   UserFacili tyNumber
  81   UserFacili tyName
  82   PurposeOfU Se
  83   Organizati onId
  84   UserName
  85   Details
  86  
  87   Check Poli cy from PD  Stores :
  88   Action
  89   AuditTime
  90   PatientID
  91   PatienLast NAme
  92   PatientGiv enName
  93   PatientSSN
  94   PatientFac ilityNumbe r
  95   PatientFac ilityName
  96   UserId
  97   UserRole
  98   PurposeOfU Se
  99   UserFacili tyNumber
  100   UserFacili tyName
  101   UserName
  102   Organizati onId
  103   RemoteOrga nizationId
  104   Details
  105  
  106   ,
  107  
  108  
  109  
  110   SHEET: She et2
  111  
  112  
  113   SHEET: She et3