| # of Frames (Frame Count) | - Indicates the total number of image frames available within the OmegaAI image viewer for a selected image or series.
- The frame count is fetched directly from the image data loaded into the OmegaAI viewer and reflects the frames rendered from the underlying DICOM instance(s).
- Focuses on how many visual frames the user can navigate in the viewer.
- This value represents how many individual frames can be scrolled through or played sequentially in the viewer (for example, axial slices or multi-frame images).
- If a study does not contain multi-frame or stack-based image data, this field may appear blank.
|
| # of Images (Image Count) | - Indicates the total number of distinct images contained within a study.
- This count is derived from the DICOM images associated with the study, regardless of how many frames each image contains.
- Focuses on how many image objects make up the study, not how they are displayed in the viewer.
- Each image typically corresponds to a DICOM image object or instance.
|
| # of Instances (Instance Count) | - Refers to the total number of DICOM instances (objects) associated with a study.
- This count is derived directly from the study's DICOM dataset at the storage/object level.
- Focuses on how many DICOM objects exist for the study.
- Each instance is a stored DICOM object, which may be single-frame or multi-frame.
|
| Anatomic Focus (Target Anatomy) | - Indicates the specific anatomical structure or organ system examined in the study.
- Fetched from the study metadata provided by the originating order or imaging system (RIS/PACS).
- Used to provide clinical context and support study filtering, categorization, and review.
- Identifies a specific organ or targeted anatomical region (for example, Abdomen Wall, Brain, Liver, Pancreas, Aorta, or Knee).
|
| Availability | - Represents the availability status of the study or associated resources.
- Derived from system workflow states and object availability.
- Used to determine whether the study is ready for viewing or further processing.
|
| Body Part | - Identifies the general body region examined or intended to be examined as part of a study (for example, Chest, Abdomen, Eye).
- Fetched from the study order or procedure metadata, based on the body part selected during order entry or protocol configuration.
- Applicable across different stages of a study lifecycle.
|
| Imaging Modality | - The imaging technique or equipment used to perform the study.
- Captured from the procedure or modality information associated with the study.
- Represents modalities such as CT, MR, CR, AR, BI, or other configured modality types.
- Used to categorize and filter studies by imaging type.
- Supports workflow routing, modality-based worklists, and reporting.
|
| Laterality | - Specifies the side of the body to which the study or anatomical focus applies.
- Derived from study-level metadata.
- Used to ensure correct interpretation, reporting, and clinical context.
- Common values include bilateral, unilateral left, unilateral right, or unpaired.
|
| Modality | - Specifies the imaging modality used to perform the study (for example, CT, MR, US, DX).
- Values are sourced from the study modality field, typically populated via order entry, modality worklist (MWL), or DICOM metadata.
- Used to narrow worklists, optimize reading workflows, and segment studies based on imaging technology.
- Supports multi-select filtering to allow users to view studies performed using one or more modality types.
|
| Modality Modifier Array | - Represents modifiers applied to the modality or procedure.
- Captured from order configuration or modality data.
- Used to refine procedure classification and billing.
|
| Pharmaceutical Dosage | - The amount of a pharmaceutical agent administered to the patient during the imaging procedure.
- Captured from the modality, technologist input, or integrated clinical systems at the time of administration.
- Used for audit trails, reporting, quality control, and review of contrast or medication usage across studies.
- Typically recorded with appropriate units (for example, mg, mL), based on the agent used.
- Supports clinical accuracy, patient safety, and regulatory documentation requirements.
|
| Pharmaceutical Name | - The name of the pharmaceutical agent administered during the imaging procedure.
- Captured from modality data, technologist entry, or integrated clinical systems at the time of administration.
- Used for reporting, audits, and analysis of pharmaceutical usage across studies.
- Identifies contrast agents, radiopharmaceuticals, medications, or other clinically relevant substances used in the study.
- Supports clinical documentation, traceability, and patient safety.
|
| Pharmaceutical Type | - The category or classification of the pharmaceutical agent used during the imaging procedure.
- Captured from technologist input, modality records, or integrated clinical systems when the agent is selected or administered.
- Used for filtering, reporting, compliance, and clinical review purposes.
- Indicates the nature of the agent, such as contrast media, radiopharmaceutical, medication, or another procedural agent.
- Helps standardize documentation and distinguish between different classes of administered substances.
|
| Source Device AE Title | Two descriptions for this field appear on the live page:- Longer version:
- The Application Entity (AE) Title identifying the source or destination DICOM device associated with the study.
- Captured automatically from the DICOM metadata sent by the imaging modality or source device.
- Displays the configured AE Title assigned to the sending or receiving system.
- Used to identify and route studies between modalities, PACS, and integrated systems.
- Supports device identification, workflow routing, and system-level filtering.
- Helps trace the origin of the study for operational and troubleshooting purposes.
- Shorter, second entry:
- Represents the AE Title of the source imaging device.
- Captured from DICOM metadata.
- Used for device identification and routing.
|
| Study Custom Memo | - Represents custom notes associated with the study.
- Entered manually by users.
- Used to store additional study-related information.
|
| Study Date/Time | - Represents the date and time when the imaging study was performed.
- Captured automatically from the study metadata once the exam is completed and finalized by the modality/system.
- Used to filter, sort, and audit studies in the worklist based on when the exam occurred.
- Supports date range selection using standard presets (for example, Today, Last 7 days, Last 30 days).
- Time selection becomes active only after a valid date or date range is selected.
- Critical for clinical review, reporting timelines, billing, and regulatory compliance.
|
| Study Description | - Describes the imaging study in human-readable terms (for example, CT Abdomen Liver, MRI Head Without Contrast).
- Populated from the order or modality data at the time the study is created.
- Used to clearly identify the type and scope of the exam in the worklist.
- Supports search and filtering to quickly locate studies by description.
- Helps clinicians, technologists, and readers understand the clinical context of the study.
|
| Study ID | - A system-generated unique identifier assigned to each study.
- Automatically created by the application when the study is registered or received.
- Used internally for linking the study to related orders, images, reports, and audit records.
- Serves as the primary reference for tracking and managing the study across workflows.
- Enables accurate search, filtering, and reconciliation of studies within the worklist and downstream systems.
|
| Study Reason/History | - The clinical reason or history provided to justify and support the imaging study.
- Captured from the order information entered during scheduling or order creation.
- May include clinical indications such as symptoms, conditions, or relevant history (for example, chest pain or edema).
- Used by technologists and reading physicians to understand the clinical context of the study.
- Supports filtering and searching to locate studies based on clinical indication or history.
|
| Study Status | - Represents the current stage of the study within the workflow (for example: Prior, Confirmed, Arrived, In Progress, Exam Completed, Dictated, On Hold, No Show).
- The list of available statuses in the Study Search grid is driven by the selected Managing Organization.
- Used to reflect workflow progress and operational state.
- Study statuses can be created, edited, or deleted only at the Master Organization level.
- Child organizations automatically inherit these statuses, ensuring consistency across the system.
- Statuses are color-coded in the new worklist and are configurable based on organizational workflow needs.
- See Using the Worklist Screen for the current colour table.
|
| Study UID | - A globally unique identifier assigned to a study to ensure unambiguous identification across systems.
- Automatically generated by the imaging modality or source system at the time of study creation.
- Used to uniquely link images, reports, and metadata associated with the study.
- Remains constant throughout the study lifecycle and cannot be edited.
- Critical for interoperability, data exchange, and synchronization between PACS, RIS, and other integrated systems.
- Commonly used for searching, tracking, auditing, and troubleshooting studies across workflows and external integrations.
|
| Technique object | - Represents technique-related data associated with the study.
- Captured from modality or structured data objects.
- Used for technical review and documentation.
|
| View | - The display or layout selected in the Study Info View field.
- Captured from the Study Info View setting in the system.
- Used for reporting, analysis, and user interface customization.
- Determines how study information is presented to users.
- Impacts data visibility, filtering, and user workflow.
- Ensures consistent presentation of study details across the platform.
|