Application+Ack+for+ebxml

Click here for background on the Document Submission Asynchronous Messaging Updates

Need to find ebmxl equivalent of HL7v3 application acknowledgement for Document Submission asynchronous transactions.
 * Description of Area to Address:**

**Proposed Approach:** //input from Matt Weaver (4/28/2010)// We will reference the updated messaging platform specification which defines how to use messageid, relatesto, and replyto. As far as changing the Document Submission spec the following picture describes the current approach. Notes: 1) Unchanged Document Submission request message 2) Document Submission acknowledgment message, leveraging the ebxml RegistryResponse element with a status of urn:nhin:DocumentSubmission:async:RequestAccepted, additionally the registryerrorlist element may not exist. Any errors that occur prior to the processing of the document(s) and metadata provided in message number 1 will be communicated via a soap fault. 3) Unchanged Document Submission response message. 4) Document Submission response message acknowledgment, leveraging the ebxml RegistryResponse element with a status of urn:nhin:DocumentSubmission:async:ResponseAccepted, additionally the registryerrorlist element may not be exist. Any errors that occur during the processing of the registry response message (message 3) will be communicated via a soap fault.

Request Acknowledgment:  
 * Examples:**

    

Response Acknowledgment:  

    

**Research:**

//Input from Tom Davidson (4/27/2010)://

This is the only ebXML specific solution I have been able to find. [] Section 6.3.2.6 provides a sample ebXML Acknowledge message, however, this is a SOAP Header element. I do not know if this provide the sufficient application level acknowledgement that the CONNECT team was looking for.

//Input from Karen Witting (4/20/2010)// <span style="font-family: Arial,Helvetica,sans-serif;">Feedback from Bill Majurski is: "I would use the RegistryResponse message but with a new value of status. How about RequestAccepted. This is an extendable namespace." I agree with this approach as the best way to express the ACK. Karen