Dear All
Commissioning Rule Organisation parameter is being recalculated
Our tests have highlighted a bug in the Change shortlist (A031) endpoint.
When changing a shortlist, it is possible to change the Commissioning Rule Organisation (CRO) parameter.
The CRO parameter determines a referring user’s service availability and rights when conducting a service search.
When a referral is created, the CRO is set and is used throughout the lifespan of a referral.
It is possible that after the creation of a referral, the patient changes their registered GP practice. This has no effect on the determination of the CRO parameter.
Expected result
The CRO parameter is not recalculated if the patients registered GP practice changes, and the shortlist is amended.
Actual result
The CRO parameter is being recalculated if the patients registered GP practice changes, each time the shortlist is amended.
What we’re doing to fix this
We are adding an optional CRO parameter into the Patient service search (A010) endpoint.
This is not a breaking change. However, it will require partners who intend to use Change shortlist (A031) to incorporate the new CRO parameter.
What you need to do
According to our data, there is no usage of A031 in production yet, but please do note the following if you’re currently in development with A031:
Once the above mentioned fix is available, your product must incorporate the RCO parameter.
This will ensure that services retrieved from the patient service search endpoint will match the RCO for the referral.
This will enable you to provide a valid shortlist when attempting to amend the shortlist via Change shortlist (A031).
This change will be available in our November release which will go into APIM INT environment on 28th October 2024, and into APIM Production environment on 5th November 2024
Best Regards,
The e-RS FHIR API Partners Service
E: england.nhserspartners@nhs.net