Section Number Identify the most specific section number the issue occurs (e.g. 4.1.2)
3.44.4.1.2.1
Issue Describe your issue. Don't write a book, but do include enough to indicate what you see as a problem.
QEDm specifies which search parameters for which support is required, and also which combinations of parameters much be supported. This is good. However, it does not specify for which parameters multiple values should be supported (either AND or OR).
Proposed Change Propose a resolution to your issue (e.g., suggested new wording or description of a way to address the issue). The committee might simply accept your suggested text. Even if they don't, it gives a good sense of what you are looking for. Leaving this blank means you can't imagine how to resolve the issue, which makes it easier for the committee to admit they can't imagine how to resolve it either and leave it unresolved.
Consider specifying which search parameters should require servers to support multiple values. See https://build.fhir.org/ig/HL7/US-Core/general-guidance.html#search-syntax for how this is done in US Core, and http://hl7.org/fhir/us/core/STU3.1.1/SearchParameter-us-core-location-address-state.html for an example search parameter from US Core.
Priority:
- Medium: Significant issue or clarification. Requires discussion, but should not lead to long debate.
Section Number Identify the most specific section number the issue occurs (e.g. 4.1.2)
3.44.4.1.2.1
Issue Describe your issue. Don't write a book, but do include enough to indicate what you see as a problem.
QEDm specifies which search parameters for which support is required, and also which combinations of parameters much be supported. This is good. However, it does not specify for which parameters multiple values should be supported (either AND or OR).
Proposed Change Propose a resolution to your issue (e.g., suggested new wording or description of a way to address the issue). The committee might simply accept your suggested text. Even if they don't, it gives a good sense of what you are looking for. Leaving this blank means you can't imagine how to resolve the issue, which makes it easier for the committee to admit they can't imagine how to resolve it either and leave it unresolved.
Consider specifying which search parameters should require servers to support multiple values. See https://build.fhir.org/ig/HL7/US-Core/general-guidance.html#search-syntax for how this is done in US Core, and http://hl7.org/fhir/us/core/STU3.1.1/SearchParameter-us-core-location-address-state.html for an example search parameter from US Core.
Priority: