CCOW

Last updated

In the context of health informatics, CCOW (pr /seacow/) or Clinical Context Object Workgroup is a Health Level Seven International standard protocol designed to enable disparate applications to synchronize in real time, and at the user-interface level. It is vendor independent and allows applications to present information at the desktop and portal level in a unified way.

Contents

CCOW is the primary standard protocol in healthcare to facilitate a process called "context management". Context management is the process of using particular "subjects" of interest (e.g., user, patient, clinical encounter, charge item, etc.) to virtually link disparate applications so that the end-user sees them operate in a unified, cohesive way.

Context management can be utilized for both CCOW and non-CCOW compliant applications. The CCOW standard exists to facilitate a more robust, and near "plug-and-play" interoperability across disparate applications.

Context management is often combined with single sign-on applications in the healthcare environment, but the two are discrete functions. Single sign-on is the process that enables the secure access of disparate applications by a user through use of a single authenticated identifier and password. Context management augments this by then enabling the user to identify subjects once (e.g., a patient) and have all disparate systems into which the user is granted access to "tune" to this patient simultaneously. As the user further identifies particular "subjects" of interest (e.g., a particular visit), those applications containing information about the selected subject will then automatically and seamlessly to the user "tune" to that information as well. The end result for the user is an aggregated view of all patient information across disparate applications.

Use of context management, facilitated by CCOW or non-CCOW compliant applications, is valuable for both client-server, and web-based applications. Furthermore, a fully robust context manager will enable use for both client-server and web-based applications on a single desktop / kiosk, allowing the user to utilize both types of applications in a "context aware" session.

Purpose

The goal of CCOW is seemingly simple, but its implementation is rather complex. CCOW is designed to communicate the name of the active user between various programs on the same machine. The user should only need to log into one application, and the other applications running on the machine will "know" who is logged in. There are a great deal of exceptions and circumstances that make this scenario far more difficult than it appears.

In order to accomplish this task, every CCOW compliant application on the machine must log into a central CCOW server called a Vault. The application sends an encrypted application passcode to verify its identity. Once the application is verified, it may change the active user (also called the "context") on the machine. Each CCOW application also has an application "name" for which there can only be one instance. There is no correct application name (the passcode identifies which application is logging in). There may be multiple instances of the CCOW application connected to the CCOW vault from the same computer. However, they must have different names. One name might be "I like HHAM", while the other might be "I like CCOW". The names are completely arbitrary.

After the application authenticates itself with the CCOW vault, the applications are ready to communicate the context (a.k.a. the active user). Here would be a step-by-step example of a CCOW exchange:

  1. The computer boots up and the medical applications load.
  2. Each application logs into CCOW using its secret passcode (and unique application name).
  3. The compliant application displays a login prompt, and the user logs in as "Mary Jane".
  4. Mary Jane has a "CCOW ID". Let us assume that her CCOW ID is "MJane".
  5. The compliant application notifies the CCOW vault that "MJane" is now logged in.
  6. Once CCOW verifies that "MJane" is a valid CCOW user, the vault notifies all the other applications that "MJane" is logged in.
  7. All of the other applications realize that the CCOW ID "MJane" is referring to "Mary Jane" (because they have been configured as such). They log in "Mary Jane" automatically.
  8. The transaction is complete. All of the applications running on the machine have been automatically logged in as "Mary Jane".

The purpose of the application passcode is to verify that no unauthorized applications can "hack" into CCOW and change the active user (thereby allowing unauthorized access to medical records).

Status

See also

Related Research Articles

Digital Imaging and Communications in Medicine (DICOM) is a technical standard for the digital storage and transmission of medical images and related information. It includes a file format definition, which specifies the structure of a DICOM file, as well as a network communication protocol that uses TCP/IP to communicate between systems. The primary purpose of the standard is to facilitate communication between the software and hardware entities involved in medical imaging, especially those that are created by different manufacturers. Entities that utilize DICOM files include components of picture archiving and communication systems (PACS), such as imaging machines (modalities), radiological information systems (RIS), scanners, printers, computing servers, and networking hardware.

Health Level Seven or HL7 is a range of global standards for the transfer of clinical and administrative health data between applications. The HL7 standards focus on the application layer, which is "layer 7" in the Open Systems Interconnection model. The standards are produced by Health Level Seven International, an international standards organization, and are adopted by other standards issuing bodies such as American National Standards Institute and International Organization for Standardization. There are a range of primary standards that are commonly used across the industry, as well as secondary standards which are less frequently adopted.

<span class="mw-page-title-main">Electronic health record</span> Digital collection of patient and population electronically stored health information

An electronic health record (EHR) is the systematized collection of patient and population electronically stored health information in a digital format. These records can be shared across different health care settings. Records are shared through network-connected, enterprise-wide information systems or other information networks and exchanges. EHRs may include a range of data, including demographics, medical history, medication and allergies, immunization status, laboratory test results, radiology images, vital signs, personal statistics like age and weight, and billing information.

Continuity of Care Record (CCR) is a health record standard specification developed jointly by ASTM International, the Massachusetts Medical Society (MMS), the Healthcare Information and Management Systems Society (HIMSS), the American Academy of Family Physicians (AAFP), the American Academy of Pediatrics (AAP), and other health informatics vendors.

Logical Observation Identifiers Names and Codes (LOINC) is a database and universal standard for identifying medical laboratory observations. First developed in 1994, it was created and is maintained by the Regenstrief Institute, a US nonprofit medical research organization. LOINC was created in response to the demand for an electronic clinical care and management database and is publicly available at no cost.

Context management is a dynamic computer process that uses 'subjects' of data in one application, to point to data resident in a separate application also containing the same subject.

The HL7 Clinical Document Architecture (CDA) is an XML-based markup standard intended to specify the encoding, structure and semantics of clinical documents for exchange. In November 2000, HL7 published Release 1.0. The organization published Release 2.0 with its "2005 Normative Edition".

Health information management (HIM) is information management applied to health and health care. It is the practice of analyzing and protecting digital and traditional medical information vital to providing quality patient care. With the widespread computerization of health records, traditional (paper-based) records are being replaced with electronic health records (EHRs). The tools of health informatics and health information technology are continually improving to bring greater efficiency to information management in the health care sector.

The ISO/TC 215 is the International Organization for Standardization's (ISO) Technical Committee (TC) on health informatics. TC 215 works on the standardization of Health Information and Communications Technology (ICT), to allow for compatibility and interoperability between independent systems.

VistAWeb is a portal accessible through CPRS, the graphical user interface for the Veterans Health Information Systems and Technology Architecture (VistA), the electronic health record used throughout the United States Department of Veterans Affairs (VA) medical system.

ClearHealth is an open-source practice management (PM) and electronic medical records (EMR/EHR/PHR) system available under the GNU General Public License.

The Continuity of Care Document (CCD) specification is an XML-based markup standard intended to specify the encoding, structure, and semantics of a patient summary clinical document for exchange.

Health informatics in China is about the Health informatics or Medical informatics or Healthcare information system/technology in China.

This article documents the effort of the Health Level Seven(HL7) community and specifically the former HL7 Architecture Board (ArB) to develop an interoperability framework that would support services, messages, and Clinical Document Architecture(CDA) ISO 10871.

International HL7 implementations is a collection of known implementations of the HL7 Interoperability standard. These do not necessarily refer to cross-border health information systems.

The Fast Healthcare Interoperability Resources standard is a set of rules and specifications for exchanging electronic health care data. It is designed to be flexible and adaptable, so that it can be used in a wide range of settings and with different health care information systems. The goal of FHIR is to enable the seamless and secure exchange of health care information, so that patients can receive the best possible care. The standard describes data formats and elements and an application programming interface (API) for exchanging electronic health records (EHR). The standard was created by the Health Level Seven International (HL7) health-care standards organization.

Medical device connectivity is the establishment and maintenance of a connection through which data is transferred between a medical device, such as a patient monitor, and an information system. The term is used interchangeably with biomedical device connectivity or biomedical device integration. By eliminating the need for manual data entry, potential benefits include faster and more frequent data updates, diminished human error, and improved workflow efficiency.

Health Level Seven International (HL7) is a non-profit ANSI-accredited standards development organization that develops standards that provide for global health data interoperability.

Clinical data standards are used to store and communicate information related to healthcare so that its meaning is unambiguous. They are used in clinical practice, in activity analysis and finding, and in research and development.

References

  1. ↑ "Infrastructure and Messaging | HL7 International".
  2. ↑ "HL7 Standards Product Brief - HL7 Context Management Specification (CCOW), Version 1.6 | HL7 International".
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.