So working with HL7 is not that steep learning curve. Problem is there is lot to remember, by that I mean lots of table enumerations, data types etc. A lesson learnt today when I try to create a custom trigger event is, not only you change the namespaces, create a party definition, update the tables with the new values (table 3, 76, 354) but also requires to change the value in the shared MSH schema, there are tables defined there as well.

Good thing is BizTalk is written from .net, so whenever confusion, just reflect the DLL see what happens exactly. This helps me a lot while the accelerator keeps complaining message type cannot be found, (of course since I updated namespace) I was frustrated until I reflect the code, saw the line below for the logic. I then created a party, problem went away.

this.mDocumentSpecType = this.GetDocSpecType(this.mPartyConfig.PartyDefined ? this.mPartyConfig.TargetNS : “http://microsoft.com/HealthCare/HL7/2X”, this.mDocumentSpecType);

and

string str = (string) context.Read(“MSH5_1”, “http://HL7Schemas.HeaderPropertySchema”); string str2 = (string) context.Read(“MSH5_2”, “http://HL7Schemas.HeaderPropertySchema”); string str3 = (string) context.Read(“MSH5_3”, http://HL7Schemas.HeaderPropertySchema);

…

this.mPartyConfig = ConfigurationManager.GetPartyConfig(str4);