patient management software patient management software patient management software (pms) is referred to as software that is regulated as a medical device. it is software that is used to acquire medical information from a medical device to be used in the treatment or diagnosis of a patient. it can also be software that is an adjunct to a medical device and directly contributes to the treatment of the patient by performing analysis, or providing treatment or diagnosis functionality that replaces the decision and judgment of a physician. clinical applications medical devices are classified and these classifications became somewhat less restrictive in december, 2010. regulations provide rules for classifying medical devices into four increasing risk levels – class i, class ii, class iii, and class iv. patient management software is classified as either class i or class ii. software that is intended to be used to view images, or other real time data, as an adjunct to the monitoring device itself, for the purpose of aiding in treatment or diagnosis of a patient, would be class i medical devices. medical device software that is an adjunct to another medical device and is involved in data manipulation, data analysis, data editing, image generation, determination of measurements, identification of a region of interest in an image, or identification (by an alarm or alert) of results from a monitor that are outside of an established range, is a class ii medical device if it: (1) provides the only means and opportunity to capture or acquire data from a medical device for aiding directly in diagnosis or treatment of a patient; or (2) replaces a diagnostic or treatment decision made by a physician. examples of patient management software are pacs, remote patient monitoring. others include any medical device that is used to transmit data from a medical device or analyze data from a medical device such as blood pressure monitors and glucose monitors. controversies many in the health care industry have raised concerns over the quality and software development process of pms. the development of pms is often criticized as too focused on simply the software development process and not the product. much of these concerns are rooted in safety issues computerized physician order entry, an example of pms, highlights some of these safety concerns. other criticisms are aimed at the regulations in place. some critics argue that regulations stifle innovation and that vendors will no longer have any incentive to create new products. also, existing and future products will have to adhere to strict licensing procedures and this may affect the sustainability of these products. another concern is that the rules are disproportionately strict in comparison to the actual risk associated with a wide variety of ehealth systems and this may prevent companies from initiating the development of new products. canada regulation of patient management software applies to anyone importing, distributing or selling the software. health canada is responsible for regulating the sale, advertising and distribution of patient management software in canada. regulated software is classified based on risk increasing from class i to class ii. the type of license required depends on the classification of the software. an establishment license is required from a vendor or manufacturer of class i pms and a medical device license is required from a vendor or manufacturer of class ii pms. iso 13485 certification is required of manufacturers of class ii medical devices. history in august, 2009, health canada which is responsible for regulating the advertising, manufacturing and sale of medical devices in canada issued a notice confirming that patient management software is a medical device and is subject to the medical devices regulations and the food and drugs act. the development of the regulation of patient management software as a medical device began three years earlier when a company called medmanager created a patient portal technology that was deemed a class ii medical device and subject to regulation by health canada. developments had taken place thereafter, to indicate that medical device classification include patient management software. a notice was officially released by health canada in august, 2009 indicating that patient management software was indeed a medical device. therefore, organizations that import, sell or otherwise distribute class i patient management software must have an establishment license and class ii patient management software must have a medical device licence. in order to obtain a medical device licence, manufacturers must hold a quality management system (qms) certificate issued by an accredited registrar showing that the qms is compliant with iso 13485: 2003 medical devices – quality management systems – requirements for regulatory purposes. organizations are also required to perform certain post-market responsibilities such as maintaining distribution and complaint handling records, mandatory problem reporting and recalls. in december, 2010, a notice was released by health canada further clarifying the definition, classification and licensing requirements of software regulated as a medical device. for example, software used to transmit data from a medical device, or software that analyzes data from a medical device and makes diagnostic or treatment decisions normally made by a physician, would be considered software regulated as a medical device. a product that only stores and displays patient information is not a medical device. examples of software that are not medical devices are middleware, ehr's including those that are custom built for use only within the organization, applications that perform administrative calculations and manipulations (such as determining time between appointments, or workflow management), the wii fit video game, personal bmi calculators and pedometer software used for fitness. the regulations apply to software that is distributed with or without compensation. notes weber-jahnke, j., williams, j. (2010). regulation of patient management software. health law journal. "software regulated as a medical device - frequently asked questions". 6 august 2010. weber-jahnke, j. (2011). a preliminary study of apparent causes and outcomes of reported failures with patient management software. international conference on software engineering. new york: acm. whitney, j. (2011). let's strengthen healthcare software regulation. canadian healthcare technology. morrison, a. implications of iso certification and licensing of patient management software - environmental scan issue 5. ottawa: canadian agency for drugs and technologies in health, 2009 http://itac.ca/uploads/pdf/faq-patient_management_software_licensing_v1.pdf "software regulated as a class i or class ii medical device - health canada notice 2010-12-03". hc-sc.gc.ca. 25 january 2011. retrieved 2013-08-06. this article is issued from wikipedia. the text is licensed under creative commons - attribution - sharealike. additional terms may apply for the media files.