1990   Understanding in ICT an UUID in ObjectReference defined by an SCT

Created: 05 Aug 2025

Status: Discussion (red)

Part: Part 6 (2025; Edition 2.2)

Links:

Page: 257

Clause: Annex G

Paragraph: Table G.1

Issue

In SICS, the ICT statement I47 "Generate and handle UUID" is optional. But when an SCT is defining UUID and use it in an ObjectReference with #UID then, the importing ICT needs to be able to recognize the referenced element.
The ICT is still not required to produce UUID, but need to recognize it.

A Typical usecase is the GoCBRef in LGOS which can use UUID when the publisher is already supporting UUIDs.

Proposal

The SICS statement I47 needs to be updated to "Generate UUID" only and stay oprional. Need to add an I48 "Handle UUID" which will be mandatory to understand #UID in ObjectReference

Page 52 first paragraph gives details on the requirement to keep coherency between UUID and naming reference. It will require to add a dedicated paragraph explaining the usecase and detailing why generation remain optional and handle is mandatory for ICT.

It will also explain that UUID generated by SCT do not need to be fully understood by the ICT except this specific case and just need to be kept and exported by in the IID

Discussion Created Status
proposal to provide 10 Oct 25 Discussion (red)
accepted 10 Oct 25 Accepted
I agree: an ICT claiming conformance to Part 6 Ed2.2 shall understand the #UID <Val> representation in an SCD file, and therefore understand the configured Val. 15 Aug 25 Triage

 

Privacy | Contact | Disclaimer

Tissue DB v. 26.1.29.1