LOCATION OID Issue

[vishj1717]

We are using an IWRS and eCOA integrations which uses RWS exchange. We have a single Medidata rave URL because of which site number can only be used more than once. IWRS and eCOA have used LOCATION OID as Site Number for integrations because of which integration is not successfull as the same site numbers have already been used in another study. I have the below suggestions. can you please comment if it would work or help me with a possible solution.

1. Can we append the study number to the site Number. Example if the study is ABC_01 and the site number is 00001, to make it unique we add ABC_01_00001(Study_Sitenumber) and update this in the integration spec for location OID will the integration be successful? i would assume this ABC_01_00001(Study_Sitenumber) will have to to be updated in the code as the target location correct?

2. Can Study site number be used as a Location OID?

[isparks]

I think these are questions for whoever provided you the integration specification. The Location OID can be one of several things:

When mdsol:LocationOIDType="SiteUUID" : The location identifier is the UUID When mdsol:LocationOIDType="SiteName" : The location identifier is the site number (default) When mdsol:LocationOIDType is missing : The location identifier is the site number (default) Every Site in Rave has a unique identifier, stored as [Sites].[UUID]

See the learn.mdsol.com site: https://learn.medidata.com/en-US/bundle/rave-web-services/page/locate_a_site.html

[glow-mdsol]

Is this resolved @vishj1717 ? If not, raise a Helpdesk ticket and let me know so I can see if we can come up with a solution for you.