Pular para o conteúdo principal

Table of Worklist Fields

This is the full reference list of fields available for worklist columns, filters, and sorting, organized by category below. Use it alongside Customizing a Worklist and Creating a Worklist when building or editing a worklist.

Note: Several field descriptions below reference Digital Imaging and Communications in Medicine (DICOM), the standard used to store and transmit medical images, and related systems such as the Radiology Information System (RIS), Hospital Information System (HIS), and Admission, Discharge, and Transfer (ADT) messaging.

Patient demographic fields

FieldDescription
Age at Study
  • Represents the patient's age at the time the study was performed.
  • Calculated using the patient's date of birth and the study date.
  • Reflects age at the moment of imaging, not the current age.
  • Used for clinical context, interpretation, and reporting accuracy.
  • Important for age-dependent protocols, measurements, and assessments.
Birth Sex
  • The gender assigned to the patient at birth.
  • Captured during patient registration as part of demographic details.
  • Used for patient identification, clinical context, and reporting.
Date of Birth
  • The patient's date of birth captured during patient registration.
  • Fetched from the patient demographic record.
  • Used for patient identification, age calculation, and clinical context.
Ethnicity
  • Represents the patient's self-reported ethnicity captured during registration.
  • Values are sourced from the demographic record and follow configured ethnicity lists.
  • Used for demographic reporting, analytics, and regulatory or compliance purposes.
Gender
  • Represents the gender as declared or recorded for the patient.
  • Values are captured during patient registration or demographic updates.
  • Used for demographic reference, reporting, and downstream clinical or administrative workflows.
  • May include standard options such as Female, Male, Other, or Unknown, depending on system configuration.
  • Supports filtering and grouping of studies based on patient demographic attributes.
Home Phone
  • Stores the patient's primary home telephone number.
  • Typically captured during patient registration or demographic intake.
  • Used for non-urgent patient communication, appointment coordination, or administrative follow-ups.
  • Sourced from the patient demographics record within the system or received via inbound ADT/registration messages (when integrated).
  • May be used as a searchable or filterable field where patient contact information is required.
Languages
  • Indicates the language(s) the patient is fluent in or prefers for communication.
  • Captured as part of the patient's demographic record during registration or subsequent updates.
  • Used to support appropriate communication, care delivery, and accessibility requirements.
Patient Address
  • Displays the patient's recorded address as stored in the patient demographics record.
  • Retrieved from the patient's demographics.
  • Supports search and multi-select filtering to narrow results based on one or more patient addresses.
  • Includes street-level address values and may contain multiple distinct address entries across patients.
  • A (Blank) option is available to filter records where the patient address is missing or not recorded.
Patient Balance
  • Displays the outstanding financial balance associated with the patient.
  • Represented from billing and financial records.
  • Used for filtering and reviewing studies or orders with pending patient financial responsibility.
  • Represents the amount currently owed by the patient after applied payments, adjustments, or insurance processing.
Patient Cell Phone
  • Displays the patient's registered mobile phone number.
  • Values are pulled from the patient profile.
  • Used for identifying, filtering, or contacting the patient for notifications such as appointment reminders, order updates, or verification workflows.
  • Values may include country codes and are displayed as stored in the patient profile.
Patient Email
  • Patient's email ID used during the registration process.
  • Pulled from the Patient Demographics record.
  • Used for electronic communications such as appointment notifications, reports, billing updates, and system alerts, depending on the patient's contact preferences and consent settings.
  • Captured during patient registration or profile updates.
Patient First Name
  • Represents the first name of the patient.
  • Captured during patient registration.
  • Used for identification and search.
Patient ID
  • A unique identifier assigned to a patient to consistently identify and track their medical records across the system.
  • Automatically generated by the system during patient registration or received from external systems through HL7/API integrations (such as HIS, EMR, or RIS).
  • Used to associate studies, orders, reports, and all related clinical data with the correct patient.
  • Retrieved from and maintained within the Patient Demographics.
  • Enables accurate retrieval and longitudinal viewing of a patient's imaging and clinical history.
  • Acts as the primary reference point for patient-level data consistency across workflows and systems.
  • Incorrect, missing, or duplicate values may lead to data fragmentation or incorrect record association.
  • Commonly referred to as the Medical Record Number (MRN) in clinical environments and remains consistent unless formally merged or corrected by authorized users.
Patient Last Name
  • Represents the last name of the patient.
  • Captured during patient registration.
  • Used for identification and search.
Patient Location
  • Indicates the patient's current or associated location based on visit-level information recorded in the system.
  • Derived from the Visit section and linked to the active or selected visit for the patient.
  • Used to contextualize where the patient is receiving care at the time of the study or order.
  • Determined using visit attributes such as Visit Number and Visit Class (for example, short stay, virtual, or ambulatory).
  • Captured automatically during visit creation or updated through integrations with upstream systems such as HIS or EMR.
  • Supports operational workflows, reporting, and filtering based on care setting or visit type.
  • Ensures studies and orders are accurately associated with the correct visit and care context.
Patient Name
  • Represents the full name of the patient as recorded in the system.
  • Captured at the time of patient registration or intake and maintained within the patient demographic record.
  • Used as a primary identifier for displaying, searching, and validating patient records across workflows.
  • Populated or updated via integrations with external systems such as HIS, EMR, or registration interfaces.
  • Appears on studies, orders, reports, and related clinical and administrative views.
  • Supports accurate patient identification and reduces the risk of record duplication or misassociation.
Patient State/Province
  • Represents the state or province associated with the patient's address.
  • Captured during patient registration or demographic entry, typically as part of the address details.
  • Used for patient identification, filtering, reporting, and regional or jurisdiction-based workflows.
  • Commonly stored using a standardized two-letter abbreviation (for example, CA for California, ON for Ontario), though values may vary based on data source or integration.
  • Supports administrative, billing, and compliance requirements that depend on geographic location.
Race
  • Indicates the patient's self-reported racial classification.
  • Captured during patient registration or demographic data entry.
  • Used for demographic reporting, regulatory compliance, and population health analysis.
  • May be optional or recorded as unknown/declined based on patient preference.
Smoking Status
  • Indicates the patient's tobacco use status as recorded in their demographic or clinical profile.
  • Sourced from patient registration or clinical intake records and may vary based on data availability.
  • Captures standardized values such as heavy smoker, former, never, light smoker, or unknown smoking history.
Special Arrangement
  • Indicates any special accommodations or assistance required by the patient before or during the examination.
  • Captured during order entry, scheduling, or patient intake based on clinical or mobility needs.
  • Used by scheduling, technologists, and clinical staff to prepare appropriate resources and ensure patient safety.
  • Values may be selected from predefined options (for example, wheelchair assistance, non-responsive patient) or left blank if not applicable.
  • Helps avoid delays, rescheduling, or incomplete exams by aligning operational readiness with patient needs.
SSN
  • Represents the patient's Social Security Number (SSN).
  • Captured during patient registration or demographic data entry, if provided and permitted by policy.
  • Used as a secondary identifier to help uniquely distinguish patients with similar demographic details.
  • Typically entered manually or received from an integrated registration system.
  • May support insurance verification, billing, and regulatory or audit requirements.
  • Subject to strict privacy, security, and access controls due to sensitive personal information.

Study and imaging fields

FieldDescription
# 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 TitleTwo 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.

Order and workflow fields

FieldDescription
Accession # (Accession Number)
  • Unique identifier assigned to an imaging study or order when it is created in the RIS or HIS.
  • Fetched into the worklist through system integrations (for example, HL7 or DICOM).
  • Used to link the study across RIS, PACS, reporting, and billing systems.
  • Represents a single imaging request and remains consistent across workflow steps.
  • Enables accurate study identification, tracking, and retrieval.
CDS ID (Clinical Decision Support Identifier)
  • Unique identifier associated with a Clinical Decision Support (CDS) rule or configuration.
  • Derived from the CDS configuration defined within the system.
  • Used to filter, reference, or track records influenced by CDS logic.
Department
  • Identifies the department to which the study is assigned.
  • Values are populated from the department master data configured in the system.
  • Enables filtering of studies based on departmental ownership for operational, reporting, and workload views.
  • The department association is typically derived from the ordering context, scheduled location, or managing organization rules, depending on workflow configuration.
  • Supports type-ahead search and selection, displaying matching departments as the user enters text.
Filler Order # (Filler Order Number)
  • A unique order number assigned by the receiving application (filler system).
  • Retrieved from the receiving application at order creation.
  • Serves as the permanent identifier for the order and all related observations.
  • Used to consistently reference and track the order throughout its lifecycle.
Healthcare Service
  • Identifies the healthcare service or operational location where the study is scheduled to be performed.
  • Values are sourced from configured healthcare services/resources within the system (for example, modality and location master data).
  • Used to filter, route, and prioritize studies based on service location or modality availability.
  • Typically represents a modality, room, mobile unit, or service area (for example, CT Room, Mobile CT, or a named clinical service).
  • Assigned at the time of scheduling and may be updated if the study is rescheduled or reassigned.
  • Supports operational reporting, workload distribution, and resource utilization analysis.
Order Custom Field 1
  • An optional, configurable field used to capture additional order-specific information.
  • Data is sourced from the order entry process and is stored with the order record.
  • Can be used for internal tracking, filtering, or reporting purposes.
  • Content is defined by the organization and may vary based on workflow or operational needs.
Order Custom Field 2
  • An optional, configurable field used to capture additional order-specific information.
  • Data is sourced from the order entry process and is stored with the order record.
  • Can be used for internal tracking, filtering, or reporting purposes.
  • Content is defined by the organization and may vary based on workflow or operational needs.
Order Custom Memo
  • An optional free-text field used to capture detailed, order-specific notes or remarks.
  • Information is entered during order creation or update and stored with the order record.
  • Can be used for internal reference, clarification, or workflow-specific communication.
  • Intended for additional context that does not fit into structured order fields.
Order Notes
  • Represents notes associated with the order.
  • Entered during order creation or updated later by authorized users and may also be received from integrated ordering systems.
  • Displays the note text and supports search and filtering based on the entered content.
  • Used to communicate additional instructions or context related to the order for clinical and operational workflows.
Order of Appropriateness
  • Represents the appropriateness level assigned to the imaging order.
  • Captured from clinical decision support systems or order entry details.
  • Used to support compliance with imaging guidelines and clinical review.
Order Placement Date/Time
  • Represents the date and time when the order was initially created in the system.
  • Retrieved from the order creation timestamp stored in the order management module.
  • Used for order tracking and lifecycle analysis.
  • Supports filtering by a selected date range; time selection is enabled only after a valid date or date range is chosen.
  • Preset ranges (for example, Today, Last 24 hours, Last 7 days, Last 30 days) can be used for quick filtering.
Order Priority
  • Indicates the urgency level assigned to an order, defining how quickly it should be addressed.
  • Captured during order creation and may be updated by authorized users.
  • Used across clinical, operational, and reporting workflows to support effective triage and order management.
  • Common values include STAT, URGENT, ASAP, ROUTINE, or numeric priorities, depending on system configuration.
  • Influences scheduling precedence, workflow routing, and expected turnaround times.
Order Status
  • Represents the current status of the order within the order lifecycle.
  • Derived automatically from the statuses of the studies on the order; it is not set by hand.
  • Displays the order status values used by OmegaAI — draft, active, on-hold, completed, revoked, entered-in-error and unknown — and supports filtering, sorting and grouping.
  • Used to track order progress and support scheduling, processing, and operational workflows.
Placer Order #
  • Represents the order number assigned by the ordering (placing) physician or originating clinical system.
  • Captured from the inbound order request (for example, HL7 ORM or electronic requisition).
  • Used for order reconciliation, interoperability, audit tracking, and communication with referring facilities.
  • Serves as an external reference to link the imaging order back to the referring provider's system.
  • May differ from the internal Filler Order # generated by the imaging application.
Reason For Exam
  • Indicates the clinical reason or justification for performing the imaging exam.
  • Captured from the order details entered by the referring provider or scheduling workflow.
  • Used to support medical necessity, interpretation accuracy, and downstream reporting or billing.
  • Provides clinical context to technologists and reading physicians.
Requested Appointment Date/Time
  • Indicates the date and time requested for scheduling the patient's appointment.
  • Captured when the appointment request is created or updated in the system.
  • Used to filter, prioritize, and manage studies based on requested scheduling timelines.
  • Requires selection of a valid date or date range before the time selection becomes active.
  • Supports preset ranges (for example, Today, Last 7 days, Last 30 days) as well as custom date ranges.
  • Helps coordinate scheduling workflows and assess demand against available resources.
Requested Procedure ID
  • Represents the unique identification number assigned to the requested procedure.
  • Captured from the order or scheduling request when the procedure is created.
  • Used to uniquely identify, track, and differentiate procedures across orders, studies, and workflows.
  • Plays a key role in mapping orders to modalities, protocols, billing, and clinical documentation.
  • Enables accurate filtering, reporting, and downstream processing of studies based on the requested procedure.
Scheduled Date/Time
  • Represents the scheduled appointment date and time for the study.
  • Captured during appointment scheduling.
  • Used to manage patient appointments and operational workflows.
  • Requires selection of a specific date or date range to activate time selection.
  • Time slots displayed are constrained to the selected date period.
  • Supports preset ranges (e.g., Today, Last 7 Days) as well as custom ranges.
Started
  • The date and time when the study or workflow activity was marked as started.
  • Captured automatically when the study status or workflow step changes to a started or in-progress state.
  • Displays date and time values and supports filtering using presets or a custom date/time range.
  • Used to track workflow progression and measure turnaround times.
  • Helps identify when the study processing or examination began.
Status To Scheduled
  • Represents the system-generated timestamp indicating when a study's workflow status was updated to Scheduled.
  • Automatically captured during status transition.
  • Can be used for filtering, sorting, and auditing studies based on scheduling activity.
  • The timestamp is sourced from the study workflow.
  • Reflects the exact date and time of the status change, based on the server/system time.
  • Supports preset date ranges (for example, Last 24 hours, Today, Last 7 days, Last 30 days) as well as custom date and time selection.
  • Selecting a date is mandatory before a time can be specified when using custom filters.
Visit #
  • The unique number assigned to a patient visit.
  • Captured from the system when a visit is created or registered.
  • Used in reporting, audits, and cross-referencing patient data.
  • Identifies and differentiates individual patient visits.
  • Impacts scheduling, record linking, and workflow tracking.
  • Ensures accurate tracking of visits within the organization's records.
Visit Class
  • The category or type of the visit, e.g., emergency, daycare, or ambulatory.
  • Captured from the Visit Class field in the system.
  • Used for workflow, reporting, and operational purposes.
  • Categorizes visits for filtering, scheduling, and resource allocation.
  • Filters available include Emergency, Outpatient, or Blank to refine views.
  • Ensures clear classification and management of patient visits across the organization.
Workflow Step
  • The current workflow stage of the order or study within the system.
  • Captured automatically as the order or study progresses through the workflow.
  • Represents operational stages such as Requested, Ordered, Confirmed, Signed, Completed, or Cancelled.
  • Used by staff to monitor progress and identify the current processing stage.
  • Supports filtering and tracking of studies based on their workflow progression.

Physician and staff fields

FieldDescription
Consulting Physician
  • Represents the physician consulted for the study or patient care.
  • Captured from order details or manual assignment.
  • Used for clinical coordination and reporting.
Performing Physician
  • Identifies the physician who performs or is responsible for conducting the imaging study.
  • Typically selected from the configured provider directory within the system.
  • Used for clinical accountability, study attribution, and operational tracking.
  • Impacts reporting, physician workload metrics, credentialing compliance, and downstream clinical documentation.
Performing Physician NPI
  • Uniquely identifies the performing physician using their National Provider Identifier (NPI) or internal provider ID.
  • Captured from the physician profile when the performing physician is assigned to the study.
  • Used for billing, claims submission, and regulatory compliance.
  • Sourced from the provider master data and not typically entered manually at the order level.
  • Ensures accurate provider attribution across clinical, financial, and reporting workflows.
Performing Technologist
  • Identifies the technologist who performed or is assigned to perform the imaging study.
  • Captured when the technologist is assigned during scheduling, workflow progression, or exam completion.
  • Used for operational tracking, productivity reporting, and audit purposes.
  • Typically selected from the system's technologist or user directory.
  • Supports accountability and traceability within clinical and quality workflows.
Reading Physician
  • Identifies the physician responsible for interpreting and reporting the imaging study (for example, a Radiologist or Urologist).
  • Captured by assigning a physician to the study, either through workflow routing or manual selection.
  • Used for workload distribution, accountability, audit trails, and reporting analytics.
  • Can be searched and selected directly from the worklist header for quick filtering and assignment.
  • Determines clinical responsibility for image interpretation and report sign-off.
Reading Physician NPI
  • Represents the National Provider Identifier (NPI) or internal ID of the physician assigned to interpret the study.
  • Captured automatically when a reading physician is assigned or populated from provider master data if manually selected.
  • Used for attribution, auditing, analytics, and downstream workflows such as reporting and reimbursement.
  • Serves as a unique, standardized identifier to distinguish the physician across systems and integrations.
  • Supports regulatory compliance, billing, and payer reporting requirements.
Reading Physician Specialty
  • The specialty associated with the reading physician assigned to interpret the study.
  • Captured from the physician profile and automatically linked when a reading physician is assigned to the study.
  • Displays configured specialty values such as Radiology, Cardiology, Dermatology, Anesthesiology, Psychiatry, and others.
  • Used for filtering, assignment, and reporting based on physician expertise.
  • Helps ensure studies are interpreted by appropriately qualified physicians.
Referring Physician
  • Identifies the physician who referred the patient for the study (for example, a primary care physician or a specialist).
  • Captured from the order or referral details at the time the study is created.
  • Used for referral tracking, communication, reporting, and clinical accountability.
  • Displayed and selectable via the worklist header filters for quick searching and filtering.
Referring Physician NPI
  • Represents the National Provider Identifier (NPI) or internal ID of the referring physician.
  • Captured from the referral or order information provided at study creation or during order updates.
  • Used to uniquely identify the referring physician across systems and integrations.
  • Displayed as a searchable and filterable field in the worklist header.
  • Supports accurate billing, compliance, reporting, and audit workflows.
Referring Physician Specialty
  • The specialty associated with the referring physician who requested the study.
  • Captured from the referring physician's profile and automatically linked when the physician is assigned to the order.
  • Displays configured specialty values such as Cardiology, Family Medicine, Orthopedics, Radiology, and others.
  • Used for filtering, reporting, and analyzing referral patterns by specialty.
  • Helps identify the clinical domain responsible for requesting the study.
Transcriptionist
  • The individual assigned to perform the transcription for a study.
  • Captured from the user or staff assigned in the system.
  • Used in reporting, performance monitoring, and audits.
  • Identifies responsibility for transcript creation and accuracy.
  • Impacts workflow tracking, quality review, and accountability.
  • Ensures clear assignment of transcription tasks within the organization.
Transcriptionist Organization
  • The entity responsible for performing the transcription.
  • Captured from the assigned organization in the system or workflow.
  • Used for tracking performance, audits, and invoicing.
  • Identifies who is accountable for transcript accuracy and delivery.
  • Impacts workflow routing, quality checks, and reporting.
  • Ensures proper assignment and accountability within transcription processes.

Organization fields

FieldDescription
Assigning Authority (Issuer)
  • Identifies the issuer, representing the organization or authority that issued the identifier.
  • Defaults to the organization's configured issuer when no external issuer is specified.
  • Supports accurate identification and interoperability in multi-organization environments.
Imaging Organization
  • Identifies the organization responsible for performing the imaging study.
  • Values are populated from configured imaging organizations within the system and may include externally integrated organizations.
  • Used to filter, group, and report studies based on the performing imaging organization.
  • Represents the imaging provider or facility under which the study is conducted (for example, hospital networks, imaging groups, or internal organizations).
  • Supports organizations with long or descriptive names, including those exceeding standard character lengths.
  • Commonly leveraged in multi-organization or multi-site environments to distinguish studies performed across different providers.
Managing Organization
  • Identifies the organization responsible for managing and overseeing the study.
  • Typically derived from the study or account configuration.
  • Used to support ownership, workflow routing, reporting, and administrative control across multi-organization environments.
  • May differ from the imaging or referring organization.
Reading Organization
  • Represents the organization responsible for interpreting and reporting the imaging study.
  • Captured from the order configuration, routing rules, or manual selection during workflow assignment.
  • Used for operational routing, audit trails, analytics, and billing or contractual attribution.
  • Determines where studies are sent for diagnostic reading and which organization issues the final report.
  • Impacts reporting ownership, turnaround time tracking, and clinical accountability.
Referring Organization
  • Identifies the organization that referred the patient for the study.
  • Captured from the referral or order information provided during order creation.
  • Used for coordination, communication, and audit or compliance purposes.
  • Helps establish referral source for operational tracking and reporting.
  • Can be manually searched and filtered using the worklist header filters.

Insurance and billing fields

FieldDescription
Account #
  • A unique identifier assigned to a patient account within the system.
  • Automatically generated by the system or sourced from the upstream registration/ADT system.
  • Used to group and track all studies, visits, and billing records associated with the patient.
  • Helps distinguish patients with similar demographics and reduces the risk of record duplication.
  • Commonly used in search filters, reconciliation, reporting, and financial workflows.
Account Status
  • Indicates the current status of the patient's account in the system.
  • Derived from the patient or account configuration maintained by the organization.
  • Used to control visibility, workflow eligibility, and operational handling of studies.
Authorization Period
  • Represents the valid date range for an insurance authorization.
  • Captured from authorization details entered manually or received from integrated systems.
  • Used to verify that the study is scheduled and performed within the approved timeframe.
Eligibility
  • Indicates the patient's insurance coverage eligibility for the associated study.
  • Values are derived from insurance verification workflows or eligibility checks performed against payer information.
  • Used to support billing readiness, workflow prioritization, and operational filtering of studies.
  • Possible statuses include Yes, No, Pending, and Unknown, reflecting the current verification outcome.
  • Not to be confused with the Eligibility indicator in the worklist's Indicators column, which uses a different set of values (Eligible, Not Eligible, Pending Eligibility). Whether the two represent the same underlying data or something genuinely different isn't confirmed.
Financial Class
  • Indicates the patient's payment or reimbursement category for the study or encounter.
  • Values are derived from the patient's registration and billing information configured in the system.
  • Used for financial workflows such as billing, reporting, eligibility checks, and revenue analysis.
  • Classifies how charges are expected to be covered (for example, insurance-based, government-funded, or self-funded).
  • Supports filtering and segmentation of studies based on payment responsibility.
Insurance Copay
  • Indicates the portion of the total cost that the patient is required to pay toward the study.
  • Retrieved from the patient's insurance and billing details associated with the study.
  • Used to support billing review, financial validation, and eligibility-related workflows.
  • Can be defined as either a fixed monetary amount (currency) or a percentage of the total charge.
  • May vary based on the patient's insurance plan, financial class, and coverage rules.
Insurance Expiry
  • Indicates the date on which the patient's insurance coverage is no longer valid.
  • Retrieved from the insurance details recorded in the patient's demographic.
  • Used to determine coverage validity at the time of scheduling, ordering, or performing a study.
  • Helps identify studies that may require insurance renewal, re-verification, or self-pay handling.
  • Supports filtering and reporting based on active versus expired insurance coverage.
Insurance Status
  • Indicates the current state of the patient's insurance coverage (for example, Eligible, Pending, Ineligible, or Unknown).
  • Derived from insurance eligibility and verification workflows within the system.
  • Used to support billing decisions, scheduling readiness, and operational follow-up.
  • Reflects the most recent insurance verification result associated with the patient or study.
  • Enables filtering and reporting based on insurance verification outcomes.
Primary Insurance
  • Represents the primary insurance provider or payment source associated with the patient.
  • Captured during patient registration or insurance entry and may be received from integrated registration or billing systems.
  • Multiple options may be available, such as Self Pay, or other commercial or government insurance providers, depending on system configuration.
  • Used for eligibility verification, billing workflows, and financial processing.
Primary Prior Authorization #
  • The prior authorization reference number issued by the patient's primary insurance payer.
  • Captured manually in the Prior Authorization drawer for the primary insurance payer.
  • Displays once the prior authorization number is entered and saved.
  • Used to validate insurance approval for the associated order or study.
  • Supports claim submission, compliance tracking, and audit verification.
  • Confirms payer authorization prior to scheduling or performing the exam.
Primary Prior Authorization Total Amount Due
  • Represents the total amount due associated with the primary prior authorization.
  • Captured from authorization or billing details.
  • Used for financial tracking and billing workflows.
Secondary Insurance
  • Represents the secondary insurance provider or payment source associated with the patient.
  • Captured during patient registration or insurance entry and may be received from integrated registration or billing systems.
  • Multiple options may be available, such as Self Pay, or other commercial or government insurance providers, depending on system configuration.
  • Used for coordination of benefits, eligibility verification, and billing workflows.
Secondary Prior Authorization
  • Represents the authorization number for the secondary insurance.
  • Captured from authorization details.
  • Used for insurance verification and billing.
Secondary Prior Authorization Total Amount Due
  • Represents the total amount due associated with the secondary prior authorization.
  • Captured from authorization or billing details.
  • Used for financial tracking and billing workflows.
Tertiary Insurance
  • Represents the tertiary insurance provider or payment source associated with the patient.
  • Captured during patient registration or insurance entry and may be received from integrated registration or billing systems.
  • Multiple options may be available, such as Self Pay, or other commercial or government insurance providers, depending on system configuration.
  • Used for extended coverage processing, coordination of benefits, and billing workflows.
Tertiary Prior Authorization #
  • Represents the authorization number for tertiary insurance.
  • Captured from authorization details.
  • Used for insurance verification and billing.
Tertiary Prior Authorization Total Amount Due
  • Represents the total amount due associated with tertiary prior authorization.
  • Captured from authorization or billing details.
  • Used for financial tracking and billing workflows.

Document, report, and communication fields

FieldDescription
# of Documents
  • Represents the total number of documents associated with the study or order.
  • Automatically calculated based on the documents linked to the study, such as reports, attachments, or related files stored in the system.
  • Displayed as a numeric value and can be used as a filter to identify studies with or without associated documentation.
  • Used to track document availability and support workflow tasks such as review, verification, and completion.
# of Reports (Number of Associated Reports)
  • Displays the total number of reports associated with the selected study.
  • This count is fetched from the study's linked report records for the corresponding accession, including preliminary, final, and addendum reports available in the system.
Appointment Cancellation Reason
  • Indicates the reason an appointment was cancelled.
  • Sourced from appointment management records at the time of cancellation.
  • Captures standardized or configured cancellation reasons recorded in the system.
Blume Status
  • Indicates whether the study's patient has an active Blume Patient Portal account, or the status of an invitation to create one.
  • Four states, all using the Blume Patient Portal icon distinguished by colour: Active (blue, tooltip "Blume Active"), Invite Not Sent (gray/white, tooltip "Blume Invite Not Sent"), Invite Sent (green, tooltip "Blume Invite Sent"), and Invite Error (red/pink, tooltip "Blume Invite Error").
  • Displayed as an icon in the worklist's Indicators column, with a tooltip identifying the status on hover.
  • Supports filtering, so the worklist can be narrowed to studies with or without an active Blume account.
  • Sourced from feature ticket MAV-3119 (Add Blume Status to the Indicator Column); the ticket's acceptance criteria named the fourth state "Invite Sent in Error," but the confirmed live tooltip reads "Invite Error."
Clinical Comments
  • Contains clinician-entered notes related to the study or patient encounter.
  • Sourced from the document viewer (clinician's notes) entered during order creation or review.
  • May include observations, provisional diagnoses, or relevant remarks.
Communication Status Name
  • Represents the communication status associated with the study or report.
  • Captured from communication or notification workflows.
  • Used to track whether results or updates have been communicated.
Custom Field 1
  • A configurable field used to capture additional, site-specific information.
  • Values are populated based on how the field is defined within the system configuration.
  • The content and usage depend on local configuration and workflow requirements.
Custom Field 2
  • A configurable field used to capture additional, site-specific information.
  • Data is populated based on how the field is defined and used within the system setup.
  • The purpose and values of this field are determined by local configuration and operational workflows.
Date/Time Addendum
  • Displays the date and time when an addendum was created.
  • Populated from the addendum metadata at the time the addendum is saved.
  • Represents the addendum creation timestamp, independent of the original study or report date.
Date/Time Last Updated
  • Displays the most recent date and time when the study record was modified.
  • The value is system-generated and fetched from the study's audit/update timestamp within the backend data store.
  • Used for filtering and sorting studies based on recent activity, regardless of current study status (ordered, in progress, completed, or rejected).
  • Reflects updates resulting from actions such as status changes, data edits, or workflow progress.
Date/Time Ordered
  • Indicates the date and time when the study order was created in the system.
  • Captured at the point the order is placed in the system.
  • Can be used for order lifecycle tracking and TAT analysis.
  • Date range selection is mandatory to activate time-based filtering.
  • Time selection becomes available only after a valid date range is selected.
  • The timestamp reflects the system/server time at which the order was created.
Date/Time Read
  • Indicates the date and time when the study was marked as read by a radiologist.
  • The value is fetched from the study reporting or interpretation record.
  • Can be used for report TAT measurements.
  • Captured when the study status transitions to Read.
  • Users must first select a date range to activate time selection.
  • Time values refine results within the selected date window only.
  • Supports preset ranges (e.g., Today, Last 7 Days) as well as custom ranges.
Date/Time Received
  • Indicates the date and time when the RIS/PACS received the study.
  • Populated when the study is successfully ingested via DICOM/HL7 interfaces.
  • Used for analysis of study intake and processing timelines.
  • Reflects the system/server time of receipt.
  • Time filtering is enabled only after selecting a specific date range.
  • Supports preset ranges (e.g., Today, Last 7 Days) as well as custom ranges.
Date/Time Signed
  • Represents the date and time when the report was electronically signed.
  • Recorded at the moment of final report sign-off.
  • Supports report completion tracking and compliance auditing.
  • The timestamp is sourced from the report signature audit trail.
  • Date selection is required before the time picker is enabled.
  • Time filters apply only to studies within the selected date range.
  • Supports preset ranges (e.g., Today, Last 7 Days) as well as custom ranges.
Date/Time Transcribed
  • Indicates the date and time when the transcription was completed.
  • Captured after manual transcription or speech-to-text processing finishes.
  • Used to track transcription turnaround times.
  • Timestamp is sourced from the transcription or dictation workflow.
  • Users must select a date range to enable time-based filtering.
  • Time selection refines transcription events within the chosen date range.
  • Supports preset ranges (e.g., Today, Last 7 Days) as well as custom ranges.
Date/Time Verified
  • Indicates the date and time when the study was verified.
  • Automatically populated when the study status changes to verified.
  • Used for workflow completion tracking and audit purposes.
  • Timestamp is sourced from the workflow status log.
  • Time selection remains disabled until a date range is selected.
  • Supports preset ranges (e.g., Today, Last 7 Days) as well as custom ranges.
History
  • Captures a summary of the patient's relevant medical history, symptoms, or presenting complaint related to the study.
  • Typically entered by the ordering provider or clinical staff at the time of order creation or scheduling.
  • Used by radiologists and technologists to understand clinical context and support accurate interpretation.
  • May include prior conditions, current symptoms, injury details, or clinical indications that justify the exam.
  • Sourced from the order entry workflow, referral information, or inbound HL7 order messages (when integrated).
  • Supports filtering and review workflows where clinical indication or history is required for triage or quality checks.
Procedure Code
  • Identifies the specific procedure ordered or performed for the study using a standardized or organization-defined code.
  • Captured during order entry or derived from the selected procedure/exam configuration in the system.
  • Used for clinical clarity, operational tracking, and interoperability with external systems (for example, billing or payer systems).
  • Drives downstream workflows such as scheduling, modality assignment, billing, and reporting.