TMCnet News

FDA's Software Monsters: Cybersecurity, Interoperability, Mobile Apps and Home Use (California, United States - March 8-9, 2018) - ResearchAndMarkets.com
[January 23, 2018]

FDA's Software Monsters: Cybersecurity, Interoperability, Mobile Apps and Home Use (California, United States - March 8-9, 2018) - ResearchAndMarkets.com


The "FDA's Software Monsters: Cybersecurity, Interoperability, Mobile Apps and Home Use" conference has been added to ResearchAndMarkets.com's offering.

Software's level of complexity and use is expanding at exponential levels. Likewise, the potential risks to health follow suit. Ransomeware attacks hold your software hostage until you pay hundreds or thousands of dollars. Life supporting and life sustaining healthcare grinds to a halt. Extracting personal healthcare information is another plague that has a huge financial incentive for hackers. Your software is running on thin ice.

The FDA looks at software in one of three ways: Standalone, such as for a mobile app; device-based software used to control a device's performance, or simply electronic records. FDA's risk classification will gradually clarify how it intends to manage the health risks with premarket and postmarket controls. What the FDA did not see was the cancer of cybersecurity attacks, the failure of interoperability, and the explosion in the use of wireless communication and mobile apps.

Inadequate cybersecurity programs and the lack of interoperability for healthcare users pose the gretest threat to any healthcare system. Software exploitations are using more sophisticated approaches and the hackers' programs are readily available on the "dark web."



The increasing sophistication required to protect software programs and have them work with other programs requires progressive software design and software validation considerations. In many instances, validation is limited to the immediate use of the software rather than its environment of use, its performance with other software programs and software hacking. FDA can ask you what you have considered before you take a product to market. Whether your software can survive unscathed is another question.

When software causes a problem, fixing the malfunction or "bug" may be more difficult as software becomes more sophisticated, customized by users and placed in a network system. In these kinds of circumstances, it is difficult to decide who is responsible for managing and fixing the software problems, preventing them from recurring. This becomes a major regulatory headache for FDA and generates business-to-business conflicts. When firms are designing and marketing software, they should be mindful of the unknowns that lurk in the future of software regulated as a device by the FDA.


Topics:

  • FDA's risk-based regulatory strategy
  • Cybersecurity
  • Interoperability
  • National Institute of Standards and Technology
  • Voluntary standards and programs
  • Mobile Apps
  • Premarket software validation and design requirements
  • Postmarket Software recalls

Who Should Attend:

  • Regulatory Affairs
  • Quality Assurance
  • Software Design Engineers
  • Manufacturing
  • Complaint Dept.
  • Hospital Risk Dept.
  • Own label marketers

For more information about this conference visit https://www.researchandmarkets.com/research/hxt6kr/fdas_software?w=4


[ Back To TMCnet.com's Homepage ]