Step | Description |
1 | The client sends the HIPAA message with the content type application/ x-wmflatfile to Integration Server, which in turn passes the HIPAA message to the application/x-wmflatfile content handler. The content handler performs initial processing, including forming the pipeline and placing the ffdata variable in the pipeline. The ffdata variable contains the HIPAA message data. |
2 | The content handler invokes the service specified by the client. For a HIPAA message, the client should specify the
pub.estd.hipaa:receive service. This service determines that the HIPAA message is a TA1 technical acknowledgment, and therefore, acts as a gateway service for Trading Networks flat file processing. The
pub.estd.hipaa:receive service adds information to the pipeline. It also creates the BizDocEnvelope and sets the TN document type for the HIPAA message to X12 TA1. The service then invokes the wm.tn.route:routeBizdoc service. |
3 | The wm.tn.route:routeBizdoc service sends the HIPAA message directly to Trading Networks processing rules, bypassing document recognition. Trading Networks document recognition is bypassed because the
pub.estd.hipaa:receive service already performed this function by creating the BizDocEnvelope and determining the TN document type to use for the HIPAA message. |