1 / 13

OASIS Litigant Portal Technical Committee

OASIS Litigant Portal Technical Committee. Face-to-Face Meeting August 21 st to 22 nd , 2017 IAALS at University of Denver. Monday, August 21, 2017. Tuesday, August 22, 2017. Litigant Portal Overview. 1. Increase assistance for legal problems

pelham
Download Presentation

OASIS Litigant Portal Technical Committee

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OASIS Litigant Portal Technical Committee Face-to-Face Meeting August 21st to 22nd, 2017 IAALS at University of Denver

  2. Monday, August 21, 2017 • Tuesday, August 22, 2017

  3. Litigant Portal Overview 1. Increase assistance for legal problems 2. Improve integration of self-help resources 3. Improve focus on potential litigants 4. Increase use of non-traditional resources Registration/ Login Description/ Navigation Problem Identification Solutions Assistance Tradeoff Preferences Probabilistic Outcomes Capacity Assessment

  4. Monday, August 21, 2017 • Tuesday, August 22, 2017

  5. Data Flow - Registration & Login Module Registered & Anonymous User Profile/Status What is an issue? Is there a issue? Status of Litigant/Issue 2. Referrals Provided 3. Referrals Accepted or Rejected 4. System/Self Assessment of Tradeoffs, Capacity Assessment, Assistance (urgency, complexity, etc.), Navigation, & Problem Identification Modules 5. Qualifications/Eligibility for Referrals (Financial, Geography, Subject Matter, Immigrant Status, etc.) Registered User 1. Case Details (For existing cases, ECF Standardized, multi-system interoperability) 2. Case Roles & Associations 3. Basic Demographic Information 4. Optional – Financial & Circumstantial Details Framework to Synchronize Credentials

  6. Data Flow - Description & Navigation Module • Orientation of the Litigant • i.e., Doc Assembly is step 3 of 7, and referral receiving should know next steps to route the Litigant

  7. Data Flow – Problem ID Module Case Type/Area of Law Urgency Location/Jurisdiction Marital Status Family Relationships Immigration Staatus Age (Senior Citizen) Disabilities Language Proficiencies (Other Languages Spoken) Other Legal Problems/Cases Litigant Identity Employment Status Assistance for Someone Else (Juvenile/Senior Citizen) Real Estate vs. Family Attorney Conflict of Interest Information RE: Conflict Resolution Financial Status/Circumstances (Indigency Status/Affordability) ( Are details about the specific problems outside of the scope of OASIS standards? i.e. why is the litigant being evicted, etc.)

  8. Data Flow – Problem ID Module Case Type/Area of Law Urgency/Emotion

  9. Data Flow – Solutions Module Financial Status/Circumstances (Indigency Status/Affordability) Solution(s) Selected (i.e. lawyer referral, doc assembly, etc.) Solution(s) Sub-category Legal versus Non-Legal Solutions (i.e., social services, etc.) Subsequent Determinations (i.e. other problems identified during the use of the solution selected) Service Provider Discovery (input required to triage and output from triage)

  10. Data Flow – Assistance Module • Legal Service Providers • 1. Referral Number (to track users and cases over the life cycle) • 2. Legal Subject Matter Included in Service Provider’s Priorities (i.e. LSC Problem Codes & National Subject Matter Index) • a. Code Number of Case Type • b. Where code is from • 3. Service Provider’s Available Capacity (each service will maintain resource availability in their own systems) • a. Code Number for Case Type • b. Where code is from • c. Availability (Numerical or True/False) • d. Referral Accepted or Rejected • Information Required by Service Provider • (i.e. Name, Demographic Information, Financial Information, Subject Matter, and Capacity Information) • Libraries • SNAP (Benefits Providers)

  11. Data Flow – Tradeoff Preferences Module 1. Time 2. Cost 3. Process Complexity 4. Due Process 5. Predictability of Outcome 6. Enforceability

  12. Data Flow – Probabilistic Outcomes Module • Case Types (ECF Standards) • Issue Type (NSMI) • 3. Outcome Types • - winning/losing • - judgment amount vs. claimed amount • 4. Probability Score • - Consider prior cases outcomes

  13. Data Flow – Capacity Assessment Module Urgency (Score(s)/Scale) 1. There is urgency 2. Basis for that assessment (i.e. Domestic Violence, Garnishment imminent, legal filing deadline) 3. What is the urgency Complexity (Score(s)/Scale) (Self and/or system determined) 1. Number of Jurisdictions (Incl. any foreign jurisdictions) 2. Limited ability to resolve the matter 3. Multiple/Number of legal issues Situational Complexity User Capacity (Score(s)/Scale) (Need a better understanding of what goes into making a determination) (Self and/or system determined) 1. Technical Skills/Ability to use automated systems 2. Languages 3. Literacy 4. How score was derived 5. User’s Prior Legal Experience 6. Social Support (support to take on effort required – take time off, have a baby sitter, have someone to discuss issues with)

More Related