Move Patient.animal to a standard extension - 2018-Jan Core #272

XMLWordPrintableJSON

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

      After community consultation we did not get any negative feedback to move the animal components to a standard extension we will make this change as voted on in New Orleans.

      Including the descritve text on veterinary usage in the notes section of patient.

      Show
      After community consultation we did not get any negative feedback to move the animal components to a standard extension we will make this change as voted on in New Orleans. Including the descritve text on veterinary usage in the notes section of patient.
    • Cooper Thompson/Simone Heckmann:5-0-0
    • Enhancement
    • Non-compatible
    • STU3

      Comment:

      *Cooper Thompson 1/10/2018 9:31 AM

      Do we really feel that it is useful to include Patient.animal as a part of the base spec? That is a modifier element, and in practice, I expect nearly all (human-centric) implementations will ignore the fact that it is a modifier, and thus not strictly be spec-compliant. If everyone is going to intuitively do the wrong thing per the spec, that seems like a problem with the spec. My suggestion is to remove Patient.animal from the core spec and make it standard extension.

      See also 14393

      Summary:

      Move Patient.animal to a standard extension

            Assignee:
            Unassigned
            Reporter:
            Cooper Thompson
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: