birth/death attributes should be structures

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • Normative
    • Patient
    • Hide

      Using extensions on the primitives, or the root of the patient resource is standard FHIR, and the descriptions of the extensions should be clear as to their purpose. Including a backbone element would not make this any clearer.

      The Patient resource has been extensively implemented with the current structure and would be greatly disruptive to change this modeling design preference at this stage.

      (In the json representation an exension on the primitive sits beside the property)

      Note: If you are at the Cologne WGM and would like to come and discuss this resolution, please come visit PA or on an upcoming conference call.

      Show
      Using extensions on the primitives, or the root of the patient resource is standard FHIR, and the descriptions of the extensions should be clear as to their purpose. Including a backbone element would not make this any clearer. The Patient resource has been extensively implemented with the current structure and would be greatly disruptive to change this modeling design preference at this stage. (In the json representation an exension on the primitive sits beside the property) Note: If you are at the Cologne WGM and would like to come and discuss this resolution, please come visit PA or on an upcoming conference call.
    • Brian Postlethwaite/Andrew Torres:7-0-1
    • Enhancement

      Recommend that birth and death be structures rather than simple types since a number of other attributes will be added pertaining to each. A structure provides a place to add these additional attributes. For instance, birth/deathAddress, birthPlurality, birthOrder, birth/deathCertificateNumber, etc...

      Extending primitives is really not the way to go. Adding sibling attributes would not make it clear that these attributes are related the birth/death data for this patient. For instance, we would propose a birthData attribute of type BackboneElement with two attributes in FHIR core: birthDate and multipleBirth. The would provide a cleaner future extension path for Patient.

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

              Created:
              Updated:
              Resolved: