Hi @Adrian_Hall and @Laura_Avram ,
Is there any more information to review and provide feedback on in terms of the V2 API? At a high level the approach listed in the post sounds good, but the devil will be in the detail.
Also, for the proposed address lookup, will the expectation be to use a third-party system for this or will the address lookup function be provided alongside the V2 API?
Thanks
Hi Owen, Laura has left the organisation, so I will be following up.
As it currently stands, the address lookup requirements will be that an address is looked up from the authoritative data source - OS NGD - which may be OS Places API, or another service that sources its data from the same place. Under the PSGA licence, public sector use cases can use the OS Places API, and that extends to consumers of PDS where we have required that this data is used. Ordnance Survey Places API - NHS England Digital
There will be required mappings from the OS Places dataset fields or equivalent.
Manual address entry should only be used as a last resort, as without the lookup, there will be no UPRN (which we should all be using) and whilst we can match most addresses after update, it will mean some still can’t be matched (automated processes not as good at picking from a list) and data quality will be poorer.
Hi Adrian,
Thanks for linking the OS Places API and for the extra background information. I’ll keep a watch on this thread for updates as the spec progresses. Thanks
We’ll be reaching out with a survey shortly, with some one-to-one chats to discuss the proposals.
This thread will be one place that we’ll look for volunteers.