<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<key-projects><projects><title>Code Sharing of Device Related Software</title><description>CDRH develops software programs as part of regulatory science research projects. A significant number of these software programs have utility to medical device industry as well as academia. There are issues related to transfer of these programs and tools to regulated industry. Some of these issues are: intellectual property ownership, regulatory impact and liability of ownership. The goal of this project is to develop a system where issues mentioned above are resolved and the distribution of CDRH-developed software programs is expedited.</description><dictionary></dictionary><outcome></outcome><accomplishment>Through the code sharing initiative, CDRH engineers have developed several computational methods to facilitate the development and evaluation of medical devices.  For example, the Therapeutic Python script language project (TheraPy) is a collection of Python scripts developed to model the evolution of chemical and physical inhomogeneities in drug-polymer composites, available at: &lt;a href=http://matforge.org/redmine/projects/therapy/wiki target=”_blank”&gt;http://matforge.org/redmine/projects/therapy/wiki&lt;/a&gt;.  A workshop on implementation has been held and the software has been used in industrial R&amp;D. The Monte Carlo Graphics Processing Unit (MC-GPU) is X-ray imaging system simulation code implementing an accurate Monte Carlo x-ray transport algorithm that can be efficiently executed in a state-of-the-art Graphics Processing Unit (GPU). MC-GPU generates clinically-realistic projection or tomographic images of the human anatomy that can be used in the assessment and optimization of imaging systems.  This code is available at: &lt;a href=http://code.google.com/p/mcgpu target=”_blank”&gt; http://code.google.com/p/mcgpu&lt;/a&gt;</accomplishment><table><title></title><overall-status><briefing></briefing><prior-briefing></prior-briefing></overall-status><row><type></type><milestone-description>A. Identify all software tools under development in OSEL that are ready for code sharing</milestone-description><milestone-date>2/28/2010</milestone-date><milestone-status>Completed</milestone-status><milestone-completion-date>2/28/2010</milestone-completion-date></row><row><type></type><milestone-description>B. Identify issues and differences in all software tools</milestone-description><milestone-date>3/31/2010</milestone-date><milestone-status>Completed</milestone-status><milestone-completion-date>3/31/2010</milestone-completion-date></row><row><type></type><milestone-description>C. Identify different methods of code sharing suitable for all or selected software tools</milestone-description><milestone-date>4/30/2010</milestone-date><milestone-status>Completed</milestone-status><milestone-completion-date>4/30/2010</milestone-completion-date></row><row><type></type><milestone-description>D. Have in place policies and procedures for code sharing and dissemination of software tools</milestone-description><milestone-date>7/31/2010</milestone-date><milestone-status>Completed</milestone-status><milestone-completion-date>6/15/2010</milestone-completion-date></row><row><type></type><milestone-description>E. Have in place templates for Office/Center clearance and web posting of documents for open source access and modification</milestone-description><milestone-date>9/30/2010</milestone-date><milestone-status>Completed</milestone-status><milestone-completion-date>9/30/2010</milestone-completion-date></row><footnotes><note></note></footnotes></table></projects><glossary></glossary><related-links><link><url>http://www.fda.gov/AboutFDA/Transparency/track/ucm203038.htm</url><text>FDA-TRACK CDRH Dashboard</text></link></related-links></key-projects>਍††਍਍਍਍਍਍਍