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

Can't query MedicationKnowledge instances that are FormularyDrugs

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive
    • US Da Vinci Drug Formulary (FHIR)
    • 1.0.1
    • Pharmacy
    • Formulary Drug
    • Hide

      agree with not using search by _profile.

      As part of the Patient Access API, the client will have the PlanId and can query the MedicationKnowledge with the extension that includes PlanID.

      For the shopping experience, this would only be relevant for a client system that does not know a PlanID, but only wants resources associated with a formulary.  This can be done with MedicationKnowledge?PlanID:missing=false (assuming the server supports ":missing")

       

      Show
      agree with not using search by _profile. As part of the Patient Access API, the client will have the PlanId and can query the MedicationKnowledge with the extension that includes PlanID. For the shopping experience, this would only be relevant for a client system that does not know a PlanID, but only wants resources associated with a formulary.  This can be done with MedicationKnowledge?PlanID:missing=false (assuming the server supports ":missing")  
    • David Hill / Corey Spears : 6-0-0
    • Clarification
    • Non-substantive
    • current

    Description

      Since query by _profile is not required, there is currently no way to query for MedicationKNowledge instances that are FormularyDrugs.  The only required element of the Formulary drug that is queryable is PlanID, and this can only be searched by exact match.   So, a client can distinguish a formularyDrug instance from another use of MedicationKNowledge following retrieval – the existence of the PlanID extension – but there is no way to query for them.   So, retrieving by code might return extraneous instances.

      If this is a bug: One possibility is requiring support for the :missing qualifier on the PlanID search parameter.  The would enable a search:
      <fhir-base>/MedicationKnowledge?PlanID:missing=false
      that would do the trick.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              saul_kravitz Saul Kravitz
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: