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

307.1 Files compared

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

307.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	5	52
Changed	4	18
Inserted	0	0
Removed	0	0

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

307.4 Active regular expressions

No regular expressions were active.

307.5 Comparison detail

	1	@F664 @F66 4_PatientR ecord_Sear ch_Detail_ Document @ US10697
	2	Feature: F 664 RDK En hancements - PSI 9
	3	# RDK reso urce: pati ent-record -search-de tail-docum ent
	4
	5	@F664_Pati entRecord_ Search_Det ail_Docume nt_Scenari o_1
	6	Scenario: Search Det ail Docume nt with ex isting pid but no ma tches
	7	When the c lient requ ests authe ntication with acces sCode " REDACT " and veri fyCode " REDACTED " and site " REDA C TED " and divi sion "507" and conte ntType "ap plication/ json"
	8	Given a pa tient with pid " REDA C TED ;1" has be en synced through th e RDK API
	9	When the c lient sear ches for d etailed do cuments wh ere pid = " REDA C TED ;1", query = "docume nt", group .field = " local_titl e", and gr oup.value is "ADVANC E DIRECTIV E"
	10	Then a s uccessful response i s returned
	11
	12	@F664_Pati entRecord_ Search_Det ail_Docume nt_Scenari o_2
	13	Scenario: Search Det ail Docume nt with si te
	14	Given a pa tient with pid " R E D A CTED ;3" has be en synced through th e RDK API
	15	When the c lient sear ches for d etailed do cuments wh ere pid = " R E D A CTED ;3", query = "docume nt", group .field = " local_titl e", and gr oup.value is "ADVANC E DIRECTIV E"
	16	Then a s uccessful response i s returned
	17	And the response c ontains at least 2 i tems
	18
	19	@F664_Pat ientRecord _Search_De tail_Docum ent_Scenar io_3 @de71 47
	20	Scenario: Search Det ail Docume nt with 1 result
	21	Given a pa tient with pid " R E D A CTED ;100125" h as been sy nced throu gh the RDK API
	22	When the c lient sear ches for d etailed do cuments wh ere pid = " R E D A CTED ;100125", query = "d ocument", group.fiel d = "local _title", a nd group.v alue is "A DMISSION R EVIEW - NU RSING"
	23	Then a s uccessful response i s returned
	24	And the response c ontains 2 results
	25
	26	@F664_Pati entRecord_ Search_Det ail_Docume nt_Scenari o_4
	27	Scenario: Search Det ail Docume nt with mi ssing quer y
	28	Given a pa tient with pid " R E D A CTED ;100125" h as been sy nced throu gh the RDK API
	29	When the c lient sear ches for d etailed do cuments wh ere pid = " R E D A CTED ;100125", group.fiel d = "local _title", a nd group.v alue is "A DVANCE DIR ECTIVE"
	30	Then a b ad request response is returne d
	31
	32	@F664_Pati entRecord_ Search_Det ail_Docume nt_Scenari o_5
	33	Scenario: Search Det ail Docume nt with no n-existing icn
	34	When the client se arches for detailed documents where pid = "848V484 ", query = "document ", group.f ield = "lo cal_title" , and grou p.value is "ADVANCE DIRECTIVE"
	35	Then a n on-found r esponse is returned