2015May core #534 - Clarify use case for Location vs. Organization.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Administration
    • Organization
    • 5.5.2
    • Hide

      You are correct that there is ambiguity in what is an organization and what is a location.


      This is our understanding and would appreciate more detail.


      The ambiguity is within the business usage, and not necessarily something that the spec can constrain too much further.

      Show
      You are correct that there is ambiguity in what is an organization and what is a location. This is our understanding and would appreciate more detail. The ambiguity is within the business usage, and not necessarily something that the spec can constrain too much further.
    • Brian/Line 4-0-0
    • Clarification

      Existing Wording: When populating the organization and location hierarchies there is often not a clear distinction between these 2, however to assist in making the decision, Locations are always used for recording where a service occurs, and hence where encounters and observations are associated. The Organization property on these resources may not be the location where the service took place.

      Comment:

      There is some ambiguity regarding when to use a Location vs. an Organization (encounter or observation could reasonably use either one). Recommend that there is more explicit language to determine when to use one vs. the other so that clients know what to expect.

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

              Created:
              Updated:
              Resolved: