491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
86 6 The Product Development Pathway
BookID 185346_ChapID 6_Proof# 1 - 20/08/2009
BookID 185346_ChapID 6_Proof# 1 - 20/08/2009
use population and/or run by the intended end-user. Ideally, this means com-
pleting development of a prototype that is near final or very close to it.
Notwithstanding regulatory issues, there could be reasons why one would want
to use an early stage prototype and introduce final changes later, if a new tech-
nology such as a better chip is available soon. However, be wary of unproven
components no matter how wonderfully touted. You do not want to place the
future of your product into the hands of others by becoming codependent on
their quality and performance. For medical tests, realize that downstream
changes may introduce variation or unforeseen chemical reactions that may
alter results in an unanticipated manner.
Some prototype development activities should be contracted out to help keep
your infrastructure at a reasonable level. As discussed previously there may be the
temptation to significantly expand the capabilities of your organization because you
have the funds in the bank and you need the work done. Before doing this you
should determine which core competencies are your strategic assets. If an activity
is not a core competency you should not consider anything other than subcontract-
ing the service, unless it is reasonably inexpensive, requires little human capital, and
you will always need it, and you can do it cheaper, faster or better in-house –
otherwise forget about it. However, if a new function strengthens your core compe-
tency, then add to it. For instance, if you are a gene discovery company and your
core competency is proprietary methods of discovering genes that correlate with
disease, anything tangential to this objective builds on your strength. Whereas, you
would outsource, say specimen acquisition or regulatory functions early on in the devel-
opment of an organization. Do not forget that your functions during this stage are
dynamic and should be reassessed periodically. What is best now may not be ideal
six months or a year later.
Prototype development time and costs differ significantly, depending on the
development objectives. This is the stage when companies typically run out of
money, or find that the development timeframe takes longer than expected. The
ultimate goal at this stage is to produce a prototype that demonstrates its intended
capabilities, and allows the company to move to the subsequent stage where a final
assessment of efficacy can be determined.
Analytics and Tools: Clinical Validation Stage
During this stage, the company must have a final product that will be used for com-
mercialization. This is because they must test the product in, or on, the intended use
population. For medical testing and devices not considered to be “High Risk,” some
studies may be conducted on clinical specimens without first receiving an
Investigational Device Exemption (IDE) from the FDA prior to testing (companies
developing High Risk medical devices must first file and receive IDE approval prior
to testing in humans). The goal during this stage is to validate results in multiple
populations. Ideally, you will want to have independent validation from other