org.openehealth.ipf.commons.ihe.xds.core.metadata.DocumentEntryType, but it is an enum and it only provides two values, STABLE or ON_DEMAND.
When setting a documentEntryType value in the query, I get:
<ns2:Slot name="$XDSDocumentEntryType">
<ns2:ValueList>
<ns2:Value>('urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1')</ns2:Value>
</ns2:ValueList>
</ns2:Slot>
Parsing through the standard, it seems to agree that DocumentEntryType must have one of those two values, and there is no reference to DocumentEntryTypeCode.
So, my question is twofold:
* Is this XDSDocumentEntryTypeCode element outside of the scope of the standard/library? I start thinking this is kind of a homegrown extension. I realize this is more of a question for the contractors, but they are in defensive mode and I cannot get an answer.
* If the previous answer is no, which way should I use to set the element in the query?
* If the previous answer is yes, there is a an in-built way to add additional custom ns2:Slot elements to the query? I realize I could fork the library and add those relatively easily, but I prefer not to do so unless necessary.
Thanks in advance,
Sergio.