Try something like this:

• Response Timeout: 10 (Timeout for getting a response from the server (the timeout for opening the connection to the server is always 5 seconds). Setting the timeout to -1 means wait forever.)
• Reply Code Actions: E=R (R - Retry the message according to the configured RetryInterval and FailureTimeout; finally Fail unless a different action is also specified.)
• Retry Interval: 1 (How frequently to retry access to the output system)
• Failure Timeout: 60 (Total number of seconds to keep trying to deliver the message. After this number of seconds has elapsed, the business operation discards the message data and returns an error code. To ensure that no message is ever skipped, enter a Failure Timeout value of -1, which means 'Never time out'. Use a setting of -1 when complete data delivery is critical, for example in health care applications. )

All object properties in a request or response object must extend %XML.Adaptor.

Lists and arrays of streams are skipped.

Private properties are skipped.

MultiDimensional properties are skipped. 

XMLIO = "IN" properties are skipped.

XMLPROJECTION = "NONE" properties are skipped.

$property works with all objects, dynamic or not:

>s a={"b":2}
>w $property(a, "b")
2

Use $zdth to convert unixtime into horolog and then $zdate to convert it to date string:

write $zd($zdth(572486400, -2),3)
1988-02-22

UPD: Never mind, that's the wrong answer as it's about HL7. Sorry about that.

There are two ways to do that:

1. Use EnsLib.MsgRouter.VDocRoutingEngine, it has Validation setting which is a string specifying types of validation to perform. Set to 1 to block documents that don't pass default validation. Default validation checks for DocType assignment and successful BuildMapStatus. This is equivalent to 'dm': 'd' - require DocType 'm' - require successful BuildMap status. Set to 0 to skip validation. In addition configure Bad Message Handler setting to handle messages which fail validation. I'm not sure it your messages would fail BuildMap validation, but that's the easiest option to implement.
2. Create a subclass of EnsLib.MsgRouter.RoutingEngine and implement OnValidate method to provide custom validation. You'll also need to add Validation property to settings, same as EnsLib.MsgRouter.VDocRoutingEngine  does. In OnValidate method you can perform any checks you like.