integration:ivedix

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
integration:ivedix [2024/10/18 08:45] – [23.09. iVEDiX integration] Gary Willettsintegration:ivedix [2025/05/07 04:28] (current) – [Errors] Gary Willetts
Line 37: Line 37:
   * transactionDate: the transaction's confirmed date in ISO date format.   * transactionDate: the transaction's confirmed date in ISO date format.
   * warehouse: the store code; WH0004, 6 or 7 and the corresponding Malaria stores take the corresponding main store code.   * warehouse: the store code; WH0004, 6 or 7 and the corresponding Malaria stores take the corresponding main store code.
-  * donor: the transactino category of the transaction.+  * donor: the transaction category of the transaction.
   * productCode: the item code.   * productCode: the item code.
   * batchNumber: the batch of the stock.   * batchNumber: the batch of the stock.
Line 44: Line 44:
   * quantity: pack size x number of packs for this transaction line.   * quantity: pack size x number of packs for this transaction line.
  
 +There are actually two schedulers running to control sending transactions to iVEDiX: one picks up all new transactions and sends them for the first time. The other picks up all the failed transactions and sends them again until they have reached the maximum number of retries before permanent failure.
 ===== Errors ===== ===== Errors =====
 If errors are encountered during either of the sending processes then the information to be sent is entered into a queue. All pices of information (batches or transactions) in that queu are attempted to be resent after the number of minutes stored in the **Interval between retries** field. When a piece of informaiton is successfully sent it is removed from the queue. If a piece of information is not sent successfully after the number of retries in the **Number of times to retry sending** field then it is removed from the queue, the final failure is logged (see the [[admin:the_log]] page for details on how to view the log) and an email giving details of the error is sent to the email address stored in the **Send errors ro this email address** field.  If errors are encountered during either of the sending processes then the information to be sent is entered into a queue. All pices of information (batches or transactions) in that queu are attempted to be resent after the number of minutes stored in the **Interval between retries** field. When a piece of informaiton is successfully sent it is removed from the queue. If a piece of information is not sent successfully after the number of retries in the **Number of times to retry sending** field then it is removed from the queue, the final failure is logged (see the [[admin:the_log]] page for details on how to view the log) and an email giving details of the error is sent to the email address stored in the **Send errors ro this email address** field. 
Line 50: Line 50:
 \\ \\
 \\ \\
-|  //  Previous:  **[[integration:hl7_integration]]** | | Next: **[[tables_fields:]]** //  |+|  //  Previous:  **[[integration:hl7_integration]]** | | Next: **[[integration:siglofa]]** //  |
  
 ---- struct data ---- ---- struct data ----
  • Last modified: 2024/10/18 08:45
  • by Gary Willetts