Rename/redefine Bundle.timestamp - 2018-May Core Norm Infrastructure #19

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Bundle
    • 2.34.3, 2.34.7
    • Hide

      Clarify that different pages MAY have different timestamps but need not. Clarify that timestamp = time the Bundle was assembled.

      Show
      Clarify that different pages MAY have different timestamps but need not. Clarify that timestamp = time the Bundle was assembled.
    • Grahame Grieve/Josh Mandel: 6-0-0
    • Non-substantive
    • STU3

      Existing Wording: timestamp element

      Comment:

      • searchset : the time that the search set was assembled. Note that different pages will have different timestamps

      Comment:

      "timestamp" isn't very descriptive - we don't know what it is a timestamp of. Suggest "created" or "assembled". This is especially true in uses like document or collection.

      Is it required that different search pages will have different timestamps? Isn't this determined by implementation? (e.g. If I perform the entire query on the first search, and only return it one page at a time, I'd thing that the timestamp would be the initial query.)

      Why should "the timestamp value be dreate than the lastUpdated and other timestamps in the resources in the bundle"? If it is a collection or document that references resources on the server, then the resources could have been modified since being put in the bundle, and would thus have a newer timestamp. Otherwise, it seems that the timestamp is more than the time of assembly.

      Summary:

      Rename/redefine Bundle.timestamp

            Assignee:
            Unassigned
            Reporter:
            Elliot Silver
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: