• Item:operations-top-levelMoreItem:operations-workItem:greenhopper_issue...Item:operations-archiveItem:operations-attach...Item:operations-votesw...Item:operations-subtasksItem:devstatus-cta-listItem:operations-operat...Item:operations-deleteItem:operations-manual...
  • Published
  • AdminItem:operations-fieldsItem:operations-admin-...
  • Item:operations-restore
Item:jira.issue.tools ExportXMLWordPrintableJSON

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

      Further guidance required to explain why this is the case, especially how transfers of care would be handled, and how multiple orgranisations would have their own EpisodeOfCare instances.

      Show
      Further guidance required to explain why this is the case, especially how transfers of care would be handled, and how multiple orgranisations would have their own EpisodeOfCare instances.
    • Enhancement
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording
      managingOrganization - The organization that has assumed the specific responsibilities for the specified duration
      period - The interval during which the managing organization assumes the defined responsibility

      Comments
      It would appear that managingOrganization and period are intended to be tightly coupled. I think it would make sense to incorporate them into the specification as tightly coupled items. E.g.\\managingOrganization
      -> reference
      -> period
      It might also make sense to allow for multiple different managing organizations.

      Grahame's Comments
      makes sense to me

            Panel: location:atl.jira.view.issue.left.context

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

                Created:
                Updated:
                Resolved:

                  Panel: location:atl.jira.view.issue.right.context