Where a directly bookable referral is sent to us via the API, then triaged, added to a worklist, redirected, or otherwise acted upon within our EPR, I don’t believe that there is an endpoint available to allow us to communicate the corresponding outcome back to eRS.
Would someone be able to confirm if that is the case, and if so, how we raise a change to have this added to the ERS API, as this functionality is not consistent with that for RAS.
This sounds like something that would need to be summarised and added to the backlog. I suppose the challenge here is that e-RS know’s nothing about the current state unless there is a direct link between the two systems, so anything that happens beyond the e-RS transaction is invisible to it.
Perhaps if you could write this in the form of a user need with specific jump off points in relation to your EPR, we can at least get this logged on your behalf.