Update README with DICOM support implementation steps

Revised steps for adding DICOM support in the extension manager, including updates to Slicer ExtensionsIndex and core functionalities.

Author: fedorov

PW44_2026_GranCanaria/Projects/AddingDicomSupportInformationToExtensionManager/README.md

@@ -47,12 +47,14 @@ Currently DICOM support in extensions is written to a json file in the slicer re
 <!-- Describe here HOW you would like to achieve the objectives stated above. -->
 
 
-1. Update [Slicer Package Manager](https://github.com/girder/slicer_package_manager) to handle additional DICOM support metadata
+1. Update Slicer ExtensionsIndex to include DICOM related metadata, update schema (Kyle has the branch)
+2. Update [Slicer Package Manager](https://github.com/girder/slicer_package_manager) to handle additional DICOM support metadata
     - This can be done by specifying a [rule-engine](https://pypi.org/project/rule-engine/) string that can be used to define extension compatibility with Modality and SOPClassUID.
     - Ex:
     ```"(Modality == 'SEG') or (SOPClassUID == '1.2.840.10008.5.1.4.1.1.30') or (Modality == 'SR' and (SOPClassUID == '1.2.840.10008.5.1.4.1.1.88.22' or SOPClassUID == '1.2.840.10008.5.1.4.1.1.88.33'))"```
-3. Update 3D Slicer core to query the list of available extensions to find an extension that can handle the current modality.
-4. Integrate this PR with other efforts to update the extension manager (extensions tiers, multiple categories, etc.).
+3. Update 3D Slicer core to query the list of available extensions to find an extension that can handle the current modality. (Kyle has the branch already)
+4. Integrate this PR with other efforts to update the extension manager (extensions tiers, multiple categories, etc. - see https://github.com/girder/slicer_package_manager/pull/124)
+5. Update SlicerIDCBrowser?
 
 
 ## Progress and Next Steps