throbber
From:
`Sent:
`To:
`Subject:
`
`kate dawson/cambridge/biogenidec;nsf;kate.dawson@biogenidec.com;smtp
`Thu Dec 21 2006 16:51:48 EST
`
`MRI minutes
`
`Here is how I editted. I have sent to
`
` for input - hope that is ok.
`
`
`
`Happy Holidays!
`
`Kate
`
`Page 1 of 3
`
`Biogen Exhibit 2211
`Coalition v. Biogen
`IPR2015-01993
`
`

`

`Date: Monday. 18 December 2006
`
`
`
`
`
`
`
`Meeting Agenda:
`
`
`. The purpose of the discussion:
`0
`
`
`
`
`
`
`
`0
`Initiate discussion between the two contracted Central MRI Reading Centers for the BGOOOI2 Phase 3
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Program. Protocol #L l09MS30l and 109MS302
`
`
`
`
`
`Discuss and document how the MRI Reading Centers plan to conduct the analysis of the MRI Data
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`(i.e.._ lesion and Volume counts, etc) and,
`
`
`
`
`
`
`
`Ensure data analysis as consistent as possible across both the Reading Centers and studies
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Meeting Attendees:
`
`
`Bio en Idec
`DB :
`
`
`
`Kate Dawson. MD
`
`
`
`
`
`
`
`
`
`
`
`. Independent Contractor (piiniany liaison between- and Biogen Idec)
`Minhua Yang. Lead Biostatistician
`
`lO9MS30l Ccnlrzil Reading Center :
`
`g 109MS302 MR1 Central Reading Center}:
`
`Discussion Points:
`
`I
`
`
`Time points:
`
`
`0
`In a subset of subjects. MRI are being collected at Baseline. Week 48 (year 1) and Week 96 (year
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`2).
`
`The FDA recently reviewed the protocol and provided cormnents to BBB: these cornnients may
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`lead to a protocol amendinent. BBB is evaluatin the conirnents. and these ma lead to chan es in the
`
`
`
`
`
`
`
`
`
`
`
`
`current MRI data plan
`
`
`
`
`
`
`
`
`
`
`Page 2 of 3
`
`

`

`
`
`Page 3 of 3Page 3 of 3
`
`Page 3 0f 3
`
`Page 3 of 3
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket