2015May core #901 - Make managing organization 0..*?

XMLWordPrintableJSON

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

      The detailed description of this property will be updated to better describe the usage of this property.

      It does reflect the "owner" of the record, and when considered via messaging can be known as who created and manages the content.

      The cardinality is to remain as 0..1 to ensure there is no ambiguity as to who is responsible for maintaining this record.

      (This clarification is in the comments section for this property)

      Show
      The detailed description of this property will be updated to better describe the usage of this property. It does reflect the "owner" of the record, and when considered via messaging can be known as who created and manages the content. The cardinality is to remain as 0..1 to ensure there is no ambiguity as to who is responsible for maintaining this record. (This clarification is in the comments section for this property)
    • Peter Bernhardt/Brian Postlethwaite:8-0-0
    • Enhancement
    • Non-substantive
    • Yes
    • DSTU1 [deprecated]

      Existing Wording: Patient.managingOrganization

      Comment:

      Can there only be one managing organization? How does this address a continuum of care use case? Should this be left to provenance and not be directly in the patient resource?

            Assignee:
            Unassigned
            Reporter:
            Claude Nanjo (Inactive)
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: