HMIS XML v2.8 was just released in April 2008, so we haven't gathered requirements yet for 3.0.
- Need to synchronize 3.0 again with CAN Client Data Standard XML. Here are the elements in CDS and whether or not there is a corresponding HMIS 2.8 data element:
| CDS .301 | HMIS 2.8 | Notes |
| Client | Person | |
| FirstName | LegalFirstName | |
| MiddleName | LegalMiddleName | |
| LastName | LegalLastName | |
| Suffix | LegalSuffix | |
| DateOfBirth | DateOfBirth | |
| Ethnicity | Ethnicity | |
| Race | Race | |
| Gender | Gender | |
| PreDisasterLivingSituation | residence | Note: it was requested to remove pre and post disaster living situation (or residence) and just have living situation with a date stamp. |
| CaseID | not in standard (add in 2.9 by importing from CDS) | |
| PreferredLanguage | not in standard (add in 2.9 by importing from CDS) | |
| EnglishSpeaker | not in standard (add in 2.9 by importing from CDS) | |
| DateReleaseSigned | (implied effective date, period not tracked) ReleaseGranted, EffectivePeriod (date signed not tracked) | |
| DisasterEventDate | not in standard (add in 2.9 by importing from CDS) | |
| AliasOrLegalName | OtherNames sequence which includes OtherFirst, Middle, Last, Suffix | |
| FEMARegistrationNumber | not in standard (add in 2.9 by importing from CDS) | |
| GovernmentShare | not in standard (add in 2.9 by importing from CDS) | |
| IncidentDRONumber | not in standard (add in 2.9 by importing from CDS) | |
| IndividualRecordID | !PersonID | |
| Addresses (with PreDisaster flag) | PersonAddress (Predisaster flag not needed, since this could be determined from a DisasterEventDate) | |
| BestPhone | PersonPhoneNumber | |
| OtherPhone | PersonPhoneNumber (multiple allowed, “best” flag add attribute in 2.9) | |
| VerificationDocumentation | not in standard (add in 2.9 by importing from CDS) | |
| ServicesNeeded | Need | |
| ServicesProvided | ServiceEvent | |
| Referral (with string ResourceName and Referral Description, etc.) | IsReferral is compatible except that it doesn't allow for a string description or resource name -> just uses AIRS (which CDS also has) | |
| SpecialNeeds | not in standard (add in 2.9 by importing from CDS) | |
| ReleaseInformation | Documentation | |
| DisasterName | not in standard (add in 2.9 by importing from CDS) | |
| CaseManager | not in standard (add in 2.9 by importing from CDS) | |
| CaseManagerBestPhone | not in standard (add in 2.9 by importing from CDS) | |
| DamageAssessment | not in standard (add in 2.9 by importing from CDS) | |
| AltContactBestPhone | not in standard (add in 2.9 by importing from CDS) | |
| AltContactOtherPhone | not in standard (add in 2.9 by importing from CDS) | |
| Narrative | not in standard (add in 2.9 by importing from CDS) | |
| Household | Household | |
| HouseholdID | HouseholdID | |
| HohID | HeadOfHouseholdID | |
| Members | Members | |
| MemberID | PersonID | |
| RelationshipToHoh | RelationshipToHeadOfHousehold |
Fix Needed: Make the ServiceType reference the tTaxonomy code in the same way Needs do. Also add version number restrictions picklist to the code.
Possibly change SourceDatabase to just dataroot. Then have SourceDatabase as the repeatable first/only subelement. That might be better than the current 2.8 way, which is more flattened.
Time Zones: Double check that either UTC is specified or offsets are allowed for in the schema. http://en.wikipedia.org/wiki/ISO_8601#Time_zone_designators
The definition of the hmis:decimal type has in its annotation Program-Specific Data element 3.1 which is not the case. Make sure the actual place 3.1 is has the correct annotation.
-Eric
