mCSD Queries and searchParams

[IrfanH99]

Section: In the IHE mCSD iGuide version 3.8.0

Issue: The problem that we have ran into is that ITI-90 and the mCSD Supplier CapabilityStatements often list the full set of parameters, some of which will not be used in all Canadian directories (e.g., some Organization implementers may not support searching on partOf because they don't have advanced hierarchy modelling in place in their current directory or use cases).

In some ways, the R2 Conformance Definition is looser than applying SHALL:able-to-populate, allowing more conditional rules that allow vendors who don't support a given thing to not have to demonstrate it or send it in production. How does the R2 conformance expectation for "support" impact mCSD queries?

Proposed Change: Would like additional guidance on search parameters and/or conformance strengths on said searchParams in the CapabilityStatements.

Priority: Medium/High

[lukeaduncan]

@IrfanH99, are there other searchParameters or elements that are an issue with your use case or is it only Organization.partOf? We're discussing at the face to face this week and trying to find a good solution.

[JohnMoehrke]

assigned CP-ITI-1316