EHR requirements

Published requirements for the EHR are principally available via ISO 18308. They are statements defining the generic features necessary in any Electronic Health Record for it to be communicable and complete, retain integrity across systems, countries and time, and be a useful and effective ethico-legal record of care. Examples of requirements are provided in four themes: -EHR functional requirements; Ethical, legal, and security requirements; Clinical requirements; Technical requirements. The main logical building blocks of an EHR are described using the terminology of CEN TC251 ENV13606. Examples are given of the placement of attributes to satisfy contextual and other requirements at the level of specific building blocks. A worked example of the use of the building blocks is given for the request-report cycle for an imaging investigation

Towards a scope management of non-functional requirements in requirements engineering

Getting business stakeholders’ goals formulated clearly and project scope defined realistically increases the chance of success for any application development process. As a consequence, stakeholders at early project stages acquire as much as possible knowledge about the requirements, their risk estimates and their prioritization. Current industrial practice suggests that in most software projects this scope assessment is performed on the user’s functional requirements (FRs), while the non-functional requirements (NFRs) remain, by and large, ignored. However, the increasing software complexity and competition in the software industry has highlighted the need to consider NFRs as an integral part of software modeling and development. This paper contributes towards harmonizing the need to build the functional behavior of a system with the need to model the associated NFRs while maintaining a scope management for NFRs. The paper presents a systematic and precisely defined model towards an early integration of NFRs within the requirements engineering (RE). Early experiences with the model indicate its ability to facilitate the process of acquiring the knowledge on the priority and risk of NFRs

Against requirements of rationality

Are inferences, theoretical and practical, subject to requirements of rationality? If so, are these of the form 'if … ought …' or 'ought … if …'? If the latter, how are we to understand the 'if'? It seems that, in all cases, we get unintuitive implications (often involving bootstrapping) if 'ought' connotes having reason. It is difficult to formulate such requirements, and obscure what they explain. There might also be a requirement forbidding self-contradiction (not that one's current beliefs can be consciously contradictory). It is a good question whether self-contradiction constitutes, or evidences, irrationality; but talk of a rational requirement causes trouble

General aviation's meteorological requirements

Communication of weather theory and information about weather service products to pilots in an accurate and comprehensible manner is essential to flying safety in general. Probably no one needs weather knowledge more than the people who fly through it. The specific subject of this overview is General Aviation's Meteorological Requirements