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

Inconsistencies between profiles and search parameters

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci CRD (FHIR)
    • 2.0.0
    • Financial Mgmt
    • (many)
    • Hide

      Will keep mustSupport as is and retain the search in the prefetch query.  However, we'll add a dagger note that says:

      "serviceProvider is not a mustSupport element.  This search parameter only needs to be supported by the server if they support the serviceProvider element."

      Show
      Will keep mustSupport as is and retain the search in the prefetch query.  However, we'll add a dagger note that says: "serviceProvider is not a mustSupport element.  This search parameter only needs to be supported by the server if they support the serviceProvider element."
    • Clarification
    • Non-substantive

    Description

      prefetch guidelines include an expectation to support certain search parameters, however, the data elements being searched aren't necessarily expected to be supported, which doesn't make much sense.  We should either drop the parameters where the elements aren't supported or add them to the profiles as mustSupport.

      Specific issue:

      • Encounter.serviceProvider

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: