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

Patient.contact lists guardian as a use case, but code system for Patient.contact.relationship does not include a code for guardian.

    XMLWordPrintableJSON

Details

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

      The Patient.contact.relationship currently includes the value set for the contact role.  Rather than expanding the valueset to include relationship, we'll create a new property to contain the contact role, and update the value set for relationship:

       

      Patient.contact.relationship  0..* (preferred) Update value set from Patient Contact Relationship (which is mostly role codes) to v3-PersonalRelationshipRoleType

      Definition: The nature of the personal relationship between the patient and the contact person. 

      Short Display: The kind of personal relationship

      Requirements: Used to determine the nature of the relationship between the patient and the contact person.

      Comment: This property is for personal relationships.  Functional relationships would be represented in Patient.contact.role.

       

      Summary of changes (which we do not think count as breaking):

      • Update the binding from extensible to preferred.
      • Update the value set
      • Update the definition or the property to indicate this is about personal or professional relationships, NOT functional relationships. 

       

       

      Patient.contact.role 0..* (preferred) Use ValueSet relatedperson-relationshiptype

      Definition: The nature of the functional role between the patient and the contact person. 

      Short Display: The kind of functional role 

      Requirements: Used to determine which contact person is the most relevant to approach, depending on circumstances.

      Comment: This property is for representing the functional role.  Personal relationships would be represented in Patient.contact.relationship.

       

      Summary of changes:

      • Net new property

       

      We will deprecate Patient Contact Relationship.

       

      Similarly for RelatedPerson:

      RelatedPerson.relationship 0..* (preferred) from relatedperson-relationshiptype to ValueSet to v3-PersonalRelationshipRoleType

      Definition: The nature of the personal relationship between the patient and the related person. 

      Short Display: The kind of personal relationship

      Requirements: Used to determine the nature of the relationship between the patient and the related person.

      Comment: This property is for personal relationships.  Functional relationships would be represented in RelatedPerson.role.

       

      Summary of changes:

      • The binding will be updated from extensible to preferred.
      • The value set will be changed to the new one indicated above.

       

      RelatedPerson.role 0..* (preferred) to ValueSet relatedperson-relationshiptype

      Definition: The nature of the functional role between the patient and the related person. 

      Short Display: The kind of functional role 

      Requirements: Used to determine which related person is the most relevant to approach, depending on circumstances.

      Comment: This property is for representing the functional role.  Personal relationships would be represented in RelatedPerson.relationship.

      Summary of changes:

      • Net new property

       

       

       

      Examples:

      Patient.contact[0]

         .relationship   (mother, parent, employer)

        .role (billing, allowed-to-pick-up, emergency)

        .name (Mary)

      Patient.contact[1]

         .relationship   (father, parent, employer)

        .role (emergency, allowed-to-pick-up)

        .name (Joe)

      Patient.contact[2]

         .relationship   (grandmother)

        .role (allowed-to-pick-up)

        .name (Grandma)

      Show
      The Patient .contact.relationship currently includes the value set for the contact role.  Rather than expanding the valueset to include relationship, we'll create a new property to contain the contact role, and update the value set for relationship:   Patient.contact.relationship   0..* (preferred) Update value set from Patient Contact Relationship (which is mostly role codes) to v3-PersonalRelationshipRoleType Definition : The nature of the personal relationship between the patient and the contact person.  Short Display : The kind of personal relationship Requirements : Used to determine the nature of the relationship between the patient and the contact person. Comment: This property is for personal relationships.  Functional relationships would be represented in Patient.contact.role.   Summary of changes (which we do not think count as breaking): Update the binding from extensible to preferred. Update the value set Update the definition or the property to indicate this is about personal or professional relationships, NOT functional relationships.       Patient.contact.role 0..* (preferred) Use ValueSet relatedperson-relationshiptype Definition : The nature of the functional role between the patient and the contact person.  Short Display : The kind of functional role  Requirements : Used to determine which contact person is the most relevant to approach, depending on circumstances. Comment: This property is for representing the functional role.  Personal relationships would be represented in Patient.contact.relationship.   Summary of changes: Net new property   We will deprecate Patient Contact Relationship .   Similarly for RelatedPerson : RelatedPerson.relationship 0..* (preferred) from relatedperson-relationshiptype to ValueSet to v3-PersonalRelationshipRoleType Definition : The nature of the personal relationship between the patient and the related person.  Short Display : The kind of personal relationship Requirements : Used to determine the nature of the relationship between the patient and the related person. Comment: This property is for personal relationships.  Functional relationships would be represented in RelatedPerson.role.   Summary of changes: The binding will be updated from extensible to preferred. The value set will be changed to the new one indicated above.   RelatedPerson.role 0..* (preferred) to ValueSet relatedperson-relationshiptype Definition : The nature of the functional role between the patient and the related person.  Short Display : The kind of functional role  Requirements : Used to determine which related person is the most relevant to approach, depending on circumstances. Comment: This property is for representing the functional role.  Personal relationships would be represented in RelatedPerson.relationship. Summary of changes: Net new property       Examples : Patient.contact [0]    .relationship   (mother, parent, employer)   .role (billing, allowed-to-pick-up, emergency)   .name (Mary) Patient.contact [1]    .relationship   (father, parent, employer)   .role (emergency, allowed-to-pick-up)   .name (Joe) Patient.contact [2]    .relationship   (grandmother)   .role (allowed-to-pick-up)   .name (Grandma)
    • Joanie Harper / David Pyke : 12-0-1
    • Enhancement
    • Compatible, substantive

    Description

      Patient.contact lists guardian as a use case, but code system for Patient.contact.relationship does not include a code for guardian.

      http://build.fhir.org/v2/0131/index.html

      Suggest creating a value set that is complete for the use case, or at a minimum creating a guardian example so implementers know the recommended code and system to use. Suggest GUARD from RoleClass: 2.16.840.1.113883.11.11555 to align with CDA).

      Attachments

        Activity

          People

            Unassigned Unassigned
            rgeimer Rick Geimer
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: