Description
This report processes all EDI orders in the order table NC301.
For each order, the system checks whether a message must be created forthe corresponding recipient.
If the recipient (for example, the health insurance company) is to beinformed of the event that has occurred, an appropriate message isgenerated and is first stored in a database table. A correspondingstatus record is also generated at the same time.
By evaluating this status record, it is possible to determine whetherthis message is new or has already been sent. This status managementfunction can be used to prevent change messages from being sentunnecessarily and also allows evaluations to be performed at any time.
All of the NC301 records are deleted from the database after they havebeen processed.
The report must be triggered on a cyclical basis. Usually the frequencyis every 5 to 10 minutes for each EDI procedure. If more than one EDIprocedure is active, you should schedule this report to run as a seriesof steps in the same background (batch) job, whereby each active EDIprocedure is processed in one step.
Recommended naming convention: It is recommended to use the conventionISH_EDI_BUILDER_xxx for the background job (where xxx is the client inwhich the job is scheduled. This specification is not necessary whenonly one client is used).

Precondition
To execute this program you require all IS-H authorizations. Inparticular, you must have authorization to read all case and patientdata in all institutions and to make database changes necessitated bythe EDI procedure (in the case of P301, changes to documents in FI whencopayment is deducted).
Missing authorizations result merely in incomplete or incorrect EDImessages that are inconsistent with the data in the database.
A data collection point must be defined for each insurance provider andEDI Communication must be activated in Customizing (Electronic DataInterchange -> Activate EDI Procedure).
On the selection screen, you can restrict processing to one EDIprocedure. It is also possible to have the program process only ordersthat are older than the number of days you specify.
Example: If you do not want the orders created on December 24 to beturned into messages until December 27, enter the value 3 for the numberof days.

Output