How to trick BizTalk process all trigger events for a domain

Editorial architecture visual showing system boundaries, service interaction, and technical tradeoffs

Problem is if you come up with a custom trigger event within a domain, i.e. ADT_ZZZ, the accelerator requires not only update the MSH schema, but also create the custom schema, i.e. ADT_ZZZ_231_GLO_DEF.xsd. It would be nice if to get rid of this behavior and a single schema handles all custom trigger event within a domain.

The trick is,

  • Create a schema for domain, i.e. ADT_Everything_231_GLO_DEF.XSD, with type ADT_Everything_231_GLO_DEF
  • Create a custom pipeline component,
    • Update MSH9 with ADT^Everything^ADT_Everything, this will force HL7DataReader to look for ADT_Everything instead of the individual triggering event message structure

Next step

Need this reviewed in a real system?

Use the article as a starting point, then bring the actual decision, constraints, and failure paths into an architecture review.