Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-24350

Topic.canFilterBy.matchType needs to be explicit what default behavior is

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Topic (see SubscriptionTopic) [deprecated]
    • Hide

      We will

      • rename "matchType" to "modifier" and
      • make it 0..1;
      • meaning when missing is: search without a modifier.

      This will clarify the correspondence between subscription matching and search.
       

      Show
      We will rename "matchType" to "modifier" and make it 0..1; meaning when missing is: search without a modifier. This will clarify the correspondence between subscription matching and search.  
    • Michael Donnelly/Dennis Patterson: 7-0-2
    • Enhancement
    • Non-compatible
    • R5

    Description

      Topic.canFilterBy.matchType needs to specify what the default behavior is if it is not populated. Discussion: should we require it or should it default to the default for that parameter type normally? Document expectations.

      Attachments

        Activity

          People

            ginocanessa Gino Canessa
            jenni_syed Jenni Syed (Inactive)
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: