Jan 2015 Ballot Comment #111

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Modeling & Methodology
    • Datatypes
    • 1.14.0.1
    • Hide

      Technically, it is the type that permits these things to exist - allowing an id and extensions is done at the type level. ?However, the revised wording isn't wrong and if it helps make things clearer/more understandable, happy to make the change

      ?

      2015-01-19 MnM Q2 Craig/Bill 16-0-0

      Show
      Technically, it is the type that permits these things to exist - allowing an id and extensions is done at the type level. ?However, the revised wording isn't wrong and if it helps make things clearer/more understandable, happy to make the change ? 2015-01-19 MnM Q2 Craig/Bill 16-0-0
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording
      In addition to having a value as described above, these primitive data types can also have an identity (e.g. xml:id), and they may have extensions like any other element in a resource.

      Proposed Wording
      In addition to having a value as described above, elements using these primitive data types can also have an identity (e.g. xml:id), and they may have extensions like any other element in a resource.

      Comments
      The original statement sounds like the "data type" can have an id, but isn't it really a specific resource data element (e.g., Observation valueDateTime) that can have the id? I don't think the data type (e.g., timestamp) itself has an id, does it?

      Grahame's Comments
      yes, it does, but this could be clearer

            Assignee:
            Unassigned
            Reporter:
            david_tao
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: