[vc_row][vc_column][vc_column_text]DICOM Migrations are complex and can be very time consuming for the PACS team. You can streamline your migration by using a DICOM Inventory as the basis for migration decisions. The primary objective for the DICOM inventory is to increase visibility and awareness of the data and allow the team to evaluate the data prior to migrating. The inventory generation and inventory review process are two key steps in any DICOM data migration project. In this article, we will cover everything you need to know about DICOM inventories.

Everything You Need to Know About a DICOM Inventory

  1. What is a DICOM Inventory.
  2. How to create a DICOM inventory.
  3. DICOM Supplement 223 – The DICOM inventory IOD and repository query.
  4. Contents of the DICOM inventory.
  5. Defining the DICOM source of truth.
  6. DICOM inventory use cases.
  7. Generate delta inventories.

What is a DICOM Inventory?

A DICOM inventory is a working list of medical imaging studies. The DICOM inventory may also be referred to as a DICOM data migration inventory, DICOM index, PACS index, or PACS extract. The reasons for generating a DICOM inventory are numerous, including the most obvious, as a basis for a DICOM data migration. The first step in performing a DICOM data migration is to create the inventory of the medical imaging studies that are going to be migrated. Now that we know what a DICOM inventory is, we can discuss how to create the DICOM inventory.

How To Create a DICOM Inventory

  1. DICOM Inventory IOD and DICOM Repository Query.

  2. DICOM C-FIND.

  3. Database Extract.

  4. DICOM filesystem Inventory.

DICOM Inventory IOD and DICOM Repository Query

Thanks to the arduous work of DICOM Working Group 33, the medical imaging industry now has a method for requesting the complete inventory of a PACS or VNA from a single request using the repository query and DICOM Inventory IOD. The DICOM Inventory IOD is an object that can house the requested data from the repository query. The generation and transmission of DICOM inventories in a defined and actionable format can enhance the reliability, speed, and accuracy of a DICOM data migration.  While adoption and implementation of supplement 223, the DICOM Inventory IOD, and repository query are in their infancy, the standard will allow medical imaging data to be inventoried, extracted, transformed, imported, and migrated in record time. The ability to segment millions of records and quickly identify groups of studies that qualify or do not qualify for migration can reduce the overall time needed to complete even the most complex migrations.

DICOM C-FIND

The most frequently used method for generating an inventory is the date range DICOM C-FIND aggregation. This entails performing consecutive DICOM C-FINDs for all studies acquired during a date range. There are some limitations to this method, such as studies not being included for various reasons. One case is when the study count performed during a specific date has exceeded the internal response limits of the source system. The source may impose an arbitrary results limit of, say, 200 results. Therefore, any query would be limited to 200 results. Care and close monitoring must be instilled when building a DICOM C-FIND inventory, as studies may be omitted and therefore missed during the migration.

Database Extract

One of the fastest and most reliable methods for generating a PACS migration inventory is leverage the source database directly and perform database queries for the information. Performing a query of the database and then extracting the DICOM data allows you to review the contents of the migration in near real-time. This method requires advanced knowledge of databases and read-only access to the source database. Most PACS vendors will grant the customer read-only access to the database, if the customer signs a waiver of liability.

DICOM Filesystem Inventory

Many institutions have DICOM data that is available in a filesystem or directory, but no database associated to manage the files. This means that you cannot query the data directly. To make this offline data searchable and ultimately available to be migrated, you must index the data and present it to a DICOM interface to facilitate the migration.  Often these studies will need to have data added to the header and or generate orders to be able to store them in the destination and image enable the studies in the EMR.

DICOM Supplement 223 – The DICOM Inventory IOD & Repository Query SOP Class

DICOM Working Group 33 began meeting in January 2020 and worked towards a method for requesting and transmitting DICOM inventories. The outcome of the group was DICOM Supplement 223, which provides guidelines for the creation, storage, and transmission of the DICOM Inventory IOD. This supplement includes references to guidelines for the use of DICOM Part 10 files, which are used to store DICOM data, as well as guidelines for the use of DICOM query and retrieve mechanisms to enable requesting and transmitting the inventory.

DICOM Supplement 223 also provides guidelines for the use of delta inventories, which involves generating a list of the changes that have been made to the source system since the last inventory was created. Delta inventories significantly reduce the time and resources required to maintain an ongoing inventory comparison between systems. Delta inventories also improve the accuracy of the destination archive by ensuring that it reflects the most up-to-date information. Organizations can obtain more information about DICOM Supplement 223 by visiting the DICOM Working Group 33 webpage or reviewing the Repository Query SOP Class.

Contents of the DICOM Inventory

The DICOM data inventory is the source of truth for the DICOM data migration. The DICOM inventory provides a detailed list of the data that needs to be migrated, the storage path of the data, and metadata associated with each file. Essentially, it is a list of all the files and metadata that should be migrated from the source into the destination PACS or VNA. It should include:

  • Patient Level: Patient Name, Patient ID, DOB, Sex
  • Study Level: Issuer of Patient ID, Accession Number, Study Instance UID, Study Description, Study Date & Time, Modalities in Study
  • Image Level: SOP Instance UID, SOP details
  • Other Information: Storage path, access information

The primary role of the DICOM inventory is to provide reliable metadata from the source system. This metadata includes information such as patient information, study information, and image information. Once the metadata is extracted, it can be indexed, filtered, and sorted to display specific patients and studies. The inventory will allow the users to identify studies that may or may not need to be migrated.

The DICOM inventory can be a flat file, a combination of files, or a database extract that contains metadata associated with each DICOM file, including the location of the file, the patient and study information, and other relevant data that improves the accuracy and reliability of the migration. The burden of the migration vendor is to ensure a complete inventory of the DICOM data that needs to be migrated is generated, and it is used as a source of truth throughout the migration process. It is best practice for the internal team to have visibility and access to review and scrutinize the inventory.

Defining the DICOM Source of Truth

Which system should be the source of truth (SOT) for the migration, the PACS or the VNA? One of the risks of selecting the incorrect source for migration, is that often the archive is not in sync with the source PACS.  Many times, even if the PACS and Enterprise Archive are from the same vendor, there are discrepancies in the data. Sometimes there are cases where institutions have multiple RIS feeds, with or without an EMPI (Enterprise Master Patient Index), which can create conflicts between patient names, medical record numbers, department to enterprise patient ids, and sometimes even duplicate patient MRNs, or duplicate accession numbers. These discrepancies can cause incorrect data to be migrated or auto merged into destination systems, which can result in patient harm if not corrected.

When preparing for a DICOM migration, it is important to determine which PACS, DICOM Archives, or VNA systems need to be indexed and the level of conformance required. The level of conformance refers to the extent to which the PACS or VNA system adheres to the DICOM standard, IHE standard, HL7 updates, and proper QA maintenance. To ensure that the migrated data is true, accurate, and compatible with other DICOM-compliant systems, it is important to ensure that the source system stores DICOM data using the correct identifiers and adheres to other guidelines specified by the DICOM standard. For instance, some systems may support HL7 patient merge messages, and some systems do not; but rely upon PACS administrators to manually merge patients. Sometimes there are multiple RIS feeds with multiple patient identifiers for the same patient. Many of these issues are not easily identified from within the systems themselves, you must generate the inventories and compare them.

If the migration team is trying to determine which source to choose (PACS or VNA), the first step is to inventory and compare the PACS and the Archive to identify any patients and studies that are out of sync between the systems.  Once this comparison is complete, the team can review the discrepancies and determine the best course of action for cleanup and migration. It is often best to update the data in the source and the archive, and then start the migration from a synchronized state.

Generate Delta Inventories

A static inventory is created by indexing all the DICOM data in the source system at a single point in time. However, as data is added, updated, or deleted, the inventory can quickly become outdated, resulting in missing or incorrect data during migration. To address this issue, organizations can perform delta inventories throughout the project, which involves indexing only the changes that have been made to the source system since the last inventory was created.

Performing delta inventories throughout the project can reduce the time and resources required to create the inventory and can improve the accuracy of the index by ensuring that it reflects the most up-to-date information. It also helps ensure that the data being migrated is accurate and complete, reducing the risk of data loss or corruption. In addition to delta inventories, organizations should also perform data validation to ensure the completeness and accuracy of the DICOM data being migrated. This data validation process involves verifying that the metadata associated with each file is correct, that the relationships between different files are maintained, and that the data being migrated is completely accepted and processed by the destination system.

Limitations of the migration efforts refer to the technical, resource, and other constraints that may impact the success of the migration process. For example, technical limitations may include issues with the source system, while resource limitations may include a lack of budget or staffing resources. By defining these limitations upfront, organizations can proactively address potential issues and ensure that the migration process stays on track.

In Conclusion

DICOM inventories are generated for a multitude of reasons including:

  • DICOM data migration: Identify data to include and exclude on the migration.
  • DICOM synchronization: Ensure your PACS and imaging archives are in sync.
  • Research data identification: Identify and collate research data for deidentification and extraction.
  • AI toolset targets: Identify and pool datasets for AI tool testing and validation.
  • PACS administration: Generate business analytics, management reports, and review storage.
  • PACS quality control: Identify data anomalies, perform annual data reviews, storage management with study access analysis.

By leveraging a DICOM inventory, organizations can ensure that they have a complete awareness and analysis of the DICOM data that needs to be migrated and can use the inventory as their source of truth throughout the migration. Leveraging the DICOM standard and adhering to guidelines such as DICOM Supplement 223 can also improve the migration strategy and ensure the accuracy and completeness of the data being migrated. Organizations should also allocate the necessary resources, both internal and external, to ensure that the project is completed successfully. Defining timelines, milestones, and acceptable failure and limitations of the migration efforts can also help ensure that the project stays on track and that resources are allocated appropriately.

A DICOM data migration project can be a complex and resource-intensive project, but by following best practices and referencing a DICOM Inventory, organizations can successfully migrate their DICOM data. By creating and consistently reviewing the DICOM inventory, organizations can ensure that they have a complete overview of the DICOM data that needs to be migrated and can use this index as a source of truth throughout the migration process.  If you need assistance generating a DICOM inventory, or seeking a second opinion with your DICOM migration, please Contact Us.