Jan 2015 Ballot Comment #142

  • 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 with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Administration
    • RelatedPerson
    • 5.2.1
    • Hide

      Happy to change the text as suggested without the example

      "For keeping information about people for contact purposes for a patient, use a Patient's Contact element.
      Some individuals may serve as both a Patient's Contact and a Related Person."

      Show
      Happy to change the text as suggested without the example "For keeping information about people for contact purposes for a patient, use a Patient's Contact element. Some individuals may serve as both a Patient's Contact and a Related Person."
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording
      For keeping information about persons for contact purposes for a patient, use a Patient's Contact element instead.

      Proposed Wording
      For keeping information about persons for contact purposes for a patient, use a Patient's Contact element. Some persons may serve as both a Contact and a Related Person (e.g., caregiver).

      Comments
      Some persons can be both a related person and a contact. Especially the patient's spouse could easily be both a contact and a person involved in the patient's care. They should be allowed to be represented in both resources. The proposed wording allows for that possibility.

      Grahame's Comments
      ok

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

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

                Created:
                Updated:
                Resolved:

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