Clarify allowed user-specified code comparison operations

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • Clinical Quality Language (FHIR)
    • 1.5 [deprecated]
    • Clinical Decision Support
    • Authors Guide
    • Filtering with Terminology
    • Hide

      Agreed, clarify that the allowed terminology operations of `in` and `~` (equivalent) can be specified (and link to the terminology operators section)

      Show
      Agreed, clarify that the allowed terminology operations of `in` and `~` (equivalent) can be specified (and link to the terminology operators section)
    • Chris Moesel/Isaac Vetter: 15-0-0
    • Clarification
    • Non-substantive

      The text says:

      When the code path is specified, the code comparison operation can be specified as well

      I expect it is still restricted to only in and {} (as opposed to not in, !, or even  = (although I don't think that's really defined well for code anyway)). Should we clarify that in the spec?

            Assignee:
            Bryn Rhodes
            Reporter:
            cmoesel
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: