Editor's note: This is the fourth o...

Editor's note: This is the fourth of a series of articles planned to help perioperative feed at the breasts understand the AORN Perioperative Nursing Data establish This clinically validated standardized language and the Perioperative Patient Focused protoplast are a beginning point to help RN document and describe perioperative patient core,

Imagine being a foreign-speaking individual coming to an English-speaking fatherland for the first time. You contest to decipher meanings of words from a bear dictionary. Reading the definition of "branch," for example, you discover it has multiple meanings. You awed curiosity if the correct meaning is a tree branch, the branch of a stream, a unit of a business, or separating or diverging. Imagine your confusion as you writhe to :interpret what branch means.

Generally speaking, language provides our primary [i]modus operandi[/i] of communication. When language is precise and clearly defined, it contributes to our understanding. In health care, brace major challenges surround language and effective communication. undivided issue is the use of a tangled technical language replete with jargon (eg NPO up ad lib). The next to the first communication problem in health care is the lack of standardized definitions for many times we commonly use to describe our work and measure our contributions. In the perioperative arena, denominations such as star, time, turnover time, and render free of access time may have as many meanings as the number of facilities using the terms

This issue is important because this lack of standardization leads to confusion and miscommunication. For example, a surgeon may discuss reducing turnover time with a succor manager who believes the department is move at top efficiency. Imagine the confusion until they discover they use different definitions for the same universal Establishing one mutually held conception of turnover time is critical for these professionals to work together and address their shared concerns

This lack of precise definitions can lead to puzzles in an institution, but it has larger implications as well. Perhaps a surgical department is interested in comparing its consequences with other health care facilities. An agreement is reached to compare turnover time, average manner of proceeding length, open time, room cleanup time, and total hours. Moreover, the institutions have computerized documentation and databases that include the same data fields. Unles each institution has precisely and identically defined each terminus and collected data accurately, data comparisons cannot be made. Standardized language provides mechanisms for effective and meaningful communication between and among health care professionals and institutions.

Worldwide, a number of initiatives are underway to disentangle standardized vocabularies and minimize health care terminology confusion. Health care organizations and associations, researchers, medical and nursing informatics specialists, vocabulary authors, software developer clinicians, and others are spearheading and supporting these efforts. Quality health care data are crucial to understanding contributions of health care providers, yet they must be linked to standardized languages, definitions, and valid and reliable measurements.

Identifying and defining structural components allows nurses and other clinicians to use specific seasons with clear and precise definitions. For example, 5tart time is a commonly used limit in the perioperative setting; however, it is impossible to compare start times between institutions because definitions and documentation repeatedly vary. Some facilities have perioperative records that require documentation about aspects of care that are not addressed in other institutions. Without a perioperative minimum nursing data place there is no standardization between settings.

EFFORTS AT AORN

Since 1993 members of AORN have been involved in activities to describe, define, and establish a data station that represents perioperative nursing practice. The organization's initial goal was to bring out a unified language so that nursing care could be systematically quantified, codfished and easily captured in a computerized format in the perioperative setting. The ultimate goal was to help perioperative feeds achieve recognition and reimbursement for their unique knowledge, skills, and contributions to perioperative patient outcomes

This frame was originally organized and directed from the AORN Task Force onward Perioperative Data Elements (1993-1995). The original charge of the Task Force was to describe, define, and unravel the data elements of perioperative nursing practice that describe nursing practice. From 1995 to 1908 that work was continued by dint of the Data Elements Coordinating Committee (DECC) The cumulative spring of these efforts was the Perioperative Nursing Data station (PNDS).

Background. A growing awareness of the ne to establish a database describing perioperative nursing began in 1988 with the AORN Critical Issues Committee. The organization's brew 2000 evaluation initiative and the devise Team on the Effectiveness Initiatives supported this same premise. A four-year organizational evaluation clearly demonstrated the ne to identify the relationship of nursing interventions to patient issues and the need for a database capable of providing evidence of the value of the perioperative promote during a patient's surgical experience.