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

MedicationDispense Scope of use Conflicts

    XMLWordPrintableJSON

Details

    • Change Request
    • Resolution: Persuasive with Modification
    • Highest
    • US Core (FHIR)
    • 6.0.0-ballot
    • Cross-Group Projects
    • STU
    • US Core MedicationDispense Profile
    • Hide

      The scope for US Core MedicationDispense is the medications Fill Status and we disagree that the definition is misleading or that implementers will misinterpret it to mean that all medication resource should have a fill status.

      1) The citation

       “state of a medication with regards to dispensing or other activity. (e.g., dispensed, partially dispensed, not dispensed)” 

       

      is taken directly from USCDI v3 and used to make the association to the corresponding USCDI Fill Status clear.   However, the statement by the commenter that 

      The resource is in fact an event that occurs, not the state of a medication.

      omits the key context - "dispensing".

       

      2) Will change whenHandedOver from min =1 to min =0  +  an invariant: see FHIR-40205

       

      Show
      The scope for US Core MedicationDispense is the medications Fill Status and we disagree that the definition is misleading or that implementers will misinterpret it to mean that all medication resource should have a fill status. 1) The citation  “state of a medication with regards to dispensing or other activity. (e.g., dispensed, partially dispensed, not dispensed)”    is taken directly from USCDI v3 and used to make the association to the corresponding USCDI Fill Status clear.   However, the statement by the commenter that  The resource is in fact an event that occurs, not the state of a medication. omits the key context - "dispensing".   2) Will change whenHandedOver from min =1 to min =0  +  an invariant: see  FHIR-40205  
    • Eric Haas/Brett Marquard: 13-0-1
    • Correction
    • Non-substantive

    Description

      Currently the profile claims that the medicationdispense represents the "state of a medication with regards to dispensing or other activity". The resource is in fact an event that occurs, not the state of a medication. Using this verbiage could be misleading to implementers in that a medication resource should in fact have a medicationdispense. A mediationdispense event, should be representative of a medicationrequest action that has occurred.

      Either the scope of the profile needs changed to only dispensed medications or the requirement for a whenHandedOver needs to be dropped. Currently the constraints allow for all status - only 1 of which should have a "whenhandedover" datetime.

      Recommend that scope and elements be reevaluated.

      Attachments

        Issue Links

          is voted on by

          Ballot Vote - The designation of a comment about a specification as related to an overall Ballot Submission BALLOT-46331 Negative - Joseph R. Kelly : 2023-Jan-FHIR US CORE R5.1.0 STU

          • Balloted

          Ballot Vote - The designation of a comment about a specification as related to an overall Ballot Submission BALLOT-46719 Negative - Rebecca Baker : 2023-Jan-FHIR US CORE R5.1.0 STU

          • Balloted

          Ballot Vote - The designation of a comment about a specification as related to an overall Ballot Submission BALLOT-47084 Negative - Joseph Shook : 2023-Jan-FHIR US CORE R5.1.0 STU

          • Retracted

          Activity

            People

              Unassigned Unassigned
              joseph_kelly Joseph R. Kelly
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: