body site should be a datatype - but used consisitantly throughout the standrard.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Very High
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Orders & Observations
    • BodyStructure
    • Hide

      See PC/OO disposition at Paris meeting Wed, 13 May 2015 05:21:14 : Suggest that referencing BodySite be handled as an extension given that, within the 80%, a simple CodeableConcept is generally sufficient. This may reduce angst. Eric/Rob 16-0-2

      Agree to use BodySite Data Type if that is final resolution in FHIR (rather than BodySite resource), ?This would replace current bodySite and laterality elements.

      Show
      See PC/OO disposition at Paris meeting Wed, 13 May 2015 05:21:14 : Suggest that referencing BodySite be handled as an extension given that, within the 80%, a simple CodeableConcept is generally sufficient. This may reduce angst. Eric/Rob 16-0-2 Agree to use BodySite Data Type if that is final resolution in FHIR (rather than BodySite resource), ?This would replace current bodySite and laterality elements.
    • Fred Behlen/Kevin O'Donnell: 4-0-0
    • Enhancement
    • Non-compatible
    • DSTU1 [deprecated]

      body site should be a datatype - but used consisitantly throughout the standard. including in imaging and medicationadministration resource where I think it would be useful.

            Assignee:
            Unassigned
            Reporter:
            Eric Haas
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: