Study Validation

Study Validation helps ensure that patient and study information stored in AdvaPACS remains accurate, complete, and consistent.

When studies are imported into AdvaPACS, they are automatically evaluated against a set of validation rules. These checks identify missing information, demographic discrepancies, or issues matching studies to existing orders and patient records. If a study cannot be automatically validated, it is placed in the Study Validation Queue for review and resolution by a user.

Study Validation Queue

The Study Validation Queue contains studies that require manual review before they can be fully processed.

Studies may appear in the queue when:

• Required patient or study information is missing
• Patient demographics do not match an existing patient record
• An expected order cannot be found
• Multiple matching orders are found
• An unrecognised assigning authority is received (when Assigning Authorities are enabled)

Users can review each study, compare it with existing patient records, update missing information, and validate the study for import.

Validation Behaviour

When a study is received, AdvaPACS performs a series of validation checks based on the configured validation behaviour.

The validation process can evaluate:

• General study information
• Order matching
• Patient demographic consistency

If all configured checks pass, the study is automatically processed. If any validation rule fails, the study is routed to the Study Validation Queue for manual review.

General Information

AdvaPACS checks that key patient and study identifiers are present. Studies may be flagged for validation if required information is missing, including:

• Patient ID
• Patient Name
• Date of Birth
• Sex
• Accession Number

info

When the Assigning Authorities feature is enabled, if an imported study has an unrecognized Issuer of Patient ID or Issuer of Accession Number, the study will be placed in the study validation queue.

Unrecognized Issuers of Patient ID in the Other Patient IDs Sequence will be ignored.

Order Validation

Order validation determines how incoming studies are matched against existing orders. The validation behaviour can be configured either globally, or to a specific Remote AE.

To change the validation criteria, please refer to our guide here to configure it globally, or here to configure it to a Remote AE. Depending on your configuration, AdvaPACS can:

Validation Behaviour	Description
Do Not Validate	Studies are accepted without checking for a corresponding order.
Validate Against Orders	Studies must match a single existing order and the following DICOM tags will be checked:
Automatically Generate Orders	Orders are automatically created when no matching order exists.

If studies are being validated against an order, AdvaPACS will check the following fields in the study's DICOM tags to ensure they match an order in the system.

Field	DICOM Field
Accession Number	(0008,0050) AccessionNumber
Scheduled Procedure Step ID	(0040,0009)
Request Procedure ID	(0040,1001)

Demographic Validation

Demographic Validation compares incoming patient information against existing patient records to help maintain data quality and reduce duplicate patients. When enabled, AdvaPACS evaluates key demographic fields including:

• Patient Name
• Date of Birth
• Sex

If the incoming demographics do not match the existing patient record according to the configured validation rules, the study will be routed to the Study Validation Queue for review.

The following validation modes are available:

Mode	Description
Strict	All configured demographic fields must match exactly. Any mismatch will trigger validation.
Relaxed	Allows one demographic mismatch before validation is required.
Disabled	Demographic information is not validated against existing patient records.

The Demographic Mismatch Behavior is configured in the Admin Settings.

This behavior affects all studies that are imported into AdvaPACS, regardless of their Remote AE of origin. Follow the steps in this article to select a a Demographic Mismatch Behavior.

Validating Studies

Studies that require manual review are displayed in the Study Validation Queue. From the queue, select a study and open the Manual Study Validation page to review and resolve the validation issue.

The page is divided into two main areas:

Section	Description
Study Requiring Validation	Displays the incoming patient and study details.
Search Patient	Allows you to search for an existing patient, compare patient details, update the accession number, or create a new patient record.

Before validating a study, search for an existing patient record. This helps determine the correct validation approach and reduces the risk of creating duplicate patient records.

Checking for an Existing Patient

To check for an existing patient:

1. Enter the Patient ID in the Search Patient section.
2. Click Search.
3. Review the search results.
4. Choose the appropriate validation approach based on whether an existing patient record is found.

Create a New Patient Record

Use this option when the study does not match an existing patient record, or when a new patient record should be created.

To create a new patient:

1. Click Create New Patient.
2. Enter or confirm the required patient details.
3. Click Create & Import Study.

Choose an Existing Patient

Use this option when the study belongs to an existing patient.

To validate against an existing patient:

1. Search for the patient using the Search Patient section.
2. Select the correct patient record.
3. Review any highlighted mismatches.
4. Select the correct values for details such as Patient Name, Date of Birth, and Sex.
5. Click Validate.

Generate or Update an Accession Number

Use this option when the study has a missing or incorrect accession number.

To generate an accession number:

1. Clear the Accession Number field.
2. Click Generate.
3. Review the generated accession number.
4. Click Validate.

To update an accession number:

1. Click the Accession Number field.
2. Enter the correct accession number.
3. Click Validate.

note

Depending on your configuration, additional fields may be available during validation, such as Organisations or Assigning Authorities.