2013 ohsug - use cases for using the program type view in oracle life sciences data hub (lsh)

PREVIOUS NEXT PREVIOUS NEXT Oracle Health Sciences User group September 2013

Slide 1

Use Cases for using the

Program Type View

September, 2013

Mike Grossman Vice President of

Clinical Data Warehousing and

Analytics

BioPharm Systems


Slide 2

Welcome & Introductions

Mike Grossman Vice President of Clinical Data Warehousing and Analytics BioPharm Systems, Inc.

• CDW/CDA practice lead since 2010

– Expertise in managing data for all phases and styles of clinical trials

– Leads the team that implements, supports, enhances, and integrates Oracle’s LSH and other data warehousing and analytic solutions

• Extensive Oracle Life Sciences Hub (LSH) experience

– 10 years of experience designing and developing Oracle Life Sciences Hub at Oracle

– 27 years in the industry

– 5+ years of experiencing implementing LSH at client sites


Slide 3

Agenda

• What is a view program

• Use case 1 – Data pooling

• Use case 2 – Data security

• Use case 3 – Data blinding


Slide 4

What is a view program?

• An LSH program that has the “VIEW” technology type

• Allows you to combine data from multiple LSH table

instances without storing the data multiple times

• Creates a user-defined view of data across multiple table

instances


Slide 5

View Program


Slide 6

View Program Type


Slide 7

Table Descriptors

• Multiple LSH data sources

• A single target table


Slide 8

Source Code


Slide 9

Source Code

SELECT [ hint ] [ { { DISTINCT | UNIQUE } | ALL } ] select_list FROM table_reference [, table_reference ]. . . [ where_clause ] [ hierarchical_query_clause ] [ group_by_clause ] [ HAVING condition ] [ model_clause ] [ { UNION [ ALL ] | INTERSECT | MINUS } ( subquery ) ] [ order_by_clause ]


Slide 10

Source Code

• Can only reference the program’s source table descriptors

• Can call functions/procedures which are included in

PL/SQL programs that are included as static references

• Cannot reference public database objects


Slide 11

View Table


Slide 12

View Table

• The view table is created

– When the view program is installed

– As a database view

• Can be used as a source table for other LSH programs,

data marts, or business areas

• The currency timestamp is applied every time you access

the view’s current data

• If you remove the view program instance the

corresponding table instance is also removed


Slide 13

View Data

From source DM

Data Currency

From source AE


Slide 14

Use Case 1 – Data Pooling

• The key to data pooling is having data that is standard, or

conformed

– SDTM or SDTM+

– Company standards

• Data can be pooled by

– Indication

– Therapeutic area

– Compound or device

– Etc.


Slide 15


• Pooled data can be used for

– On-going safety review

– Efficacy analysis

– To present the data to the sponsor in business area visualizations

– Etc.

• Data pooling can be

– Manual

– Automated


Slide 16



Slide 17

Manual Pooling

• Create the view program

• Add multiple table descriptors

• Launch the IDE to create and verify the source code

• Install the program

• Manually update the program

– When the source metadata changes

– To maintain the list of studies to be pooled


Slide 18

Automated Pooling

• Create and validate the pooling automation program

• Maintain the list of studies to be pooled


Slide 19

Automated Pooling

Tables to support the list of studies to be pooled,

metadata verification, etc.


Slide 20

Automated Pooling

Primary source code and shared PL/SQL

utilities


Slide 21

Automated Pooling

PL/SQL source code


Slide 22

Automated Pooling

Stores a list of LSH studies to include in the

automated pooling


Slide 23

Automated Pooling • The results in

LSH

View programs

View tables


Slide 24

Use Case 2 – Security • Use program views to limit a user’s access to only those

studies to which they’re authorized

• The DM_ALL dataset contains data for two studies but

the user should only have access to one of them


Slide 25

Security

• The view program

– Uses DM_ALL as the data source

– Generates the SECURITY_V table view


Slide 26

Security • The view program’s source code

– Restricts access at the study level


Slide 27

Security

• The results in a business area visualization

– Display only the study the user should be able to access


Slide 28

Use Case 3 – Data Blinding

• Views on tables to mask data

• Authorize feature

• Multiple views for blinded/dummy data


Slide 29

Q&A


Slide 30

Contact Us

• North America Sales Contacts:

– Rod Roderick, VP of Sales, Trial Management Solutions

– [email protected]

– +1 877 654 0033

– Vicky Green, VP of Sales, Data Management Solutions


– +1 877 654 0033

• Europe/Middle East/Africa Sales Contact:

– Rudolf Coetzee, Director of Business Development


– +44 (0) 1865 910200

• General Inquiries:


2013 ohsug - use cases for using the program type view in oracle life sciences data hub (lsh)

Technology

view data

data pooling pooled

userdefined view of

clause group

view table

data currency

data pooling use case

data marts