B2B ocument Editor - widlcard HL7 Event - how can I specify?

Question

I am new to B2b Document Editor, distributed with the Oracel B2B 11g. I am trying to construct a HL7 v2.3.1 spec which will accommodate any HL7 ADT message. I am striking an issue where I don't know how to specify a wildcard Event in Message Properties of the guideline in such a way that the guideline will accept any ADT events. Ideally I would like an equivalent of the following regular expression [A-Z][0-9][0-9]. The Event property is one of the properties accessible wen one clicks on root node f the guideline - for example v2.3.1 ADT - ADT .... I start with an ADT A01 and modify it. I can remove segments and change other proeprties at will. Ican't change the Evet string - empty doe not wok, "*" wildcard does not work, regular expression [A-z][0-9][0-9] does not work. Data analysis fails with "Event ID mismatch. Event ID from data: A01. Guideline Event ID: *. Event ID mismatch.".
Any advise will be greatly appreciated.
Regards
Michael

Answer 1

Thank you, Nitesh and Anuj, for your responses.
I can, as you pointed out, create a generic message type, for example ADT, and it will be used to identify messages of ADT type unless there is a more specific type, say ADT_A01, defined.
Some of the issues I see with this approach are that:
a) I can only have one ADT_A01 and one ADT anything. I can't have more then one document type that represents some variant on the ADT_A01 structure(which the HL7 standard allows me to do)
b) With generic ADT I can't enable validation because anything other then a message matching the message type definiton (ADT_A01 for example) will fail validation. I can get ADT A01 and ADT A03 accepted and processed but only ADT A01 (in my example here) will be considered valid.
c) I would expect the dpcument type and document type definioton to be associated with a specific trading partner agreement - instead the document type is used to locate the trading partner agreement - this prevents multiple agreement and multiple parties from using varations on the document type and forces the developer to forego message validation. The need to introspec the message to identify the agreement can be overcome by enabling "associate channel" flag for a channel but I still can't associate document type definioton with an agreement or channel.
Unlike most other B2B protocols, which are standard and don't vary, HL7 is a very lax protocol and message structure variations are common. The Oracle implementation does not seem to provide for this variablity and does not seem to support the common practice.
I will keep n digging deeper to see what else I discover and how I can address some of the requirements I see in HL7 messaging.
Regards
Michael