Skip to main content
Log in

Expert identification and selection: Legal liability concerns and directions

  • Published:
AI & SOCIETY Aims and scope Submit manuscript

Abstract

Legal liabilities pertaining to the identification and selection of domain experts is an issue that could adversely impact expert systems developers. Problems pertaining to flawed knowledge, improperly defined expertise, and behavioural and psychological impediments are just some of the issues. This paper examines the torts of strict products liability and negligence that system developers could incur as a result of expert-related difficulties. Parallels from legal scholars and federal and state court decisions are discussed relevant to expert system projects and developers. The paper concludes with a presentation of steps that systems developers can take to minimize potential legal liability.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  • Birnbaum, N. (1988) Strict Products Liability and Computer Software.Computer/Law Journal,8, 135–156.

    Google Scholar 

  • Bjorn-Anderson, N. (1988) Are ‘Human Factors’ Human?The Computer Journal,31, 386–390.

    Google Scholar 

  • Black, H.C. (1979).Black's Law Dictionary. West Publishing, St Paul, MN.

    Google Scholar 

  • Bloombecker, R. (1989). Malpractice in IS?Datamation,35, 85–86.

    Google Scholar 

  • Bost v. Riley. (1980). 44 NC App 638, 262 SE2d 391.

  • Brannigan, V. and Dayhoff, R. (1981) Liability for Personal Injuries Caused by Defective Medical Computer Programs.American Journal of Law & Medicine,7, 123–144.

    Google Scholar 

  • Brown R. and McCombs, D. (April 1991). Legal Aspects of Artificial Intelligence.Research Report, Haynes and Boone, Dallas, TX.

    Google Scholar 

  • Cole, G.S. (1990). Tort Liability for Artificial Intelligence and Expert Systems,Computer/Law Journal,X, 127–231.

    Google Scholar 

  • Connolly, T. (1980). Uncertainty, Action and Competence: Some Alternatives to Omniscience in Complex Problem-Solving. In Fiddle (ed)Uncertainty: Social and Behavioral Dimensions, Praeger, New York, 69–91.

    Google Scholar 

  • Constantine, M. and Ulvila, J. (1990). Testing Knowledge-Based Systems: The State of the Practice and Suggestions for Improvement,Expert Systems With Applications,1, 237–248.

    Google Scholar 

  • Fridena v. Evans. (1980). 127 Ariz 516, 622 P2d 463.

  • Germignani, M. (1981). Product Liability and Software.Rutgers Computer & Technology Law Journal,8, 173–204.

    Google Scholar 

  • Glavin v. Rhode Island Hospital. (1879). 12 RI 411.

  • Hagendorf, W. (1990). Bulls and Bears and Bugs: Computer Investment Advisory Programs That Go Awry.Computer/Law Journal,X, 47–69.

    Google Scholar 

  • Halstead v. United States. (1982), 535 F. Supp. 782 (Conn. 1982).

  • Independent School District No. 454 v. Statistical Tabulating Corp. (1973), 359 F. Supp. 1095 (N.D. Ill. 1973).

  • Jacob, V., Gaultney, L. and Salvendy, G. (1986). Strategies and Biases in Human Decision-Making and Their Implications for Expert Systems.Behaviour and Information Technology,5, 119–140.

    Google Scholar 

  • Jennings, M. (1991).Business and the Legal Environment. PWS-Kent, Boston MA.

    Google Scholar 

  • Joiner v. Mitchell County Hospital Authority. (1971). 125 GA App 1, 186 SE2d 307.

  • Kociemba v. Searle (1989). 707 F. Supp. 1517 (D. Minn. 1989).

  • Lathrop, B. (1990) Design-Induced Errors in Computer Systems.Computer/Law Journal,X, 87–126.

    Google Scholar 

  • Madden, M. (1988). The Duty to Warn in Product Liability: Contours and Criticism.Journal of Products Liability,11, 103–179.

    Google Scholar 

  • Martin, J. and Oxman, S. (1988).Building Expert Systems. Prentice-Hall, Englewood Cliffs, N.J.

    Google Scholar 

  • Massingale, C.S. and Borthick, A.F. (1988) Risk Allocation for Injury Due to Defective Medical Software.Journal of Products Liability,II, 181–198.

    Google Scholar 

  • Mykytyn, K., Mykytyn, P., and Slinkman, C. (1990). Expert Systems: A Question of Liability?MIS Quarterly,14, 27–42.

    Google Scholar 

  • Nycum, S. (1979). Liability for Malfunction of a Computer Program.Rutgers Journal of Computers, Technology and the Law,7, 1–22.

    Google Scholar 

  • O'Keefe, R., Balci, O., and Smith E. (1987). Validating Expert System Performance.IEEE Expert,2, 81–89.

    Google Scholar 

  • Prietula, M. and H. Simon. (1989). The Experts in Your Midst.Harvard Business Review,67, 120–124.

    Google Scholar 

  • Restatement (Second) of Torts. (1965). American Law Institute, St. Paul, MN.

  • Restatement (Second) of Torts. (1977). American Law Institute, St Paul, MN.

  • Roach v. Kononen. (1974). 264 Or. 457, 525 P. 2d 125.

  • Roszkowski, M. (1992)Business Law, 3rd Edition, Harper Collins, New York.

    Google Scholar 

  • Saloomey v. Jeppesen & Co. (1983). 707F.2d 671 (2d. Cir. 1983).

  • Thomas, B.T. (Fall 1979). Unauthorized Practice and Computer Aided Legal Analysis Systems.Jurimetrics Journal,20 (1), 41–51.

    Google Scholar 

  • Tyde, J. (1990). Medical Computer software: RX for Deadly Errors.Software Law Journal,IV, 117–145.

    Google Scholar 

  • Warner, E. (1990). Expert Systems and the Law. In Boynton and Zmud (eds)Management Information Systems, Scott Foresman/Little Brown Higher Education, Glenview, IL, 144–149.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Mykytyn, K., Mykytyn, P.P. & Lunce, S. Expert identification and selection: Legal liability concerns and directions. AI & Soc 7, 225–237 (1993). https://doi.org/10.1007/BF01901818

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1007/BF01901818

Key words

Navigation