Jan 2015 Ballot Comment #310

XMLWordPrintableJSON

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

      Although the existing resource definition permits such a usage, the "Person and Linking" section clearly describes the 2 expected scenarios, which do not include the linkage of patient with practioner resources.

      Show
      Although the existing resource definition permits such a usage, the "Person and Linking" section clearly describes the 2 expected scenarios, which do not include the linkage of patient with practioner resources.
    • Clarification

      Comments
      I have concerns with this resource in general. In Canada, we never associate a Practitioner in the healthcare system with their interactions as a Patient within the healthcare system. This may be different in different countries. Also, this resource seems a large step backwards, FHIR originally had a Person in addition to Patient and Practitioner and the implementors said it made implementation needlessly complex. Patient already has a link class to link together multiple occurrences for an single individual, what use case is this solving? If it is necessary to link a Practitioner to their occurence as a Patient, then Practitioner should have a link (and I would need to be convinced that this was really something that the moajority of applications do)

      Grahame's Comments
      need to add a little more documentation, but also, this is not the same as we had - Person is solving a different problem

      Disposition
      Not Persuasive

      Disposition Comment
      Person allows linking a variety of types. It can be used to link multiple Patient records, link Patient and RelatedPerson records. It can also be used to link multiple Practitioner records. Will add language to make these multiple potential uses.

            Assignee:
            Unassigned
            Reporter:
            Andy Stechishin (Inactive)
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: