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

`date from` does not specify how to truncate the timezone offset from DateTime

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • Clinical Quality Language (FHIR)
    • 1.4
    • Clinical Decision Support
    • Appendix B - Reference
    • Hide

      Agreed, clarify this sentence:

      When extracting the Time from a DateTime value, implementations should normalize to the timezone offset of the evaluation request timestamp.

      to say:

      When extracting the Date or Time from a DateTime value, implementations should normalize to the timezone offset of the evaluation request timestamp.

      Show
      Agreed, clarify this sentence: When extracting the Time from a DateTime value, implementations should normalize to the timezone offset of the evaluation request timestamp. to say: When extracting the Date or Time from a DateTime value, implementations should normalize to the timezone offset of the evaluation request timestamp.
    • Chris Moesel/Jen Seeman: 17-0-5
    • Clarification
    • Non-substantive

    Description

      Since dates don't have a timezone, but DateTimes do, it is unclear to me how the `date from` operation deals with truncating the timezone. Do we need to normalize to Zulu first before taking the date, or do we take the date components from the DateTime at the currently specified timezone? What if there is no timezone (although that's the trivial case)?

      Attachments

        Activity

          People

            bryn.rhodes Bryn Rhodes
            ewout Ewout Kramer
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: