ImmunizationRecommendation missing metadata to differentiate forecasting from order

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"

      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"
    • Craig Newman/John roberts: 10-0-0
    • Enhancement

      FHIR 3.0 ImmunizationRecommendation modeling is consistent with information provided by clinical decision support for immunization forecasting. (Definition: A patient's point-in-time immunization and recommendation (i.e. forecasting a patient's immunization eligibility according to a published schedule) with optional supporting justification.- [[1]]. There is no concept comparable to MedicationRequest which includes an .intent metadata element allowing 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. Thus, Immunization, Order should have a ImmunizationRecommendation.intent to indicate the "order" which is distinct from an ImmunizationRecommendation.intent proposal for forecasting and ImmunizationRecommendation.plan for a recommendation to a patient which may or may not be heeded.

      Recommend addition of .intent metadata consistent with MedicationRequest, ProcedureRequest and ReferralRequest to manage CDS, recommendations from providers to patients and orders placed in clinical software.

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

              Created:
              Updated:
              Resolved: