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

Dosage Timing start date and Duration/Range (Timing data type)

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Modeling & Methodology
    • MedicationRequest
    • Hide

      We will add an 'uncertainDate' extension with datatype Period to the dateTime datatype to allow for the expression of uncertainty.

      This extension can then be used in the boundsPeriod with a period.end that uses this extension.

      Start on 2021-01-15 and continue for 10-15 days would be expressed as:

      Period.start = 2021-01-15
      Period.end.extension[uncertainDate].start = 2021-01-25
      Period.end.extension[uncertainDate].end = 2021-01-30

      Show
      We will add an 'uncertainDate' extension with datatype Period to the dateTime datatype to allow for the expression of uncertainty. This extension can then be used in the boundsPeriod with a period.end that uses this extension. Start on 2021-01-15 and continue for 10-15 days would be expressed as: Period.start = 2021-01-15 Period.end.extension [uncertainDate] .start = 2021-01-25 Period.end.extension [uncertainDate] .end = 2021-01-30
    • Lloyd McKenzie / Ron Shapiro: 3-0-0
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      This is discussed in zulip stream: https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Dosage.20Timing.20start.20date.20and.20Duration.2FRange

      In stream it was asked to raise a Jira issue about this and suggested that the committee should look at adding something to Timing to allow for an optional start date to be specified. 

      The problem:

      We are specifying Dosage Timing (FHIR R4). We have a use case where we have boundsRange, saying for example 10-15 days. But then we also have to give the start date, saying for example start on 2021-01-15. Another use case is similar but with boundsDuration, saying for example 5 days, start on 2021-01-15.

      Timing's bounds[x] is 0..1, so only boundsDuration or boundsRange or boundsPeriod can be used (but not boundsRange or boundsDuration at the same time with boundsPeriod, which is our need). In boundsDuration case, the end date can be calculated but boundsRange case needs at the same time both boundsRange and boundsPeriod. And we think that the users want also support for giving at the same time boundsDuration and boundsPeriod.

      Attachments

        Activity

          People

            marc.duteau Marc Duteau
            mikatuomainen Mika Tuomainen
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: