23.03.2013 Views

White Guide and Orange Guide Formatting Project - Pfizer

White Guide and Orange Guide Formatting Project - Pfizer

White Guide and Orange Guide Formatting Project - Pfizer

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Orange</strong> <strong>Guide</strong> – Chapter 5: Interactions with Health Systems <strong>and</strong> Medical Groups<br />

Assisting a Customer with the Development of a Protocol<br />

Q. One of my customers wants to implement a diabetes screening protocol<br />

within their Health Information Technology (HIT) system. The protocol they<br />

have chosen is not RC-approved, but it was developed by a credible <strong>and</strong> wellregarded<br />

independent organization <strong>and</strong> is publicly available. Can I assist with<br />

the implementation (i.e., to advise on appropriate pDPN metrics)?<br />

A. Perhaps, but you must first consult your team attorney before you use or<br />

engage a customer around any resource that hasn’t been expressly RCapproved.<br />

This is a strict requirement, since the protocol may be inconsistent<br />

with <strong>Pfizer</strong> approved messaging. For example, it may recommend use of a<br />

<strong>Pfizer</strong> product that is not consistent with the label.<br />

Disease State Discussions with Customers<br />

Q. After preliminary needs assessment meetings the <strong>Pfizer</strong> team would like to<br />

present to a Health System customer the areas of mutual interests for<br />

potential collaboration. One potential opportunity is in a disease state where<br />

<strong>Pfizer</strong> has a prominent product. How much can be said about the disease<br />

state <strong>and</strong> can <strong>Pfizer</strong> mention its product in the presentation? Will the<br />

presentation need to be approved?<br />

A. The particular disease state <strong>and</strong> the <strong>Pfizer</strong> product in that disease state will<br />

dictate how much can be said. In certain cases, where a risk of off-label use<br />

exists, <strong>Pfizer</strong>’s disease state discussion must be consistent with the label for<br />

the specific <strong>Pfizer</strong> product. In other cases, the disease state discussion could<br />

be broader, as long as there is no implication that use of the <strong>Pfizer</strong> product<br />

would result in broader benefits than those mentioned in the product’s label.<br />

Regarding approval, if the discussion around the disease state is more detailed<br />

or the product is mentioned by name, then the presentation will need to be<br />

approved by the product attorney, <strong>and</strong> may require full br<strong>and</strong> RC approval.<br />

Note that before presenting to the customer, proposals related to a disease<br />

area should be appropriately vetted with the relevant internal stakeholders in<br />

order to help ensure that all relevant <strong>Pfizer</strong> stakeholders are aligned with<br />

respect to strategies in disease areas in which we promote. Such stakeholders<br />

may include the respective br<strong>and</strong> team(s), Channel Strategies <strong>and</strong> Solutions<br />

Group, Medical <strong>and</strong> Legal.<br />

103<br />

Rev. 09/12<br />

Page 8 of 18

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!