Upgrade to UK standard and compliance rules (version 3.0)

The UK profile to Open Referral (HSDS and HSDA) 3.0 is now online and documented at Open Referral UK — Open Referral UK Profile 3.0.0 documentation. It is currently draft but will be made official if no errors or significant concerns are raised during September 2023.

This is an upgrade to the original Open Referral UK documented at https://developers.openreferraluk.org/ and supported by tools including a validator and dashboard. New versions of these tools are being developed as described here.

Whilst the original standard will remain in place and supported for a year or more, we urge developers to move to the new version which responds to feedback on the original and ensures ongoing consistency with the international standard. Of course the upgrade has been discussed in the Workgroup and in other posts here, including What constitutes compliance in the UK.

The Changelog lists changes from the current version. We would expect fewer changes in future versions.

Please post any issues with the UK profile here and let us know if you need any help migrating to it.

1 Like

Great work y’all! Thanks to everyone who made this happen.

I’m planning a blog post about this, let me know if anyone has any suggestions for aspects we should highlight or questions we should answer.


I don’t want to create myself too much work here, but the blog could mention some of the changes (in summary form) and the reasoning behind them.

1 Like

Well done OR UK! This looks great! I had a few thoughts about the Profile docs:

  • I think that the framing of “Open Referral UK Profile 3.0.0” might be a little bit confusing. Currently, HSDS is version 3.0 and previous OR UK Data Standard states itself to be version 1.0. I think there’s arguments to say that the new OR UK Profile is either version 1.0 of a new thing, and replaces the old OR UK standard, or is version 2.0 of that standard which just happens to have been implemented as a Profile of HSDS 3.0. There is likely a larger conversation to have around how Profiles should version themselves, which is out of scope for this thread! For now, if you’re in agreement then I think the “fix” is just a statement on your docs landing page explaining how you arrived at your version number (whichever number you end up choosing!).
  • I’m sure you’re aware but as an FYI there’s some boilerplate text from the Example Profile, at the top of each docs page which should be adjusted or removed. This is particularly prevalent on the API Reference Page
  • Since the API Reference Page and the SwaggerUI link on the sidebar repeat the same content you could probably remove the API Reference Page entirely. The core HSDS docs link to the SwaggerUI from the canonical API Reference page as a special treat for developers familiar with SwaggerUI, but our discussions indicated to me that fore-fronting the SwaggerUI page was a priority for the UK Profile. Therefore it might be best to avoid confusion and treat the SwaggerUI as the canonical API Reference for your Profile and remove template API Reference page.
  • The Changelog page boilerplate states that it’s intended to be used for internal versioning changes to the Profile. I think when I set up the proof-of-concept docs for the Profile, I probably put these in the wrong place so I’ll own this one! I think there’s two jobs for the docs wrt “changes”: (1) Inform people what changes the Profile makes against the base HSDS 3.0 model/schemas (2) inform people of internal version changes (i.e. if the OR UK Profile goes from version 1.0 to 1.1 etc). I think “Changelog” is usually used for the latter, so to prevent confusion I think the current content of Changelog should probably be migrated to e.g. Profile Compliance, and then the Changelog page can contain the changes from version 1.0 of the UK Profile to the current version.

This is really good to see that you’ve been able to spin this up so quickly and effectively.

Thanks @mrshll. I’ve modified the documentation to address your points. I need to get back to the Changelog point to make sure I’ve understood it, but the rest should be done.