410. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 6/22/2018 1:30:25 PM 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.

410.1 Files compared

#	Location	File	Last Modified
1			Fri Jun 22 18:30:23 2018 UTC
2	v1603_release_60.zip\Docs	176406 - VCCM_6_S#687707_UX_ Streamline Request and Progress Note Forms.docx	Thu Jun 21 14:49:50 2018 UTC

410.2 Comparison summary

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

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

410.4 Active regular expressions

No regular expressions were active.

410.5 Comparison detail

				1		176406: VC CM_6_S#687 707_UX: St reamline R equest and Progress Note Forms
				2		Creation D ate: Apr 26, 2018 1 0:54:06 AM (UTC-05:0 0)Last Mod ified: Apr 26, 2018 11:11:46 A M (UTC-05: 00)
				3
				4		State: App roved
				5		Originator : Pribyl, Brent (BA H)Owner:
				6		Type: Manu al
				7		Test Data: Unassigne d
				8
				9		Descriptio n: 1. Hor izontal CR M tabs (bl ue headers ) on reque st form wi ll have ma tching lin ks/buttons across to p of Reque st form (b elow reque st ribbon) . There wi ll be one button for each CRM tab (blue header) on the form.
				10
				11		Create a n ew collaps ible Secti on for Pro gress Note s on the R equest for m
				12		Do not ope n a separa te tab for new progr ess notes
				13		Add Note t ype field: Drop down should ha ve the fol lowing opt ions:
				14		Historical
				15		Workload
				16		CRM only
				17		Allow user the flexi bility to change Not e Type whe n necessar y
				18
				19		The body o f the prog ress note will be di splayed ne xt
				20		Keep exist ing config uration fo r what get s added to the body of the pro gress note
				21
				22		The Intera ction and Request No tes grid i s placed a bove Progr ess Note s ection [PE NDING APPR OVAL OF NE W AC IN 68 8762 - Now called "C omments" g rid]
				23		Refresh Co mments Gri d and Appl y Selected Comments buttons ar e at the b ottom of t he grid
				24		Displayed with all n otes type
				25
				26		Create new options t o "Save" a nd "Add Ad ditional S igners" at the end o f Progress Notes Sec tion
				27
				28		Add Collap sible sect ion to dis play all a dditional signers ad ded to the request
				29
				30		Summary
				31
				32		Categories
				33		Function: Unassigned
				34		Test Phase : Develope r Test
				35
				36		Formal Rev iew
				37
				38
				39		General Co mments
				40
				41		Manual Ste ps
				42
				43
				44		Step 1
				45		Execution Step
				46
				47		Descriptio n*
				48		In the VCC M CRM appl ication, l og-in to t he system as an FTP CCA/TAN/Ph armacy/Pha rmacyTech test user
				49
				50		Expected R esults
				51		The user i s able to log-in as a FTP CCA/ TAN/Pharma cy/Pharmac yTech test user Comm ents
				52		Validates
				53
				54
				55
				56		Attachment s
				57
				58
				59		Step 2
				60		Execution Step
				61
				62		Descriptio n*
				63		Click on M VI Search from the U SD ribbon
				64
				65		Expected R esults
				66		The user i s directed to the MV I search p age Commen ts
				67		Validates
				68
				69		Attachment s
				70
				71
				72		Step 3
				73		Execution Step
				74
				75		Descriptio n*
				76		Search for a Veteran (by trait s or EDIPI )
				77
				78		Test Veter an Record: George VC CMAlberts 333624237, 10/18/197 4 Expected Results
				79		Veteran re cord is re trieved fr om MVI. Co mments
				80		Validates
				81
				82		Attachment s
				83
				84
				85		Step 4
				86		Execution Step
				87
				88		Descriptio n*
				89		Click on t he test fa cility for the Veter an record
				90
				91		Expected R esults
				92		An interac tion is ge nerated al ong with V eteran Inf o and Medi cal Charts tabs Comm ents
				93		Validates
				94
				95		Attachment s
				96
				97
				98		Step 5
				99		Execution Step
				100
				101		Descriptio n*
				102		User popul ates the r equired fi elds on th e Interact ion form a nd makes F irst Call Resolution = No and clicks Sav e
				103
				104
				105
				106		Expected R esults
				107		The reques t form is generated Comments
				108		Validates
				109
				110		Attachment s
				111
				112
				113		Step 6
				114		Execution Step
				115
				116		Descriptio n*
				117		On the Req uest form the user v erifies th ere are ho rizontal t abs across the top o f the Requ est form. There will be one bu tton for e ach tab on the reque st form
				118
				119		Expected R esults
				120		Horizontal tabs are displayed correctly Comments
				121		Validates
				122
				123		Attachment s
				124
				125
				126		Step 7
				127		Execution Step
				128
				129		Descriptio n*
				130		User verif ies the 'P rogress No te' sectio n contacts a Note Ty pe field t hat allows the user to change the Progre ss Note to : Historca l, Workloa d (default view), an d CRM Only
				131
				132		Expected R esults
				133		User is ab le to chan ge the Not e Type to Historical , Workload , or CRM O nly Commen ts
				134		Validates
				135
				136		Attachment s
				137
				138
				139		Step 8
				140		Execution Step
				141
				142		Descriptio n*
				143		User verif ies the fo llowing:
				144
				145		When you s elect Work load or Hi storical, the form i s configur ed for tha t specific use. The buttons di splayed as sociated w ith these Note Types are as fo llows:
				146
				147		TEMPLATE ( Used to ge nerate the note text from temp late logic based upo n data alr eady enter ed on the request fo rm)
				148
				149		CANCEL (Us ed to Canc el and Del ete all da ta entered in the Pr ogress Not e area, an d set the form up fo r entering a new not e)
				150
				151		SIGNERS (U sed to ass ociate add itional si gners with the note or view th ose that h ave been a ssociated previously )
				152
				153		SAVE TO VI STA (Used to send th e note cre ated to VI STA via th e existing progress note entit y logic. T his will a utomatical ly start t he integra tion proce ss to VIST A/CPRS. Th e progress note data entered o n the Requ est form w ill be cle ared and t he Request reset for the creat ion of ano ther note if needed. )
				154
				155
				156
				157
				158
				159		NOTE 1: Wh en working with a wo rkload enc ounter tha t always r equire som e addition al attribu tes, you w ill notice that cert ain attrib utes will be marked as require d. These f ields are only marke d as requi red when t here is no te text en tered. Thi s is imple mented thi s way so t hat the Re quest form can be sa ved withou t completi ng those r equired at tributes w hen the no te text ha s not been entered y et.
				160
				161
				162		NOTE 2: Af ter saving a Workloa d/Historic al Note to Vista the y will be displayed in the 'Pr ogress Not es' grid o n the Requ est form. They user can double click any row in th e grid and it will t ake the us er to the Progress N otes form (tab). If it was sav ed to Vist a successf ully the s tatus will be marked as comple ted and th e progress note will be read o nly
				163
				164		Expected R esults
				165		Request fo rm functio ns correct ly based o n the user selecting Workload or Histori cal Commen ts
				166		Validates
				167
				168		Attachment s
				169
				170
				171		Step 9
				172		Execution Step
				173
				174		Descriptio n*
				175		User verif ies the fo llowing:
				176
				177		When you s elect CRM Only, the form is co nfigured f or that sp ecific use . The butt ons displa yed associ ated with that Note Type are a s follows:
				178
				179		TEMPLATE ( same as de scribed ab ove)
				180
				181		CANCEL (sa me as desc ribed abov e)
				182
				183		SAVE TO CR M (Used to save the note to CR M. Upon su ccessful c reation of the CRM N ote, the p rogress no te data en tered on t he Request form will be cleare d and the Request re set for th e creation of anothe r note if needed.)
				184
				185		NOTE: The 'Comments' grid will display t he new CRM Note adde d Expected Results
				186		CRM Only f unctionali ty works c orrectly C omments
				187		Validates
				188
				189		Attachment s
				190
				191		Associated E-Signatu res
				192
				193
				194		SignedActi onSignerCo mmentAddit ional Info rmation