I ran into a little conundrum. AIRS guidelines, the most used guidelines for community resource data in the USA, does not require a location to be specified for virtual services. In some US based software solutions, this means that virtual services will not have a corresponding location record.
In HSDS however, the “type” of “virtual” is set on the location record.
So, per AIRS, virtual records won’t even have a location record, which is the only place for an HSDS spec record to gather the
When translating these AIRS compliant records into HSDS, at least one I&R vendor is considering adding an “is virtual” flag to their service records, which we can probably read and then turn into the appropriate location records for HSDS.
More of the I&Rs simply allow users to not include location data and throw no flags. I hesitate to just assume that any service without a location is virtual, but that’s outside the scope of Open Referral.
Nevertheless, the question here might be whether we want align OR with AIRS, or push AIRS to align with OR. Perhaps AIRS simply needs to clarify more specifically how to mark a service as virtual. I would prefer a solution that doesn’t rely on omitting data and making assumptions.
In fact, as I write this, I wonder if I shouldn’t be talking to AIRS instead.
@bloom do you have any feedback on this?