PHC Hub Administrator
User Guide (v. March 2018)
|
|
|
Reciprocal batch processing works in conjunction with the inbound unsolicited HL7 interface in PHC Hub. Its purpose is to identify, format, and send HL7 messages for new patient immunization activity back to the provider's system over the same HTTPS connection used to receive incoming messages.
One requirement for WIR reciprocal batch processing is to maintain a separate set of demographics representing the data received from the provider's system. When HL7 messages are formatted for return to the provider, the demographics from received messages are used instead of demographics from WIR. When the inbound interface profile is linked to an export profile via the "Reciprocal Update" parameter, then all inbound demographics are saved to a separate table in WIR as part of inbound processing. If the export profile parameter "Send name, general DOB from reserve record" is selected/enabled, then all outbound HL7 messages use the saved demographics instead of the patient demographics maintained in WIR.
The reciprocal batch process can be triggered on demand or scheduled. The on demand function requires a start and stop date. A scheduled process identifies new activity that has occurred since the last scheduled run. Only patients with a relationship to the organization associated with the export profile are considered for the reciprocal batch. If the "last_updated_date" value associated with the immunization is later than the date/time of the previous reciprocal batch run, that immunization is included.
 |