We designed the Human Service Data Specifications (HSDS)to make it easy to share information about human services of any kind. But given the many nuanced differences across human service sectors – and states and countries and etc – it’s just not feasible to standardize every possible kind of information associated with any kind of service anywhere. So we didn’t try to do that!
Instead, HSDS standardizes the most common information elements that can be expected in virtually any service – which turns out to be a relatively small set of fields, especially when it comes to the core requirements. This ensures that HSDS is relatively practical to adopt; however, at the same time, we do want users to be able to share additional information that is important to their communities even if not specified in the core format. To strike this balance, we’ve encouraged adopters to develop extensions through which they could include information that HSDS does not specify.
Now, with the publication of the new and improved HSDS version 3.0, we’ve gone even farther in enabling users to customize the specification to meet their specific needs, while preserving interoperability across our diverse ecosystem.
HSDS 3.0 supports “Profiles” through which adopters can publish a formalized set of extensions, constraints, and enumerations that together amount to their own tailored version of the standard. Continue reading
As Open Referral’s network grows – involving more stakeholders in the development of interoperable resource directory information supply chains – our tools and practices must evolve in kind to support more complex needs.
So we are excited to share that Open Referral has initiated a new development cycle to upgrade the Human Service Data Specifications. This cycle has kicked off with a specific objective to address a significant issue: our specifications need to be adapted across diverse contexts, to support different conventions in different places, while preserving a core of interoperability across our ecosystem.
To support this workgroup’s efforts, we are seeking feedback from a broad array of stakeholders across our network. For instance, this Friday (July 22nd) from 11a-1p, we will host an open “fishbowl” discussion in which workgroup members will review proposals line-by-line, at which any members of our community are welcome to observe and discuss by chat – invitations available by request. We encourage interested parties to comment on the documents above, or discuss in our issues queue on Github, or reach out directly via [email protected]
Often people ask how we enable care providers to actually refer their clients to another service. The answer is, well, Open Referral doesn’t actually deal with the process of “making a referral” at all!
We’re working to ensure that there’s open access to information about the services to which someone might be referred.
But the challenges related to actually sending a person’s information from one provider’s system to another? That’s a whole other tangle of knots. I’ve long hoped that someone somewhere would work on those problems, while believing it should remain outside Open Referral’s scope.
So I’m excited to see that this work is now under way.
The Gravity Project is like kin to the Open Referral Initiative: Gravity is a community of practice that is developing and testing consensus-based open standards to facilitate capture and exchange of data pertaining to people and their social circumstances across a variety of healthcare and social service systems.
Open Referral went to San Francisco on Wednesday August 9th to participate in a social good hack-day at Optimizely. In collaboration with our partner Benetech, Open Referral set up as one of the social good projects that 20+ employees worked on for the day.
Overall, our team was strong in front-end web and mobile developers, so we decided to “forward engineer” Zendesk’s Link-SF application so that it can be deployed on any Open Referral-compatible API. […]
You can find the updated Link source code in our Github repository. If you want to run this app locally, you can save a file as `config.js`and follow the instructions on the setup page. Continue reading