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

The query for notify pull wouldn't be in the Topic, only the query "name" would

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR R5 Subscriptions Backport (FHIR)
    • 1.2.0-ballot
    • FHIR Infrastructure
    • STU
    • Notifications
    • Hide

      Propose accepting the change as requested.

      Show
      Propose accepting the change as requested.
    • Clarification
    • Non-substantive

    Description

      https://hl7.org/fhir/uv/subscriptions-backport/2024Jan/notifications.html#adding-queries-to-notifications

      "In this guide, the query and coded information are paired together as a string and a Coding respectively. There are two places that need to contain this data: the topic definition and the notification itself."

       

       

      This implies that both the query string and the coded name for the query will be in the Topic.  The query string MAY be something that can only be determined at run time.  This is how I would describe it:

       

      "In this guide, the query and a coded description of the data provided by the query are paired together as a string and a Coding respectively. For example, you may have a coded description of the query of "patient-problem-list", and an associated query of /Condition?patient=<patient ID>&category=http://terminology.hl7.org/CodeSystem/condition-category|problem-list-item. 

      The topic definition would contain the coded description of the queries, and MAY contain the query string itself.  The notification will contain both the coded description and the query string.  In cases where the query string does not depend on parameters determined at run time, it SHOULD be included in the topic definition."

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            cooper.thompson Cooper Thompson
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: