My company would like to uses FSPs to build clinical databases using Oracle Clinical, but they would like have back-end access (read only) to run diagnostics reports and scripts. T
he reports and scripts (SAS, Business Objects) are used to identify potential database issues prior to releasing the database for production use. Because of the way OC is designed, back-end access would expose the FSP or CRO to all studies rather than the one that they are working on.
Does anyone know of any best practice methods that will will allow the back end access that the CRO needs, but limits their access to specific studies?
One way to go forward would be to create a seperate Oracle schema and keep all reports/metrics tables here. Then schedule PL/SQL scripts to populate report related data to these tables for selected studies.
The FSP can then grant the CRO full access to this schema. The resource intensive scripts run only on the seperate schema and will not affect the OC server.
This way it is advantage to both the FSP and CRO.