Detention Requirements
Office of the Administrator for the Courts
JIS JUVENILE AND CORRECTIONS ADVISORY COMMITTEE MEETING MINUTES
February 12-13, 1998
Present: Ross Austin (Lewis County), Sharon Bell, Kimberly Burns (Clallam County),
Jim Cory (Snohomish County), Bernard Dean, Bruce Eklund, David Gelinas, John Gray,
Judy Higgins, Mel Hyden (Thurston County), Rawleigh Irvin, Dave Johnson, Kathy Lyle,
John McCardle (Skagit County), Sharon Miller (King County), Mel Rigdon (Yakima County), Craig Stoner, Fred Thompson, Mark Tipps (Thurston County), Craig Stoner, Ernie Veach-White, Mike Wait (Clallam County), Rich Wilson (Cowlitz County), Deborah Yonaka, John Bauer, Norma Bryce, Mike Curtis, Alan Erickson, Allyson Erickson, Virginia Neal, Charlene Stevenson
Absent: Bill Holmes, Margaret Yetter, Vacant Limited Jurisdiction Court Representative
The purpose of this meeting is to:
Review detention requirements with detention managers;
Complete items deferred from the Committee’s January meeting;
Review Probation, Dependency, and Law Table requirements; and
Define Report requirements.
Charlene gave a brief system overview for the benefit of the detention managers/staff present by reviewing the new JUVIS model bubble charts and their relationships to existing functions.
Persons and organizations
- Uniquely identified persons: Juvenile, parents, and aliases.
Name and identifiers (PINs)
Address
Alias
Relationships
- Uniquely identified groups: Agencies and organizations.
Name
Address
- Unidentifiable persons: Codefendants, care takers, siblings, victims, etc.
Name
Address
Referral
- Uniquely identified with new numbering structure (to be determined).
- Referral reason becomes a subset of the referral number (unlimited number of reasons for referral).
- Capture referral reason using RCW number instead of codes.
- Can be created automatically from detention during screening process.
Referral Case Management Chart
The following chart is a high-level picture which shows how the case management function relates to existing JIS functions and newly created JIS (JUVIS) functions.
Superior Court (SCOMIS)
Entry of docket codes
Changes in cause of action
Entry of resolution and completion codes
Court Automated Proceedings (CAPS)
Setting of calendar dates
Recording of a (dismissed, continued, etc.) hearing outcome
Recording of minute entries
JASS Accounting
Entry of payments
Entry of legal financial obligations, including restitution
Detention
Entry of tracking records
Probation Management
Entry of compliance
Entry of violations
[pic]
Creation actions are equivalent to filing events.
1. DETENTION REQUIREMENTS
Detention Detail Screen
JVARUF1 DETN FACILITY: Z991 01/13/98 15:32:26 PAGE 1 OF 2
CONTROL# 099242 DETN# 001 CTY: 31
NAME SMITH, JOHN A.K.A. SMITH, JOHN
DOB 080865 AGE 32 SEX M RACE 0 EYES ___ HAIR ___ HGT 0 00 WGT 000
SSN ___ __ ____ DRIVER LICENSE# ____________ STATE ID# __________
MARKS/SCARS ____________________________________________________________
CONTACT ___________________________________ HME ___ _______ WRK ___ _______
NOTIFIED ___________________________________ DATE/TIME ______ ____
ARREST DATE/TIME ______ ____ ARRESTING OFFICER ____________________
AGENCY ____ REPORT# _________ RFL# A 010
HOLD FOR/RECORD ACCESS 99
WARRANT _
NEW REFERRAL REASONS
___ _____ ___ _____ ___ _____ ___ _____
___ _____ ___ _____ ___ _____ ___ _____
SCREENED BY ___ DATE/TIME ______ ____
DECISION _ A/R/P DATE/TIME ______ ____ RELEASE TO ____________________
COMPLETE, CHANGE, OR ADD ENTRIES AND (ENTER); OR (CLEAR) TO CANCEL
Detention Tracking Screen
JVARUF2 DETN FACILITY: Z991 01/13/98 15:36:54 PAGE 2 OF 2
CONTROL# 099242 DETN# 001 CTY: 31
NAME SMITH, JOHN A.K.A. SMITH, JOHN
STA: TIME DETAINED TO DATE DAYS HOURS MIN
LOC: NEXT-IN NEXT-OUT
ALRT1 ______ BY1 ___ CMT1 __________________________________________________
ALRT2 ______ BY2 ___ CMT2 __________________________________________________
LVL 0 CMT3 _________________________________________________________________
REFERRAL RECORD REFERENCE A: 010 B: ___ C: ___ D: ___ E: ___ F: ___
SCROLL SIZE 05
TYPE DESC RFL
LN BY DATE TIME CODES SEQ TO/COMMENT DESCRIPTION
KLS 011398 0300 SCR ____ ___ ____________________
KLS 011398 0300 LOC ____ ___ ____________________
KLS 011398 0300 STA ____ 010 ____________________
KLS 011398 0300 ADM ____ ___ ____________________
KLS ______ ____ NXT ____ ___ ____________________
___ ______ ____ ___ ____ ___ ____________________
___ ______ ____ ___ ____ ___ ____________________
___ ______ ____ ___ ____ ___ ____________________
___ ______ ____ ___ ____ ___ ____________________
___ ______ ____ ___ ____ ___ ____________________
COMPLETE, CHANGE, OR ADD ENTRIES AND (ENTER); OR (CLEAR) TO CANCEL
1. On-line Review
The current detention(episode) number is based on the juvenile control number and a system generated number starting with one (001). It is used to identify each unique detention episode for a juvenile. Since the juvenile is being separated from the detention data, a unique number for detention must be identified.
1.1 How is the detention number used within the facility?
RESPONSE:
5. Tracks detention history statewide, need sequential aspect for a person to track detention episode count statewide.
6. Need number of days served on a referral in a specific facility. Would like to have the ability to distinguish time served in another county’s facility, to track time served by episode and by county, and to track total time served for a referral.
7. Made a note that if change in facility, need new episode. Need many (referrals) to many (episodes) relationship.
8. Detention episode number is person-facility based.
1.2 What problems are introduced by changing the structure of the detention number?
RESPONSE: None.
1.3 Is it possible for a referral reason to be tracked in multiple episodes at the same time?
RESPONSE: No.
Definition of detention episode is kid-in/kid-out. Kid can have only one episode at the same time. For one episode, track calendaring. Charlene asked if having a list/report of all entries calendared would meet this need and the only entries tracked with detention are the reasons for the episode. The work group felt this would satisfy the need. What is calendared for a kid statewide needs to be available to detention center where kid is resident.
A detention episode is referral reason based. When screening occurs, the referral and the specific reasons are needed. When a juvenile is screened into detention and the referral has not been created, it is a requirement to create an episode automatically.
A juvenile is added to a detention episode (during manual episode creation) using a phonetic name search. An option to search for parents and alias names phonetically during the detention intake process will need to be developed. However, these parties can be added without unique identification. All parties added during this process will be added to the referral if it does not exist.
1.4 Parents are currently not captured during the screening process but are available on the Master file. Would it be useful to have this information available with each episode?
RESPONSE: Yes, if it exists on system. The information may be unavailable to detention.
1.5 If an episode exists and a new referral is attached to the episode, which parties are used from the episode to create the new referral? (Assuming parents are attached to an episode)
RESPONSE: All parties—prefill information on subsequent episodes (modifiable); ability to search for all parties and re-use as much as possible while allowing for updates; relationships should remain with episode.
1.6 (A) Can an episode be created which refers to a new referral and an existing referral or (B) is the episode created with one referral then additional referrals are attached?
RESPONSE: A detention e episode is created with one referral then additional referrals can be attached to it.
Need the ability to create an episode across county boundaries. A detention facility can be in a different county than the referral.
1.7 Can the first referral be considered the “primary referral” or should the current rule for determining “primary referral” still be enforced? The current rules are:
9. Only referrals that are “open” (no ENS record) may be a primary;
10. Pre-adjudication status referrals are primary over post-adjudication status;
11. The highest offense severity level associated with a referral takes precedence for open referrals which have the same status; and
12. For “open” referrals with the same referral status and same severity level, the lowest referral sequence number is the primary referral.
RESPONSE: Use current rule and display primary referral as default but allow user to override. For reporting—split pre-adjudication and post-adjudication.
1.8 If the current rules are being used, shall we use category since severity will be removed in the new system?
RESPONSE: Yes.
1.9 Can the referral date be used to define which referral occurred first (replace the lowest referral sequence number)?
RESPONSE: Yes.
1.10 When the juvenile court determines a kid is to be sent to detention, can a detention entry be created automatically?
RESPONSE: Yes, but make it optional. When entry is created, the detention date due-in reservation should be captured and intended length of stay should be record without affecting the actual population count.
1.11 If there are multiple active episodes for the kid and we automatically create (a JUVIS reason assigned to detention) detention entries, can it be determined which episode should be used?
RESPONSE: On TLV (temporary leave from an existing episode), can determine because it will be closed and new episode will be created. If not on TLV, rule changes depending on the county.
ISSUE: How can we determine which episode to use if there are multiple active episodes and we are assigning a referral reason to detention?
1.12 Are there times when an existing episode should be used when we are automatically creating an episode?
RESPONSE: Always use existing episode.
ISSUE: The current business rule is to close an active episode, then create a new one if a kid is on temporary leave and is re-admitted into detention. Cannot currently have more than one active episode. The group felt this rule needs to be changed and referred it to the detention managers committee.
The current detention system allows you to:
13. Enter detail information about an episode (Detention Detail),
14. Track various movements in the facility or when the kid is temporarily released from a facility (Detention Tracking),
15. Enter many entries at one time on an episode (Quick Entry), and
16. View and/or print detention history summaries, reports, and forms.
The same functionality will be included in the new system, but how these functions are presented and maintained will be changed. The following changes have been identified:
17. The need to record the release date and time;
18. The need to track the legal status;
19. The ability to keep a history of tracking records;
20. The ability to easily identify which referral time is being served;
21. Wen a juvenile is in detention and a warrant has been issued, the system should notify (give a warning message) the user of the warrant;
22. Ability to track more than two alerts and comments;
23. Alerts should be statewide and a history should be kept;
24. The ability to identify pre-adjudication (before findings), pre-disposition (before sentence), and post-disposition (after sentence) time served.
1.13 There is an existing request to increase the number of referrals associated with an episode from six. Is there a limit to the number of referrals that can be attached?
RESPONSE: No limit.
1.14 What changes should be made to the screening and admission process?
RESPONSE: Ability to record release date for “good time” served and for regular time release date. Also need to be able to enter race code.
1.15 How should the temporary leave and release process be changed?
RESPONSE: TLV—on readmit, provide optional court-based re-calculation of release date based on TLV duration.
1.16 What information is needed about the facility that can be part of the statewide system?
RESPONSE: Electronic monitoring tracking. Add additional level of tracking by adding new codes for detention types and statuses.
1.17 IN-DATE, OUT-DATE, and CENTER are obsolete data items stored on the Master file. Can we assume we will not convert this data since it is not displayed or used anywhere in current JUVIS? Note: Only 1% of the referral records have this information.
RESPONSE: Don’t convert.
1.18 There are approximately 87,000 old detention records on file which can be accessed with the JIMU transaction (control and detention number must also be provided). This is not a supported process and does not appear to be used. Can we assume this data will not be converted nor retained for historical purposes in the new system?
RESPONSE: Don’t convert.
1.19 Is there additional functionality needed in the new JUVIS model?
RESPONSE: Additional space for alert comments; larger comment line.
2. Forms
After reviewing the forms which are being produced for sixteen(16) courts, with additional courts being added because new facilities are being built, there appears to be no duplicate or similar forms. A copy of all existing forms is in the reports booklet.
2.1 Does the current form generation process meet your needs?
RESPONSE: No; need flexible (interactive) form generation/modification process. Current forms are not used.
2.2 Should form generation be handled at the local level?
RESPONSE: Yes, assuming data availability.
2.3 If not, are there additional form requirements?
RESPONSE: No, because new forms generation process needs to be created.
2.4 Which forms can be changed?
RESPONSE: Standard change process will be used.
2.5 Which forms can be eliminated?
RESPONSE: The following counties do not use the current form generation process:
Pierce Snohomish Clark
Clallam Grant Lewis
Skagit
The following counties use the current form generation process:
Benton/Franklin Cowlitz (face sheet only)
Yakima Mason
The following counties were not present but have forms:
Spokane Thurston Whatcom
Chelan Clallam Grays Harbor
Okanogan
Counties not listed do not currently have forms.
1. Reports
Review the detention reports in the reports booklet. For each report, consider:
3.1 If changes are required?
RESPONSE: Ability to run a report (including birth date) for a specific date. Add alerts to 607. 611 needs codes for Border Patrol, Tribal Police. 605 needs subtotals by gender.
3.2 What additional reports are needed?
RESPONSE: Mel will send survey to detention managers.
3.3 Which reports can be eliminated?
Because many existing JUVIS reports were seen for the first time, we could not determine if changes were needed or if the report is useful. Virginia will run all reports for the members of the Committee and they will verify the output and usefulness of the report and report back at the next meeting.
The following list of reports can all be submitted from the JUVIS Detention Reports Menu.
|JVR600 |Detention Population Roster (Detail Report) |
|JVR601 |Detention Referred But Not Admitted Report |
|JVR602 |Releases Report |
|JVR603 |Detention Population Summary Report |
|JVR604 |New Admissions To Detention Population |
|JVR605 |Alphabetical Listing Of Juveniles In Detention Center |
| |Subtotals On Gender |
| |Ability To Sort By Location |
|JVR606 |Alerts Report |
|JVR607 |Detention Room List |
| |Print Alerts |
|JVR608 |Detention List Of Juveniles With Scheduled Events |
|JVR609 |Juveniles On Temporary Leave |
|JVR610 |Juveniles Pending Screening Decision |
|JVR611 |Juveniles Held For Other Counties/Agencies |
| |Reflect Status hold for. Conversion--Don’t convert; run report before conversion|
| |and change status on primary referral. |
|JVR612 |Referral Status Report |
a) Are all of these reports needed?
b) Are these reports satisfying Detention Requirements?
The following list of reports can be submitted from the Job Submit Menu and report strictly from data which has been extracted from Detention. The extract occurs around the 3rd of each month.
|PRDJ700 |Admission And Release |
|PRDJ701 |Admission And Release/Non-DJR |
|PRDJ702 |Length Of Stay At Release |
|PRDJ703 |Length Of Stay At Release/Non-DJR |
|PRDJ704 |FTE For New Admissions And Carryovers |
|PRDJ705 |Carryover Name List |
|PRDJ706 |Admissions Referral Reasons By Age |
|PRDJ707 |Admissions Referral Reasons By Ethnic Group |
|PRDJ708 |Daily Population 6:00 a.m. Snap-Shot |
|PRDJ709 |Daily Population |
|PRDJ710 |Federal Census Admissions Report |
|PRDJ711 |ADM/Release Time Of Day - SCR/REL Length |
(a) Are all of these reports needed?
(b) Have not seen any use of PRDJ701 and PRDJ703, can these be eliminated?
(c) As reports PRDJ708 and PRDJ709 are titled Daily Population, are they useful since the data is a monthly extract?
2. APPROVE JANUARY 14-15 MEETING MINUTES
The minutes were approved as amended below:
Page 1 - Page 8, #4 & 5 from December 17-18 meeting minutes should read:
“4. Event - In detention
Outcome: Notifications
A) Probable Cause hearing/order within 48 hours of arrest
B) Information filed within 72 hours of arraignment or booking from detention admission excluding weekend and holidays, county-specific
C) Petition Detention hearing within 72 hours of filing petition/
information
D) Arraignment within 14 days of filing
E) Trial within 40 30 days of arraignment
F) Disposition within 14 days of adjudication
5. Event - Petition filing, not in detention
Outcome: Notifications
A) Arraignment within 14 21 days of filing
B) Trial within 60 days of arraignment
C) Disposition within 21 days of adjudication”
Attachment 6: Probation, Page 34, Questions/concerns raised by Committee should read:
“Probation conditions, violations and terminations should be separate from Chrono-notes.”
3. ISSUES
Alan stated that the Committee needs to start thinking about the work group (16-18 members, some from this Committee) which will be involved in design. Some of the issues: responsibility for business issues, “best practices” work group.
4. REQUIREMENTS REVIEW
1. Juvenile Transfers
The following is a data representation of how a referral would look if transferred. Note the minutes from our January (attachment 4, case management) meeting for the event model.
Refer: 9401-00194 Type: JO Date: 01 20 1994 Dist: Thurston
Source: Intake Date: 01 20 1994 By: HUL
Agency: Mason Sheriff’s Office Agy Nu: B981432
Court#: 94 8 01234 Filed: 02 08 1994 Court: S34
Intake: Date: Assignor: HOB Date: 01 20 1994
Prob Off: Date: Contact: Date:
Reason: 001 Theft3 Date: 01 20 1994
Days Detention: Date:
Status Status description Date Src User
FOR Forward to Another County 01 30 1994 J23 ABC
CAC Accept from County 02 07 1994 J34 BXC
INF Information Filed 02 08 1994 S34 IKP
PTH Pre-trial hearing 02 24 1994 S34 UKT
The transfer process as described by Charlene was acceptable to the work group. Juvenile transfers can be handled in the new model. For both juvenile and CLJ courtesy probation supervision, legal jurisdiction remains in the originating court while probation cases are managed by another court.
ISSUE: Transfer for interstate/inter-country courtesy supervision is a requirement (probation case must be created without a link to a legal case), but there is no statute to support it.
1. Conversion of JUVIS Calendar Data
The following is calendar information currently being captured:
Court case number 5 characters
Hearing officer 3 characters
Disposition date 8 characters
Hearing time 4 characters
Hearing type 2 characters
Court room 3 characters
SCOMIS case number data
Site 2 characters
Case type 2 characters
Year 2 characters
Sequence no 5 characters
Check digit 1 character
2.1 It was stated that the court case number will not be converted. Not true any more. What should be done with calendar information which has the court case number? Alan says convert them where they exist alone, convert SCOMIS number where there is one. Can you use the real SCOMIS number to calendar when implemented? 5 digit serial number case number has only historical value at the time of implementation. Could that field be turned off now? Form 6 prints the 5 digit number so it is used now. Form needs to be looked at. Probably not enough room to print the full SCOMIS number on it now. How to convert cannot be resolved until issue below is resolved.
ISSUE: Keep or remove court case number? Questionnaire will be sent to the 22 courts using Calendaring to determine if the 5-digit number is being used.
2.2 Are the current calendar entries used for court dates or are other types of activity being scheduled (e.g., diversion meetings)?
RESPONSE: Yes, for other activities; for example, diversion is identified by hearing officer code. Conversion process will assume the referral is being scheduled if the court case number and SCOMIS data are blank. For historical calendar information, past dates will not be converted to the new system.
2.3 Is there a need for multiple jurisdictions (Benton/Franklin) to get a list of all cases scheduled in the juvenile court?
RESPONSE: Yes, need calendar that combines the county cases for hearing in a single facility.
2.4 Should referrals be scheduled in CAPS or should the court case be scheduled and notify JUVIS of the scheduled event (what part does the juvenile court play in process)?
RESPONSE: Both.
1. CAPS Outcome Issue
At the last meeting, we were unclear how CAPS would capture the outcome from a hearing. The CAPS team stated they would be capturing minute entries but the level of detail is not known at this time. Minute entries are part of Phase I and standard minute categories will be created for statewide use.
Since these entries may not capture the level of detail needed by the juvenile courts, we will change the disposition bubble to outcome. We stated at our last meeting the need to capture different types of outcomes. The outcome type will be better defined as we explore what information is captured with an outcome. Coordination of CAPS minute entry discussions will continue.
ISSUE: Need a common data entry screen for conditions of sentence; who enters additional conditions of sentence information into the system?
1. Probation
At our last meeting, we discussed the need to capture:
25. Various types of outcomes, not just arraignment as depicted before;
26. Ability to enter conditions of a violation via outcome type;
27. Capture restitution, detention, and fees as line items since they occur most frequent; and
28. Violations at the condition level.
The following is a sample of data to meet those needs.
Reason: 001 No Parent or Guardian Willing or Capable Date: 06 15 1994
Outcome: FACTF Response : __ __ __ ____
Finding/Jdgmt: ORDD 06 19 1994 Judge: JUD Fnd/Jdgmt Rev : 12 19 1994
Jdgmt Rsn: __
Fine: ___________ Suspended Fine: ___________
Restitution: ___________
Detention: ___ _
Violation: __ __ ____
Other Review Total Time Total Fees Assign
Cond Date Time Serve Fees Paid Contact Super Violation Cmp
CDF 06 20 1995
ACTION: In Probation and Calendaring, move Chrono-notes to Participants and Probation bubbles. Add a section on the outcome screen for fees and community service.
5. Dependency
After reviewing the diagram for dependency case flow, the following is an example of what would appear in JUVIS when a dependency case is filed in SCOMIS.
Refer: 9406-02102 Type: JD Date: 06 12 1994 Dist: J34
Source: Intake Date: 06 12 1994 By: HUL
Agency: DSHS Agy Nu: 9833432
Court#: 94 301245 Filed: 06 11 1994 Court: S34
Intake: SWA Date: 06 12 1994 Assignor: OBL Date: 06 13 1994
Prob Off: Date: Contact: YUJ Date: 06 23 1994
Reason: 001 No Parent or Guardian Willing or Capable Date: 06 15 1994
Days Detention: Date:
Status Status description Date Src User
PLADNF Rec’d Placemnt Invest. Request-Dep 06 09 1994 J23 SWA
CDF Custody to DSHS; Foster Care 06 12 1994 J23 SWA
DPF Dependency Filed 06 15 1994 S34 ABC
SHELTR Shelter care hearing requested 06 17 1994 S34 Dyr
FFH Finding of dependency 06 17 1994 S34 JUD
FFDHD Disposition hearing 06 19 1994 S34 Dyr
ORDD Order of dependency 06 19 1994 S34 juD
REvewd Regular review of prior disp-Depend 12 19 1994 S34 Dyr
PPHDEP Permanency plan hrg sch-dependenc 12 28 1994 S34 DYR
REvewd Regular review of prior disp-Depend 06 12 1995 S34 Dyr
PPHDEP Permanency plan hrg sch-dependenc 12 28 1995 S34 DYR
Party Seq Party Begin Date end date
DeP 1 Williams, James 06 15 1994
PAR 1 Jones, Diane 06 15 1994
GAL 1 DSHS div 34 06 12 1994
INT 1 Harrison, ford 06 12 1994
ASG 1 olsen, Linda 06 13 1994
CON 1 Yearly, Jim 06 23 1994
Comments: Need to capture DSHS Caseworker as a party on the case; don’t know where this information comes from.
29. A referral can exist with statuses before a dependency case is filed.
There are three referral reasons as reflected in RCW 13.34.030, that can be used for SCOMIS DEP cause;
REFERRAL REASON DESCRIPTION
NPGWC No Parent or Guardian Willing or Capable
ABNEG Abuse/Neglect
ABAND Abandonment
4.1 What determines the reason given a cause DEP?
ISSUE: Not a one-to-one relationship.
4.2 Can the referral be created when the DEP case is filed or is there a delay?
RESPONSE: Yes; there is no delay.
4.3 Which court level is responsible for 12 month permanency planning goal?
RESPONSE: Superior court (order).
4.4 Which court level is responsible for the six month review?
RESPONSE: Superior court.
6. Law Table
At our last meeting, we decided to separate the current JUVIS tables into different tables. The proposed breakout of all JUVIS codes are in Attachment 1. Five tables are identified currently:
30. Law Table - Has the RCW associated with the reason for the referral. These entries are used to track activity involving a referral to the juvenile court.
31. (Referral) Case Management - Has status information about a referral reason, intake decision, or disposition code. All the data displayed is in reference to the referral reason being displayed and tracked.
32. Outcome - Has information which will be used as an outcome to a hearing or special processes, like a diversion or probation
33. Conditions - Has information which will be used as conditions to an outcome. This table will change as it is better defined.
ISSUES:
1. The conditions vary at each court level. When probation is tracking and entering discretionary conditions, will statewide codes be used or will they be controlled at the court level?
1. Will discretionary conditions be part of the court ordered conditions? They should be identified with the JUVIS outcome process but should they be reflected in court processes like PLS?
34. Deleted Items - Has information which will not be converted.
Comment: Need specific offense descriptions on forms.
Several corrections were made. See Attachments 1 for revisions.
Committee question: Why are disposition codes in case management?
RESPONSE: There were several codes in the disposition table which Charlene felt were not disposition but case management. From the January meeting, Charlene was tasked with separating the current JUVIS tables into the proper table in the new system. These codes must be reviewed and verified for completeness. The codes will be reviewed several times for categories and tie case management codes to new JUVIS in JIS.
Question: Alan asked about emancipation of minor—
Do we need to create referral for these?
Are they filed in superior court?
Does petitioner need to be uniquely identified?
Are mental illness cases filed in juvenile court?
ACTION: OAC will check system to see what courts are using these codes.
ISSUES:
1. How to deal with emancipation of minors and mental illness, step-parent adoption cases when juvenile courts are performing investigations.
1. Need to determine if O/C will be tied to case management status codes or use a process.
When these codes are converted, old codes will be end-effective dated if used, and not converted into new JUVIS if code is not used.
Committee Question: Will adults use same table for conditions of outcome?
RESPONSE: Don’t know yet what edits will be applied to codes. We will try to make new codes consistent in JIS; coordination is needed with superior and limited jurisdiction requirements for recording outcome conditions.
Question: How should we convert the Public and Private Agency disposition codes?
ACTION: Virginia will do a query to see who uses these besides Spokane.
7. Criminal History
What should show on criminal history? There are two rules, a general and a specific rule, in the current system.
The general rule has four criteria:
35. The referral reason must have a severity rating of 1 through 9. Most are marked with an asterisk (*) in the first position of the code title in Appendix 5. (JUVIS Codes Manual)
36. The intake decision must show a diversion or filing action. Most are marked with an asterisk (*) in the first position of the code description column in Appendix 8. (JUVIS Codes Manual)
37. The history control field must have an entry that indicates criminal history.
38. A found guilty (F), plead guilty (P), or criminal history diversion (V) indicates a finding of guilt.
1. Can we simplify the general rule, above, to be based on the referral type and on the finding of guilt, a plea, or diversion?
RESPONSE: Yes, need to define referral types. This means the new general rule becomes:
• The referral reason must be included on a referral whose referral type is determined using a category code. Therefore, all referral reasons with a category code can be given one or more referral types. Whatever referral types are determined to be valid for criminal history will be used in the criteria.
• A found guilty, plead guilty, or criminal history diversion indicates a finding of guilt.
What types of offenses could be on same referral?
RESPONSE: Need business rule.
RESPONSE: If there is an outcome, it should show as criminal history.
ISSUE: Who records outcome for criminal history?
An adjudication date MUST be entered to show the date that a finding was made.
The specific requirement address when a referral can be displayed on the Form 6 and the Criminal History Display screen (on-line version of the Form 6). Both are dependent on rules used for the History Control Codes setting.
The Form 6/Criminal History screen is broken into three sections:
39. Deferred Adjudication/Disposition,
40. Criminal History, and
41. Pending Matters.
Deferred Adjudication/Disposition Section
A referral will be reported under this section based on the disposition codes associated with the referral reason code. Each referral reason line for a referral is reported in this section if the associated disposition code is either
731 (DEA - Deferred Adjudication) or
732 (DDS - Deferred Disposition)
Additionally, these same referrals may also be reported under the Criminal History or Pending Matters, depending on further tests.
Criminal History Section
A referral will be reported under this section based on the history control code associated with the referral reason. Each referral reason line for a referral is reported in this section if the associated history control code is either
42. P (plead guilty) or
43. F (found guilty) or
44. V (diversion) or
45. @ (old system generated code indicating reason should be counted as history)
When setting the history control code, the following conditions must be met:
46. If the history control code is set to P, F, or V, the referral reason code on the table (Appendix 5) must have its valid for criminal history flag set.
47. If the intake decision code has been recorded for the referral reason, it must have its valid for criminal history flag set on the table (Appendix 8).
48. If a disposition has been recorded, at least one of the disposition codes must be valid for criminal history (Appendix 13).
Pending Matters Section
A referral will be reported under this section based on the values associated with each referral reason. In order to be reported, the following conditions must be met:
49. The valid for criminal history flag for the referral reason must be set
50. If there is no intake decision for the reason, the reason is considered pending
If there is an intake decision, the following conditions must also be met:
51. The intake decision must be either valid for criminal history (based on a flag) or be considered open (based on a flag)
The history control code must be blank; if the history control code contains an ‘X’ or a ‘#’ (neither counts as criminal history), then the disposition codes are tested.
The dispositions codes must be blank for the reason to be considered Pending.
If a disposition code is found, if must be considered an open disposition to be considered Pending.
FORM 6 Review
The group reviewed the Form 6 and determined the following changes:
Add Diversion Section (Note: Diversions do not count as criminal history after 7/1/98)
Alias & IN #
Race
Ethnic Group (Hispanic/Non/Unknown) Living With
Legal Parents with Addresses School District & Name
Take Out Census Items B, D-N Probation Officer Information
Include referral and court case information
Referral# Case#
Category Intake Officer
Status Date Current Status (Last Case Management)
Court Case # (SCOMIS or CLJ #) Hearing Type
Judge Remove History Control
Disposition/Adjudication Date Remove Disposition Applied
1 Outcome
Question: For conversion, Clark uses JUVIS control number as its social file number—do any other courts do this?
Does Form 6 have to be a form or could it be a report?
RESPONSE: Form 5/6 can be reports. They will be reports in the new system.
Question: Who receives Form 6?
ISSUE: Case history with outcome also needed.
Scheduled Batch Reports
ACTION: Members need to review their court’s scheduled report list, the following questions, and identify new report requirements for the next meeting.
General revisions to all reports:
Change Control # to IN #
Change Seq to Referral #
Records Management
The following reports are used to identify juveniles who may qualify to have their records destroyed as per RCW 13.50.050.
| | |
|JVR001 |Juveniles 23 Years and Older |
| |(used to id social files for destruction) |
| | |
| |MODIFICATION: |
| |Change to 27 |
|JVR008 |Juveniles Eighteen Years Of Age Or Older |
| |(used to pull old files for archiving or destruction) |
| | |
| |MODIFICATIONS: |
| |Add Social File # |
|JVR801 |Juveniles 18 Years And Older With One Diversion Only |
| |(used to destroy diversion files) |
| | |
| |MODIFICATIONS: |
| |Remove Intake Section |
| |Remove Disp Date |
Note: Cover archiving and destruction (questions 1 - 5) of records at a future meeting.
1. What records management tasks should be done at age 18?
2. What records management tasks should be done at age 23?
3. Who should be responsible for these tasks? (Note person information will be secured at a statewide level, and referral/case information will be secured at the court level).
4. Can the record destruction process be automated?
5. Can we archive referral and or case information at any time?
6. Is there any point in continuing with any of these reports?
RESPONSE: Yes.
Juvenile Lists - Based on Selection Criteria
The following reports list juveniles based on some selection criteria. The criterion is referral reason, intake decision, or disposition code. In some cases all three are used for selecting juveniles to report on.
|JVR014 |Juveniles With Sex Offenses |
|JVR016 |Juveniles With Probation Violations Filed |
|JVR7062 |Warrants Outstanding/Selected Warrant Dispositions |
|JVR7063 |Juvenile Offenders Who Are Due To Have A Review |
|JVR7064 |Warrants Issued On Court Order And Warrants Authorized |
|JVR7067 |Penalty Assessments By Class Of Offense |
ACTION: Virginia will run set up reports for each court represented in the Committee.
1. Are these reports providing the needed information?
2. Though the selection criteria may differ, can the reports all include the same information and display it all in the same format?
3. Can the reports be generated from an extract rather than from live data?
4. Can the requirements for this type of report be met by using a query tool?
5. Dependency/ARP/CHINS Hearings, report JVR7061, uses calendar information. What changes are required?
Juvenile Lists - Official Activity Lists
The following report is on workloads for the various officials. Also included in this group is a list of juveniles based on the referral agencies.
|JVR111 |Probation Officer Report |
|JVR140 |Referral Source Report |
|JVR3100 |Intake Officer Activity Report |
|JVR3200 |Assignor Activity Report |
|JVR460 |Judicial Workload Report |
1. Are these reports currently meeting management needs to track the workload of staff?
2. JVR3100 and JVR3200 also report on statistical information for each officer. Should this statistical information remain as part of this report? Or would a separate report better serve the need? Would a query tool allow the statistical information to be gathered?
3. The JVR3100 & JVR3200 reports both include a Calendar Date and a Disposition Date. Currently, these should be the same value in JUVIS. What date should be reported on for the activity lists, a Disposition Date or a Hearing Date? Or is either date necessary?
4. JVR460 actually has 5 separate types of reports rolled into one large report for each Judicial Officer. One section of the report falls into the Juvenile List category. The other 4 sections are statistical. Should the report be broken into smaller, more manageable pieces?
5. The section titled Number of Hearings Held is reporting on calendar information. Would it be a good candidate for a query tool?
6. The section titled Hearing Held reports on Hearings Held by Type of Hearing and by Type of Offense. Should changes be made given this information is stored in CAPS?
7. If the activity reports, which have statistical information, can be removed leaving only the juvenile lists, can a standard format be used for presenting the lists. That is, each list would include the same information and be laid out in the same manner. If this were possible, what information about the juvenile would be needed?
8. If a standard format can be determined for the activity lists, can this same format be used for the lists of juveniles based on selection criteria?
Statistical Information - Offense Activity
The following report statistical information is based on offense activity. Counts are done for all offenses, primary offenses, and diverted/adjudicated primary offenses. Counts are accumulated by case types and can be reported by age, sex, and ethnicity.
|JVR005 |Diverted/Adjudicated Primary Offense Activity |
|JVR3000 |Total Offense Activity By Sex |
|JVR3001 |Total Offense Activity By Age |
|JVR3002 |Total Offense Activity By Ethnicity |
|JVR3010 |Primary Offense Activity By Sex |
|JVR3011 |Primary Offense Activity By Age |
|JVR3012 |Primary Offense Activity By Ethnicity |
1. What offense related statistical information is needed?
2. Do these reports provide the needed information?
3. Can the reports be generated from an extract rather than from live data?
4. Can requirements for this type of statistical information be met by using a query tool?
5. Is there a need to collect non-offense related statistics on the same report (i.e., non-offense and dependency reasons are counted on these reports)?
Statistical Information - Counts
The following reports provide simple counts.
|JVR015 |Count Of ARPs/CHINs, Deps, And Info Filed |
|JVR7060 |Count Of Juveniles By School Code With Referral Activity |
1. Can the reports be generated from an extract rather than from live data?
2. Can requirements for this type of statistical information be met by using a query tool?
The following two reports provide matrix style counts using referral reasons, intake decisions, and disposition codes.
|JVR7065 |Court Summary (Intake Decision Codes 400 & 402) |
|JVR7066 |Diversion Summary Report (Intake Decision Codes 101 & 106) |
1. Can the reports be generated from an extract rather than from live data?
2. Can requirements for this type of statistical information be met by using a query tool?
Social-Biographical Information Report, JVR230, provides counts for information reported in the Census Data fields of the Master Update Screen.
1. As all but the Ethnic Origin and Presently Living With categories will be eliminated, is there a need to keep this report?
The Management Summary report, JVR7040, is the most complex of all the JUVIS reports. It gathers data and produces 5 sections.
1. Is this report currently meeting management needs?
2. Are all the sections of the report necessary?
3. As section 4 is reporting on hearing information, would additional information be needed since more data is being captured?
4. Could some of the information be extract using a query tool and be eliminated from this report?
Reports to Outside Agencies
The next two reports have been created within the last couple of years and are intended to satisfy legislative requirements to report to outside agencies.
|JVR250 |School Report for Juveniles With Adjudicated or Diverted Offenses |
|JVR315 |Juvenile Justice System Process Review Report |
| | |
| |ACTION: |
| |Remove Option B |
| | |
| |Add Chemical Disposition Alternative subtotal |
| |Change Deferred Adjudication to Deferred Disposition. |
| | |
| |Add mandatory and discretionary declines of jurisdiction and mandatory decline |
| |hearings to report. |
| | |
| |Add deferred prosecution decisions and link it to case dismissal/subsequent |
| |prosecution. |
1. Are these reports providing the needed information to satisfy the legislative requirements?
2. What concerns are there regarding the information being reported on the JVR315 report?
6. NEXT MEETING: March 19, 2 Union Square, Seattle
Future meetings were set for April 16, May 20, June 23.
ATTACHMENT 1
This table has the RCW associated with the reason for the referral. These entries are used to track activity involving a referral to the juvenile court.
|RCW |Reason |Cat |Description |Begin Date |End Date |
|FEDERAL |00615 |C |Federal Mail Theft |19871125 | |
|CYL94E1 |00656 |C |Theft of a Firearm |19960307 |19971015 |
| 9.40.100 |00908 |E |Tampering w/Fire Alarm |19871125 | |
| 9.40.120 |00206 |A |Possession of Incendiary |19940607 | |
| 9.41.025 |00508 |C+ |Commit Crime Armed |19871125 | |
|9.41.040 |00449 |B |Unlawful Possession of Firearm 1 as of 7/23/95 |19960507 | |
|9.41.040 |00634 |C |Possession of a Firearm by a Minor |19970711 | |
|9.41.040 |00655 |C |Unlawful Possession of a Firearm |19940606 |19971015 |
|9.41.040 |00658 |C |Unlawful Possession of Firearm 2 as of 7/23/95 |19960507 | |
| 9.41.050 |00913 |E |Possession of Concealed Weapon |19871125 | |
|9.41.230 |00844 |D |Discharge of Dangerous Weapon as of 6/13/94 |19960621 | |
| 9.41.230 |00921 |E |Discharge of Dangerous Weapon |19871125 |19971015 |
| 9.41.240 |00920 |E |Firearm by Minor |19871125 |19971015 |
|9.41.250 |00708 |D+ |Possession of Dangerous Weapon |19890929 | |
| 9.41.270 |00814 |D |Carry/Display Dangerous Weapon |19871125 | |
| 9.41.280 |00817 |D |Student Carrying Weapon |19880426 | |
| 9.47A.050 |00917 |E |Unlawful Inhalation of Toxic Fumes |19871125 | |
| 9.61.160 |00411 |B |Bomb Threat |19871125 | |
| 9.61.230 |00642 |C |Repeat Harassment on 9.61.230 |19880322 | |
| 9.61.230 |00842 |D |Obscene Harass Phone Call After 1985 |19880322 |19971015 |
| 9.61.230 |00910 |E |Obscene/Harassing Phone Call |19871125 | |
|9A.08.020 |00238 |A |Accomplice to Class A Offense |19940607 | |
|9A.08.020 |00138 |A+ |Accomplice to A+ Offense |19940607 | |
|9A.08.020 |00290 |A- |Accomplice to A- Offense |19940607 | |
|9A.08.020 |00438 |B |Accomplice to Class B Offense |19871125 | |
|9A.08.020 |00442 |B |Accomplice to Burglary 2 |19871125 | |
|9A.08.020 |00444 |B |Accomplice to Residential Burglary |19910214 | |
|9A.08.020 |00446 |B |Accomplice to Theft 1 |19871125 | |
|9A.08.020 |00338 |B+ |Accomplice to B+ Offense |19871125 | |
|9A.08.020 |00342 |B+ |Accomplice to Burglary 1 |19871125 | |
|9A.08.020 |00637 |C |Accomplice to Taking Motor Vehicle |19871125 | |
|9A.08.020 |00638 |C |Accomplice to Class C Offense |19871125 | |
|9A.08.020 |00538 |C+ |Accomplice to C+ Offense |19871125 | |
|9A.08.020 |00838 |D |Accomplice to Class D Offense |19871125 | |
|9A.08.020 |00738 |D+ |Accomplice to D+ Offense |19871125 | |
|9A.08.020 |00938 |E |Accomplice to Class E Offense |19871125 | |
|9A.08.040 |00937 |E |Conspiracy to D Offense |19910923 | |
|9A.20.010 |00399 |B+ |Other B+ Offense |19871125 | |
|9A.20.010 |00699 |C |Other Class C Offense |19871125 | |
|9A.20.010 |00599 |C+ |Other C+ Offense |19871125 | |
|9A.20.010 |00899 |D |Other Class D Offense |19871125 | |
|9A.28.020 |00313 |B+ |Attempted A- Offense |19900105 | |
|9A.28.020 |00389 |B+ |Attempted Other Class A Offense |19940607 | |
|9A.28.020 |00654 |C |Attempted Residential Burglary |19910214 | |
|9A.28.020 |00669 |C |Attempted Other Class B Offense |19871125 | |
|9A.28.020 |00569 |C+ |Attempted Other B+ Offense |19871125 | |
|9A.28.020 |00869 |D |Attempted Other Class C Offense |19871125 | |
|9A.28.020 |00769 |D+ |Attempted Other C+ Offense |19871125 | |
|9A.28.020 |00989 |E |Attempted Other Class D Offense |19871125 | |
|9A.28.040 |00240 |A |Conspiracy to Murder 1 |19940607 | |
|9A.28.040 |00340 |B+ |Conspiracy to A+ Offense |19940607 | |
|9A.28.040 |00440 |B+ |Conspiracy to Class A Offense |19951130 | |
|9A.28.040 |00640 |C |Conspiracy to Class B Offense |19871125 | |
|9A.28.040 |00641 |C |Conspiracy to Burglary 2 |19871125 | |
|9A.28.040 |00540 |C+ |Conspiracy to B+ Offense |19871125 | |
|9A.28.040 |00840 |D |Conspiracy to Class C Offense |19871125 | |
|9A.28.040 |00740 |D+ |Conspiracy To C+ Offense |19871125 | |
|9A.28.040 |00940 |E |Conspiracy to D+ Offense |19871125 | |
|9A.32.030 |00252 |A |Attempted Murder 1 |19940607 | |
|9A.32.030 |00102 |A+ |Murder 1 |19940607 | |
|9A.32.050 |00203 |A+ |Murder 2 |19940607 | |
|9A.32.055 |00207 |A |Homicide by Abuse |19940607 | |
|9A.32.060 |00307 |B+ |Manslaughter 1 |19940607 | |
|9A.32.070 |00502 |C+ |Manslaughter 2 |19940607 | |
|9A.36.010 |00101 |A |Assault 1 |19940607 |19971015 |
|9A.36.011 |00103 |A |Assault 1 as of 7-1-88 |19940607 | |
|9A.36.020 |00301 |B+ |Assault 2 |19940607 |19971015 |
|9A.36.021 |00418 |B |Assault 2 as of 7-1-88 |19940607 |19971015 |
|9A.36.021 |00320 |B+ |Assault 2 as of 7-1-89 |19940607 | |
|9A.36.030 |00501 |C+ |Assault 3 |19871125 |19971015 |
|9A.36.031 |00647 |C |Assault 3 as of 7-1-88 |19880714 |19971015 |
|9A.36.031 |00520 |C+ |Assault 3 as of 7-1-89 |19890713 | |
|9A.36.040 |00701 |D+ |Simple Assault |19871125 |19971015 |
|9A.36.041 |00819 |D |Assault 4 |19880714 |19971015 |
|9A.36.041 |00707 |D+ |Assault 4 as of 7-1-89 |19890630 | |
|9A.36.041 |00962 |E |Attempted Assault 4 |19890630 | |
| | | | | | |
|9A.36.045 |00657 |B |Reckless Endangerment 1 as of 6-13-94 |19940727 |19971015 |
|9A.36.045 |00326 |B+ |Drive-by Shooting as of 7/1/97 |19970711 | |
|9A.36.045 |00651 |C |Reckless Endangerment 1 as of 5-7-89 |19910131 |19971015 |
|9A.36.050 |00703 |D+ |Reckless Endangerment |19871125 |19971015 |
|9A.36.050 |00710 |D+ |Reckless Endangerment as of 7/1/97 |19970711 | |
|9A.36.050 |00821 |D+ |Reckless Endangerment 2 as of 5-7-89 |19910131 |19971015 |
|9A.36.060 |00509 |C+ |Promote Suicide Attempt |19871125 | |
|9A.36.070 |00705 |D+ |Coercion |19871125 | |
|9A.36.080 |00624 |C |Malicious Harassment |19871125 | |
|9A.36.090 |00667 |C |Threaten Governor or H/H Family |19970903 | |
|9A.36.100 |00627 |C |Custodial Assault as of 7-1-88 |19880510 |19971015 |
|9A.36.100 |00513 |C+ |Custodial Assault as of 7-1-89 |19890630 | |
|9A.36.150 |00827 |D |Interfering w/DV Reporting |19970903 | |
|9A.40.020 |00202 |A |Kidnapping 1 |19940607 | |
|9A.40.030 |00306 |B+ |Kidnapping 2 |19940607 | |
|9A.40.040 |00507 |C+ |Unlawful Imprisonment |19871125 | |
|9A.40.050 |00803 |D |Custodial Interference |19871125 |19971015 |
|9A.40.060 |00661 |C |Custodial Interference 1st |19970903 | |
|9A.40.070 |00662 |C |Custodial Interference 2nd-2nd Offense |19970903 | |
|9A.40.070 |00807 |D |Custodial Interference 2nd |19970903 | |
|9A.40.090 |00635 |C |Luring |19970903 | |
|9A.42.020 |00420 |B |Criminal Mistreatment 1 |19880809 | |
|9A.42.030 |00628 |C |Criminal Mistreatment 2 |19880809 | |
|9A.44.030 |00204 |A |Rape 1 |19940607 | |
|9A.44.040 |00322 |B+ |Attempted Rape 1 |19940607 | |
|9A.44.050 |00297 |A- |Rape 2 |19940607 | |
|9A.44.050 |00308 |B+ |Rape 2 |19940607 |19971015 |
|9A.44.050 |00323 |B+ |Attempted Rape 2 |19940607 | |
|9A.44.060 |00504 |C+ |Rape 3 |19940607 |19971015 |
|9A.44.060 |00522 |C+ |Rape 3 |19970903 | |
|9A.44.060 |00709 |D+ |Attempted Rape 3 |19900529 | |
|9A.44.070 |00298 |A- |Statutory Rape 1 |19940607 |19971015 |
|9A.44.070 |00310 |B+ |Statutory Rape 1 |19940607 |19971015 |
|9A.44.073 |00291 |A- |Rape of Child 1 |19940607 | |
|9A.44.073 |00324 |B+ |Attempted Rape of Child 1 |19940607 | |
|9A.44.076 |00421 |B |Rape of Child 2 as of 7-1-89 |19940607 |19971015 |
|9A.44.076 |00325 |B+ |Rape of Child 2 as of 7/1/97 |19970711 | |
|9A.44.076 |00512 |C+ |Rape of Child 2 |19880908 |19971015 |
|9A.44.076 |00519 |C+ |Attempted Rape of Child 2 7-1-89 |19940607 | |
|9A.44.079 |00648 |C |Rape of Child 3 |19940607 | |
|9A.44.079 |00823 |D |Attempted Rape of Child 3 |19900529 | |
|9A.44.080 |00506 |C+ |Statutory Rape 2 |19871125 |19971015 |
|9A.44.083 |00292 |A- |Child Molestation 1 as of 7/1/97 |19970711 | |
|9A.44.083 |00315 |B+ |Child Molestation 1 |19940607 |19971015 |
|9A.44.083 |00521 |C+ |Attempted Child Molestation 1 |19940607 | |
|9A.44.086 |00425 |B |Child Molestation 2 as of 7/1/97 |19970711 | |
|9A.44.086 |00316 |B+ |Child Molestation 2 |19880809 |19971015 |
|9A.44.086 |00636 |C |Attempted Child Molestation 27-1-89 |19940607 | |
|9A.44.086 |00518 |C+ |Child Molestation 2 as of 7-1-89 |19940607 |19971015 |
|9A.44.089 |00649 |C |Child Molestation 3 |19940607 | |
|9A.44.089 |00824 |D |Attempted Child Molestation 3 |19900529 | |
|9A.44.090 |00626 |C |Statutory Rape 3 |19871125 |19971015 |
|9A.44.093 |00650 |C |Sexual Misconduct w/Minor 1 |19940607 | |
|9A.44.093 |00825 |D |Attempted Sexual Misconduct w/Minor 1 |19900529 | |
|9A.44.096 |00820 |D |Sexual Misconduct w/Minor 2 |19880809 | |
|9A.44.096 |00941 |E |Attempted Sexual Misconduct w/Minor 2 |19900529 | |
|9A.44.100 |00304 |B+ |Indecent Liberties |19940607 |19971015 |
|9A.44.100 |00328 |B+ |Indecent Liberties/Violent |19970904 | |
|9A.44.100 |00419 |B+ |Indecent Liberties as of 7-1-88/Not Violent |19940607 | |
|9A.44.105 |00665 |C |Sexually Violating Human Remains |19970903 | |
|9A.44.110 |00511 |C |Com w/Minor Immoral Purpose Prior |19940607 | |
|9A.44.130 |00670 |C |Failure to Register as Sex Offender (Class A |19971121 | |
| | | |Offense) | | |
|9A.44.130 |00833 |D |Failure to Register as Sex Offender (Not Class A|19971121 | |
| | | |Offense) | | |
|9A.46.020 |00643 |C |Repeat Harassment on 9A.46.020 |19900105 | |
|9A.46.020 |00841 |D |Harassment Class D |19880322 | |
|9A.46.080 |00928 |E |Violate No Contact Order |19970903 | |
|9A.46.110 |00666 |C |Stalking/Class C Offense |19970903 | |
|9A.46.110 |00831 |D |Stalking/Class D Offense |19970903 | |
|9A.48.020 |00201 |A |Arson 1 |19940607 | |
|9A.48.030 |00401 |B |Arson 2 |19940607 | |
|9A.48.040 |00606 |C |Reckless Burning 1 |19871125 | |
|9A.48.050 |00808 |D |Reckless Burning 2 |19871125 | |
|9A.48.070 |00404 |B |Malicious Mischief 1 |19871125 | |
|9A.48.080 |00604 |C |Malicious Mischief 2 |19871125 | |
|9A.48.090 |00805 |D |Malicious Mischief 3 |19871125 | |
|9A.48.090 |00904 |E |Malicious Mischief (Under $50) |19871125 | |
|9A.48.110 |00927 |E |Defacing a State Monument |19970903 | |
|9A.52.020 |00302 |B+ |Burglary 1 |19871125 | |
|9A.52.025 |00443 |B |Residential Burglary |19900726 | |
|9A.52.030 |00402 |B |Burglary 2 |19871125 | |
|9A.52.030 |00652 |C |Attempted Burglary 2 |19871125 | |
|9A.52.060 |00801 |D |Burglary Tools Possession |19871125 | |
|9A.52.070 |00802 |D |Criminal Trespass 1 |19871125 | |
|9A.52.080 |00901 |E |Criminal Trespass 2 |19871125 | |
|9A.52.095 |00622 |C |Vehicle Prowling 1 |19871125 | |
|9A.52.100 |00810 |D |Vehicle Prowl |19871125 |19971015 |
|9A.52.100 |00815 |D |Vehicle Prowling 2 |19871125 | |
|9A.52.100 |00980 |E |Attempted Vehicle Prowl |19871125 | |
|9A.56.030 |00406 |B |Theft 1 |19871125 | |
|9A.56.040 |00608 |C |Theft 2 |19871125 | |
|9A.56.040 |00858 |D |Attempted Theft 2 |19871125 | |
|9A.56.050 |00809 |D |Theft 3 |19871125 | |
|9A.56.050 |00979 |E |Attempted Theft 3 |19871125 | |
|9A.56.0604 |00659 |C |Unlawful Issuance of Check >$250 |19960621 | |
|9A.56.0605 |00845 |D |Unlawful Issuance of Check ................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.