Home : Products : Hach WIMS : Interfaces : Hach WIMS Direct Server-Side Interface to Custom EDI Lab Data Files : Documentation : Topics specific to the operation of this interface : Work Flow and Technical Notes
Q14283 - INFO: Work Flow and Technical Notes

This article mainly covers how data goes from the EDI Lab Data Files (see SDWIS/Stat Fixed-Format Lab EDI File Structure) into Hach WIMS Client and updates LabCal Samples and Tests.

Work Flow:

  1. The interface will first get a listing (array) of all files in the source folder.
  2. Each file is opened and examed; if it is invalid then the file is logged and skipped
  3. Each record in the file is added to a list (array) depending on the record type: header/summary records (HDR) or detailed records (DTR)
  4. After all the files and records are added to the lists, the program goes thru each record listed and attempts to import data into Hach WIMS Client. It will:
    • Validate the result, and the date and time of the sample
    • Check the data against the business rules (see EDI Lab Data and LabCal Business Rules)
    • Get the variable ID for the resulting value, from the Sample Test table
    • Update LabCal Sample and Sample Test tables, setting the status to received
    • Update LabCal Sample Notes if option values present (all are in the HDR record):
      • Sampling Point; field no. 10
      • Sampling Location; field no. 11
      • Sampling Rejection Reason; field no. 23
      • Collection Method Code, 24
    • Update the variable with the result
  5. After all records processed, it will scan the LabCal Sample table to see if we can set any of the updated Samples to Analyzed (only when all of the Tests in the Sample have a result for that sample date)

Technical Notes:

  • Facilities can be limited by creating a 'Facility.ini' file where the interface application is located. Add the facility names (like OPSWWTUTOR) to the file, one facility per line.
  • Note that the interface will import results if the cross reference works, but the LabCal update fails. This is by design so that values will be updated.
  • Note that when the interface fails to process a file and skips it, that file will remain in the folder and the interface will continue to process it. So if the user set up Archive and Delete but files are not being moved, then it's possible the interface is not processing the file, or doesn't have permissions to move the file.
  • Most issues will cause the interface to write information to the log file, and other messages are based on the Verbosity setting in Configuration > Advanced Configuration. If you need more information, try setting this to 3, then 5, then 7 and then finally 9. As the number goes up, more information will be logged.
Related Articles
No Related Articles Available.

Article Attachments
No Attachments Available.

Related External Links
No Related Links Available.
Help us improve this article...
What did you think of this article?

poor 
1
2
3
4
5
6
7
8
9
10

 excellent
Tell us why you rated the content this way. (optional)
 
Approved Comments...
No user comments available for this article.
Created on 11/19/2014 1:46 PM.
Last Modified on 11/21/2014 11:27 AM.
Last Modified by No Author Name Available!.
Article has been viewed 1959 times.
Rated 0 out of 10 based on 0 votes.
Print Article
Email Article