Open DaleFitch opened 10 years ago
Looks like we have a new vocabulary term candidate. In HMIS, they call it a "target population". Sort of cold: "target lock acquired: commence service sequence". Maybe "intended community" served?
"Target population" works for me. We most likely only want agencies to include these terms when it become an exclusion criteria for someone who is not a part of that population.
Hi Dale and Eric, this is well established in the AIRS world. Target Populations is one entire branch of the Taxonomy. The convention is to always use a Target Population in conjunction with a base service term, and the syntax is to connect them with an asterisk. Relatedly, base service terms can also be used standalone if they serve the general population.
Examples of using Target populations (these are real taxonomy terms): Dog Walking Services * Experiencers of Paranormal Phenomena Fast Food Chicken * School Dropouts
Conceptually that makes sense to me - thanks Neil
But target populations served are different than eligibility requirements and exclusions, Dale. You won't be able to determine populations that are excluded by looking at target population indexing. Another reason why there needs to be a way to capture this information separately. I know Neil has mentioned the distinction elsewhere.
Where would I find the descriptors related to "domains" that go beyond classifying an agency. That is, the elements used on most online resource directory sites that only contain service, location, etc., do not capture the domain or population actually served. For example: You can have a "housing" agency that serves senior citizens among other age groups. However, a housing agency for seniors will be specifically geared to addressing the needs of seniors who may have various types of housing needs dependent upon age (young senior vs older senior), independent living status (very independent with ADLs to very dependent on ADLs), and various income categories. As such, where will agency domain be captured?