Registry behavior regarding unexpected parameters in ITI-18 (Stored Query)
Gregorio Canal
Morning ITI,
During the execution of our project, we encountered a scenario where a Document Consumer is performing an ITI-18 (Registry Stored Query) transaction including parameters that are not defined in the technical frameworks for the requested query type.
For instance, in a GetDocuments query, the client is adding an extra parameter (e.g., status) alongside the mandatory ones defined in the integration profile.
We have reviewed the IHE TF-2 specifications, but we couldn't find a definitive instruction on how the Document Registry should handle these unexpected parameters. Specifically:
Should the Registry ignore the additional parameters and process the query based only on the valid ones?
Should the Registry return an error (such as
XDSRegistryError)?
In our view, the Registry should trigger an error. If the Registry ignores the unexpected parameters, the Document Consumer might misinterpret the results, assuming the filter was applied when it actually was not.
Could you please clarify the expected behavior or point us to the specific section of the Technical Framework that addresses this?
Best regards,
Gregorio
John Moehrke
--
You received this message because you are subscribed to the Google Groups "IHE ITI Technical Committee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ititech+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ititech/CALqztJPe1%3D0qDRESxLDaramkG40oGgGnPKUFFHobH9iU3aAFEg%40mail.gmail.com.