Lets just say that there is a set of published companion documents that a client has distributed to a client. In there, the list of valid values are even more restritive than what is published publicly. These codesets are valid only for this client, and additional codesets are valid for another client.
The ability to make partner specific schemas is possible! Yes, I know, this is what we all have been losing sleep over!
If you really want to make specific schemas it is possible. This works on both the v3.0 and v3.3.
It is pretty straight foward:
- Make sure that you have the party defined
- The party has to be defined in a recieve location, if it is not defined, the schema will not show it as an available Partner URI in the schema.
- In the schema that you want to be specifically defined for, click on the root node of the schema, in the properties there is a Partner URI drop down list.
- Choose the partner you wish to make the customization for from the drop down list.
- Change the target namespace to make it unique for that partner
- Make your modifications to the schema.
- Validate the schema so the customization is uploaded to the database.
Note: If you do not see the Partner URI in the list even though you have defined the recieve location (possibly with a binding file), re define the recieve location by changing the address to another partner, and then assign it correctly again, restart the HIPAA service, and it should show up.
You now have a specific partner schema that BizTalk will parse depending on the party definition you have defined. There you can make your specific mapping for that client. In my case I am able to have the accelerator parse the client’s file using their additionally restrive schema definition, and the subsequently map it to the standard schema wherein it then goes into the universal mapping that has been developed for all of the clients.
Actually this functionality exists in both the HIPAA accelerator and the Base EDI adapter. From ages past I worked on the Covast Accelerator, but I can’t remember if that functionality is present there.
Not too bad.