Hi, we are establishing a regional health information exchange for genomics in the North West (from Apr 26 we will be known as NHS North West Genomics).
The potential users of our test system may be from a variety of NHS Trusts and Boards from across the UK and probably NHS England itself.
As we cover a wide geographic spread we ideally want the ODS codes used PDS FHIR API Int environment to match those on ODS Organisation Terminology FHIR API.
e.g. Patient 9000000009 on PDS Int has a GP Surgery Y12345 which does not existing on ODS Int
So in our int environments we have issues with PDS GP Practice ODS codes because those ODS codes don’t exist on INT and we can only test properly on live which is not ideall.
In addition we have some IG rules where we are not allowed share data for patients from outside an ICS (e.g. Greater Manchester). For these scenarios we would to have dummy GP Practices for the 3 ICS within our region.
You should have your own test data pack set up by the test data team, and you can configure as you desire. Setting up test data in our path to live environments - NHS England Digital
I believe we’ve done that and we don’t get the option of using ODS codes for our region (north west). We may also get other test systems from other regions …. plus Wales, Scotland and NI (we also have test results for EU countries)
Ideally we need the ODS codes available in PDS INT to match ODS INT environment.
e.g. all the patients have place surnames, the ODS codes are all practices in that city or town.
Most of the ODS codes belong to different ICS, those ICS may have data sharing agreements which limit what the can or can’t share, and we can’t share with them, etc).
The patients are currently on PDS INT, the ODS codes are in ODS int … we can’t link them together in PDS in INT
OK. I see your problem. I’ll flag to relevant people.
Hi Kevin,
TDSSP users now have the ability to update the GP Practice (Primary Care Code) for a patient to a value of their choosing, as well as selecting from the pop-up search dialog. The values in the pop-up are PCCs that have been explicitly assigned to the organisation which the user’s [TDSSP] account is linked to (if any) and a default of A20047.
Validation on Primary Care Code checks that the value exists in the tooling’s internal organisation table.
Once the Primary Care Code for the records in the PDS pack that you reference is updated on TDSSP it can be reloaded into spine INT which will reset PDS to match the details in TDSSP. If there are PCCs that don’t validate let us know and we can add them to our internal database.
If you have any further issues or queries please email testdata@nhs.net
Cheers,
Nick.
Principal Systems Engineer, Delivery Lead, Delivery Manager & Product Manager
Test Data Cloud Services – Spine, GPES and National Datasets
Data Governance, Assurance and Testing
Data and Analytics
NHS England
1 Like
Yes we are already doing this.
The problem is the member of staff doing this is contract (like me) and this reseting of patients needs to continue into the future.
This is the same issue GP Connect and EDI Test patients have, we are not short lived projects.
I have also been told other users of PDS should not alter other projects test patient and we should log an incident when this occurs again.
I’m assuming that when your contract is over, that your work will be handed over to a support team in the organisation?
Operational side yes but not this part, I think also happened with:
- GP Connect - this has two test packs which come from two teams
- EDI Test Patients - NHS England ownership has since been lost
Note we will also be reusing these test packs for integration testing with primary care and pathology. We are intending to use our test packs with NHS England NRL and Genomics projects (but would also accept theirs).
Think a key issue here is we are doing cross sector integration testing, not individual service testing - it’s a bit of an organisational issue. Logically we are after spine test patients, which cover all sectors, trusts, ICS and regions and are not specific to our Genomic Service.
1 Like
