When judges are reviewing their cases to assign, they need to see if any of their cases have specialty case team issues, so they know the case must be assigned to a particular attorney.
What are specialty case teams?
BRIEFF.BFBOXNote: When browser width is narrow, we can stack labels vertically to save horizontal space. If browser width permits, place multiple labels side by side (limit 2 horizontally before wrapping)

Note: When browser width is narrow, we can stack labels vertically to save horizontal space. If browser width permits, place multiple labels side by side (limit 2 horizontally before wrapping)

From https://github.com/department-of-veterans-affairs/dsva-vacols/issues/8#issuecomment-413600936

@laurjpeterson sorry to ask you to do this but could we find out what this looks like in DAS? I see that the indicator is pink, but also am reading that there are numbers attached to different types of SCT cases. I'd like to know what that number in conjunction with the color looks like. Also, what is the range of numbers?
If there is a person I can reach out to myself for this info, let me know!
@mkhandekar here you go!

Additional resources:
If we have any more questions about SCTs, we can continue this thread with Jed - https://github.com/department-of-veterans-affairs/dsva-vacols/issues/8
Notes from post-standup discussion on Aug 16:
For legacy cases:
For AMA cases:
Asked Jed a few more questions today in the dsva-vacols github issue, also linked in the Resources section of the main comment above.
Could you share your VACOLS logic for designating a case should go to a specialty case team?
Also, could you share the field that creates the pink specialty case team identifier in VACOLS?
How often have you been asked to update the specialty case team issues list since the program started?
// Look at open issues to get SCT group
setnull(ls_sct)
SELECT min(vacols.sct_group(issprog, isscode, isslev1, isslev2)) into :ls_sct
from issues where isskey = :gs_folder and issdc is null;
if ls_sct = '' then setnull(ls_sct)
UPDATE BRIEFF SET BFBOX = :ls_sct WHERE BFKEY = :gs_folder USING SQLCA;
// VACOLS.SCT_GROUP function
FUNCTION VACOLS.SCT_GROUP
(inprog CHAR, incode CHAR, inlev1 CHAR, inlev2 CHAR )
RETURN CHAR AS pending varchar2(1);
BEGIN
if inprog = '12' then return '01'; end if;
if inprog = '02' and incode = '05' then return '02'; end if;
if inprog = '04' then return '03'; end if;
if inprog = '02' and incode = '22' then return '04'; end if;
if inprog = '02' and incode = '21' then return '05'; end if;
if inprog = '02' and incode = '10' then return '06'; end if;
if inprog = '05' then return '07'; end if;
if inprog = '02' and incode = '20' then return '08'; end if;
if inprog = '11' then return '09'; end if;
if inprog = '02' and incode = '06' then return '10'; end if;
if inprog = '09' then return '11'; end if;
if inprog = '08' then return '12'; end if;
if inprog = '02' and incode = '02' then return '13'; end if;
if inprog = '10' then return '14'; end if;
if inprog = '02' and incode = '03' then return '15'; end if;
if inprog = '02' and incode = '16' then return '16'; end if;
if inprog = '02' and incode = '13' then return '17'; end if;
if inprog = '01' then return '18'; end if;
if inprog = '02' and incode = '19' then return '19'; end if;
if inprog = '02' and incode = '11' then return '20'; end if;
if inprog = '02' and incode = '14' then return '21'; end if;
if inprog = '02' and incode = '07' then return '22'; end if;
if inprog = '03' then return '23'; end if;
if inprog = '02' and incode = '01' then return '24'; end if;
if inprog = '02' and incode = '18' then return '25'; end if;
if inprog = '06' then return '26'; end if;
if inprog = '07' and (incode = '03' or incode = '07') then return '27'; end if;
if inprog = '07' then return '28'; end if;
if inprog = '02' and incode = '12' and (inlev2 >= '6000' and inlev2 <= '6099') then return '29'; end if;
-- SC Eye issues removed 5/16/18
-- if inprog = '02' and incode = '15' and (inlev2 >= '6000' and inlev2 <= '6099') then return '29'; end if;
if inprog = '02' and incode = '15' and inlev1 = '02' then return '30'; end if;
if inprog = '02' and incode = '15' and (inlev2 >= '9900' and inlev2 <= '9999' and inlev2 <> '9905') then return '30'; end if;
if inprog = '02' and incode = '12' and (inlev2 >= '9900' and inlev2 <= '9999') then return '30'; end if;
return '';
END;
More SCT notes from today's standup discussion (08/16/18)
Attributes such as:
Specialty cases: How does this work?
- Senior counsel are responsible for assigning specialty cases to certain attorneys (preselected)
- Judges care to see that they are specialty cases (to understand workload)
- Judges who have to sign specialty cases care when signing that they are specialty cases.
- Attorneys work a mix of specialty cases AND non-specialty cases.
- Board employees want to track
- Allyce: Would colocated want to know if specialty?
- Often cases with these specialty issues have paper documents.
Specialty cases back-end approach:
For legacy cases, point to Jed’s tagging work
For AMA issues, a mapping doesn’t exist yet.
Mixed docket = display of which lane this case is in
4 lanes:
H - hearing
E - evidence
DR - direct review
L - legacy
H = If a hearing has been done for this case, if I HAVE done this case
Impact: bigger reach (all judges)
SCT = one or more specialty issues
Impact: small group of attorneys would be affected by this.
we don’t yet know how we’re displaying issues yet
engage with CHRISTI and the folks who’ve designed SCT
OT = overtime cases
OtH = One-touch hearings: Hearing prep feature
- One-touch hearing box (out of docket order)
- this program may not last that long
Good morning,
I am the coordinator for the Specialty Case Teams, a pilot the Board is running in which attorneys predominately draft decisions in one or two assigned topic areas. I have met a few weeks ago with Lauren Peterson about the pilot and the needs we will have under AMA.
There have been some changes to the SCT program that you will need to be aware of.
Cases involving 1151 and SC/IR dental are no longer in the SCT pilot program. This removal was thought to be a temporary pause but likely will be permanent, pending a decision by senior leadership. Jed Wagner has updated the VACOLS programming for legacy cases.
There is a pending proposal with the Chairman to include SC PTSD due to MST as an specialty within SCT. These cases are designated as sexual assault/harassment in VACOLS and can be coded as SCT by using this designation. If this proposal is approved by the Chairman, attorneys will start drafting SCT cases in the SC PTSD due to MST area beginning in approximately mid-November.
Here is a list of the items needed to ensure that SCT pilot continues to be functional within AMA.
Report showing SCT attorney production (for both SCT designated cases and non-SCT designated cases) for AMA cases. It is my understanding that the creation of reports are under development. I will require a specific report showing the number of signed AMA cases drafted by SCT attorneys, including SCT and non-SCT cases. This production information is critical to determine the success of SCT and production information is reported to external stakeholders. For instance, I have answered congressional inquiries about the SCT pilot and the associated production just two weeks ago.
A way to continue to designate and charge SCT cases to SCT VLJs/attorneys. For legacy appeals, this is currently completed through the case distribution program. Something similar is necessary for AMA appeals.
Ideally there will be a SCT indicator somewhere in Caseflow queue to allow VLJs/attorneys to know that they have SCT appeal. I understand from Lauren that this may be a challenge due to space limitations in the columns.
Please let me know if you require any additional information.
Kristy L. Zadora
Senior Counsel
Board of Veterans’ Appeals
@sneha-pai - can you paste in your queue table designs with SCT label to the original issue?
@joeyyang - Following up to your question from earlier this week - I got names for each specialty case team code! Please let me know if you want to add these SCT names in in this github issue, or if we should create another github issue to track that work. I don't want to add/change requirements too late in the game.
Note: When browser width is narrow, we can stack labels vertically to save horizontal space. If browser width permits, place multiple labels side by side (limit 2 horizontally before wrapping)

Note: When browser width is narrow, we can stack labels vertically to save horizontal space. If browser width permits, place multiple labels side by side (limit 2 horizontally before wrapping)

LARGE
Most helpful comment
@mkhandekar here you go!
Additional resources:
If we have any more questions about SCTs, we can continue this thread with Jed - https://github.com/department-of-veterans-affairs/dsva-vacols/issues/8