Name | Kind | Description |
Search for Court Case | use case | |
Select Resolution | use case | Help potential litigants decide how best to resolve their legal problem |
Select Type of Assistance | use case | Help litigants decide if they need full legal representation Help potential litigants decide what kind of legal assistance they need. |
SelectedProviderName | attribute | Name of Provider (Legal or DBA) |
SelectedSolutionType | class | |
Sequence1 | sequence diagram | |
ServiceArea | attribute | The area in which the solution provider provides the services. The service area taxonomy is identified in ServiceAreaTaxonomy, |
ServiceAreaTaxonomy | attribute | The taxonomy used to identify service areas (e.g. OCID). |
ServiceProvided | attribute | A message from the Provider system outlining the services that were provided to the user. (Service Types will be mapped to standardized lists, such as Open Referral) |
ServiceType | class | |
SolutionCategoryDeclined | attribute | Categories of solutions the user explicitly declined to use. User may decline more than one category. (Categories will be mapped to standardized lists, such as Open Referral and should be same as "Assistance > Input > Provider Profile > Provider Categories" Refer to list discussion under Issue Type.) |
SolutionCategorySelected | attribute | Categories of solutions selected by the user. User may select more than one category, i.e. legal services and document assembly. (Categories will be mapped to standardized lists, such as Open Referral and should be same as "Assistance > Input > Provider Profile > Provider Categories" Refer to list discussion under Issue Type.) |
SolutionOptionsInputMessage | class view | |
SolutionOptionsInputMessage | class diagram | |
SolutionOptionsInputMessage | class instance | |
SolutionOptionsInputMessage | class | |
SolutionOptionsInterface | class | |
SolutionOptionsModule | component | If the problem identified is not a legal problem, the portal may suggest several generic non-legal solutions with an appropriate handoff. If the problem is a genuine legal problem, it should suggest several alternative solutions, some of which involve the formal legal system and some of which do not. In both cases the module should provide appropriate tradeoff information to aid the litigant in making a choice. Comments and Issues: Some non-traditional options may be appropriate in some cases. For example, in some states one option might be a tribal court. Legal problems that appear to track the traditional court process may be open to various types of diversion at various points in the process. The portal should make those options clear, even where the litigant does not have full control over the decision. Policies around data transparency and access must be made clear to all users of the modules in the portal, especially for this module (and the Capacity Assessment module below). |
SolutionOptionsOutputMessage | class view | |
SolutionOptionsOutputMessage | class instance | |
SolutionOptionsOutputMessage | class | |
SolutionOptionsOutputMessage | class diagram | |
SolutionPathwaySelectedByUser | class | |
SolutionProvideProfileInterface | class | |
SolutionProvider | class | |
SolutionProviderProfileModule | component | |
SourceSystemOfRegistration | attribute | Name (Legal Name or DBA) of source system where user created an account. |
State | attribute | |
State | attribute | |
StateJurisdiction | attribute | Geographically, the state(s) that may have jurisdiction over the legal issue(s). State jurisdiction should be associated with System Determined Issue(s). There may be multiple states with jurisdiction for different legal issues. |
StepName | attribute | |
StepOrder | attribute | |
Stereotypes | class view | |
StreetName | attribute | |
StreetNumber | attribute | |
StreetNumber | attribute | |
SystemConfidenceScore | attribute | |
SystemDetereminedUrgencyType | attribute | Types of urgencies as identified by the Problem Identification Module (i.e., eviction, physical danger, etc.). These urgencies may or not have been identified by the user. |
SystemDeterminedDeadline | attribute | Deadlines identified by the system based on the System Determined Urgency Types. These deadlines may or may not be in lined with the User Stated Urgency Deadline(s). Based on System Determined Issue(s), User Stated Timing of Issue(s), and User Stated Urgency Deadlines, the system can determine important timeframes and deadlines. There may be multiple deadlines for different issues. |
SystemDeterminedRankOrderOfPreference | attribute | This message is generated by the system and ranks in order of importance: 1) time, 2) cost, 3) process complexity, 4) due process, 5) predictability of outcome, and 6) enforceability based on user interaction and session data. |
SystemDeterminedScoreOfPreferences | attribute | This message is generated by the system and provides a score (i.e. 1 to 10 or 1 to 100) for each of the following: 1) time, 2) cost, 3) process complexity, 4) due process, 5) predictability of outcome, and 6) enforceability based on user interaction and session data. |
SystemDeterminedUrgencyDeadline | attribute | Deadlines identified by the system based on the System Determined Urgency Types. These deadlines may or may not be in lined with the User Stated Urgency Deadline(s). |
SystemDeterminedUrgencyLevel | attribute | The Problem Identification module will formulate an urgency level based on the System Determined Issues, System Determined Urgency Types and Deadlines. We need to discuss if the LP TC should standardize the output of this assessment as a level (high, medium, low) or a score (0 to 10). |
SystemDeterminedUrgencyLevel | attribute | The Problem Identification module will formulate an urgency level based on the System Determined Issues, System Determined Urgency Types and Deadlines. We need to discuss if the LP TC should standardize the output of this assessment as a level (high, medium, low) or a score (0 to 10). |
SystemDeterminedUrgencyType | attribute | Types of urgencies as identified by the Problem Identification Module (i.e., eviction, physical danger, etc.). These urgencies may or not have been identified by the user. |