We hope you'll join us for our 4/23 webinar on using data tables to apply reference ranges and AE codes in OC4. For more information and to register, visit https://register.gotowebinar.com/register/2882170018956684555

REST API depending on active study?

I currently started with utilisation of OC REST API fo in my applications and there is one thing which is bothering me a lot so I wonder if somebody is having the same troubles.

As it is stated here

It seems that REST API calls only work for the user active study. Within my applications the users can browse through their studies and dynamically select the one which they want to work with. However, from my experience, unlike it is stated in the above issue, the access is not strictly limited to active study. I do not see a pattern there because sometimes I can access the data from inactive study as well as active study, sometimes I cannot access data (getting HTTP code 500) from some studies and the others work. The only workaround which I have right now is that when the external program cannot access the data from some study, logging in to OC and changing active study to that one really helps.

It is very inconvenient for users to do it.... did somebody has a better solution?



  • kristiakkristiak Posts: 1,329 ✭✭✭

    What roles do your users have that you are referring to above? Do you run several studies on the same instance of OC? We always separate our studies on different VPN servers to avoid any conflicts and problems that you referring to. Our customers are also much happier that way and feel safer having their "own" server.



  • toskriptoskrip Posts: 271 ✭✭✭
    Hi Kristiak,

    this issue is not role dependent. I tested it with administrator, data entry, data specialist, investigator .... it is happening for all users. We are one institution so we have one productional OC instance where all our studies (mono as well as multi-centric) goes. Basically we have very similar setup like CTMM-TraiT which Jacobe mentioned couple of times on this forum.

    The point is that as Alicia already wrote somewhere on the forum the REST API is here to be used. However it is still quite new feature with some issues which prevents the third party application to utilise it in production environment.


This discussion has been closed.