306. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 10/4/2017 8:04:42 AM Central 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.

306.1 Files compared

# Location File Last Modified
1 rdk.zip\rdk\product\tests\acceptance-tests\features F586_Communication_Request_FHIR.feature Mon Aug 21 12:51:01 2017 UTC
2 rdk.zip\rdk\product\tests\acceptance-tests\features F586_Communication_Request_FHIR.feature Tue Oct 3 20:19:20 2017 UTC

306.2 Comparison summary

Description Between
Files 1 and 2
Text Blocks Lines
Unchanged 22 144
Changed 21 60
Inserted 0 0
Removed 0 0

306.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

306.4 Active regular expressions

No regular expressions were active.

306.5 Comparison detail

  1  
  2   @F586_Noti fications_ Alerts @F5 86
  3   Feature: F 586 - Noti fications  and Alerts
  4  
  5   @US10086 @ US10556 @C ommunicati on_Request _Get_All @ DE3855 @fu ture @DE60 42
  6   Scenario:  retrieve a ll request s for a re cipient
  7         Given the  system kno ws about t he followi ng communi cation req uests for  the "patie nt%2F R E D A CTED ;10045" re cipient
  8       | cate gory                        | se nder                     | mediu m                       | recipi ent           | paylo ad                      | status     | reas on                        | subj ect             | pri ority                 |
  9         | ehmp/msg /category/ clinical      | ehmp/act ivity/123/ task/1 | e hmp/msg/me dium/ui/in line    | patient/ R E D A CTED ;10045 | p atient/ R E D A CTED ;10045/lab /123 | req uested | e hmp/msg/re ason/decis ion      | patient/ R E D A CTED ;10045 | e hmp/msg/pr iority/hig h |
  10         | ehmp/msg /category/ operationa l | ehmp/a ctivity/45 /task/3    | ehmp/msg /medium/ui /overlay |  patient/ R E D A CTED ;10045 | p atient/ R E D A CTED ;data/543        | requeste d | ehmp/m sg/reason/ informatio n | patien t/ R E D A CTED ;10045 | e hmp/msg/pr iority/low     |
  11         When the c lient retr ieves all  communicat ion reques ts for rec ipient "pa tient%2F R E D A CTED ;10045"
  12       And on e of the c ommunicati on request  has the f ollowing d ata:
  13           |  field                                                          |  value                                                       |
  14           |  resourceTy pe                            |  Communicat ionRequest                          |
  15           |  category.c oding.code                    |  ehmp/msg/c ategory/cl inical                   |
  16           |  sender.ref erence                        |  ehmp/activ ity/123/ta sk/1                     |
  17           |  medium.cod ing.code                      |  ehmp/msg/m edium/ui/i nline                        |
  18             | recipien t.referenc                     | patient/ R E D A CTED ;10045                             |
  19             | payload. contentRef erence.ref erence      | patient/ R E D A CTED ;10045/lab /123                    |
  20           |  status                                   |  requested                                      |
  21           |  reason.cod ing.code                      |  ehmp/msg/r eason/deci sion                     |
  22             | subject. reference                        | patient/ R E D A CTED ;10045                             |
  23           |  priority.c oding.code                    |  ehmp/msg/p riority/hi gh                       |
  24       And on e of the c ommunicati on request  has the f ollowing d ata:
  25           |  field                                                          |  value                                                       |
  26           |  resourceTy pe                            |  Communicat ionRequest                          |
  27           |  category.c oding.code                    |  ehmp/msg/c ategory/op erational                |
  28           |  sender.ref erence                        |  ehmp/activ ity/45/tas k/3                      |
  29           |  medium.cod ing.code                      |  ehmp/msg/m edium/ui/o verlay                       |
  30             | recipien t.referenc                     | patient/ R E D A CTED ;10045                             |
  31             | payload. contentRef erence.ref erence      | patient/ R E D A CTED ;data/543                          |
  32           |  status                                   |  requested                                      |
  33           |  reason.cod ing.code                      |  ehmp/msg/r eason/info rmation                  |
  34             | subject. reference                        | patient/ R E D A CTED ;10045                             |
  35           |  priority.c oding.code                    |  ehmp/msg/p riority/lo w                        |
  36         And remove  all commu nication r equests fo r recipien t "patient %2F R E D A CTED ;10045"
  37  
  38    @US10086  @US10556 @ Communicat ion_Reques t_No_Reque sts_For_Re cipient @f uture @DE6 042
  39   Scenario:  not found  when retri eving all  requests f or a recip ient that  does have  any reques ts
  40       Given  no communi cation req uest for a  recipient
  41         When the c lient retr ieves all  communicat ion reques ts for rec ipient "pa tient%2F R E D A CTED ;10045"
  42       Then a  successfu l response  is return ed
  43  
  44   @US10089 @ US10556 @C ommunicati on_Request _Delete_Al l @future  @DE6042
  45   Scenario:  delete all  requests  for a reci pient
  46         Given the  system kno ws about t he followi ng communi cation req uests for  the "patie nt%2F R E D A CTED ;10045" re cipient
  47       | cate gory                        | se nder                     | mediu m                       | recipi ent           | paylo ad                      | status     | reas on                        | subj ect             | pri ority                 |
  48         | ehmp/msg /category/ clinical      | ehmp/act ivity/123/ task/1 | e hmp/msg/me dium/ui/in line    | patient/ R E D A CTED ;10045 | p atient/ R E D A CTED ;10045/lab /123 | req uested | e hmp/msg/re ason/decis ion      | patient/ R E D A CTED ;10045 | e hmp/msg/pr iority/hig h |
  49         | ehmp/msg /category/ operationa l | ehmp/a ctivity/45 /task/3    | ehmp/msg /medium/ui /overlay |  patient/ R E D A CTED ;10045 | p atient/ R E D A CTED ;data/543        | requeste d | ehmp/m sg/reason/ informatio n | patien t/ R E D A CTED ;10045 | e hmp/msg/pr iority/low     |
  50         Then remov e all comm unication  requests f or recipie nt "patien t%2F R E D A CTED ;10045"
  51  
  52   @US10088 @ US10089 @U S100091 @U S10556 @Co mmunicatio n_Request_ Get_By_Id  @future @D E6042
  53   Scenario:  retrieve a  single re quest for  a recipien t
  54         Given the  system kno ws about t he followi ng communi cation req uests for  the "provi der%2F REDACT " recipien t
  55       | cate gory                        | se nder                     | mediu m                       | recipi ent           | paylo ad                      | status     | reas on                        | subj ect             | pri ority            |
  56         | ehmp/msg /category/ clinical      | ehmp/act ivity/123/ task/5 | e hmp/msg/me dium/ui/in line    | provider / REDACT       | patient/ R E D A CTED ;10045/lab /123 | req uested | e hmp/msg/re ason/decis ion      | patient/ R E D A CTED ;10045 | e hmp/msg/pr iority/hig h |
  57         When the c lient retr ieves a co mmunicatio n request  for recipi ent "provi der%2F REDACT " with the  resource  id
  58       Then a  successfu l response  is return ed
  59       And th e communic ation requ est contai ns
  60           |  field                                                          |  value                                                       |
  61           |  resourceTy pe                            |  Communicat ionRequest                          |
  62           |  sender.ref erence                        |  ehmp/activ ity/123/ta sk/5                     |
  63           |  category.c oding.code                    |  ehmp/msg/c ategory/cl inical                   |
  64           |  medium.cod ing.code                      |  ehmp/msg/m edium/ui/i nline                                 |
  65             | recipien t.referenc                     | provider / REDACT                                 |
  66             | payload. contentRef erence.ref erence      | patient/ R E D A CTED ;10045/lab /123                    |
  67           |  status                                   |  requested                                      |
  68           |  reason.cod ing.code                      |  ehmp/msg/r eason/deci sion                     |
  69             | subject. reference                        | patient/ R E D A CTED ;10045                             |
  70           |  priority.c oding.code                    |  ehmp/msg/p riority/hi gh                       |
  71         And remove  all commu nication r equests fo r recipien t "provide r%2F REDACT "
  72  
  73   @US10089 @ US10556 @C ommunicati on_Request _Delete_By _Id @futur e @DE6042
  74   Scenario:  delete a s ingle requ est for a  recipient
  75         Given the  system kno ws about t he followi ng communi cation req uests for  the "provi der%2F REDACT " recipien t
  76       | cate gory                        | se nder                     | mediu m                       | recipi ent           | paylo ad                      | status     | reas on                        | subj ect             | pri ority            |
  77         | ehmp/msg /category/ clinical      | ehmp/act ivity/123/ task/5 | e hmp/msg/me dium/ui/in line    | provider / REDACT       | patient/ R E D A CTED ;10045/lab /123 | req uested | e hmp/msg/re ason/decis ion      | patient/ R E D A CTED ;10045 | e hmp/msg/pr iority/hig h |
  78         When the c lient dele tes the co mmunicatio n request  for recipi ent "provi der%2F REDACT " with a r esource id
  79  
  80   @US10088 @ US100091 @ US10556 @C ommunicati on_Request _Get_By_Id _No_Reques t @future  @DE6042
  81   Scenario:  not found  when retri eving a si ngle reque st for a r ecipient t hat does n ot exist
  82       Given  communicat ion reques t with an  unknown re source id
  83         When the c lient retr ieves a co mmunicatio n request  for recipi ent "provi der%2F REDACT " with an  unknown re source id
  84       Then a  not-found  response  is returne d
  85  
  86   @US10089 @ US10556 @C ommunicati on_Request _Add_Bad_R equest @fu ture @DE60 42
  87   Scenario:  try to add  a bad req uest
  88       Given  an invalid  communica tion reque st
  89       When t rying to a dd an inva lid commun ication re quests
  90       | cate gory                        | se nder                     | mediu m                       | payloa d                      | status     | reaso n                        | subje ct             | prio rity                |
  91         | ehmp/msg /category/ clinical      | ehmp/act ivity/123/ task/1 | e hmp/msg/me dium/ui/in line    | patient/ R E D A CTED ;10045/lab /123 | req uested | e hmp/msg/re ason/decis ion      | patient/ R E D A CTED ;10045 | e hmp/msg/pr iority/hig h |
  92       Then a  bad reque st respons e is retur ned
  93  
  94   @US10089 @ US10556 @C ommunicati on_Request _Add_Unpro cessible_R equest @fu ture @DE60 42
  95   Scenario:  try to add  a unproce ssible req uest
  96       Given  an invalid  communica tion reque st
  97       When t rying to a dd an inva lid commun ication re quests
  98       | cate gory                        | se nder                     | mediu m                       | recipi ent           | paylo ad                      | status     | reas on                        | subj ect             | pri ority                  |
  99         | ehmp/msg /category/ clinical      | ehmp/act ivity/123/ task/1 | e hmp/msg/me dium/ui/in line    | patient/ R E D A CTED ;10045 | p atient/ R E D A CTED ;10045/lab /123 | req uested | e hmp/msg/re ason/decis ion      | patient/ R E D A CTED ;10045 | e hmp/msg/pr iority/ale rt |
  100       Then a  accepted  response i s returned
  101         And remove  all commu nication r equests fo r recipien t "patient %2F R E D A CTED ;10045"
  102