Alignment with upcoming HSDS 3.0

There are backwards incompatible changes in the upcomming HSDS 3.0.

Here is a list of the changes that will affect this IG, with notes on their consequences:

• Merging of postal_address and physical_address to address
  • This should have very little effect on the IG itself as the FHIR representation already merges these. This will only affect the mappings, not the fields or definitions in the IG.
• service_attributes and other_attributes renamed to attributes
  • This should also have little effect and only affect the mappings.
• Removal of the eligibility table in preference to using attributes.
  • This is currently not mapped in the IG so should have very little effect
• Organization.tax_id is being deprecated but being replaced with new organization_identifier table

• New table could supply more fields to the FHIR Organization.identifier section.
• Should only affect mapping

• A few small field name changes
• This should only affect the mappings also.

HSDS 3.0 will have a standardised JSON representation and API specification. This will be a recommended way to publish HSDS in future.  Here is an example of a service object with all its fields https://raw.githubusercontent.com/openreferral/specification/3.0-dev/examples/service_full.json.  Having the JSON representation could make the mappings easier and clearer as you would not have to specify join conditions.  We are, however, keeping the datapackage/ database schemas as recognized representation formats, so specifying the mappings like they currently are should not be an issue.

Open Referral also aims to produce a profile of HSDS 3.0 that would help alignment with FHIR and make the mappings simpler to implement. This will be done by containing the fields in HSDS to the ones mapped, and constraining the taxonomies to map directly to the FHIR Value Sets.  Also for some cases where there are gaps in HSDS, extensions could be made.