From 675699a177b60e2550cdca558823bb619c9c06b9 Mon Sep 17 00:00:00 2001 From: jdar8 <69840459+jdar8@users.noreply.github.com> Date: Wed, 19 Jul 2023 13:57:21 -0700 Subject: [PATCH] 5092 results ordering for mdm link history is incorrect (#5093) * update docs to be more specific * fix ordering when client assigned id doesn't match pid * remove fix ordering when client assigned id doesn't match pid --------- Co-authored-by: justindar --- .../ca/uhn/hapi/fhir/docs/server_jpa_mdm/mdm_operations.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa_mdm/mdm_operations.md b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa_mdm/mdm_operations.md index ac1e1a4fa54..8e9e154e787 100644 --- a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa_mdm/mdm_operations.md +++ b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa_mdm/mdm_operations.md @@ -250,7 +250,10 @@ This operation takes the following parameters: -This operation returns a `Parameters` resource that looks like the following, in the example case where an MdmLink was updated from MATCH to NO_MATCH, with the MDM revisions sorted in *descending* order: +This operation returns a `Parameters` resource that looks like the following, in the example case where an MdmLink was updated from MATCH to NO_MATCH. The MDM revisions are sorted: +* First by golden resource ID in *ascending* order +* Second by source resource ID in *ascending* order +* Third by revision timestamp in *descending* order. If there are any duplication between results returned by a combination of golden resource IDs and source IDs, they will be included only once. So, for example, if there is one historical MDM link for golden resource 123 and source resource 456, and both of these identifiers are in the query, only a single historical entry will be returned.