Resource Locations

From FMYiRCWiki

Freemed-YiRC: Resource Locations

Contents 1 Summary 2 TERM: Resource ? 3 Visual Overview 4 Modifications required 5 Custom Fields 6 REPORTS 7 KEY CONSIDERATIONS

NOTE: This module has been created. Please see the Resource Location Module page for more information!

Summary

This article is currently used as a brainstorming page for a possible new FMYiRC module: Resource Locations. This module would be a listing point for foster homes, respit homes, adoption homes, etc...

TERM: Resource ?

• As opposed to directly using the terms foster, respite, adoptive, and possibly others. Would it be feasible to use the term resource?
  • WHY? - From my understanding, these types of functions are somewhat similar in nature (i.e., requiring the same types of documentation, fields, etc...)
    • Otherwise, these items would need to be created each individually, each requiring more effort. If it can be done once to describe common functions (and possibly unseen future functions), that saves time for all and could possibly make it more applicable to future expansion.
  • A database table of Resource Types would be included in Freemed-YiRC. This could be modifiable by the agency to add or remove types as needed.
    • This list could include:
      • Foster
      • Respite
      • Adoptive
    • i.e., if an agency only did Foster, they could just list foster. If they did foster and respite, those could be listed. Other unused items could be removed, so they would never be seen for a given agency. However, common standard types would be required, as to aid in information sharing down the road (i.e., electronic transfer of information between capable agencies)
  • Would Treatment Foster be another term, or does it fall under generic foster?
• A Resource Location would refer to a foster home, respite home, or adoptive home. And possibly others.
  • Can a location be have multiple uses? Could a foster home also be a respit or adoptive home?
    • Or would it make sense to create multiple entries for this location (i.e., the same location could be listed multiple times?)

Visual Overview

Thoughts from Jeff:

Terms: 1. “Resource” would be an appropriate synonym for a wide variety of caregivers. 2. Because foster care (generic umbrella term) has four license options (each with different requirements), perhaps we would do better to have: Pre-Adoptive Infant Foster, Family Foster, Treatment Foster, and Medically-Fragile Foster. In this way, as we create licensing modules, each identified type of resource would promulgate different screens. 3. “Resource Location” strikes me as a wonderful and encompassing generic term for virtually all treatment/care locations. a. A resource location can, in fact, have multiple uses. i. Instead of multiple listings, a single location able to identified as a multiple resource location might be less cumbersome. b. Many foster homes are also licensed as adoptive homes. c. HONH also has foster homes that are respite homes.

Modifications required

• Contact DB: Residents
  • A new section would be added titled Resource Location History. This would be similar to Groups. Except this would keep a history of all resource locations this client has been located in. The history would include:
    • The link to the resource location
    • Start date
    • End date
    • Notes
    • Another possible field would be an Experience Rating for this placement. This would be done after the placement experience. This could be used to rate if this placement experience at this location was positive or not. A scale would need to be developed...
      • Not positive, somewhat positive, neutral, somewhat negative, negative?
      • More research would be required
      • Otherwise, multiple fields could be developed to measure specific items... behavior, etc...
• Contact DB: NEW SECTION - Resource Staff
  • Is Staff a feasible term? In Freemed-YiRC currently, I use staff to indicate personnel who are on direct wage payroll. i.e., administrative staff, group home staff, etc...
    • I would like to avoid staff if possible, as well as parent.
    • Caretaker?
  • This section would be somewhat similar to the Staff type, except it will require less fields.
  • WHAT FIELDS ARE REQUIRED?
    • What kind of info do you store about foster/respite/adoptive parents?
    • DOB
    • Start date with agency (could also be indicated by history, but this could be used as a generic start date, making some reports easier)
    • SSN?
    • License info? (foster, etc...? I don't know if such things exist, or are licensed to the location)
    • etc...
  • A section called Resource Location History would be added similar/identical to what is listed under the Contact DB for Residents as described above... location, start date, end date, notes, etc...
• NEW MODULE - Resource Locations
  • This would be a menu option on the front page.
  • Locations would be somewhat similar to Groups as currently listed in the Freemed-YiRC system.
    • Standard fields would include:
      • Address
      • Telephone #
      • Fax #
      • Notes
      • Licensing info..
        • Would this require a history? i.e., license renewals, etc...?
    • A location could also be linked to a FMYiRC group. I believe right now we've created groups to form regions, or a group for foster, respite, etc...
      • This would aid in security. If a staff (social worker?) were to be limited to a specific region or type (foster, respit, etc...), linking this location to a group would be key here.
      • This would also aid in reporting efforts (i.e., automatically creating sub-sections in the report)
  • For administrative staff, the Location Types editing functionality would be a menu option here
    • i.e., the ability to determine if an agency makes use of foster, respite, adoptive, etc... (as discussed above)

Custom Fields

• The FMYiRC Contact Database contains the functionality to dynamically, on-demand, create custom fields that may be associated with one or more types of contacts (Residents, Staff, Standard, etc...). The Resource Locations module contains similar functionality. Custom fields may be created and linked to one or more Resource Types.
• This functionality should enhance data collection and reporting capabilities.

REPORTS

• For starters, the module would include the following printable reports:
  • Resource Locations list
  • Current Client Location Report
    • Would display all current clients and which location they are at.
      • Include Start date?
      • Sortable by either client or location
  • Client Resource Location History
    • FOR A GIVEN CLIENT - Would show all locations a client has been associated with (i.e., which location, start date, end date, notes, etc...)
      • Could also make use of the experience items discussed above
  • Current Staff Location Report
    • Would display all current staff and which location they are at.
      • Sortable by either staff or location
      • Include Start date?
  • Staff Resource Location History
    • FOR A GIVEN STAFF - Would show all locations a staff has been associated with (i.e., which location, start date, end date, notes, etc...)

KEY CONSIDERATIONS

• Is Resource a usable term?
• Is there something better than the term staff? Something other than parent? Caretaker?
• Would the above linkages work?
  • i.e., linking client to location, as well as staff to location?
• Would the default reports be sufficient for starters?
• Would something similar to the dynamic ContactDB Reports module be useful?
  • Or would modification to the ContactDB Reports be more useful for it to make use of Resource Staff? Since clients are already in there.
    • However, this would not be able to show Resource Locations...
• IS THIS GETTING TOO COMPLEX?
  • Is this trying to solve problems that don't exist?
  • Does this in fact solve most forseeable problems?

• Documentation