Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-20771

Add Person.deceased, Person.maritalStatus and Person.communication

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Triaged (View Workflow)
    • Priority: Medium
    • Resolution: Unresolved
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      STU3
    • Work Group:
      Patient Administration
    • Related Artifact(s):
      Person
    • Related Section(s):
      8.18.3
    • Change Category:
      Enhancement

      Description

      The Person resource needs additional information to solve common use cases described in the resource definition.

      • Person.deceased
      • Person.maritalStatus
      • Person.communication.

      As it turns out two of these proposition has been raised before by Alexander Henket

      • 17319 Summary: Person.maritalStatus missing
      • 17318 Summary: Person.deceased is missing

      Both deceased and maritalStatus change to the Person resource is refused by the workgroup on the basis: "The Person resource is not intended to be the demographic store for all patients/people.
      Its core usage is for the very basics and linkages."

      I think this explanation misses vital points in the description of the Person resource, its intended purpose and it's actual use by implementers. The description of the resource states plainly: "Demographics and administrative information about a person independent of a specific health-related context."

      The first two use-cases mentioned:
      "A set of demographics that can be used to co-ordinate the maintenance of this de-normalized information across practitioners, patients and/or related persons
      e.g. link known resources of the different types together within a system

      A state/network based Master Person Index"

      This is the exact opposite of the reasoning for rejecting these changes, I think this is a mistake that will cripple the standard for these central use-cases. The master Person Index is a central part of the healtcare sector in most European countries.

      I wan to move for the addition of these elements to the Person resource so that the resource can be used (without adding extentions) for implementing the two most central use-cases stated for the resource.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            thomiz Thomas Tveit Rosenlund
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: