You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/dicom/update-files.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -227,16 +227,18 @@ The [change feed](change-feed-overview.md) records update actions in the same ma
227
227
228
228
## Summary of DICOM UID Update Behavior by Hierarchy Level
229
229
This table outlines how bulk updates behave at different levels of the DICOM hierarchy—Study, Series, and Instance—highlighting when updates are allowed, whether a SOP Instance UID filter is required, how instances are moved, and the resulting impact on the UID hierarchy.
| Update patient demographic attributes only | ✅ | ✅ | ✅ |Not required | No movement | Attributes updated in place; original UID hierarchy preserved. |
234
-
| Update Study Instance UID | ✅ | ❌ | ❌ | ❌ | Study → New Study | All instances in study get new Study UID; series and instance UIDs remain unless explicitly changed. |
235
-
| Update Series Instance UID |❌ | ✅ | ❌ | Not required | Series → New Series | All instances in series get new Series UID; Study UID remains unless updated; SOP Instance UID unchanged. |
236
-
| Update SOP Instance UID | ❌ | ❌ | ✅ | Required | Instance → New Instance | Only the filtered SOP Instance(s) are updated; new SOP Instance UID assigned; Study/Series UID preserved. |
237
-
| Update Study & Series UIDs | ✅ | ✅ | ❌ | Not required | Study → New Study → Series → New Series | Hierarchy updated; all instances in series adopt new UIDs. |
238
-
| Update Study, Series, and SOP Instance UIDs | ✅ | ✅ | ✅ | Required | Study → New Study → Series → New Series → Instance → New Instance | Complete hierarchy updated with filtered SOP instance selection where applicable. |
239
-
| Filter specific SOP Instance(s) without UID change| ❌ | ❌ | ✅ | Required | Instance → No movement | Only selected SOP instances updated in place; other instances untouched. |
| Update patient demographic attributes only | ✅ | ✅ | ✅ |Not required| No movement | Attributes updated in place; original UID hierarchy preserved. |
236
+
| Update Study Instance UID | ✅ | ❌ | ❌ | ❌| Study → New Study | All instances in study get new Study UID; series and instance UIDs remain unless explicitly changed. |
237
+
| Update Series Instance UID | ❌ | ✅ | ❌ | Not required| Series → New Series | All instances in series get new Series UID; Study UID remains unless updated; SOP Instance UID unchanged. |
238
+
| Update SOP Instance UID | ❌ | ❌ | ✅ | Required| Instance → New Instance | Only the filtered SOP Instance(s) are updated; new SOP Instance UID assigned; Study/Series UID preserved. |
239
+
| Update Study & Series UIDs | ✅ | ✅ | ❌ | Not required| Study → New Study → Series → New Series | Hierarchy updated; all instances in series adopt new UIDs. |
240
+
| Update Study, Series, and SOP Instance UIDs | ✅ | ✅ | ✅ | Required| Study → New Study → Series → New Series → Instance → New Instance | Complete hierarchy updated with filtered SOP instance selection where applicable. |
241
+
| Filter specific SOP Instance(s) without UID change| ❌ | ❌ | ✅ | Required| Instance → No movement | Only selected SOP instances updated in place; other instances untouched. |
0 commit comments