Looking for help?
Unsure where to begin or need guidance on using Luminate? Explore our detailed articles below for step-by-step assistance.
Guides
Send us feedback
We'd love to hear your thoughts—whether it’s a feature suggestion, usability improvement, or what you love about Luminate.
We have recieved your feedback
Thank you for sharing! Your input helps us enhance Luminate for all users. Feel free to close this window now.
Hi everyone,
Has anyone recently started getting system generated error messages with the error code 422 - The LFPSE API has rejected the Incident as it cannot be processed? I am unsure if this is an Admin functionality error, but the most common ones I am getting are:
FhirOperationException: A value for 'PhysicalHarm' on Contained.Patient.patient-details is required for Incident submissions
From last night, I have started getting '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.'
Is anyone else coming across these error messages? It is extremely frustrating as no-one seems to be able to advise what is causing or how to resolve these issues, and causing so many incidents not to be submitted due to these errors. The amount of e-mails we are getting with these errors are in the hundreds.
For the Physical Harm error, these seem to be when the person affected is a third party (not a patient).
If anyone else is experiencing these errors and has resolved them, any advice on how you managed to resolve it would be greatly appreciated! Thank you!
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
Comment
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.