ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

RelatedPerson — Patient relative

Spouse, parent, caregiver, legal representative: a person linked to the patient who can make decisions, be contacted, but is not themselves treated.

Purpose

RelatedPerson models a person linked to a patient: typically an emergency contact, a parent consenting for a minor, a legal guardian consenting for a protected adult, a family caregiver attending appointments. RelatedPerson is the FHIR equivalent of the HL7 v2 NK1 segment.

Key fields

FieldTypeCardinalityRole
identifierIdentifier[]0..*Persistent identifiers.
activeboolean0..1Relationship still active.
patientReference(Patient)1..1Mandatory. Linked patient.
relationshipCodeableConcept[]0..*Relationship type (v3-RoleCode, v2-0131).
nameHumanName[]0..*Name(s).
telecomContactPoint[]0..*Contact points (phone, email).
gendercode0..1Administrative gender.
birthDatedate0..1Birth date (useful to identify a minor representative).
addressAddress[]0..*Addresses.
photoAttachment[]0..*Photo (rare).
periodPeriod0..1Relationship validity period.
communicationBackboneElement[]0..*Spoken languages.

JSON example

Spouse as emergency contact, FR preferred language:

json relatedperson-spouse.json
{
  "resourceType": "RelatedPerson",
  "id": "spouse-doe-jane",
  "identifier": [{
    "system": "urn:oid:1.2.34",
    "value": "RP-2026-001"
  }],
  "active": true,
  "patient": { "reference": "Patient/doe-john" },
  "relationship": [{
    "coding": [{
      "system": "http://terminology.hl7.org/CodeSystem/v3-RoleCode",
      "code": "SPS",
      "display": "spouse"
    }]
  }, {
    "coding": [{
      "system": "http://terminology.hl7.org/CodeSystem/v2-0131",
      "code": "C",
      "display": "Emergency Contact"
    }]
  }],
  "name": [{
    "use": "official",
    "family": "Doe",
    "given": ["Jane"]
  }],
  "telecom": [{
    "system": "phone",
    "value": "+33 6 12 34 56 78",
    "use": "mobile",
    "rank": 1
  }, {
    "system": "email",
    "value": "jane.doe@example.org",
    "rank": 2
  }],
  "gender": "female",
  "birthDate": "1976-03-22",
  "address": [{
    "use": "home",
    "line": ["12 rue de la République"],
    "city": "Lyon",
    "postalCode": "69001",
    "country": "FR"
  }],
  "communication": [{
    "language": {
      "coding": [{
        "system": "urn:ietf:bcp:47",
        "code": "fr-FR"
      }]
    },
    "preferred": true
  }]
}

Common pitfalls

  • Confusing with Patient — a RelatedPerson is not treated. If they become a patient themselves (e.g. hospitalization), create a separate Patient linked via Person.
  • No relationship — an untyped relationship is unusable: how to know if it's the guardian or just a friend?
  • Medical data on RelatedPerson — anti-pattern, no Observation/Condition tied to a RelatedPerson. Use FamilyMemberHistory.
  • Multiple code systems mixedrelationship accepts v3-RoleCode AND v2-0131: document the code system per entry.
  • Forgotten period — an ex-spouse stays linked without period.end: confusion source.