XDS Metadata Update – XDSResultNotSinglePatient blocks retrieving version history after a Patient ID change

[strauc...@googlemail.com]

Hi all,

We keep running into a tension in the XDS Metadata Update supplement (Rev. 1.14) in real projects and would like to know if it is known, whether a fix is planned, and how others handle it.

Scope: this is only about the single-patient check in the LeafClass Get* queries – not about the ability to change patientId, which we understand is intended (section 3.57.4.1.3.4).

What happens first

An Update Document Set [ITI-57] creates v2 (Approved, patient B) and deprecates v1 (patient A). Changing patientId across versions is explicitly allowed – section 3.57.4.1.3.4: “Two versions … are not required to carry the same Patient ID.” Both versions share the same uniqueId / logicalID (ITI TF-3 section 4.1.5).

The consequence at query time

A GetDocuments [ITI-18] by uniqueId (or logicalID) with $MetadataLevel=2 returns both versions, so the registry rejects it with XDSResultNotSinglePatient (LeafClass single-patient footnote, section 3.18.4.1.2.3.7.5).

Yet the same supplement tells consumers to expect this. Section 3.18.4.1.2.5.1:

“Patient ID agreement is not guaranteed on Deprecated objects.”
“Multiple DocumentEntry objects may be returned carrying the same uniqueId … At most one version shall have a non-Deprecated status.”

Open issue MV037 even notes that uniqueId queries became “awkward” under versioning, resolved only by “adding footnotes.”

Net effect: once patientId differs across versions, no single LeafClass Get* query can return the full version history – only per-version entryUUID queries survive the check.

Questions

• Is this known, and is a Change Proposal planned to reconcile the single-patient check with the versioning + Patient-ID-change capability?
• Should the check apply only to non-Deprecated objects (aligning section 3.18.4.1.2.3.7.5 with section 3.18.4.1.2.5.1 and section 3.57.4.1.3.4)?
• How do others retrieve a document’s full history after a Patient ID change – iterate per-version entryUUID, or something else?

Thanks!

Kind Regards
Marco