Significance and Use
5.1 RADT Object Model as a Basis for Communication—The RADT object model is the first model used to create a common library of consistent entities (objects) and their attributes in the terminology of object analytical models as applied to the healthcare domain. These object models can be used to construct and refine standards relating to healt care information and its management. Since the RADT object model underpins the design and implementation of specific systems, it provides the framework for establishing the systematics of managing observations made during health care. The observations recorded during health care not only become the basis for managing an individual's health care by practitioners but are also used for research and resource management. They define the common language for abstracting and codifying observations. The inconsistency and incompleteness of the data recorded in paper records is well known and has been noted by the Institute of Medicine's study (4). The ability to build the recommended EHR begins with RADT, as noted in Practice E1239. A more detailed specification of the RADT process and its specific functional domain shall begin with a formal model. Furthermore, following agreement on the initial model, that model shall evolve as knowledge accumulates and the initial view of the healthcare domain extends to other social and psychologic processes that link healthcare with other functional domains of society. The management of lifelong cases of care, such as those of birth defects in newborns, will involve interactions with social work and educational functional domains of experience. It has been recognized for some time (5) that a “healthcare team,” in the broader sense, is involved in dealing with these complex cases. The RADT model is the core to linking these functional domains together in a transparent way. For that reason, the object terminology is used to enable the most global view and vernacular that will facilitate communication among technical specialties that participate in managing some aspect of health care or that build systems to manage the required information.
5.2 Common Terminology as a Basis for Education—The use of models and their associated terminology implies that education of the healthcare practitioners shall incorporate this view to a significant extent. While a detailed specification of systems requires extensive lexicons of carefully defined terms, a more understandable terminology shall evolve for the process of educating practitioners during their formal education as well as continuing to educate current practioners concerning how this new technology can be integrated with their existing practices. This challenge has yet to be met, but the objects and modeling concepts presented here are intended to be named with the most intuitive titles in order to promote clear understanding during their use in instruction. Nevertheless, relating these objects and their properties to everyday practice remains a significant challenge, for both the implementors of systems and educators. The perspectives cataloged here can be used in the creation of system documentation and curricula represented in a variety of media.
Scope
1.1 This practice is intended to amplify Practice E1239 and to complement Practice E1384 by detailing the objects that make up the reservation, registration, admitting, discharge, and transfer (RADT) functional domain of the computer-based record of care (CPR). As identified in Practice E1239, this domain is seminal to all patient record and ancillary system functions, including messaging functions used in telecommunications. For example, it is applicable to clinical laboratory information management systems, pharmacy information management systems, and radiology, or other image management, information management systems. The object model terminology is used to be compatible with other national and international standards for healthcare data and information systems engineering or telecommunications standards applied to healthcare data or systems. This practice is intended for those familiar with modeling concepts, system design, and implementation. It is not intended for the general computer user or as an initial introduction to the concepts.
