Jan 2015 Ballot Comment #81

  • 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

      Provide further clarification and guidance on the usage of the status history sub-component.

      "This removes the requirement of the server to support FHIR versioning for access to this information..."

      Expectation of this relationship to the periods also.

      Show
      Provide further clarification and guidance on the usage of the status history sub-component. "This removes the requirement of the server to support FHIR versioning for access to this information..." Expectation of this relationship to the periods also.
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording \\statusHistory

      Comments
      When I reviewed the specification with some of our application developers, they had a hard time understanding how this would be implemented/used by disparate systems.

      Is there more use case information around this that could be provided?
      Could FHIR versioning be sufficient for supporting these use cases?

      Grahame's Comments
      no opinion

            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