My favorites | Sign in
Project Home Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 30: Southern Ute, mutiple success exports followed by a fail
1 person starred this issue and may be notified of changes. Back to list
 
Project Member Reported by cectow...@gmail.com, Nov 13, 2013
We have had a function for some time that checks whether there are messages in the export queue log that should have been sent but are still in the log.  The situation we ran into at Southern Ute where for several days in a row, the final step of actual file creation wasn't being completed highlighted a weakness or problem with this function.  The weakness with the function was that it only went back to the 'last' failed export to see if there were messages to be included that hadn't completed the file creation/transmission process.  Southern Ute had several sequences with multiple failed exports followed by a successful export - still don't know why that was happening.  So, if there were two or more failed exports in a row, only the immunizations from the most recent failed export were being considered for inclusion in the current export.  I changed the processing logic so it would go back and look for any messages that hadn't been exported successfully - again, by 'exported successfully' I mean that the entire process was completed successfully including all the patient and immunization evaluation, HL7 message formatting and creation, creating the log of all messages to be exported and putting those into the GIS queue for inclusion in the host file that needs to be created.  It is that very last step, the actual creation of the host file, the 'izdata2012113.dat' for today as an example, that for some reason wasn't always getting completed.  When it isn't created, there there are a bunch of HL7 messages left in limbo that haven't been put in a file that gets transmitted to the IIS.



Nov 13, 2013
Project Member #1 cectow...@gmail.com
(No comment was entered for this change.)
Labels: Milestone-Release2.0p4

Powered by Google Project Hosting