Home > Articles

This chapter is from the book

This chapter is from the book


[Adelard13]. Adelard. “Claims, Arguments and Evidence (CAE).” http://www.adelard.com/asce/choosing-asce/cae.html, 2013.

[Alexander07]. R. Alexander, T. Kelly, Z. Kurd, and J. Mcdermid. “Safety Cases for Advanced Control Software: Safety Case Patterns.” Technical Report, University of York, 2007.

[Amnell03]. T. Amnell, E. Fersman, L. Mokrushin, P. Pettersson, and W. Yi. “TIMES: A Tool for Schedulability Analysis and Code Generation of Real-Time Systems.” In Formal Modeling and Analysis of Timed Systems. Springer, 2003.

[Arney09]. D. Arney, J. M. Goldman, S. F. Whitehead, and I. Lee. “Synchronizing an X-Ray and Anesthesia Machine Ventilator: A Medical Device Interoperability Case Study.” Biodevices, pages 52–60, January 2009.

[ASTM09]. ASTM F2761-2009. “Medical Devices and Medical Systems—Essential Safety Requirements for Equipment Comprising the Patient-Centric Integrated Clinical Environment (ICE), Part 1: General Requirements and Conceptual Model.” ASTM International, 2009.

[Ayoub13]. A. Ayoub, J. Chang, O. Sokolsky, and I. Lee. “Assessing the Overall Sufficiency of Safety Arguments.” Safety Critical System Symposium (SSS), 2013.

[Ayoub12]. A. Ayoub, B. Kim, I. Lee, and O. Sokolsky. “A Safety Case Pattern for Model-Based Development Approach.” In NASA Formal Methods, pages 223–243. Springer, 2012.

[Ayoub12a]. A. Ayoub, B. Kim, I. Lee, and O. Sokolsky. “A Systematic Approach to Justifying Sufficient Confidence in Software Safety Arguments.” International Conference on Computer Safety, Reliability and Security (SAFECOMP), Magdeburg, Germany, 2012.

[Becker09]. U. Becker. “Model-Based Development of Medical Devices.” Proceedings of the Workshop on Computer Safety, Reliability, and Security (SAFECERT), Lecture Notes in Computer Science, vol. 5775, pages 4–17, 2009.

[Behrmann04]. G. Behrmann, A. David, and K. Larsen. “A Tutorial on UPPAAL.” In Formal Methods for the Design of Real-Time Systems, Lecture Notes in Computer Science, pages 200–237. Springer, 2004.

[Bequette03]. B. Bequette. Process Control: Modeling, Design, and Simulation. Prentice Hall, 2003.

[Bloomfield07]. R. Bloomfield, B. Littlewood, and D. Wright. “Confidence: Its Role in Dependability Cases for Risk Assessment.” 37th Annual IEEE/IFIP International Conference on Dependable Systems and Networks, pages 338–346, 2007.

[Carr03]. C. D. Carr and S. M. Moore. “IHE: A Model for Driving Adoption of Standards.” Computerized Medical Imaging and Graphics, vol. 27, no. 2–3, pages 137–146, 2003.

[Clarke07]. M. Clarke, D. Bogia, K. Hassing, L. Steubesand, T. Chan, and D. Ayyagari. “Developing a Standard for Personal Health Devices Based on 11073.” 29th Annual International Conference of the IEEE Engineering in Medicine and Biology Society, pages 6174–6176, 2007.

[Clifford09]. G. Clifford, W. Long, G. Moody, and P. Szolovits. “Robust Parameter Extraction for Decision Support Using Multimodal Intensive Care Data.” Philosophical Transactions of the Royal Society A: Mathematical, Physical and Engineering Sciences, vol. 367, pages 411–429, 2009.

[Clinical07]. Clinical Alarms Task Force. “Impact of Clinical Alarms on Patient Safety.” Journal of Clinical Engineering, vol. 32, no. 1, pages 22–33, 2007.

[Cobelli09]. C. Cobelli, C. D. Man, G. Sparacino, L. Magni, G. D. Nicolao, and B. P. Kovatchev. “Diabetes: Models, Signals, and Control.” IEEE Reviews in Biomedical Engineering, vol. 2, 2009.

[Commission13]. The Joint Commission. “Medical Device Alarm Safety in Hospitals.” Sentinel Event Alert, no. 50, April 2013.

[Cyra08]. L. Cyra and J. Górski. “Expert Assessment of Arguments: A Method and Its Experimental Evaluation.” International Conference on Computer Safety, Reliability and Security (SAFECOMP), 2008.

[Denney11]. E. Denney, G. Pai, and I. Habli. “Towards Measurement of Confidence in Safety Cases.” International Symposium on Empirical Software Engineering and Measurement (ESEM), Washington, DC, 2011.

[Dias07]. A. C. Dias Neto, R. Subramanyan, M. Vieira, and G. H. Travassos. “A Survey on Model-Based Testing Approaches: A Systematic Review.” Proceedings of the ACM International Workshop on Empirical Assessment of Software Engineering Languages and Technologies, pages 31–36, 2007.

[Dolin06]. R. H. Dolin, L. Alschuler, S. Boyer, C. Beebe, F. M. Behlen, P. V. Biron, and A. Shvo. “HL7 Clinical Document Architecture, Release 2.” Journal of the American Medical Informatics Association, vol. 13, no. 1, pages 30–39, 2006.

[Donchin02]. Y. Donchin and F. J. Seagull. “The Hostile Environment of the Intensive Care Unit.” Current Opinion in Critical Care, vol. 8, pages 316–320, 2002.

[Edworthy06]. J. Edworthy and E. Hellier. “Alarms and Human Behaviour: Implications for Medical Alarms.” British Journal of Anaesthesia, vol. 97, pages 12–17, 2006.

[EBMWG92]. Evidence-Based Medicine Working Group. “Evidence-Based Medicine: A New Approach to Teaching the Practice of Medicine.” Journal of the American Medical Association, vol. 268, pages 2420–2425, 1992.

[FDA10]. U.S. Food and Drug Administration, Center for Devices and Radiological Health. “Infusion Pumps Total Product Life Cycle: Guidance for Industry and FDA Staff.” Premarket Notification [510(k)] Submissions, April 2010.

[FDA10a]. U.S. Food and Drug Administration, Center for Devices and Radiological Health. “Infusion Pump Improvement Initiative.” White Paper, April 2010.

[Garg05]. A. X. Garg, N. K. J. Adhikari, H. McDonald, M. P. Rosas-Arellano, P. J. Devereaux, J. Beyene, J. Sam, and R. B. Haynes. “Effects of Computerized Clinical Decision Support Systems on Practitioner Performance and Patient Outcomes: A Systematic Review.” Journal of the American Medical Association, vol. 293, pages 1223–1238, 2005.

[Ginsberg09]. B. H. Ginsberg. “Factors Affecting Blood Glucose Monitoring: Sources of Errors in Measurement.” Journal of Diabetes Science and Technology, vol. 3, no. 4, pages 903–913, 2009.

[Goldman05]. J. Goldman, R. Schrenker, J. Jackson, and S. Whitehead. “Plug-and-Play in the Operating Room of the Future.” Biomedical Instrumentation and Technology, vol. 39, no. 3, pages 194–199, 2005.

[Goodenough12]. J. Goodenough, C. Weinstock, and A. Klein. “Toward a Theory of Assurance Case Confidence.” Technical Report CMU/SEI-2012-TR-002, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 2012.

[Harris13]. Harris Healthcare (formerly careFX). www.harris.com.

[Hatcliff12]. J. Hatcliff, A. King, I. Lee, A. Macdonald, A. Fernando, M. Robkin, E. Vasserman, S. Weininger, and J. M. Goldman. “Rationale and Architecture Principles for Medical Application Platforms.” Proceedings of the IEEE/ACM 3rd International Conference on Cyber-Physical Systems (ICCPS), pages 3–12, Washington, DC, 2012.

[Hawkins09]. R. Hawkins and T. Kelly. “A Systematic Approach for Developing Software Safety Arguments.” Journal of System Safety, vol. 46, pages 25–33, 2009.

[Hawkins09a]. R. Hawkins and T. Kelly. “Software Safety Assurance: What Is Sufficient?” 4th IET International Conference of System Safety, 2009.

[Hawkins11]. R. Hawkins, T. Kelly, J. Knight, and P. Graydon. “A New Approach to Creating Clear Safety Arguments.” In Advances in Systems Safety, pages 3–23. Springer, 2011.

[Henzinger07]. T. A. Henzinger and C. M. Kirsch. “The Embedded Machine: Predictable, Portable Real-Time Code.” ACM Transactions on Programming Languages and Systems (TOPLAS), vol. 29, no. 6, page 33, 2007.

[Hovorka04]. R. Hovorka, V. Canonico, L. J. Chassin, U. Haueter, M. Massi-Benedetti, M. O. Federici, T. R. Pieber, H. C. Schaller, L. Schaupp, T. Vering, and M. E. Wilinska. “Nonlinear Model Predictive Control of Glucose Concentration in Subjects with Type 1 Diabetes.” Physiological Measurement, vol. 25, no. 4, page 905, 2004.

[Imhoff06]. M. Imhoff and S. Kuhls. “Alarm Algorithms in Critical Care Monitoring.” Anesthesia and Analgesia, vol. 102, no. 5, pages 1525–1536, 2006.

[Imhoff09]. M. Imhoff, S. Kuhls, U. Gather, and R. Fried. “Smart Alarms from Medical Devices in the OR and ICU.” Best Practice and Research in Clinical Anaesthesiology, vol. 23, no. 1, pages 39–50, 2009.

[Isaksen97]. U. Isaksen, J. P. Bowen, and N. Nissanke. “System and Software Safety in Critical Systems.” Technical Report RUCS/97/TR/062/A, University of Reading, UK, 1997.

[ISO/IEEE11073]. ISO/IEEE 11073 Committee. “Health Informatics—Point-of-Care Medical Device Communication Part 10103: Nomenclature—Implantable Device, Cardiac.” http://standards.ieee.org/findstds/standard/11073-10103-2012.html.

[Jackson07]. D. Jackson, M. Thomas, and L. I. Millett, editors. Software for Dependable Systems: Sufficient Evidence? Committee on Certifiably Dependable Software Systems, National Research Council. National Academies Press, May 2007.

[Jee10]. E. Jee, I. Lee, and O. Sokolsky. “Assurance Cases in Model-Driven Development of the Pacemaker Software.” 4th International Conference on Leveraging Applications of Formal Methods, Verification, and Validation, Volume 6416, Part II, ISoLA’10, pages 343–356. Springer-Verlag, 2010.

[Jeroeno4]. J. Levert and J. C. H. Hoorntje. “Runaway Pacemaker Due to Software-Based Programming Error.” Pacing and Clinical Electrophysiology, vol. 27, no. 12, pages 1689–1690, December 2004.

[Kelly98]. T. Kelly. “Arguing Safety: A Systematic Approach to Managing Safety Cases.” PhD thesis, Department of Computer Science, University of York, 1998.

[Kelly98a]. T. Kelly. “A Six-Step Method for Developing Arguments in the Goal Structuring Notation (GSN).” Technical Report, York Software Engineering, UK, 1998.

[Kelly07]. T. Kelly. “Reviewing Assurance Arguments: A Step-by-Step Approach.” Workshop on Assurance Cases for Security: The Metrics Challenge, Dependable Systems and Networks (DSN), 2007.

[Kelly97]. T. Kelly and J. McDermid. “Safety Case Construction and Reuse Using Patterns.” International Conference on Computer Safety, Reliability and Security (SAFECOMP), pages 55–96. Springer-Verlag, 1997.

[Kelly04]. T. Kelly and R. Weaver. “The Goal Structuring Notation: A Safety Argument Notation.” DSN 2004 Workshop on Assurance Cases, 2004.

[Kim11]. B. Kim, A. Ayoub, O. Sokolsky, P. Jones, Y. Zhang, R. Jetley, and I. Lee. “Safety-Assured Development of the GPCA Infusion Pump Software.” Embedded Software (EMSOFT), pages 155–164, Taipei, Taiwan, 2011.

[Kim12]. B. G. Kim, L. T. Phan, I. Lee, and O. Sokolsky. “A Model-Based I/O Interface Synthesis Framework for the Cross-Platform Software Modeling.” 23rd IEEE International Symposium on Rapid System Prototyping (RSP), pages 16–22, 2012.

[King09]. A. King, S. Procter, D. Andresen, J. Hatcliff, S. Warren, W. Spees, R. Jetley, P. Jones, and S. Weininger. “An Open Test Bed for Medical Device Integration and Coordination.” Proceedings of the 31st International Conference on Software Engineering, 2009.

[Kovatchev09]. B. P. Kovatchev, M. Breton, C. D. Man, and C. Cobelli. “In Silico Preclinical Trials: A Proof of Concept in Closed-Loop Control of Type 1 Diabetes.” Diabetes Technology Society, vol. 3, no. 1, pages 44–55, 2009.

[Lee06]. I. Lee, G. J. Pappas, R. Cleaveland, J. Hatcliff, B. H. Krogh, P. Lee, H. Rubin, and L. Sha. “High-Confidence Medical Device Software and Systems.” Computer, vol. 39, no. 4, pages 33–38, April 2006.

[Lee12]. I. Lee, O. Sokolsky, S. Chen, J. Hatcliff, E. Jee, B. Kim, A. King, M. Mullen-Fortino, S. Park, A. Roederer, and K. Venkatasubramanian. “Challenges and Research Directions in Medical Cyber-Physical Systems.” Proceedings of the IEEE, vol. 100, no. 1, pages 75–90, January 2012.

[Lofsky04]. A. S. Lofsky. “Turn Your Alarms On.” APSF Newsletter, vol. 19, no. 4, page 43, 2004.

[Lublinerman09]. R. Lublinerman, C. Szegedy, and S. Tripakis. “Modular Code Generation from Synchronous Block Diagrams: Modularity vs. Code Size.” Proceedings of the 36th Annual ACM SIGPLAN-SIGACT Symposium on Principles of Programming Languages (POPL 2009), pages 78–89, New York, NY, 2009.

[Lynn11]. L. A. Lynn and J. P. Curry. “Patterns of Unexpected In-Hospital Deaths: A Root Cause Analysis.” Patient Safety in Surgery, vol. 5, 2011.

[Maddox08]. R. Maddox, H. Oglesby, C. Williams, M. Fields, and S. Danello. “Continuous Respiratory Monitoring and a ‘Smart’ Infusion System Improve Safety of Patient-Controlled Analgesia in the Postoperative Period.” In K. Henriksen, J. Battles, M. Keyes, and M. Grady, editors, Advances in Patient Safety: New Directions and Alternative Approaches, Volume 4 of Advances in Patient Safety, Agency for Healthcare Research and Quality, August 2008.

[Masci13]. P. Masci, A. Ayoub, P. Curzon, I. Lee, O. Sokolsky, and H. Thimbleby. “Model-Based Development of the Generic PCA Infusion Pump User Interface Prototype in PVS.” Proceedings of the 32nd International Conference on Computer Safety, Reliability and Security (SAFECOMP), 2013.

[Mazoit07]. J. X. Mazoit, K. Butscher, and K. Samii. “Morphine in Postoperative Patients: Pharmacokinetics and Pharmacodynamics of Metabolites.” Anesthesia and Analgesia, vol. 105, no. 1, pages 70–78, 2007.

[McMaster13]. Software Quality Research Laboratory, McMaster University. Pacemaker Formal Methods Challenge. http://sqrl.mcmaster.ca/pacemaker.htm.

[MDCF]. Medical Device Coordination Framework (MDCF). http://mdcf.santos.cis.ksu.edu.

[MDPNP]. MD PnP: Medical Device “Plug-and-Play” Interoperability Program. http://www.mdpnp.org.

[Menon09]. C. Menon, R. Hawkins, and J. McDermid. Defence “Standard 00-56 Issue 4: Towards Evidence-Based Safety Standards.” In Safety-Critical Systems: Problems, Process and Practice, pages 223–243. Springer, 2009.

[Nuckols08]. T. K. Nuckols, A. G. Bower, S. M. Paddock, L. H. Hilborne, P. Wallace, J. M. Rothschild, A. Griffin, R. J. Fairbanks, B. Carlson, R. J. Panzer, and R. H. Brook. “Programmable Infusion Pumps in ICUs: An Analysis of Corresponding Adverse Drug Events.” Journal of General Internal Medicine, vol. 23 (Supplement 1), pages 41–45, January 2008.

[Oberli99]. C. Oberli, C. Saez, A. Cipriano, G. Lema, and C. Sacco. “An Expert System for Monitor Alarm Integration.” Journal of Clinical Monitoring and Computing, vol. 15, pages 29–35, 1999.

[Pajic12]. M. Pajic, R. Mangharam, O. Sokolsky, D. Arney, J. Goldman, and I. Lee. “Model-Driven Safety Analysis of Closed-Loop Medical Systems.” IEEE Transactions on Industrial Informatics, PP(99):1–1, 2012.

[Phillips10]. Phillips eICU Program. http://www.usa.philips.com/healthcare/solutions/patient-monitoring.

[Rae03]. A. Rae, P. Ramanan, D. Jackson, J. Flanz, and D. Leyman. “Critical Feature Analysis of a Radiotherapy Machine.” International Conference of Computer Safety, Reliability and Security (SAFECOMP), September 2003.

[Sapirstein09]. A. Sapirstein, N. Lone, A. Latif, J. Fackler, and P. J. Pronovost. “Tele ICU: Paradox or Panacea?” Best Practice and Research Clinical Anaesthesiology, vol. 23, no. 1, pages 115–126, March 2009.

[Sentz02]. K. Sentz and S. Ferson. “Combination of Evidence in Dempster-Shafer Theory.” Technical report, Sandia National Laboratories, SAND 2002-0835, 2002.

[Shortliffe79]. E. H. Shortliffe, B. G. Buchanan, and E. A. Feigenbaum. “Knowledge Engineering for Medical Decision Making: A Review of Computer-Based Clinical Decision Aids.” Proceedings of the IEEE, vol. 67, pages 1207–1224, 1979.

[Simone13]. L. K. Simone. “Software Related Recalls: An Analysis of Records.” Biomedical Instrumentation and Technology, 2013.

[UPenn]. The Generic Patient Controlled Analgesia Pump Model. http://rtg.cis.upenn.edu/gip.php3.

[UPenn-a]. Safety Requirements for the Generic Patient Controlled Analgesia Pump. http://rtg.cis.upenn.edu/gip.php3.

[UPenn-b]. The Generic Patient Controlled Analgesia Pump Hazard Analysis. http://rtg.cis.upenn.edu/gip.php3.

[Wagner10]. S. Wagner, B. Schatz, S. Puchner, and P. Kock. “A Case Study on Safety Cases in the Automotive Domain: Modules, Patterns, and Models.” International Symposium on Software Reliability Engineering, pages 269–278, 2010.

[Weaver03]. R. Weaver. “The Safety of Software: Constructing and Assuring Arguments.” PhD thesis, Department of Computer Science, University of York, 2003.

[Weinstock09]. C. Weinstock and J. Goodenough. “Towards an Assurance Case Practice for Medical Devices.” Technical Report, CMU/SEI-2009-TN-018, 2009.

[Ye05]. F. Ye and T. Kelly. “Contract-Based Justification for COTS Component within Safety-Critical Applications.” PhD thesis, Department of Computer Science, University of York, 2005.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020