Out of curiosity, why isnt this table included in the documentation?
Yes 2.7 is the latest.
Actually, it isn't necessarily the case that there needs to be a household
table. The Householdid is used simply as a value to group clients
together (or more precisely, to group clients together within a particular
program participation, since household affitiliation is not really static
across
a clients' range of program use.)
In the model, there are no other data elements in the specification that
are collected at the "household" level as a distinct entity apart from the
individual clients, and therefore there is no table for it. That is, not
all clients in a family have the same name or race, they might not all
have first become homeless on the same date, . Put another way, if there
were such a table, it would only contain the primary key.
It does get a little tricky when using the service table, since services
can apply to a whole household, but not necessarily. We compensate with the
"SeviceUnit" field on the ServiceTable.
I hope that helps.
Brian Sokol
Abt Associates Inc.
Phone: 617-349-2532
Fax: 617-349-2670
http://www.abtassociates.com
"Robert
Santorelli"
<SONORACA@gmail.c To
om> "HMIS_Data_Integration"
Sent by: <HMIS_Data_Integration@googlegroups
HMIS_Data_Integra .com>
tion@googlegroups cc
.com
Subject
[HMIS Data Integration] Household
03/23/2007 03:21 id no primary key?
PM
Please respond to
HMIS_Data_Integra
tion@googlegroups
.com
-----------------------------------------
This message may contain privileged and confidential information intended
solely for the addressee. Please do not read, disseminate or copy it unless
you are the intended recipient. If this message has been received in
error, we kindly ask that you notify the sender immediately by return email
and delete all copies of the message from your system. Thank you.