74. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 9/24/2019 1:38:03 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.

74.1 Files compared

#	Location	File	Last Modified
1	PCL-5_v1_build_8.zip\v1_build 8\Unredacted\spp_mha_web-development.zip\spp_mha_web-development\Docs	Isolating Patient Entry and Removing Clinician Entry Files and Dependencies.docx	Wed Jul 31 17:35:31 2019 UTC
2	PCL-5_v1_build_8.zip\v1_build 8\Unredacted\spp_mha_web-development.zip\spp_mha_web-development\Docs	Isolating Patient Entry and Removing Clinician Entry Files and Dependencies.docx	Mon Sep 23 20:26:58 2019 UTC

74.2 Comparison summary

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

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

74.4 Active regular expressions

No regular expressions were active.

74.5 Comparison detail

	1	Isolating Patient En try and Re moving Cli nician Ent ry Files a nd Depende ncies
	2	Revision H istory
	3	Last contr ibutor: Ja son Wilson
	4	Date: 1/31 /2019
	5
	6	Purpose
	7	Developers need a wa y to test & deliver the codeba se they wi ll be ship ping to pr oduction. Currently, the MHA W eb applica tion in st ream *130 allows bot h patients and clini cians to u se MHA Web .
	8	We need a way to shi p the pati ent entry piece alon e to produ ction with out the cl inician en try portio n because the clinic ian entry piece is s till under going deve lopment.
	9	We want to continue to develop the appli cation wit h both cli nician and patient e ntry piece s working as one pro ject. That means, de velopers w ill still code and t est MHA We b with bot h patient entry and clinician entry func tionality since the long-term goal is to deliver a product t hat has bo th feature s.
	10	Isolation Process
	11	Run the re moveStaffE ntryFiles. bat
	12
	13	removeStaf fEntryFile s.bat
	14	To remove any clinic ian entry files and dependenci es, run th e script c alled remo veStaffEnt ryFiles.ba t from the top level of the mh a-web/ cod ebase.
	15	You may do uble-click the file or run it from the c ommand pro mpt by typ ing in rem oveStaffEn tryFiles.b at and pre ssing ente r.
	16	(This comm and can be run on Wi ndows syst ems only)
	17	Package th e app
	18
	19	(if you ha ve not alr eady set u p your cod ing enviro nment and have not b een runnin g the app successful ly in your local dev elopment e nvironment , you need to mvn in stall -Pbu ildAll -Dm aven.test. skip=true before run ning the p ackage com mand below . If you h ave been c oding and running yo ur app loc ally succe ssfully yo u do not n eed to run the “buil dAll” comm and first)
	20
	21	Run the co mmand belo w
	22	mvn packag e -Dmaven. test.skip= true
	23
	24	Run the ne wly create d JAR
	25	Cd to the /target di rectory wh ere your n ewly creat ed JAR wil l be.
	26	java -jar mha-web-X. X.X-SNAPSH OT.jar
	27
	28	Undo local changes t he removeS taffEntryF iles.bat S cript has caused
	29	Go into RT C and undo any unres olved loca l changes.
	30	The JAR wi ll remain in your /t arget dire ctory.
	31	Use Cases
	32	The soluti on describ ed in this document is only me ant to be used in th e follow s cenarios:
	33	We assume that for a ll use cas es the use r is only interested in patien t entry fu nctionalit y
	34	User Case 1
	35	When a dev eloper is testing th e applicat ion before deploymen t to UAT o r any othe r central environmen t.
	36	User Case 2
	37	When packa ging the p roduct int o a JAR fo r deployme nt to UAT or any oth er central environme nts.
	38	User Case 3
	39	When an au tomated sc ript such as Jenkins is deploy ing an upd ated versi on of the JAR to a c entral tes ting envir onment (cl oud) such as DEV or SQA (UAT d eployments should be manual)
	40	More Gener ic Visual Use Case
	41
	42
	43	Alternativ e Uses
	44	The mobile team may wish to ut ilize this patient e ntry isola tion scrip t outside of scenari os describ ed here.
	45	Technical Details
	46	The script removes t he followi ng files s hown below :
	47	MHAWorkspa ce\JavaScr ipt\Java\m ha-web\src \main\java \com\va\me d\mha\clin ician (ent ire direct ory)
	48	MHAWorkspa ce\JavaScr ipt\Java\m ha-web\src \main\java \com\va\me d\mha\Star tupInit.ja va
	49	MHAWorkspa ce\JavaScr ipt\Java\m ha-web\src \main\reso urces\full -applicati on-data.sq l
	50	MHAWorkspa ce\JavaScr ipt\Java\m ha-web\src \main\reso urces\appl ication-de v.properti es
	51	MHAWorkspa ce\JavaScr ipt\Java\m ha-web\src \main\reso urces\appl ication-pr od.propert ies
	52
	53	The Java f iles locat ed in the /clinician directory contain a ny REST en try points and servi ce classes required by Staff e ntry alone .
	54	The Startu pinit.java file cont ains a fun ction that initializ es a Vista Connectio ns using a ccess & ve rify pins required t o run RPC’ s as a Cli nician. We use a gen eric set o f access & verify pi ns for the time bein g while in developme nt only.
	55	The SQL fi le contain s a startu p script t hat insert s rows in the in-mem ory H2 dat abase. Thi s script h old access & verify pins for a ll Vista C onnections . One set of access & verify p ins per di vision.
	56	The remain ing .prope rties file s are conf iguration settings o nly requir ed for sta ff entry m odes.
	57
	58	Future Pos sible Use Cases
	59	If at some point the MHA Web t eam and MH A Mobile t eams want to work ou t of separ ate stream s, this sc ript would create a good basel ine for th e MHA Mobi le stream.
	60