ImmunizationRecommendation missing metadata to specify order details

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Public Health
    • STU
    • ImmunizationRecommendation
    • Hide

      This will be resolved as part of R5 and will not be addressed in R4.

      Our recommendation is that that any immunization order should use the MedicationRequest resource. In order to accomplish this, we will need to make a change to MedicationRequest.basedOn to include a reference to ImmunizationRecommendation. If/When an "ordering immunizations" IG is written, MedicationRequest will be profiled so that immunization orders can only use a MedicationRequest.intent value "order" (or other flavors of an order) but not a "proposal" or "plan". MedicationRequest already contains a dosage element with these concepts in it.

      Show
      This will be resolved as part of R5 and will not be addressed in R4. Our recommendation is that that any immunization order should use the MedicationRequest resource. In order to accomplish this, we will need to make a change to MedicationRequest.basedOn to include a reference to ImmunizationRecommendation. If/When an "ordering immunizations" IG is written, MedicationRequest will be profiled so that immunization orders can only use a MedicationRequest.intent value "order" (or other flavors of an order) but not a "proposal" or "plan". MedicationRequest already contains a dosage element with these concepts in it.
    • Craig Newman/John Roberts: 11-0-0
    • Enhancement

      The FHIR Immunization resource addresses only immunizations that have been administered. The FHIR ImmunizationRecommendation resource addresses only immunization forecasting, such as that provided by a forecasting engine / clinical decision support. The modeling is inconsistent with the was comparable items are modeled in FHIR - e.g., MedicationRequest, ReferralRequest and ProcedureRequest. Each of these resources includes an .intent metadata element that allows reference to "proposal" consistent with clinical decision support forecasting, "plan" consistent with a recommendation a clinician provides to a patient, and "order" consistent with an order placed in EHRs or other clinical software. This is an important distinction since in some practices, the physician sends a prescription (order) to a pharmacy for the patient to pick up, bring back to the practice for it to be administered. To further support immunization orders, ImmunizationRecommendation needs to support doseQuantity and route (which are part of the order). The current metadata only allows specification of a forecast that includes dose number and sequence in a series.

            Assignee:
            Unassigned
            Reporter:
            Floyd Eisenberg
            Floyd Eisenberg
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: