2015May core #535 - Require server behavior for merged patients.

XMLWordPrintableJSON

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

      The subsequent behaviour of patient merge/linking on other operations (eg searching etc) is currently undefined.

      This has been done poorly in the past and requires extensive experimentation before being included in the specification.

      We have addd notes requesting implementer feedback on how they would like the change to be implemented.

      This is to be added to the section on Merging Patients.

      Show
      The subsequent behaviour of patient merge/linking on other operations (eg searching etc) is currently undefined. This has been done poorly in the past and requires extensive experimentation before being included in the specification. We have addd notes requesting implementer feedback on how they would like the change to be implemented. This is to be added to the section on Merging Patients.
    • Brian Postlethwaite/Alex de Leon:5-0-0
    • Enhancement
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: This specification does not specify merge functionality: if multiple patient records are found to be duplicates, they can be linked together, as described above.

      Comment:

      This language leaves multiple alternatives for server behavior when receiving a merged-off resource ID for a patient. Suggest defining required behavior to redirect to current patient with a notification of content location change.

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

              Created:
              Updated:
              Resolved: