Evaluating existing security and privacy requirements for legal compliance.
Saved in:
| Title: | Evaluating existing security and privacy requirements for legal compliance. |
|---|---|
| Authors: | Massey, Aaron K.1 akmassey@ncsu.edu, Otto, Paul N.1,2 paul.otto@law.duke.edu, Hayward, Lauren J.1 ljhaywar@ncsu.edu, Antón, Annie I.1 aianton@ncsu.edu |
| Source: | Requirements Engineering. Mar2010, Vol. 15 Issue 1, p119-137. 19p. 4 Diagrams, 6 Charts. |
| Subjects: | Computer security laws, Computer engineers, Medical records, Right of privacy, Electronic records |
| Abstract: | Governments enact laws and regulations to safeguard the security and privacy of their citizens. In response, requirements engineers must specify compliant system requirements to satisfy applicable legal security and privacy obligations. Specifying legally compliant requirements is challenging because legal texts are complex and ambiguous by nature. In this paper, we discuss our evaluation of the requirements for iTrust, an open-source Electronic Health Records system, for compliance with legal requirements governing security and privacy in the healthcare domain. We begin with an overview of the method we developed, using existing requirements engineering techniques, and then summarize our experiences in applying our method to the iTrust system. We illustrate some of the challenges that practitioners face when specifying requirements for a system that must comply with law and close with a discussion of needed future research focusing on security and privacy requirements. [ABSTRACT FROM AUTHOR] |
| Copyright of Requirements Engineering is the property of Springer Nature and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.) | |
| Database: | Engineering Source |
Be the first to leave a comment!
