Don't require subsecond precision

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Request Context Change
    • Hide

      We will remove references to "subsecond accuracy" in the timestamp parameters. It isn't clear as is what subsecond means and what the timestamp should look like. Following the ISO format should be enough guidance especially since the timestamp (used for ordering messages) handles edge cases already.

      Show
      We will remove references to "subsecond accuracy" in the timestamp parameters. It isn't clear as is what subsecond means and what the timestamp should look like. Following the ISO format should be enough guidance especially since the timestamp (used for ordering messages) handles edge cases already.
    • Eric Martin / Bill Wallace: 8-0-0
    • Correction
    • Non-compatible

      FHIR itself doesn’t require second accuracy, it would be very hard to go to subsecond accuracy - and this also requires clock synchronization, which is unrealistic.. Even when a clock is synchronized, it is unlikely to be this accurate. Possibly consider “seconds ago” type responses?

            Assignee:
            William Maethner
            Reporter:
            Jenni Syed
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: