User bio
404 bio not found
Member since Aug 26, 2022
Posts:
show all 39
Replies:
show all 77
Colin Brough · Mar 9 go to post

Thanks for those that took the time to reply. Summary of where we've got to:

  • "structural" support for what we are trying to do isn't there in Ensemble 2018; another piece of ammunition to use when kicking our management into upgrading to Iris 😁
  • we had a further think, and also had a conversation with someone from WRC where were able to go into a bit more detail about our application, which resulted in a (very promising looking) solution. We already have a table whose contents includes the MessageBodyId, so we when we come to process a message for a LabReportId we can see whether there is an entry in the table for that LabReportId, and if there is compare the MessageBodyId in the table with that from the current message to ensure they are processed correctly.
Colin Brough · Oct 7, 2025 go to post

Yeah, this is what we were doing (and wanting to avoid). So being able to do the queries in SQL, including the HL7 content, and exporting the output to CSV (which Excel can import) means we have the tools we need for future diagnostics/issue resolution.

Certifications & Credly badges:
show all 1
Followers:
show all 5
Tom C.
Melissa W.
Dewey H.
Nick H.
Liubov Z.
Following:
Colin has not followed anybody yet.