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

Loosen the binding requirements on Timing.repeat.when

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Modeling & Methodology
    • Datatypes
    • Hide

      There is a difference between defining a "trigger" for an event - essentially the "PRN" in a PRN med and defining a code for the regularly occurring time of day when something should occur. These concepts should be worked into the Dosage.prn[x] structure to allow indication of a time before (or after) an event.

      Show
      There is a difference between defining a "trigger" for an event - essentially the "PRN" in a PRN med and defining a code for the regularly occurring time of day when something should occur. These concepts should be worked into the Dosage.prn [x]  structure to allow indication of a time before (or after) an event.
    • Grahame Grieve/Ron Shapiro: 2-0-0

    Description

      The timing datatype has a required binding for timing.repeat.when - I think this should be loosened to extensible or example. There is a lot of variety that could consitute the definiton of when: "Regular life events the event is tied to". Right the provided valueset is rather small. I recommend loosening the binding and not just adding more values to the valueset as there is too much variability to capture 100% of all possible values in a required binding.

      Examples of some life events Epic can capture in relation to when a medication should be given: during travel, for an appointment, for a procedure, before sex, before exercise.

      Attachments

        Activity

          People

            Unassigned Unassigned
            dfriend Danielle Friend
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: