Scope and usage

The Danish Core Related Person profile is intended to encapsulate the most common and basic data model of persons related to patients/persons in Danish healthcare systems covering both primary sector, secondary sector (specialty doctors and hospitals) and municipality cases. As such the profile should be usable in most Danish contexts. Note that the profile is usable for related persons to those that receive health and social care in municipalities, even in contexts where receivers of care are more commonly known as citizens ([DA] borgere).

Note, that professional relationships between a patient and a healthcare professional are expressed by other means e.g. through Patient.generalPractitioner.

Note also, that the intended use of Related Person is to describe a relationship, where privileges which might be associated to the relationship should be expressed by other means, e.g.the actual rights associated with being power of attorney, should be described in a legally binding document, and that document can be represented with the Consent resource.

Note furthermore, that a patients primary contact when possible should be expressed through Patient.contact. However, when this is not feasible Related Person may be used.

Identifiers for related persons

This related person profile currently reflects the use of the established national Danish citizen identifiers called CPR and (where relevant) the use of replacement CPR numbers ([DA] Erstatnings-CPR-numre eller eCPR).

CPR-identifier

The element identifier.type describes the specific purpose of an identifier. It is desired to use the code 'NNDNK' from the CodeSystem IdentifierType as the type for DkCoreCprIdentifier. However, it is currently not recommended to use this code, due to known problems with the validation tool when validating the code 'NNDNK'.

eCPR-identifier

The element RelatedPerson.identifier includes two slices to represent eCPR. Each slice includes an identifier with requirements for the specific eCPR:

• For X-eCPR, the DkCoreXeCprIdentifier must be used, which includes an OID as system and an invariant describing the requirements for the structure of the identifier, based on guidelines from Danish Health Data Authority.
• For D-eCPR, the DkCoreDeCprIdentifier must be used, which includes a ValueSet of OID's that may be used as system. The OIDs represent the D-eCPR in general and D-eCPR for each of the five regions. Further, the identifier includes an invariant describing the requirements for the structure of the identifier, based on guidelines from Danish Health Data Authority.

Relationship codes

The relationships in DK Core Related Person Relationship Types are intended to cover the most common use cases within the Danish healthcare sector. For the relationship codes that are included from the general relationship codes danish translations are provided. In cases when other relationships need to be expressed, codes from the general Related Person Relationship Type or HL7 Role Code System should be used when possible. In the latter system is e.g. the code 'CCO', which is a clinical companion (DA: Servicehund).

Use of security label on related persons

In case an implementation project needs to support name and address protection (Navne- og adressebeskyttelse) of a danish citizen, it is recommended to support this with the security label as follows:

 <RelatedPerson xmlns="http://hl7.org/fhir">
  <meta>
    <security>
      <system value="http://terminology.hl7.org/CodeSystem/v3-Confidentiality"/>
      <code value="R"/>
      <display value="Restricted"/>
    </security>
  </meta>
...  [snip] ...
</RelatedPerson>

Use of this label should be interpreted according to the law, roughly meaning that only personnel using systems in public/official affairs are allowed to see name and address for the related person/citizen.