UUIDs for Location.id, HealthcareService.id and Organization.id

The following Implementation guidance to be added to the IG:   HSDS (v.2.0.1) was the  basis for  requirements, and the mapping/alignment of HSDS data elements to profiles contained in the FHIR IG for Human Service Directories, STU1.  HSDS Version 2.0.1 applies string datatypes to nearly all HSDS table 'id' fields/ data elements, including the  id  field associated with each HSDS table (e.g.  organization.id [organization.id] ,  location.id [location.id] ,  service.id [service.id] ,  phone.id [phone.id] , etc.). In the next version of HSDS, v.3.0, each HSDS  table.id [table.id]  field will be defined using as a UUID. FHIR Resource  .ids    (and the . ids  in their inherited profiles)  are  defined with the FHIR  id  datatype, a string that supports " Any combination of upper- or lower-case ASCII letters ('A'..'Z', and 'a'..'z', numerals ('0'..'9'), '-' and '.', with a length limit of 64 characters. (This might be an integer, an un-prefixed OID, UUID or any other identifier pattern that meets these constraints.)".  Because UUIDs provide uniqueness to data/resources when they are exchanged across multiple systems, it is recommended that implementers of the FHIR IG for Human Services Directories support UUIDs in all HSDS id fields to be mapped to FHIR  .id  data elements.