Hi Aden,

Just noticed this post and wondering whether 10 months on whether NHS England have a plan on when this issue will be resolved.  We have recently launch Incident and appear to be getting the same issue with 422 error emails.

Kind regards,

Andy

Hi Aden,

This is great news, thank you for the update! Is this for both the 'Hl7.Fhir.Model.AdverseEvent' and the 'Physical Harm' errors would you happen to know?

Thank you to all of the team for your help and support with this.

Kind Regards,

Robert

Hi Robert! 

An update on this, our development team has been in touch with NHS England and it turns out the problem was their end and they have taken responsibility for the API error.

Our team is working with them through this and when they have a fix I'll let you know.

Thanks again!

Aden

Hi Aden,

Thank you very much for your help and support - I had previously escalated this post as a ticket several weeks ago when I first noticed the 'Physical Harm' error and what I believe is causing the error, I was advised that this was being looked into, but unfortunately I have not had any further movements or response.

As of yesterday evening I started getting the new 'Unable to resolve reference to profile 'https://beta-data.patientsafety.nhs.uk/taxonomy/fhir/StructureDefinition/patient-safety-adverse-event-5' AdverseEvent FhirOperationException: An error has occurred when validating Hl7.Fhir.Model.AdverseEvent.' These seem to be much more frequent than the previous Physical Harm error - in less than a day I have received hundreds of these system generated e-mails.

Anything the Team can do to expedite reviewing and identifying a solution for these issues would be greatly appreciated. Thank you again.

Hi Robert, 

I have confirmation that the development team is looking into this.

I have escalated this post into a ticket.

As soon as we have information for you we'll let you know on both the ticket and on here.

Thank you for sending this in! 

Aden