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

Example Patients should omit Patient.link

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • Cancer Pathology Data Sharing (FHIR)
    • current
    • Orders & Observations
    • STU
    • US Pathology Bundle [deprecated]
    • Hide

      Will remove Patient.link constraint and will update examples to remove exemplifying .link. Will note in narrative/profile description that 'XML comment also clarifies that use of the standard extension is the direct linkage between the Patient and NOK. Will also acknowledge that existing implementation may only use Patient.contact.relationship CodeableConcept, however use of both (use of extension and relationshipCodeableConcept) is recommended."
       

      <Patient>
      <id value="1" />
      <meta>
      <profile value="http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient" />
      </meta>
      <identifier>...</identifier>
      <name>
      <family value="Smith"/>
      <given value="Patient"/>
      </name>
      <contact>
      <!-- use of this standard extension is the direct linkage between Patient and NOK -->
      <extension url="http://hl7.org/fhir/StructureDefinition/patient-relatedPerson">
      <reference value="RelatedPerson/2" />
      </extension>
      <relationship>
      <coding>
      <code value="N" />
      <system value="http://terminology.hl7.org/CodeSystem/v2-0131" />
      <display value="Next-Of-Kin" />
      </coding>
      </relationship>
      <name>
      <family value="Smith"/>
      <given value="Aunt"/>
      </name>
      </contact>
      </Patient>

       

      <RelatedPerson>
      <id value="2"/>
      <patient>
      <reference value="Patient/1"/>
      </patient>
      <relationship>
      <coding>
      <code value="N"/>
      <system value="http://terminology.hl7.org/CodeSystem/v2-0131"/>
      <display value="Next-Of-Kin"/>
      </coding>
      </relationship>
      <name>
      <family value="Smith"/>
      <given value="Aunt"/>
      </name>
      </RelatedPerson>

      Show
      Will remove Patient.link constraint and will update examples to remove exemplifying .link. Will note in narrative/profile description that 'XML comment also clarifies that use of the standard extension is the direct linkage between the Patient and NOK. Will also acknowledge that existing implementation may only use Patient.contact.relationship CodeableConcept, however use of both (use of extension and relationshipCodeableConcept) is recommended."   <Patient> <id value="1" /> <meta> <profile value="http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient" /> </meta> <identifier>...</identifier> <name> <family value="Smith"/> <given value="Patient"/> </name> <contact> <!-- use of this standard extension is the direct linkage between Patient and NOK --> <extension url="http://hl7.org/fhir/StructureDefinition/patient-relatedPerson"> <reference value="RelatedPerson/2" /> </extension> <relationship> <coding> <code value="N" /> <system value="http://terminology.hl7.org/CodeSystem/v2-0131" /> <display value="Next-Of-Kin" /> </coding> </relationship> <name> <family value="Smith"/> <given value="Aunt"/> </name> </contact> </Patient>   <RelatedPerson> <id value="2"/> <patient> <reference value="Patient/1"/> </patient> <relationship> <coding> <code value="N"/> <system value="http://terminology.hl7.org/CodeSystem/v2-0131"/> <display value="Next-Of-Kin"/> </coding> </relationship> <name> <family value="Smith"/> <given value="Aunt"/> </name> </RelatedPerson>
    • Lorraine Constable/Ruby Nash: 11-3-0
    • Correction
    • Compatible, substantive

    Description

      The examples show
       
       
      "link" : [ { "other" :

      { "reference" : "RelatedPerson/pathology-next-of-kin" }

      , "type" : "seealso" } ]
      … but this contradicts the definition of Patient.link (“Link to another patient or RelatedPErson resource that concerns the same actual patient”) since my next of kin is not the same actual patient as me. We already have examples of RelatedPerson (next of kin) linking back to the Patient, which is the direction defined/expected in FHIR core.

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            jmandel Josh Mandel
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: