2015May core #183 - Use approach site, not target

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Very High
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Care
    • Procedure
    • 4.8.6
    • Hide

      Group felt that both approach sites and target sites may need to be captured. ?Approach is typically less common than target. ?Either might be pre-coordinated into the Procedure.name.

      Decision:

      On bodySite add a "role" element, datatype "code" 0..1, valueSet "approach|target"

      The 1..1 merely says that, if you specify the bodySite element, you must always have either a code or a reference to a BodySite resource.

      Show
      Group felt that both approach sites and target sites may need to be captured. ?Approach is typically less common than target. ?Either might be pre-coordinated into the Procedure.name. Decision: On bodySite add a "role" element, datatype "code" 0..1, valueSet "approach|target" The 1..1 merely says that, if you specify the bodySite element, you must always have either a code or a reference to a BodySite resource.
    • Jay/Stephen: 8-0-4
    • Enhancement
    • Compatible, substantive
    • DSTU1 [deprecated]

      Existing Wording: Procedure.bodySite - Detailed and structured anatomical location information. Multiple locations

      are allowed - e.g. multiple punch biopsies of a lesion.

      Comment:

      Approach will be more useful than site,

      The names of the procedure will often obviate the need for a specific site. E.g. appendectomy, or Esophagoscopy say the site

      So worry about the 1...1 and how it can always be required.

      Also the difference between Procedure.body.site and procedure body.site.site is not at all clear

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

              Created:
              Updated:
              Resolved: