WO2009111210A2 - Système de gestion des données et procédé de développement pharmaceutique - Google Patents

Système de gestion des données et procédé de développement pharmaceutique Download PDF

Info

Publication number
WO2009111210A2
WO2009111210A2 PCT/US2009/034955 US2009034955W WO2009111210A2 WO 2009111210 A2 WO2009111210 A2 WO 2009111210A2 US 2009034955 W US2009034955 W US 2009034955W WO 2009111210 A2 WO2009111210 A2 WO 2009111210A2
Authority
WO
WIPO (PCT)
Prior art keywords
drug
module
data regarding
processing data
data
Prior art date
Application number
PCT/US2009/034955
Other languages
English (en)
Other versions
WO2009111210A3 (fr
Inventor
Theresa O'brien
Original Assignee
Peak Value Sarl
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Peak Value Sarl filed Critical Peak Value Sarl
Publication of WO2009111210A2 publication Critical patent/WO2009111210A2/fr
Publication of WO2009111210A3 publication Critical patent/WO2009111210A3/fr

Links

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/20—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for electronic clinical trials or questionnaires
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16B—BIOINFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR GENETIC OR PROTEIN-RELATED DATA PROCESSING IN COMPUTATIONAL MOLECULAR BIOLOGY
    • G16B50/00—ICT programming tools or database systems specially adapted for bioinformatics
    • G16B50/30—Data warehousing; Computing architectures
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16C—COMPUTATIONAL CHEMISTRY; CHEMOINFORMATICS; COMPUTATIONAL MATERIALS SCIENCE
    • G16C20/00—Chemoinformatics, i.e. ICT specially adapted for the handling of physicochemical or structural data of chemical particles, elements, compounds or mixtures
    • G16C20/90—Programming languages; Computing architectures; Database systems; Data warehousing
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16B—BIOINFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR GENETIC OR PROTEIN-RELATED DATA PROCESSING IN COMPUTATIONAL MOLECULAR BIOLOGY
    • G16B50/00—ICT programming tools or database systems specially adapted for bioinformatics

Definitions

  • the present disclosure relates generally to the field of pharmaceutical development.
  • the disclosure relates more specifically to the field of data management systems and methods for pharmaceutical development.
  • Drug development involves several sub-processes. These processes include drug discovery, drug development, preparing the drug for marketing opportunities, delivering the drug to the marketplace and deriving revenue from the drug by exploiting various business opportunities including the sale and license of the drug.
  • each sub-process has its own set of proprietary support tools, services and databases. These services often vary from one sub-process to another, producing a fragmented set of tools used throughout the drug development cycle. Further, these tools are often unnecessarily complex and expensive.
  • a data management system for pharmaceutical development includes a processor and a memory operably connected to the processor.
  • the memory is configured to store a discovery module for processing data regarding an investigation of the therapeutic value of a target molecule.
  • the memory also is configured to store a development component for processing data regarding the creation and testing of a drug related to the target molecule.
  • the memory also is configured to store a documentation module for capturing data regarding testing and trial results related to the drug.
  • the memory also is configured to store a delivery module for processing data regarding the production of the drug.
  • the memory also is configured to store a commercialization module for processing data regarding the commercialization of the drug.
  • a method for managing pharmaceutical development includes receiving a request for data, processing data regarding an investigation of the therapeutic value of a target molecule, processing data regarding the creation and testing of a drug related to the target molecule, capturing data regarding the testing and trial results related to the drug, processing data regarding the production of the drug, processing data regarding the commercialization of the drug, and making the requested data available to a user.
  • a computer program product embodied in a computer readable medium.
  • the computer program product includes computer code for receiving a request for data, computer code for processing data regarding an investigation of the therapeutic value of a target molecule, computer code for processing data regarding the creation and testing of a drug related to the target molecule, computer code for capturing data regarding the testing and trial results related to the drug, computer code for processing data regarding the production of the drug, computer code for processing data regarding the commercialization of the drug, and computer code for making the requested data available to a user.
  • a computer implemented method of managing pharmaceutical development involves receiving a request for data, processing data regarding an investigation of the therapeutic value of a target molecule, processing data regarding the creation and testing of a drug related to the target molecule, capturing data regarding the testing and trial results related to the drug, processing data regarding the production of the drug, processing data regarding the commercialization of the drug, and making the requested data available to a user.
  • a data management system for pharmaceutical development includes a client terminal configured to execute a user interface module for interacting with a web application, a web server, connected to the client terminal via a network, and an application server operably connected to the web server.
  • the application server is configured to host a discovery module for processing data regarding an investigation of the therapeutic value of a target molecule, a development component for processing data regarding the creation and testing of a drug related to the target molecule, a documentation module for capturing data regarding testing and trial results related to the drug, a delivery module for processing data regarding the production of the drug, a commercialization module for processing data regarding the commercialization of the drug, and a data access module for accessing and manipulating said data.
  • the data management system also includes a database operably connected to the application server for storing the data.
  • Figure 1 is a block diagram of an exemplary data management system, according to one embodiment.
  • Figure 2 is a block diagram of an exemplary web-based data management system, according to one embodiment.
  • Figure 3 is an exemplary technical architecture functional design, according to one embodiment.
  • Figure 4 is an exemplary technical architecture of two-way integration, according to one embodiment.
  • Figure 5 shows an exemplary process flow diagram of a method for managing pharmaceutical development within any of the data management systems of Figures 1 -4, according to one embodiment.
  • Figure 6 shows an exemplary screenshot of a homepage that may be used by an interface in any of the data management systems of Figures 1-4, according to one embodiment.
  • Figures 7-11 are schematic flow diagrams of five stages of pharmaceutical development that may be executed on any of the data management systems of Figures 1-4 according to some exemplary embodiments.
  • Figure 12 is a data model, according to one embodiment.
  • Figure 13 provides one example of a process model for developing pharmaceuticals.
  • Figure 14 provides additional information concerning certain entities and attributes utilized in Figure 13.
  • An integrated, platform of information technology, tools and services is provided to facilitate the development of life-science products.
  • the platform provides tools for managing the myriad of data required to commercialize a health-care product, including solutions ranging from planning and analyzing experiments to financial forecasting.
  • the platform enables practitioners to focus on core scientific activities and thereby decreases time to market, lowers cost and increases asset value.
  • 21 CFR ⁇ 11 refers to a regulation passed in 1997 in the USA that provides for the voluntary submission of parts or all of regulatory records for drug approval in electronic format without an accompanying paper copy.
  • Abbreviated New Drug Application relates to a proposal from a drug sponsor that the FDA expedite approval of a new pharmaceutical for sale in the U.S.
  • Active Pharmaceutical Ingredient refers to a substance or compound that is intended to be used in the manufacture of a pharmaceutical product as a therapeutically active compound (ingredient).
  • Adverse Effects Reporting System relates to a system for reporting drug safety issues.
  • Amino acid refers to a molecule that contains both amine and carboxyl functional groups. Examples include the alpha-amino acids of the general formula H 2 NCHRCOOH, which represent the twenty building blocks of proteins.
  • the term batch relates to a quantity of a compound made at the same point in time, using the same production process and same source of raw materials, identified by a number unique to the specific quantity produced.
  • BLA Biologies License Application
  • Candidate relates to a substance or compound that will be submitted for approval to be used as a drug.
  • Case Report Form refers to a part of an NDA showing results of individual patient observations from drug testing.
  • Case Report Tabulation relates to a part of an NDA showing summary results of patient observations from drug testing.
  • CBER Center for Biologies Evaluation and Research
  • CDER Center for Drug Evaluation and Research relates to a US agency which reviews applications for approval to make and distribute new drug products.
  • CTD Common Technical Document
  • DAA Drug Regulatory Authority
  • Electronic Common Technical Document refers to a structured XML style sheet which allows the electronic submission of the Common Technical Document (CTD) from applicant to regulator, with ICH-compliant (harmonized) table of contents and technical solution.
  • CCD Common Technical Document
  • Financing Services relates to the activities associated with securing funding to cover costs before sales, license revenues, trade sale or IPO create revenue streams to cover costs, in sequence from Startup to Seed to Series A (first 2-10 mio CHF), Series B (next 10-20 mio CHF), and Series C (next 10-20 mio CHF).
  • Galenical Form refers to a pharmaceutical product prepared according to an official formula expounding the identity, quantity, purity and stability of the components.
  • Individual Case Safety Report (ICSR) relates to a post marketing expedited safety report.
  • An Initial Public Offering (IPO) relates to a first sale of stock by a company to the public.
  • a company can raise money by issuing either debt or equity.
  • Intellectual Property relates to an intangible asset consisting of monetizable knowledge or information.
  • Investigational New Drug relates to a status of an experimental drug after the Food and Drug Administration agrees that it can be tested in people.
  • the term lead refers to a compound with suspected pharmacologically-active characteristics (reactivity, binding properties, ion channel effects, aptotic induction, signaling, etc.)
  • License relates to a contract to use the IP of another company to produce and distribute a drug.
  • Marker refers to a characteristic trait of a disease that facilitates differential diagnosis, for example, a particular gene sequence linked to a hereditary disease.
  • Mass-spectrometer relates to an instrument which measures the masses and relative concentrations of atoms and molecules used to identify compounds via measurement of magnetic force on moving charged particles.
  • MeDRA refers to standardized medical terminology for drug regulation.
  • Metabolite relates to a product of a set of chemical reactions that occur in living organisms in order to maintain life, allowing the organisms to grow and reproduce.
  • Monoclonal Antibody relates to a laboratory-produced substance (antibody) that can locate and specifically bind to particular antigens, for example on cancer cells.
  • antibody a laboratory-produced substance
  • Such antibodies are produced by a single clone of cells (specifically, a single clone of hybridoma cells) and, therefore, represent a single pure homogeneous type of antibody.
  • New Chemical Element refers to a new non-biologic compound which has not been previously approved for use in humans.
  • New Drug Application relates to a proposal from drug sponsors that the FDA approve a new pharmaceutical for sale in the US. Such a proposal typically includes: what happened during animal and human trials (NDA results), the ingredients of the drug, how the drug behaves in the body, and how it is manufactured, processed, and packaged.
  • Oligopeptides refers to a structure formed by the linkage of a few amino acids.
  • Orphan Drug Application relates primarily to an application under the Orphan Drug Act of January 1983 ("ODA”), a federal law concerning rare diseases (“orphan diseases”), defined as diseases affecting fewer than 200,000 people in the United States or low prevalence is taken as prevalence of less than 5 per 10,000 in the community.
  • ODA Orphan Drug Act of January 1983
  • EMEA Committee on Orphan Medicinal Products of the European Medicines Agency
  • a patent is a grant of property right by a government to an inventor to exclude others from making, using or selling an invention.
  • Peptide relates to a molecule composed of two or more amino acids, while larger peptides are generally referred to as polypeptides, or proteins.
  • Pharmacology refers to a set of activities to discover whether or not a compound or substance has benefit as a drug in humans or animals.
  • Pharmacopeia (Ph. Eur., DAB, USP) relates to a book describing chemicals, drugs, and other substances and how they are used as medicines prepared by a recognized authority.
  • Phytopharmaceutical refers to a plant or plant product used as a drug.
  • Proof of Concept relates to a dataset demonstrating that a hypothesis concerning the efficacy and safety of a compound proposed to ameliorate a disease is potentially feasible, and has less than 50% chance of failure in subsequent tests.
  • Reference substance refers to a compound subjected to analysis to be used as a comparison standard to assure the quality of chemical products and to satisfy the demands of the regulatory authorities.
  • Seed Capital relates to an initial amount of money used to start-up a company.
  • SAS Statistical Analysis System File
  • XPORT refers to a file format for transmitting statistics created in SAS.
  • DTD Structured Data Set
  • DRA Structured Data Set
  • Study Tagging File refers to a structured XML stylesheet which allows for identification all of the files associated with a study.
  • Each document typically includes: the document title, the headings under which the documents are located in the table of contents, the relationship to other documents, revision information, the location of the document, and information on the submission.
  • a target for drug discovery is typically a biological molecule that is involved in the molecular or biochemical pathway of the disease state of interest.
  • Toxicology refers to a set of activities to discover whether or not a compound or substance causes harm when used as a drug in humans or animals.
  • Validated Target refers to a target that is proven to respond phenotypically when a compound binds to it.
  • the proof consists of in vitro or in vivo evidence, such as when cell growth is inhibited by action of a biomolecule on a cell component such a ribosome.
  • Validation (GxP, GMP, GLP, GCP) relates to a process of confirming that manufacturing, laboratory, IT or clinical practices used in the discovery, development, production and distribution of drugs satisfies regulatory criteria designed to ensure drug safety and effectiveness. Such criteria can be found, for example, in the Good Manufacturing Practices or Good Laboratory Practices guidelines for the pharmaceutical industry.
  • a data management system 10 is configured to facilitate pharmaceutical (e.g., a drug, a medication, a supplement, etc.) development.
  • data management system 10 may be used to develop pharmaceuticals via various steps from analyzing therapeutic values of molecules to commercialization of the pharmaceutical.
  • Data management system 10 typically includes a processor 12, a memory 14, a user interface 16, a data access module 18, and a development database 20.
  • Processor 12 is configured to execute machine instructions or operations to control the functions, inputs to, and outputs from memory 14, user interface 16, data access module, and development database 20, According to some exemplary embodiments, processor 12 maybe implemented using a computer processor of any past, present, or future design capable of performing instructions related to pharmaceutical development. According to another exemplary embodiment, processor 12 may be a special purpose computer processor for a pharmaceutical development system, incorporated for this or another purpose, or by a hardwired system.
  • Memory 14 is generally configured to store a computer program product, computer code, and/or machine instructions that may be executed on processor 12 to facilitate development of pharmaceuticals.
  • Memory 14 typically includes computer code embodied as a discovery module 22, a development module 24, a documentation module 26, a delivery module 28, and a commercialization module 30.
  • Memory 14 may be a local cache, a local hard disk drive, a CD-ROM, a floppy disk, a random access data source (e.g., a RAM), a read-only data source (e.g., a ROM), a remote server, or any other volatile or non- volatile memory capable of storing computer code related to pharmaceutical development.
  • the above- mentioned modules 22, 24, 26, 28 and 30 are integrated so that data and processes shared between modules is in a consistent, standard format.
  • Modules are integrated by continuous adherence to voluntarily agreed data standards that are starting to appear for biotech information. Groups analagous to CDISC for development-phase data standards are starting to emerge to conduct standardization of biotech data.
  • the data management system will allow for a meta-model to maintain and update all interfaces according the latest standards.
  • Discovery module 22 is configured to process data regarding an investigation of the therapeutic value of a target molecule, for example investigating a possible affect of the target molecule on a gene, disease, disorder, ailment, irregularity, etc.
  • the discovery module can include a molecule miner module 32, a molecule modeling module 34, and an investigation module 36.
  • molecule miner modules 32 are developed and used in an academic setting. Molecule miner module 32 is configured to discover molecular substructures or target molecules while molecule modeling module 34 is configured to model the discovered molecular substructures.
  • the investigation module 36 is configured to determine what therapeutic value, if any, that the modeled molecular substructure may have.
  • Development module 24 is configured to process data regarding the creation and testing of a drug that is at least related to a target molecule discovered by discovery module 22.
  • Development module 24 comprises, for example, a patent database 38, a literature database 40, a pharmokinetic database 42, and a toxicology database 44.
  • the above-described databases are commercially available databases such as Schr ⁇ dinger, Tessella and Thomson.
  • One or more of the databases may facilitate the development of a drug based on the target molecule to have a desired therapeutic value.
  • Patent database 38 generally stores patent application templates and completed patent applications relating to, for example, the target molecules, therapeutic methods, and/or disorders of interest. Development module 24 may use patent database 38 to facilitate the drafting of patent applications related to the target molecules, therapeutic methods, and/or disorders of interest.
  • Literature database 40 generally stores literature or documentation templates that may relate to target molecules, desired therapeutic methods, or disorders of interest. Development module 24 may use literature database 40 to facilitate the drafting of literature or publications related to the target molecules, therapeutic methods, and/or disorders of interest.
  • Pharmokinetic database 42 generally stores pharmokinetic or pharmacokinetic information or templates that may relate to discovered absorption, distribution, metabolism, and excretion of target molecules. Development module 24 may use pharmokinetic database 42 to facilitate the documentation of discovered absorption, distribution, metabolism, and excretion of target molecules.
  • Toxicology database 44 generally stores information or templates related to the toxicology of target molecules, for example symptoms, mechanisms, treatments, and detection of toxic substances or reactions.
  • Development module 24 may use toxicology database 44 to facilitate the documentation of discovered symptoms, mechanisms, treatments, and detection of toxic substances or reactions.
  • Documentation module 26 is configured to capture data regarding testing and trial results related to the developed drug.
  • Documentation module 26 includes a formatting module 46, a public release module 48, a processing module 50, and a document creation module 52.
  • Formatting module 46 is generally configured to format data generated by discovery module 22 and development module 24 for regulatory submission, for example for submission of the development data to the Unites States Food and Drug Administration (FDA) for approval of clinical trials.
  • Public release module 48 is configured to organize the collected data and facilitate the release of at least a portion of the data to the public.
  • Processing module 50 is configured to process data related to a patent application, for example to examine the patentability, novelty, or patent clearance of the developed drug in view of the patent landscape.
  • Document creation module 52 is configured to create documents for clinical trials, for example clinical trial guidelines.
  • Delivery module 28 is configured to process data regarding the production of the developed drug (i.e., samples for tests and trials for production).
  • Delivery module 28 can include a services module 54 and a finance module 56.
  • the above-described modules are implemented using software-as-service applications such as Documentum and SAP.
  • Services module 54 is configured to process data regarding bioinformatics (e.g., computational biology; systems biology; sequence, gene, or protein alignment, assembly, or prediction; etc.), protocol design (e.g., FDA protocols), and/or trial insurance (e.g., risk assessment, recommended insurance coverage, etc.) and how the data may relate to the developed drug.
  • Finance module 56 is configured to process data regarding order tracking; overhead, clinical, and development costs; and revenues or potential revenues that may be related to the drug.
  • Commercialization module 30 is configured to process data regarding the commercialization of the developed drug.
  • the commercialization module 30 may facilitate project tracking, financial valuation and financial reporting.
  • the commercialization module 30 may process data regarding the sale, contracting, and/or licensing of the drug, for example potential buyers or licensees, a cost structure, marketing materials, etc.
  • User interface 16 is coupled to processor 12 and is configured process user input (e.g., via a keyboard, mouse, integrated buttons, another tactile device, an oral command, etc.) and provide user output (e.g., on a display, a printer, an audio prompt, etc.).
  • the user interface may receive commands from the user to direct or manage the development of a pharmaceutical and/or provide reports or status updates to the user on pharmaceutical development.
  • Data access module 18 is generally configured to provide processor 12 access to development database 20.
  • Figure 12 illustrates a data model
  • Development database 20 is configured to store information that may facilitate development of pharmaceuticals via execution of the computer code and data stored in memory 14.
  • development database 20 may include information related to previously developed drugs, published or patented works of others, known information on medical disorders and treatments, etc.
  • a data management system 58 is configured to facilitate pharmaceutical development in a manner similar to data management system 10, except that user interface module 16 is located in a remote location.
  • Data management system 58 includes an application server 60, a database 62, a web server 64, a network 66, and a client terminal 68.
  • Application server 60 is similar to processor 12 in that it executes computer or application code embodied as discovery module 22, development module 24, documentation module 26, delivery module 28, commercialization module 30, and data access module 18.
  • Application server 60 communicates with database 62 (e.g., development database 20) to allow data management system 58 to perform functions at least similar to that of data management system 10.
  • database 62 e.g., development database 20
  • application server 60 may be implemented using a server or computer processor of any past, present, or future design capable of performing instructions related to pharmaceutical development.
  • application server 60 may include a special purpose computer processor for a pharmaceutical development system, incorporated for this or another purpose, or by a hardwired system.
  • Web server 64 is configured to facilitate access to application server 60 via network 66 from one or more client terminals 68.
  • Web server 66 may be any computer or computer code that is configured to accept HTTP requests from client terminal 68 and serve HTTP responses and any associated data (e.g., web pages, HTML documents, images, other linked objects, etc.) back to client terminal 68.
  • Network 66 is configured to carry communication signals between web server 64 and client terminal 68.
  • network 66 may be a local area network (LAN), a wireless area network (WAN), the Internet, or any other wired or wireless network capable of carrying data between web server 64 and client terminal 68.
  • Client terminal 68 is configured to allow user access to application server 60 via network 66 using user interface 16.
  • Client terminal 68 may be either a locally connected terminal or computer or a remotely connected computer.
  • FIGS 3 and 4 further characterizations of data management systems similar to data management systems 10 and 58 of Figures. 1 and 2 are illustrated.
  • An interface provided on a website over the Internet provides access to the pharmaceutical development functionality described above. Both internal and externally hosted software packages may facilitate the management of pharmaceutical development.
  • Method 100 may be performed on any of the data management systems of Figures 1-4 or another similar system capable of managing pharmaceutical development.
  • the data management system receives a request for data.
  • a user may request data via user interface 16 that is related to: molecules that may have an affect on a specific disorder, documentation related to previously developed drugs, commercialization efforts, clinical trials, or any other information that the data management system is capable of providing.
  • the data management system processes data regarding an investigation of the therapeutic value of a target molecule, for example as described above in relation to discovery module 22.
  • the data management system processes data regarding the creation and testing of a drug related to the target module, for example as described above in relation to development module 24.
  • the data management system captures data regarding the testing and trial results related to the drug, for example as described above in relation to documentation module 26.
  • the data management system processes data regarding the production of the drug, for example as described above in relation to delivery module 28.
  • the data management system processes data regarding commercialization of the drug, for example as described above in relation to commercialization module 30.
  • the data management system makes the requested data available to a user, for example as an output via user interface 16, as described above.
  • a screenshot 120 illustrates a homepage that can be displayed by user interface 16 for user interaction in managing the development of pharmaceuticals.
  • a user may have the ability to directly manage the discovery, development, documentation, delivery, and commercialization modules via the homepage.
  • Various functions of the homepage may require that the user login to verify access privileges. By logging in, the user also may be provided with customized information or management options, for example related to drugs the user is developing.
  • the homepage also may provide search functions to search the data management system for information, documentation, statuses, or other information related to pharmaceutical development as it pertains to a specific molecule, disorder, user, document, etc.
  • the homepage also may provide options to subscribe and receive updates on further developments, for example of a drug or disorder of interest.
  • the user also may have the option of upgrading their access or the homepage client installed on their computer.
  • a blog or forum may be further provided for discussion related to any specific or general aspects of pharmaceutical development.
  • the homepage may further include advertisements that may be of interest to the user, for example from biotech providers, or based on the habits of a logged-in user.
  • an exemplary process model for developing pharmaceuticals includes five stages: a discovery or pre-clinical stage, a development stage, a documentation stage, a delivery stage, and a deal or commercialization stage.
  • Figure 13 lists the processes for carrying out the five stages in detail. Entities and attributes used and referred to in the process are described further in Figure 14. For example, the table sets forth the purpose of each process, the information used and created by the process and several process sub steps.
  • Table 1 includes processor profiles which set forth the people who are responsible, accountable, consulted and/or informed about the processes involved in each of the five stages or pharmaceutical development.
  • Figures 7-11 provide a number of operations that may be executed by the data management system during each stage of pharmaceutical development. It is noted that while the illustrated embodiments, describe five stages of development, according to other exemplary embodiments more or fewer than five stages of pharmaceutical development may be executed by the data management system. Further, while specific operations are described in the FIGURES for execution by a data management system, according to other exemplary embodiments, more or fewer than the illustrated operations may be executed.
  • FIG 7 is an overall illustration of the tasks that can be performed using the data management system.
  • the discovery module 22 allows a user to perform tasks critical to pre-clinical pharmaceutical development from the screening of molecules to the regulatory approval of a drug.
  • the development module 24 and documentation module 26 are configured to assist a user in performing the tasks shown in Figures 9(a)-(b). These tasks include tracking and documenting the testing of a drug. Further, the documentation module 26 can be used to generate documentation needed for regulatory approval of the drug.
  • the delivery module 28 is configured, as shown in Figure 10, to assist in the pre-production, manufacturing, sales and distribution of a drug. This includes packaging design, obtaining raw materials and planning manufacture, accepting orders and making deliveries.
  • Figure 11 illustrates tasks that may be performed using the commercialization module 30. Tasks facilitated by the commercialization module 30 include business plan creation, obtaining funding, performance tracking, business related report generation, payment collection and licensing.
  • the discovery 22, development 24, documentation 26, delivery 28 and commercialization 30 modules are tightly integrated which allow a user to proceed from one stage of drug development to the next without migrating data or repeating conventional setup procedures.
  • Modules are integrated by continuous adherence to voluntarily agreed data standards that are starting to appear for biotech information. Groups analagous to CDISC for development-phase data standards are starting to emerge to conduct standardization of biotech data.
  • the data management system will allow for a meta-model to maintain and update all interfaces according the latest standards.
  • the above-mentioned modules can be customized over time to fit the needs of its users to further streamline the drug development process.
  • a user may perform tasks in a non-linear fashion. For example, a user can create a business plan using the commercialization module 30 and then use the relevant data generated by the commercialization module 30 in conjunction with the discovery module 22 to identify a drug based on the pre-existing business plan.
  • the above-mentioned modules are integrated, data generated across each module can be easily shared.
  • the data stored by the development database 20 can be used in subsequent phases of drug development without the need for reformatting or other cumbersome modification.
  • the development database 20 allows users to create proprietary taxonomies. Further, the integrated development database 20 reduces the occurrence of duplicate data.
  • embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon.
  • machine-readable media can be any available media which can be accessed by a general purpose or special purpose computer or other machine with a processor.
  • machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor.
  • Machine- executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Physics & Mathematics (AREA)
  • Medical Informatics (AREA)
  • General Health & Medical Sciences (AREA)
  • Databases & Information Systems (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Bioinformatics & Computational Biology (AREA)
  • Biotechnology (AREA)
  • Evolutionary Biology (AREA)
  • Biophysics (AREA)
  • Bioethics (AREA)
  • Spectroscopy & Molecular Physics (AREA)
  • Computing Systems (AREA)
  • Software Systems (AREA)
  • Chemical & Material Sciences (AREA)
  • Crystallography & Structural Chemistry (AREA)
  • Epidemiology (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

L’invention concerne un système de gestion des données pour le développement pharmaceutique comprenant un processeur et une mémoire reliée fonctionnellement au processeur. La mémoire est configurée pour stocker un module de découverte pour le traitement des données concernant une investigation de la valeur thérapeutique d’une molécule cible. La mémoire est également configurée pour stocker un composant de développement pour le traitement des données concernant la création et le test d’un médicament lié à la molécule cible. La mémoire est également configurée pour stocker un module de documentation pour saisir les données concernant les résultats de test et d’essai liés au médicament. La mémoire est également configurée pour stocker un module de prestation pour le traitement des données concernant la production du médicament. La mémoire est également configurée pour stocker un module de commercialisation pour le traitement des données concernant la commercialisation du médicament.
PCT/US2009/034955 2008-02-29 2009-02-24 Système de gestion des données et procédé de développement pharmaceutique WO2009111210A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US3251408P 2008-02-29 2008-02-29
US61/032,514 2008-02-29

Publications (2)

Publication Number Publication Date
WO2009111210A2 true WO2009111210A2 (fr) 2009-09-11
WO2009111210A3 WO2009111210A3 (fr) 2009-12-30

Family

ID=41056541

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2009/034955 WO2009111210A2 (fr) 2008-02-29 2009-02-24 Système de gestion des données et procédé de développement pharmaceutique

Country Status (1)

Country Link
WO (1) WO2009111210A2 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5434796A (en) * 1993-06-30 1995-07-18 Daylight Chemical Information Systems, Inc. Method and apparatus for designing molecules with desired properties by evolving successive populations
US6222093B1 (en) * 1998-12-28 2001-04-24 Rosetta Inpharmatics, Inc. Methods for determining therapeutic index from gene expression profiles
US20030208378A1 (en) * 2001-05-25 2003-11-06 Venkatesan Thangaraj Clincal trial management
US20040210396A1 (en) * 2003-03-28 2004-10-21 Solutia Inc. Methods and structure for automated active pharmaceuticals development

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5434796A (en) * 1993-06-30 1995-07-18 Daylight Chemical Information Systems, Inc. Method and apparatus for designing molecules with desired properties by evolving successive populations
US6222093B1 (en) * 1998-12-28 2001-04-24 Rosetta Inpharmatics, Inc. Methods for determining therapeutic index from gene expression profiles
US20030208378A1 (en) * 2001-05-25 2003-11-06 Venkatesan Thangaraj Clincal trial management
US20040210396A1 (en) * 2003-03-28 2004-10-21 Solutia Inc. Methods and structure for automated active pharmaceuticals development

Also Published As

Publication number Publication date
WO2009111210A3 (fr) 2009-12-30

Similar Documents

Publication Publication Date Title
Vaught et al. An NCI perspective on creating sustainable biospecimen resources
US8438041B2 (en) System and method for tracking and reporting clinical events across a vast patient population
Huser et al. Standardizing data exchange for clinical research protocols and case report forms: An assessment of the suitability of the Clinical Data Interchange Standards Consortium (CDISC) Operational Data Model (ODM)
Biedermann et al. Standardizing registry data to the OMOP Common Data Model: experience from three pulmonary hypertension databases
US20140244309A1 (en) Systems and methods for assembling electronic medical records
Kudyakov et al. Electronic health record use to classify patients with newly diagnosed versus preexisting type 2 diabetes: infrastructure for comparative effectiveness research and population health management
Laurence et al. A pragmatic cluster randomised controlled trial to evaluate the safety, clinical effectiveness, cost effectiveness and satisfaction with point of care testing in a general practice setting–rationale, design and baseline characteristics
Marini et al. Systematic verification of bioanalytical similarity between a biosimilar and a reference biotherapeutic: committee recommendations for the development and validation of a single ligand-binding assay to support pharmacokinetic assessments
Nandal et al. Integrating pharmacoproteomics into early-phase clinical development: state-of-the-art, challenges, and recommendations
Mechanick et al. American Association of Clinical Endocrinologists and American College of endocrinology protocol for standardized production of clinical practice guidelines, algorithms, and checklists–2017 update
Sullivan et al. Analytic characterization of biosimilars
Adams et al. NIH HEAL Common Data Elements (CDE) implementation: NIH HEAL Initiative IDEA-CC
Rousseaux et al. Overview of drug development
Gliklich et al. Rare disease registries
Niazi The FDA’s New Guideline “Generally Accepted Scientific Knowledge”(GASK): An Opportunity to Expedite the Approval of Biosimilars
Thekkur et al. Primary health care system strengthening project in Sri Lanka: status and challenges with human resources, information systems, drugs and laboratory services
Ojha et al. International council for harmonisation (ICH) guidelines
Maignen et al. Integrating health technology assessment requirements in the clinical development of medicines: the experience from NICE scientific advice
Bouwman-Boer et al. Pharmaceutical quality systems
WO2009111210A2 (fr) Système de gestion des données et procédé de développement pharmaceutique
Ardini et al. Sample and data sharing: Observations from a central data repository
Kalouguina et al. Challenges and solutions for integrating and financing personalized medicine in healthcare systems: A systematic literature review
Uriel et al. An Adequate Pharmaceutical Quality System for Personalized Preparation
Masini et al. The challenge of sustainability of high-cost oncological drugs: a budgeting model in an Italian cancer center
Moeti et al. Regulatory registration timelines of generic medicines in South Africa: Assessment of the performance of SAHPRA between 2011 and 2022

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09717141

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09717141

Country of ref document: EP

Kind code of ref document: A2