Improve CCG to not suffer with Thread crashing or backlog queues when a bad HL7 message is received.

Improve or enhance our CCG product to better manage it's Threads if a bad HL7 message is received in. For example HL7 messages that contain any invalid characters, causing the thread to error, retry looping, thread crashes and/or queue backlogs to occur.

CCG should have the capability to park any bad HL7 messages that any of its threads has retried, but unable to successfully process correctly. Allowing then for the bad HL7 message to be quarantined, flagged as error status, that allows the thread to bypass such a bad message to continue processing other good HL7 received after the bad one. Therefore, no backlog queue would build. Reduction of CCG major incidents and impacted outages like 'No Modality Worklists' would be observed.

This Knowledge Article below is just one example of how a single bad HL7 message can impact the CCG functionality severely.

000051426

https://gehealthcare-svc.lightning.force.com/lightning/articles/HCIT_Knowledge_Article/CCG-HL7-message-with-invalid-character-causing-backups-on-thread

If CCG had the ability to put any bad HL7 messages its threads are unable to successfully process, into a FAILED state so it is automatically bypassed, allowing for the thread to continue to process HL7 msg's that are healthy. The reliability and uptime of CCG's functionality would be vastly improved.

2024 in EMEA we've identified 37 incidents related to potential CCG instability. Probability that there's more than 37 in reality. This is not saying all 37 were caused by just bad HL7 msgs alone. This is just an idea if possible that could exclude this type of fault cause incidents, allowing clearer visibility to identify any other root causes that also show the same type of fault symptom. but for different reasons.

Refer also to Problem Case P-12727 and ALM Centricity_PACS-652 in Service Cloud for related information.