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

Why having an Instant data type for Observation.effective[x], when a DateTime is allowed as well?

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Orders & Observations
    • Observation
    • Hide

      The effectiveInstant requires a higher level of precision (SHALL have at least be precise to the seconds) than a effectiveDateTime, where a profile can address what is actually needed.  This has been defined in data type definitions, providing enough guidance for the implementer to determine when they need the flexibility of level of precision with dateTime, or always require to be as precise as at least seconds.   This could then be further clarified in the profile used for the specific use case where needed.

      Show
      The effectiveInstant requires a higher level of precision (SHALL have at least be precise to the seconds) than a effectiveDateTime, where a profile can address what is actually needed.  This has been defined in data type definitions, providing enough guidance for the implementer to determine when they need the flexibility of level of precision with dateTime, or always require to be as precise as at least seconds.   This could then be further clarified in the profile used for the specific use case where needed.

    Description

      Why having an Instant data type for Observation.effective[x], when a DateTime is allowed as well? The difference looks like a difference in accuracy requirements. Why does this justify an additional field?

      This ticket is submitted on behalf of bvdh

      Attachments

        Activity

          People

            Unassigned Unassigned
            ana_kostadinovska Ana Kostadinovska
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: