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

US Core MedicationDispense Profile

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Medium Medium
    • US Core (FHIR)
    • 7.0.0-ballot
    • Cross-Group Projects
    • US Core MedicationDispense Profile
    • 13.135.1
    • Hide

      Regarding the question whether Medication.context should be 1..1

      By design, very few US Core Profiles elements are mandatory ( i.e., min =1 ), and many of those mandatory elements inherit that cardinality from the base specification.  Most Must Support elements are min=0 because this allows the US Core Profile to be used in many contexts, and in some of those contexts, the information is incomplete. Implementers need this flexibility when the data is not available and still comply with the specification.

      Show
      Regarding the question whether Medication.context should be 1..1 By design, very few US Core Profiles elements are mandatory ( i.e., min =1 ), and many of those mandatory elements inherit that cardinality from the base specification.  Most Must Support elements are min=0 because this allows the US Core Profile to be used in many contexts, and in some of those contexts, the information is incomplete. Implementers need this flexibility when the data is not available and still comply with the specification.

    Description

      In the Medication Dispense Profile, under "Each MedicationDispense Must Support", #1 is "the encounter associated with the dispense". The profile references "context" of US Core Encounter Profile" 0..1

       

      Should this be 1..1?

      It seems there would be a healthcare visit of some sort (even a telephone call) to trigger the medication order and then subsequent dispense. There may be many MedicationDispense associated with one encounter but each individual prescription would point back to the encounter.

      Attachments

        Activity

          People

            Unassigned Unassigned
            rbaker@acc.org Rebecca Baker
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: