jan_epic(wk??): Add the stopcode 179 (Veterans Video Connect-VVC) to the vizEnc on Data UI

[anazariz]

Check off requirements to verify progress through feature_tracker.

• [x] 1. DEFINE in work_breakdown
  • [ ] a. what & why - written definitions of requirements in a numbered checklist on the master_feature_card.
  • [ ] b. date & who - Verified requirement definitions an existing team meeting.

Add the stopcode 179 (Veterans Video Connect-VVC) to the vizEnc on Data UI. As we don't yet have the VVC filter built, the following image shows the CPTCode as how the VVC filter should be placed and used.

Task Cards: #

• [x] 2. DESIGN in operations_to_do and research_to_do
  • [ ] a. what & why - MVP of design of requirements in a algorithm map, wireframes or design on the master_feature_card.
  • [ ] b. date & who - Verified design asynchronously or an existing team meeting.

Design was verified with @staceypark , @lijenn and @anthonycpichardo in a Teams meeting on 11/16./20 @ 11:00 am.

1) The VVC column (stopCode(179) should be added to the dataEnc (tab). 2) If SQL adjustment is needed is should be implemented
3) The column should have 1/0 (True/False) values for VVC = True or not 4) The column should then be added to the appropriate Pivot Table on the vizEnc tab 5) Then finally the filter should be added to page filter/chart as shown in the figure aboove

Task Cards: #

• [x] 3. DEVELOP in under_development

Complete

Task Cards: #

• [ ] 4. TEST in functional_test
  • [ ] a. what & why - TEST requirements using testing_checklist on the master_feature_card.
  • [ ] b. date & who - Verified via TEST asynchronously or an existing team meeting.

In progress

Task Cards: #

• [ ] 5. PROD in done

  • [ ] a. what & why - DOCUMENT feature using document_tracker for the 5 D's.
  • [ ] b. date & who - DELEGATE
  • [ ] describe_learners [Jenn & Rita]
  • [ ] detail_facilitators [Jane & Debbie]
  • [ ] document_team [Anthony]
  • [ ] disseminate_scientists_va [Anthony]
  • [ ] depend_products [hq & ees]

  Task Cards: #

• [ ] 6. closed - fully documented, trained and ready for the next release.

[lzim]

@anazariz and @anthonycpichardo

Can you clarify what the next steps are for this?

[anthonycpichardo]

I believe this is complete and ready to close.

Can you confirm @anazariz ?

[anazariz]

@anthonycpichardo

Yes, VVC was added to the vizEnc. However, per my understanding the prototype was still being evaluated/tested (see #1581). @lijenn may have more on that.

[anthonycpichardo]

@lijenn @anazariz where did we land on this issue?

[lijenn]

VVC was tested by you, Ash, Stacey, and I. The file with the mvp was emailed to Alka & Vhee but they did not have time to review it. I recommend wrapping this in with the super user testing since I believe Alka's name was mentioned there as well.

[lzim]

@anazariz @anthonycpichardo @staceypark @lijenn

If everyone on the team has signed off on DEV QA & TEST QA, I recommend that we get PROD QA & close w/out the super users.

Many folks in MTL Red will want to see this.