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

Clarify search by date precision conformance expectations

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive with Modification
    • US Core (FHIR)
    • 3.1.0
    • Cross-Group Projects
    • Profiles and Extensions
    • 2.1.1.11
    • Hide

      Provide guidance for client search

      Precision to the day for elements of datatype date{{}}

      Precision to the "the full timezone search" for datetype of dateTime or Instant

      which servers SHALL support

      (obviously applies to periods too)

      Show
      Provide guidance for client search Precision to the day for elements of datatype date{{}} Precision to the "the full timezone search" for datetype of dateTime or Instant which servers SHALL support (obviously applies to periods too)
    • Brett Marquard/Eric Haas: 5-0-4
    • Clarification
    • Compatible, substantive

    Description

      Dates can be searched at multiple levels of precision, but there doesn't appear to be conformance expectations regarding which SHALL be supported by servers / clients.  Note that there is no discovery mechanism for clients to determine which forms are supported by a server, so having a fixed set of forms that SHALL be supported by servers needs to be considered.

      "Any degree of precision can be provided" – does that mean all must be supported by a server, or is that just a statement on what constitutes a valid date search?  http://hl7.org/fhir/R4/search.html#date 

      Attachments

        Activity

          People

            Unassigned Unassigned
            rscanlon Robert Scanlon
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: