Current Build

8.19 Resource Linkage - Content

Patient Care Work GroupMaturity Level: 0 DraftCompartments: Practitioner

Identifies two or more records (resource instances) that are referring to the same real-world "occurrence".

This resource allows the assertion of linkages between multiple resource instances (generally of the same type) that are referring to the same underlying business objects. For example, multiple Condition records that refer to the same underlying problem/issue for a Patient; multiple AllergyIntolerance records that refer to the same reaction susceptibility; multiple Patient, Practioner and/or RelatedPerson records that refer to the same human being or animal.

FHIR supports a process for sharing electronic records. It is common for multiple records to exist that deal with the same real-world phenomenon. This can result from information being captured by different systems, information being captured within a single system by different users (either deliberately to represent distinct perspectives or accidentally when a new record is created rather than updating an existing record). These multiple records may be referred to as "duplicate" records, but in practice they aren't often actually "duplicate" in that the data represented (and the history of the records) will be at least somewhat distinct.

In some cases, the solution upon identifying duplicates is to deprecate one of the records (e.g. by changing the status to "entered in error") and move all relevant information to the surviving record. In other cases, the resource may support the ability to establish a linkage directly between the resources. However, in some cases, both records may need to survive or there's a desire to have both resources continue to be maintained, perhaps because the resources live on different servers or have different 'owners'. The Linkage resource is intended to satisfy this use-case.

The Person resource should be used to link a person independent of a specific health-related context. Linkage can be used for all other use cases.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Linkage ΣIDomainResourceLinks records for 'same' item
+ Must have at least two items
Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... active Σ0..1booleanWhether this linkage assertion is active or not
... author Σ0..1Reference(Practitioner | Organization)Who is responsible for linkages
... item ΣI1..*BackboneElementItem to be linked
.... type Σ1..1codesource | alternate | historical
LinkageType (Required)
.... resource Σ1..1Reference()Resource being linked

doco Documentation for this format

XML Template

<Linkage xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <active value="[boolean]"/><!-- 0..1 Whether this linkage assertion is active or not -->
 <author><!-- 0..1 Reference(Practitioner|Organization) Who is responsible for linkages --></author>
 <item>  <!-- ?? 1..* Item to be linked -->
  <type value="[code]"/><!-- 1..1 source | alternate | historical -->
  <resource><!-- 1..1 Reference Resource being linked --></resource>
 </item>
</Linkage>

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:Linkage;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:Linkage.active [ boolean ]; # 0..1 Whether this linkage assertion is active or not
  fhir:Linkage.author [ Reference(Practitioner|Organization) ]; # 0..1 Who is responsible for linkages
  fhir:Linkage.item [ # 1..* Item to be linked
    fhir:Linkage.item.type [ code ]; # 1..1 source | alternate | historical
    fhir:Linkage.item.resource [ Reference ]; # 1..1 Resource being linked
  ], ...;
]

Changes since DSTU2

This resource did not exist in Release 2

This analysis is available as XML or JSON.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Linkage ΣIDomainResourceLinks records for 'same' item
+ Must have at least two items
Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... active Σ0..1booleanWhether this linkage assertion is active or not
... author Σ0..1Reference(Practitioner | Organization)Who is responsible for linkages
... item ΣI1..*BackboneElementItem to be linked
.... type Σ1..1codesource | alternate | historical
LinkageType (Required)
.... resource Σ1..1Reference()Resource being linked

doco Documentation for this format

XML Template

<Linkage xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <active value="[boolean]"/><!-- 0..1 Whether this linkage assertion is active or not -->
 <author><!-- 0..1 Reference(Practitioner|Organization) Who is responsible for linkages --></author>
 <item>  <!-- ?? 1..* Item to be linked -->
  <type value="[code]"/><!-- 1..1 source | alternate | historical -->
  <resource><!-- 1..1 Reference Resource being linked --></resource>
 </item>
</Linkage>

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:Linkage;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:Linkage.active [ boolean ]; # 0..1 Whether this linkage assertion is active or not
  fhir:Linkage.author [ Reference(Practitioner|Organization) ]; # 0..1 Who is responsible for linkages
  fhir:Linkage.item [ # 1..* Item to be linked
    fhir:Linkage.item.type [ code ]; # 1..1 source | alternate | historical
    fhir:Linkage.item.resource [ Reference ]; # 1..1 Resource being linked
  ], ...;
]

Changes since DSTU2

This resource did not exist in Release 2

This analysis is available as XML or JSON.

 

Alternate definitions: Master Definition (XML, JSON), XML Schema/Schematron + JSON Schema, ShEx (for Turtle)

PathDefinitionTypeReference
Linkage.item.type Used to distinguish different roles a resource can play within a set of linked resourcesRequiredLinkageType

  • lnk-1: Must have at least two items (expression : item.count()>1)

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionExpressionIn Common
authorreferenceAuthor of the LinkageLinkage.author
(Practitioner, Organization)
itemreferenceMatches on any item in the LinkageLinkage.item.resource
sourcereferenceMatches on any item in the Linkage with a type of 'source'Linkage.item.resource