FHIR listener comes with very good tutorial & a example channel.
MIRTH CONNECT CHANNEL AUTO QUEUE OF ERRORS PATCH
I'll attach a patch with my suggestions, and review it with the team on Monday. In mirth connect convert hl7 datetime in local time to iso date in UTC Tag: javascript, datetime, mirth I have the following code that parses fields from an HL7 2. ERROR (.controllers.DonkeyMessageController:458): 153 out of 157 messages failed to be reprocessed.Ĭom.channel.ChannelException: Source connector is currently stopped.Īt .(SourceConnector.java:117)Īt .vm.VmReceiver.dispatchRawMessage(VmReceiver.java:54)Īt .(DonkeyEngineController.java:387) ERROR (.controllers.DonkeyMessageController:458): 155 out of 161 messages failed to be reprocessed.Ĭom.channel.ChannelException: Could not find channel to route to for channel id: ae30ab60-9315-468f-920b-d000cfd796feĪt .(DonkeyEngineController.java:379)Īt .(DonkeyMessageController.java:450)Īt .servlets.MessageObjectServlet$1.run(MessageObjectServlet.java:176) That way if the channel is undeployed for example, instead of hundreds of log entry suddenly showing up, you would see something like: Then in DEC and SourceConnector, we can throw more meaningful exceptions, indicating that either the source connector has been stopped, or that the channel has been undeployed altogether. One such example is the content and format of patient IDs. If the site has special needs due to PACS or Modality requirements, support for this is added as well.
Instead of logging out 1-2 exceptions for -every- message in a reprocess task, one thing we can do is keep track (in DMC.reprocessMessages) of how many messages failed and the last cause, and log a single entry at the end. This channel is set up to query the respective regional database for appointments. However, if the channel was paused or stopped, then only the DMC "." entry shows in the log, without any reason.Įssentially this comes down to better exception handling for reprocess tasks. One thing to note here is that if the channel was undeployed, then the "Could not find channel" DEC exception shows up in the server log (along with the currently somewhat useless DMC log entry). ERROR 10:29:31,148 Thread-23 .: An error occurred in channel TCP Listener 1 (57bd25e4-1142-4f3d-86be-490e57dad496) while processing message ID 1578 from the source queue . This appears to occur when a channel is storing a lot of data in the channel map, messages flow at a high volume (dozens a second or more), and multiple queue threads are used (doesn't have to be a lot, it still happens with only 2 or 3. If (newenv_8 = DateUtil.This is expected in some sense if a channel is paused, stopped, or undeployed, then the reprocessing task can no longer dispatch messages to the channel. testing without this caused it to fall within the “older than 7 days” category Var newenv_8 = env_8.substr(0,8) //Convert the ENV.8 to remove the timeĭ1.setDate(d.getDate()-1) //Find the date 1 days agoĭ2.setDate(d.getDate()-2) //Find the date 2 days agoĭ3.setDate(d.getDate()-3) //Find the date 3 days agoĭ4.setDate(d.getDate()-4) //Find the date 4 days agoĭ5.setDate(d.getDate()-5) //Find the date 5 days agoĭ6.setDate(d.getDate()-6) //Find the date 6 days agoĭ7.setDate(d.getDate()-7) //Find the date 7 days agoĭ1 = DateUtil.formatDate(‘YYYYMMdd’, d1) //Format the date 1 days agoĭ2 = DateUtil.formatDate(‘YYYYMMdd’, d2) //Format the date 2 days agoĭ3 = DateUtil.formatDate(‘YYYYMMdd’, d3) //Format the date 3 days agoĭ4 = DateUtil.formatDate(‘YYYYMMdd’, d4) //Format the date 4 days agoĭ5 = DateUtil.formatDate(‘YYYYMMdd’, d5) //Format the date 5 days agoĭ6 = DateUtil.formatDate(‘YYYYMMdd’, d6) //Format the date 6 days agoĭ7 = DateUtil.formatDate(‘YYYYMMdd’, d7) //Format the date 7 days ago if A08 Block if the Appointment Date/Time in EVN_8 is more than 7 days prior to the current date/time This is messy I admit but it works just fine. JavaScript and dates are never really fun. I recently had to filter a message based on the ENV.8 date value.
0 kommentar(er)
