Hi Team,
We are doing testing for A&G Worklist retrieval in TST environment
We saw “Forbidden” errors when trying to turn on the new API.
Mainly its not bringing any attachments
Hi,
Sorry you’re having issues, I’m not quite sure what the issue is based on the above comment though. Do you mind expanding a little key info that would help is:
- which environment is this in
- do you have a correlation ID
- which app id’s are you using?
- what the expected result was vs what the actual result was
- endpoints being used
Hi Tony,
Thanks for the response
Below are the responses
- Environment: INT
- Correlation ID : uuid:f436514e-97c4-11f1-a6bd-005056964e38
- App id’s: We are using 2- sharing both
- 5ee60453-d251-4f45-9541-4a62d7fcc5b5
- 660c3b81-b5ed-4267-8dd2-76dfdda0d65e
- what the expected result was vs what the actual result was:
- Expected: Pull attachments to Epic EPR
- Actual: Attachments missing and forbidden error logged
- endpoints being used : A042
Let me know if there is any other question
thanks
Hi,
Just letting you know, one of the team has identified this issue. As your ASIDs are quite old, they need to be refreshed to get some of the latest endpoints.
I’ve raised a ticket, this should be complete next week - I’ll let you know when its ready to re-test.
Sorry for the delay on this - chasing a progress update on your behalf.
@v.jaisinghani Your ASIDs have been updated - please re-try and let me know they are working as expected for A042 
Hi Tony,
Thanks for the update.
We have tested this and used the below message to sent for worklist retrieval (2ffe196f-b1c6-11f1-97f7-005056964e38). The retrieval completes successfully and the messages are received; however, the attachments are still missing.
Interestingly, when we revert the ASIDs back to the previous values, the attachments are retrieved correctly and are visible as expected.
This suggests the issue may be related to the new ASIDs rather than the retrieval process itself.
I think below are the ASIDs we use in INT, can you confirm which ones are updated to allow the APIs to retrive through referrals
ASID 200000002206
ASID 200000002197
Thanks,
Hi @v.jaisinghani For the avoidance of doubt can you send the application IDs of the apps you are using in INT, you may be using one for user restricted, and one for application restricted. Then I can match the associated ASID and make sure we both understand the associations 
Hi tony
The user restricted one is
Application ID
5ee60453-d251-4f45-9541-4a62d7fcc5b5
And for INt is
Application ID
660c3b81-b5ed-4267-8dd2-76dfdda0d65e
Let me know if you need anything else.
thanks
Hi I have sent this to ITOC to ensure they are updated, I feel something else may be happening here also, are you able to send some correlation IDs of the event when you are missing attachments. Could you also explain what you mean by revert ASIDs, as this isn’t an action that you are able to perform, we add the ASIDs as attributes on your behalf and we did not amend them
Hi Tony
Thanks.
Our corelation id is: uuid:84e036b1-bd8d-11f1-97f7-005056964e38
This is what we are getting
“https://www.hl7.org/fhir/R4/operationoutcome.html"]},“issue”:[{“severity”:“error”,“code”:"forbidden… ASID (200000002197) does not have the interaction (urn:nhs:names:services:ers:READ_BINARY_R4_V001) required to call this endpoint.”,“details”:{“coding”:[{“system”:"https://fhir.nhs.uk/CodeSystem/http-error-codes",“code”:“REC_FORBIDDEN”}]}}]}
Thanks, has this been tried today? We recently refresh all ASIDs to include all latest interactions, this was on the list so ‘should’ be updated. If this was tried just now and doesnt work, let me know and we will figure it out.
Hi Tony,
Yes is done today.
Still no luck
looking at this today, and requesting it is investigated/added for you - will respond on here
Hi we have raised a service ticket CS1686531 for this, the reason it was missed is that the ITOC team were cautious over general updates as this looks to be a bespoke EPIC ASID with different interactions within it. I’ve requested this single interaction is added to the ASID, rather than a global update of the overall API ‘product’ which may risk over writing the ASID and non-ers interactions.
Hello,
The interaction has now been added and ready to test
Hi Tony,
Thanks for this.
Just did another test, same error as before:
The ASID (200000002197) does not have the interaction (urn:nhs:names:services:ers:READ_BINARY_R4_V001) required to call this endpoint.",“details”:{“coding”:[{“system”:“https://fhir.nhs.uk/CodeSystem/http-error-codes",“code”:"REC_FORBIDDEN”
Message ID - uuid:c64fc5e9-c22a-11f1-97f7-005056964e38
Hi @v.jaisinghani The Team looked into this and confirmed the interaction is present on the ASID, so its a little strange it still does not work. However, they had tried again, and refreshed the interaction, please could you re-test on Monday, and confirm. If the test fails please could you provide a correlation ID.