Observation.subject is too narrow

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Orders & Observations
    • Observation
    • Hide

      promote focal-subject extension to element focalSubject 0..1 with Reference(Any) as a DSTU element

      add element comment to discourage use of Observation if an appropriate resource elements exist (providing an example or two) and the caveat that in the future will look at possibility of a new resource to handle evaluation of observation or other resources.

      Show
      promote focal-subject extension to element focalSubject 0..1 with Reference(Any) as a DSTU element add element comment to discourage use of Observation if an appropriate resource elements exist (providing an example or two) and the caveat that in the future will look at possibility of a new resource to handle evaluation of observation or other resources.
    • Eric Haas/Bob Milius: 5-0-7
    • Enhancement
    • Compatible, substantive
    • STU3

      It's possible to make observations about other observations (e.g. assertions of clinical significance/importance and other interpretations that happen at a time that's separate from when the original obsrevation was made). It's also possible to make observations about practitioners, organizations and all sorts of other things. This has been done in v2 (with OBXs accompanying all sorts of things in v2 message structures) and it will be needed in the FHIR space too. There will need to be guidance on when to use observations vs. extensions. The guidance is that observations stand alone and capture information about the provenance of the assertion (who made it, when, how, etc.).

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Lloyd McKenzie
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: