-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LOCATION OID Issue #138
Comments
I think these are questions for whoever provided you the integration specification. The Location OID can be one of several things:
See the learn.mdsol.com site: https://learn.medidata.com/en-US/bundle/rave-web-services/page/locate_a_site.html |
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. |
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.
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?
Can Study site number be used as a Location OID?
The text was updated successfully, but these errors were encountered: