Skip to content

Latest commit

 

History

History

use_cases

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 

PHUSE PODR Logo Logo

PODR - Use Cases

[17 May 2020]

We're interviewing PHUSE members to identify how PODR can best meet their needs.

This is the process we're using to discover their needs:

  • Identify the critical [Business Decisions] that have
  • [Questions to Answer], to be defined as
  • [Use Cases] of Who needs to Do What using
  • [Tools] executed against
  • [Data] in the PHUSE Open Data Repository

Decisions to Data

The design and implementation of the PHUSE Open Data Repository ("PODR") is driven by Use Cases.

You can visualize PODR as a multi-dimensional object containing millions of records from multiple sources (such as the EU's EMA; the US' FDA; and the WHO; among others).

Working collaboratively across Working Groups, NIHPO is leading the definition of Use Cases that address the specific needs of PHUSE members.

Think of each Use Case as a series of Questions to Answer to help a PHUSE member to make better Business Decisions. NIHPO is then building PODR to

The sample dashboards provide a particular “view" into the data inside PODR. Where each “view” focuses on a single topic or perspective.

Use Case 01: Compound Name.

This Use Case retrieves all the relevant information based on a specific compound name.

This Use Case is designed to facilitate the tracing of a single compound across all pharmaceutical products approved in both the EU and the US. And to review published articles that mention the compound.

Use Case 02: Condition Name.

This Use Case retrieves all the relevant information for a particular condition or disease name.

This also allows researchers to list EU-, US- and WHO-listed clinical trials targeting a specific condition.

Use Case 03: Drug Name.

This Use Case compiles many available data sources by a drug’s commercial name.

Our goal here is to provide an integrated view of each approved drug, from regulatory filings to adverse events.

Use Case 04: Manufacturer Name.

This Use Case summarizes all the information PODR has available about a single manufacturer.

We use harmonized manufacturer names to facilitate searches across datasets. By “harmonized” we mean that for example in the case of “Bayer” we define dozens of variations, such as: 'BAYER PHARMACEUTICALS CORPORATION' 'BAYER GERMANY' 'BAYER HEALTHCARE LLC' 'BAYER HEALTHCARE PHARMACEUTICALS IN' 'BAYER HEALTHCARE PHARMACEUTICALS' 'BAYER PHARAMCEUTICALS CORPORATION'

Please contact Jose C. Lacal if you'd like to be interviewed to build the PODR Use Cases.