Clarify the purpose of "instant" and its use by clinical vs. administrative resources

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Modeling & Methodology
    • Datatypes
    • 2.23.0.1
    • Hide

      Clarify that the instant type is suitable for use anywhere that a work group decides that a full instant of time is required (as opposed to allowed, which is what dateTime covers)

      Show
      Clarify that the instant type is suitable for use anywhere that a work group decides that a full instant of time is required (as opposed to allowed, which is what dateTime covers)
    • Grahame Grieve/Ron Shapiro: 2-0-0
    • Clarification
    • Non-substantive
    • STU3

      This comment was entered on behalf of the SAMHSA OCP project (Ken Salyards):

      Please clarify if the instant/UTC time stamp is only to be used by the server (e.g. Resource.meta.lastUpdated) or whether it can be used by other resources for effective time (e.g. Appointment.start, Appointment.end).

      It's confusing why Appointment.start/end are "instant" while Observation.effective is not allowed this data type. The Observation timestamp is often system-generated (from a device) similar to AuditEvent. Appointment.start/end could be manually entered.

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            greg_staudenmaier, Ioana Singureanu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: