R

Name	Kind	Description
ReasonforAccomodation	attribute
Receive Court Reminders	use case
ReceiveCourtRemindersInterface	class
ReferralProvided	attribute	The referrals provided to the user can be tracked as tags and communicated between portal modules and Service Provider systems. (Referral Categories will be mapped to standardized lists, such as Open Referral.)
ReferralStatus	attribute	Acknowledged: This message indicates that the Provider system acknowledged the referral. Accepted: This message indicates that the Provider system explicitly accepted the referral. This may be based on manual action taken by the Provider or based on Provider system automation. Rejected: This message indicates that the Provider system rejected the referral. This may be based on manual action taken by the Provider or based on Provider system automation.
ReferralStatusType	class
ReferralSystemName	attribute	The name of portal, system, or entity providing the referral to the user.
ReferralSystemURL	attribute	Referral System's website where the user should be returned, if no specific URI/URL is available.
ReferralSystemUserSpecificURI	attribute	If available, the Referral System's unique URI/URL, specific to the user, where the user should be returned.
ReferralType	class
ReferralType	class
ReferralType	attribute
RegistrationLoginInputMessage	class view
RegistrationLoginInputMessage	class instance
RegistrationLoginInputMessage	class diagram
RegistrationLoginInputMessage	class
RegistrationLoginInterface	class
RegistrationLoginModule	component	Litigants may use the portal anonymously by not registering or logging in. If users wish to save their inputs or outputs and return at a later time, they must register in a way that enables identification of them in some unique way (although not necessarily in a way that permits actual identification of the person). Comments and Issues: Partner organizations will probably want to use their login methods, so the most efficient approach would be a consistent single sign on model for all of the partner organizations. Achieving this goal could be difficult. It is a classic governance problem.
RegistrationLoginOutputMessage	class view
RegistrationLoginOutputMessage	class instance
RegistrationLoginOutputMessage	class
RegistrationLoginOutputMessage	class diagram
Report Outcomes	use case	Automatically report provider outcome information to the portal Collect litigant satisfaction with outcomes
Request Accomodation	use case
RequestAccomodationInputMessage	class view
RequestAccomodationInputMessage	class diagram
RequestAccomodationOutputMessage	class view
RequestAccomodationOutputMessage	class
RequestAccomodationOutputMessage	class diagram
RequirementsfoAccomodation	attribute
ReturnToReferralSystem	class
ReturnURLforUser	attribute	If the user should be returned to a specific page on the portal, this URL will route the user to the appropriate point in their process.
Role	attribute
RoleType	class
Route Clients to Providers	use case	Automatically route eligible clients to appropriate providers.