Implement OAuth integration between PhysioNet and Tufts OHDSI tooling

[tompollard]

Background

We would like to improve support for publication of OMOP-structured datasets on PhysioNet, for example by enabling users to open and explore published OMOP datasets in OHDSI tools such as Atlas (in the same way that users can open WFDB files in Lightwave at the click of a button).

Rather than providing all of the tooling ourselves, I think it would be desirable to work with @AEW0330, @jshoughtaling and colleagues at Tufts to integrate their OHDSI tools with PhysioNet. An important first step towards integration with these tools is to create a mechanism for Tufts to know when it is acceptable to allow a user to access a protected dataset.

We should be able to achieve this using our implemented (but untested!) OAuth provider functionality, which was introduced in #2003. With OAuth we should be able set up a process for providing information such as credentialing status to Tufts (and other trusted clients).

There is a test case and description of this functionality at: #2046. The description includes the following example use case:

"As can be seen, we can implement a direct channel between PhysioNet and Health Data Nexus, which is not exposed to the regular public. An authenticated user on Health Data Nexus can easily access a protected resource on PhysioNet (for Eg: Training), since the access will be granted via the HDN platform." (i.e. Nexus can share the training status of a user with PhysioNet, allowing PhysioNet to confirm that the user has the correct training to access a protected dataset).

Next step

I think the first step towards integrating PhysioNet and OHDSI tooling is to identify and describe an appropriate tool at Tufts that could make use of this functionality. Propose a mechanism for integrating an OAuth authorisation step into the workflow. We can then start speccing out the development work needed to implement the integration.