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

Requirements dilemma

This thesis was submitted for the degree of Doctor of Philosophy and awarded by Brunel University.Knowing ‘what’ to build is an integral part of an Information System Development, and it is generally understood that this, which is known as Requirements, is achievable through a process of understanding, communication and management. It is currently maintained by the Requirements theorists that successful system design clarifies the interrelations between information and its representations. However, this belief can be shown to be based on flawed assumptions, as there are persistent reports of failures, indicating that there is a gap between the theory and the practice, and that this gap needs to be bridged. A year long in-depth case study of a project group, starting with their strategy announcement and ending with the commissioning system hand-over meeting, followed the group in their ‘doing’ of the Requirements. These mundane meetings were recorded and transcribed, forming a detailed data set of ‘what-is-done’ and ‘how-it-is-done’. The developed research approach adhesively maintained the practical situation, aiming to investigate and make sense of the here-and-now actions of the scoping and defining processes that were at work. The results of the investigation led the researcher to question previous beliefs and assumptions in Requirements, because of ambiguities that were uncovered, also because there was no sufficiently distinct process found that could assuredly be labelled as Requirements. This phenomenon evoked further questioning of “how strange?”, which triggered the testing of the validity of the Requirements theory. The second stage adapted an analysis framework on decision-making in order to reveal a causal connection between the actions found in the ‘doing’ and in the stocks of knowledge that form the Requirements theory. This phase analysed the operationalization of the theory to examine its commensurate, incommensurate and defective activities. The analysis revealed the existence of other dominant processes that affect the Requirements theory, leaving it underdetermined, with no true causal connections that can be established. This led to the inevitable conclusion that the current Information Systems thinking on Requirements is on the horns of a dilemma without any prospective resolution, because of the elliptical misalignment between the theoretical and the empirical worlds.EPSRC research grant number 00302238 partly funded this wor

Intangible trust requirements - how to fill the requirements trust "gap"?

Previous research efforts have been expended in terms of the capture and subsequent instantiation of "soft" trust requirements that relate to HCI usability concerns or in relation to "hard" tangible security requirements that primarily relate to security a ssurance and security protocols. Little direct focus has been paid to managing intangible trust related requirements per se. This 'gap' is perhaps most evident in the public B2C (Business to Consumer) E- Systems we all use on a daily basis. Some speculative suggestions are made as to how to fill the 'gap'. Visual card sorting is suggested as a suitable evaluative tool; whilst deontic logic trust norms and UML extended notation are the suggested (methodologically invariant) means by which software development teams can perhaps more fully capture hence visualize intangible trust requirements

Airline meteorological requirements

A brief review of airline meteorological/flight planning is presented. The effects of variations in meteorological parameters upon flight and operational costs are reviewed. Flight path planning through the use of meteorological information is briefly discussed