This issue is outside the scope of the 2.9.1 ballot and can be deferred until later but I just wanted to add it to the backlog.

I would appreciate it if we could update all of the example transaction MSH-7 (Date/Time of Message) fields to include a time zone offset like "-0500". Including a time zone offset is a best practice for implementers and we should model that in examples even though they're only informative. My organization sometimes receives messages from other organizations which operate across multiple time zones so the lack of a time zone offset makes it impossible to reliably determine when the message was actually sent.