High level design question

Hello,

Let me first give a little background on the idea.  I am working on developing an implementation of a spec which "uses" ws notification.  The only major difference is that this spec says that we want to populate the xsd:anyType which comes along with a subscribe message with an element which will act as our topic or filter.  We are putting a rim:adhocquery in this subscribe message which we will then need to access and process in our notificationproducer capability.  

I notice that the subscribe function which I may override has a consumer, filter, terminationTime, and policy as inputs.  So which of those inputs would I look in to find my adhocquery "payload".

Here is an example message which I might see in a typical subscribe request.

<wsnt:Subscribe xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"
    xmlns:wsa="http://www.w3.org/2005/08/addressing"
    xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0">
   
    <wsnt:ConsumerReference>
        <!-- this is the endpoint to notify -->
        <wsa:Address>http://www.carespark.org/AccessConsentUpdateService
        </wsa:Address>
    </wsnt:ConsumerReference>
   
    <rim:AdhocQuery id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
        <rim:Slot name="$XDSDocumentEntryPatientId">
            <rim:ValueList>
                <!-- this is the patient ID as known by NCHICA -->
                <rim:Value>222498764^^^&2.16.840.1.113883.3.18.103&ISO</rim:Value>
            </rim:ValueList>
        </rim:Slot>
        <!--  this ClassCode indicates the Access Consent Policy Document -->
        <rim:Slot name="$XDSDocumentEntryClassCode">
            <rim:ValueList>
                <rim:Value>XNHIN-CONSENT</rim:Value>
            </rim:ValueList>
        </rim:Slot>
    </rim:AdhocQuery>
</wsnt:Subscribe>


Please let me know if I need to provide more information.  I just started looking at Apache Muse so I am still a little shaky on how it all works.  Thanks for your time,

msw