{description: 'Determine the set relationship between the memberships of two value sets: whether they contain the same codes, whether one is a subset or superset of the other, whether they overlap, or whether they are disjoint. The comparison is over what the value sets *mean* (the set of codes each includes), not over the structure of the ValueSet resources.\n\nThe two value sets are referred to as ''this'' and ''other''. At the type level (`POST /ValueSet/$compare`), supply each one as either an inline resource (`thisValueSet` / `otherValueSet`) or as a canonical URL the server resolves (`thisUrl` / `otherUrl`). At the instance level (`POST /ValueSet/[id]/$compare`), the value set addressed in the URL is ''this'', and only ''other'' need be supplied.\n\nThe server decides from the value set definitions (the `compose`) wherever it can — this is cheap and exact, and is version-aware. Where the definitions are too complex to compare directly, it expands both value sets and compares the resulting code lists. Either way the answer is reported in the `result` output parameter. When the relationship cannot be established — for example a value set has no `compose`, an expansion is unclosed or infinite, an expansion fails, or the definitions combine in ways the server cannot soundly reason about — the result is `indeterminate` rather than a guess.\n\nIf the `diagnostics` parameter is true, the server additionally reports the codes that differ (`common-codes`, `missing-codes`, `extra-codes`) and whether it had to expand the value sets to reach its conclusion (`performed-expansion`). This operation does not change server state.', package_name: hl7.fhir.uv.tools, name: ValueSetCompare, type: 'true', package_version: 1.2.0, class: operation, kind: operation, url: 'http://hl7.org/fhir/tools/OperationDefinition/ValueSet-compare', version: 1.2.0}