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

Add Relationship Type Extension to Patient.contact

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Patient Administration
    • Patient

    • Change Request FHIR-15841 Patient.contact lists guardian as a use case, but code system for Patient.contact.relationship does not include a code for guardian.

    Description

      As part of the v2-to-FHIR project we are mapping commonly used fields in key v2 messages to FHIR resources so that messages can be transformed into bundle of FHIR resources. NK1-3 is the next of kin relationship field but there is no cognate existing data element in FHIR. We suggest that a standard extension to Patient.contact be created to allow exchange of this concept. 

      Complicating this issue is the fact that a Patient.contact.relationship element already exists (bound to a value set made up of v2 table 0131 which is used for NK1-7 the Contact Role field in v2). The RelatedPerson resource has a single element (relationship) which has is bound to a value set made up of both v2 table 0131 (contact role) and http://terminology.hl7.org/CodeSystem/v3-RoleCode which is much more similar to the NK1-3 (relationship) table.

       

      We suggest a CodeableConcept value using value set http://terminology.hl7.org/CodeSystem/v3-RoleCode with a binding other than Required.

       

      The v2 description can be reused as part of the extension narrative:

      This extension contains the actual personal relationship that the contact has to the patient. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            craig.newman Craig Newman
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: