Abstract
Depending on what trading partner you are integrating with, and what the requirements are of your integration, you may find that there are some complexities to the architecture required to deliver a fully functional solution. One such pattern that is very common, yet can be difficult to build out, is related to the outbound 834 maintenance (or effectuation/reconciliation). The pattern here is that the outbound 834 data must contain all of the original inbound 834 information related to a specific subscriber/dependent along with all of the updated information from an internal system. The complexity here lies in the fact that in general, the inbound 834 data is not mapped in its entirety to a backend system within an organization. There are aspects to the data that are irrelevant to internal processes, and often have no place to be stored. In this case, the original 834 data must be stored so that it can be referenced at a later time when the outbound data ships out.