This class contains attributes associated with Radiology or Nuclear Medicine imaging examinations. Historically, both diagnostic imaging and the scanning and retrieval of paper documents have been included in the "imaging" domain as they both share certain characteristics in terms of the equipment used to store and retrieve the images. Yet a distinction is often made with respect to the amount and type of metadata associated with the images. For example, "Diagnostic Images" are those stored and retrieved in Picture Archive and Communications Systems (PACS) which require certain codified information regarding the modality of the image, body site, etc., and are organized into Studies, Series, Images, and subsets (regions) of images. In contrast, scanned documents do not require any of these metadata. As patient-generated images become more commonplace, we foresee a need to store these images (for example, a patient uses a smart phone to take a picture of a wound and emails it to a clinician) as well. We would foresee such images stored in the "Medical Imaging Event" hierarchy, even if a relatively-empty Study and Series construct would be required to contain such images. However, scanned documents simply need a pointer to the resulting image(s), and we therefore find it useful to continue with a logical separation of the two kinds of images. Note that this class represents information about the act of performing the medical imaging event, with the majority of the results stored in the Study, Series, Image hierarchy. From a DICOM point of view, the Study and the Imaging Event are roughly synonymous, with the activities surrounding the production of the Study being implied in the resulting data. We make the distinction primarily in order to be consistent with how orders and accessions (aka promises) are treated elsewhere in the FHIM. Therefore this class could easily be merged with the Study class in resulting implementations.