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

Allow event-basedOn to be used on MedicationAdministration

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - No Change (View Workflow)
    • Priority: Medium
    • Resolution: Not Persuasive
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      R4
    • Work Group:
      Pharmacy
    • Related Artifact(s):
      MedicationAdministration
    • Grouping:
    • Resolution Description:
      Hide

      In R4, MedicationAdministration has 'request', which covers part of the basedOn semantics.  It's possible to pre-adopt the R5 MedicationAdministration.basedOn with the standard pre-adoption mechanism.  We've recommended to pharmacy that MedicationAdministration.basedOn should extend to include MedicationRequest and ServiceRequest in addition to CarePlan.

      Given that there are other ways to meet the R4 requirement, we don't feel this is an appropriate change to include as a technical correction.

      Pharmacy discussed this and will be making a separate Jira issue to discuss a change to basedOn and/or request for R5.  When that happens, this use-case be met using the R5 pre-adoption extension mechanism.  We agree with the rationale for not making this change to the event-basedOn extension because currently the semantics are split between basedOn and request.

      Show
      In R4, MedicationAdministration has 'request', which covers part of the basedOn semantics.  It's possible to pre-adopt the R5 MedicationAdministration.basedOn with the standard pre-adoption mechanism.  We've recommended to pharmacy that MedicationAdministration.basedOn should extend to include MedicationRequest and ServiceRequest in addition to CarePlan. Given that there are other ways to meet the R4 requirement, we don't feel this is an appropriate change to include as a technical correction. Pharmacy discussed this and will be making a separate Jira issue to discuss a change to basedOn and/or request for R5.  When that happens, this use-case be met using the R5 pre-adoption extension mechanism.  We agree with the rationale for not making this change to the event-basedOn extension because currently the semantics are split between basedOn and request.
    • Resolution Vote:
      Melva Peters / Jean Duteau: 12-0-0

      Description

      Given that the basedOn element was added to MedicationAdministration in R5, it should be possible to use the event-basedOn extension in R4 to represent the basedOn information.

       

      Also, please consider this item for inclusion in R4B.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              bryn.rhodes Bryn Rhodes
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: