2015May core #897 - Split multi-type attributes into separate attributes

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Infrastructure
    • (NA)
    • General
    • Hide

      Discussion - there would be some advantages and disadvantages to a change like this, but the size of the change is a problem at this point in the process. Defer the decision to a future version, and discuss at the next few connectathons.

      Show
      Discussion - there would be some advantages and disadvantages to a change like this, but the size of the change is a problem at this point in the process. Defer the decision to a future version, and discuss at the next few connectathons.
    • Ewout Kramer / Grahame Grieve : 10-0-0
    • Enhancement
    • Non-substantive

      Comment:

      Suggest re-reviewing whether overloaded attributes should in fact be separate attributes. E.g., Patient.deceased is allowed to be both boolean and dateTime. It seems like there should be a Patient.deceased with a boolean and a Patient.deceasedDateTime with a dateTime. Not sure the cost (more complicated processing logic, difficulty of mapping to a logical model where the attributes will likely be separate) is worth the benefit (use of a shorthand notation to reduce number of attributes).

            Assignee:
            Unassigned
            Reporter:
            Claude Nanjo (Inactive)
            Claude Nanjo (Inactive)
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: