+---------------------------------------------------------------+ | | | Property of the US Government. | | No permission to copy or redistribute this software is given. | | Use of unreleased versions of this software requires the user | | to execute a written test agreement with the VistA Imaging | | Development Office of the Department of Veterans Affairs, | | telephone (301) 734-0100. | | | | The Food and Drug Administration classifies this software as | | a Class II medical device. As such, it may not be changed | | in any way. Modifications to this software may result in an | | adulterated medical device under 21CFR820, the use of which | | is considered to be a violation of US Federal Statutes. | | | +---------------------------------------------------------------+ This file contains an entry for every type of object handled by the VistA Imaging System. It is exported with data. All sites must have entries for the data types distributed in order to display objects sent via multimedia mail. The Object Type file handles objects of various types. These include: * still images * image groups * graphics or waveforms * scanned documents * audio files Other types are expected in the future (i.e., image overlays, motion video chips, and office automation files). An object, such as an image series, may actually consist of multiple objects. In this case, the object type is Group. The Object Group multiple field is used to point to a set of objects in the Image file. Each object type has associated methods (software routines) for performing certain actions. For example, there are methods for displaying images and image abstracts. The group type is used to combine multiple objects of the same or different types to create complex objects. There are different image types, for example: * black and white high-resolution x-rays * black and white ultrasound images (lower resolution) * pseudo-color nuclear medicine scans * medium resolution true color bronchoscopy images * pathology images Each type of object has a number of specific characteristics, including the methods required to display them. For example, each object type has a type name and an associated display method or window. All accesses to objects use the file finder routine ^MAGFILE or ^MAGFILEA to find the network location needed. Different entry points of this routine will find locations of full files, abstract files, and jukebox copies of files. In addition, the network write location will be returned for image captures.
.01name(+)0;1FREE TEXTBEach kind of data supported by the Imaging System has an entry in the Object Type file. The Object Type file manages the kinds of actions which that type of object can have and the routines that are executed for each action.
.02abstract required0;2BOOLEAN1:YES
This field is reserved for future use and will indicates whether a separate abstract file is required for this type of object.
1actions1;0MULTIPLE2005.21This field is reserved for future use will contain the kinds of actions which apply to the object type. Generally, all objects can be displayed as a full image/object and they have an abstract display method. In addition, groups of objects may have other actions such as cineloop display or tiled display.
2edit template2;1FREE TEXTThis field is reserved for future use for the name of the edit template used to enter data pertaining to this type of object.
3parent2;2POINTER2005.02This field is reserved for future use to allow object types to inherit characteristics from a parent object type.
4child class3;0MULTIPLE2005.24This field is reserved for future use to allow object types to inherit characteristics from other object types.
5default extension4;1FREE TEXTADThis is the default extension for this type of object. When Object Type is not known, at time of capture, the extension is used to determine the type.

Referenced by 4 types

  1. IMAGE (2005) -- object type
  2. OBJECT TYPE (2005.02) -- parent
  3. IMAGE FILE TYPES (2005.021) -- default object type
  4. IMAGE AUDIT (2005.1) -- object type