Topics: |
Matching and merging can be configured by edit the OmniMaster.xml file located in the following directory:
[OmniPatient]/iway7/config/OmniPatient/resource
Mastering can be turned off by commenting out the <subject> element. For example, to turn off mastering for the Patient subject, comment out the <subject name="Patient"> element.
The mastering of an IDS document is broken into merging and matching sections under the main subject element.
<subject name=""> - The start of a new mastering section. The name attribute should equal the name of the root element of the IDS. The name is case sensitive.<matching> - Starts a new section defining the input elements for the matching service. <endpoint> - This is the endpoint URL of the cleansing web service. <request> - This is the name of the request as defined in the WSDL for the specific mastering web service it is used to wrap the request body and define the soap action. <input> - Starts the section defining the elements for the web service call. <element> <name> - The name of the element in the ws call <xpath> - Xpath to the value in the IDS document </element> <collection> <iterate_xpath> - Xpath to the collection <collection_name> - Element name used for the collection on the ws <member_name> - Element name for a member of the collection in the ws <element> - Same as element above but Xpaths are relative to the iterate_xpath </collection> </input> </matching><merging> - Starts a new section defining the request and endpoint for the merging service. <endpoint> - This is the endpoint URL of the cleansing web service. <request> - This is the name of the request as defined in the WSDL for the specific mastering web service it is used to wrap the request body and define the soap action. </merging>