Preprint version of paper forthcoming in Journal of Biomedical Informatics The goal of referent tracking is to create an ever-growing pool of data relating to the entities existing in concrete spatiotemporal reality. In the context of Electronic Healthcare Records (EHRs) the relevant concrete entities are not only particular patients but also their parts, diseases, therapies, lesions, and so forth, insofar as these are salient to diagnosis and treatment. Within a referent tracking system, all such entities are referred to directly and explicitly, something which cannot be achieved when familiar concept-based systems are used in what is called “clinical coding”. In this paper we describe the components of a referent tracking system in an informal way and we outline the procedures that would have to be followed by healthcare personnel in using such a system. We argue that the referent tracking paradigm can be introduced with only minor – though nevertheless ontologically important – technical changes to existing EHR infrastructures, but that it will require a radically different mindset on the part of those involved in clinical coding and terminology development from that which has prevailed hitherto.

We describe ELROS, an embedded language for programming distributed applications using remote operations (ISO 9072-1 and 9072-2). The motivation for this work is the development of both large scale scien - tific distributed applications as well as ISO application protocol implementations. We compare our work with other systems, such as ISODE and DAS, that support remote operations programming and point out certain advantages of ELROS. Finally, we suggest ways in which the current implementation of ELROS can be improved. 1. INTRODUCTION Given the ubiquity of networking in modern computing, it is somewhat surprising that there are few distributed applications in production. By distributed application we do not mean networking applications that require constant human involvement, such as the use of file transfer facilities (e.g., FTAM, FTP), virtual terminal services (e.g., VT, TELNET), or electronic mail (e.g., X.400, SMTP). Rather, we mean a set of cooperating, communicating processes ...

Rapid growth of computer network sizes and uses necessitate analysis of network application middleware in terms of its scalability as well as performance. In this paper we analyze a distributed network management middleware based on agents that can be dispatched to locations where they can execute close to the managed nodes. The described middleware operates between the network protocol layer and the application layer and uses standard TCP protocol and SNMP probes to interface the network. By aggregating requests from many users into a single agent, our system allows multiple managers to probe problem areas with minimal management traffic overhead. We discuss and quantify the benefits of the described middleware by implementing real-time network managers using our system.

draft-mealling-rfc3001bis-00.txt This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." To view the entire list of Internet-Draft Shadow Directories, see

EPCglobal Inc ™ is providing this document as a service to interested industries. This document was developed through a consensus process of interested parties. Although efforts have been to assure that the document is correct, reliable, and

EPCglobal Inc ™ is providing this document as a service to interested industries. This document was developed through a consensus process of interested parties. Although efforts have been to assure that the document is correct, reliable, and technically accurate, EPCglobal Inc makes NO WARRANTY,