Generated Narrative: StructureDefinition LINK

NameFlagsCard.TypeDescription & Constraintsdoco
.. LINK 0..*AnyThe `LINK` type defines a logical relationship between two items, such as two `ENTRYs` or an `ENTRY` and a `COMPOSITION`.
... meaning 1..1DV_TEXTUsed to describe the relationship, usually in clinical terms, such as in response to (the relationship between test results and an order), follow-up to and so on.
... type 1..1DV_TEXTThe type attribute is used to indicate a clinical or domain-level meaning for the kind of link, for example problem or issue .
... target 1..1DV_EHR_URIThe logical to object in the link relation, as per the linguistic sense of the meaning attribute.

doco Documentation for this format
 <status value="active"/> <experimental value="false"/> <date value="2025-09-06T15:35:39+10:00"/> <publisher value="openEHR + HL7"/> <contact> <telecom> <system value="url"/> <value value="http://www.openehr.org"/> </telecom> </contact> <description value="The `LINK` type defines a logical relationship between two items, such as two `ENTRYs` or an `ENTRY` and a `COMPOSITION`. Links can be used across compositions, and across EHRs. Links can potentially be used between interior (i.e. non archetype root) nodes, although this probably should be prevented in archetypes. Multiple `LINKs` can be attached to the root object of any archetyped structure to give the effect of a 1->N link. 1:1 and 1:N relationships between archetyped content elements (e.g. `ENTRYs`) can be expressed by using one, or more than one, respectively, `LINKs`. Chains of links can be used to see problem threads or other logical groupings of items. Links should be between archetyped structures only, i.e. between objects representing complete domain concepts because relationships between sub-elements of whole concepts are not necessarily meaningful, and may be downright confusing. Sensible links only exist between whole `ENTRYs`, `SECTIONs`, `COMPOSITIONs` and so on. "/> <jurisdiction> <coding> <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> <code value="001"/> </coding> </jurisdiction> <fhirVersion value="5.0.0"/> <mapping> <identity value="rim"/> <uri value="http://hl7.org/v3"/> <name value="RIM Mapping"/> </mapping> <kind value="logical"/> <abstract value="false"/> <type value="http://openehr.org/fhir/StructureDefinition/LINK"/> <baseDefinition value="http://openehr.org/fhir/StructureDefinition/Any"/> <derivation value="specialization"/> <snapshot> <extension url="http://hl7.org/fhir/tools/StructureDefinition/snapshot-base-version"> <valueString value="0.1.0-snapshot"/> </extension> <element id="LINK"> <path value="LINK"/> <short value="The `LINK` type defines a logical relationship between two items, such as two `ENTRYs` or an `ENTRY` and a `COMPOSITION`."/> <definition value="The `LINK` type defines a logical relationship between two items, such as two `ENTRYs` or an `ENTRY` and a `COMPOSITION`. Links can be used across compositions, and across EHRs. Links can potentially be used between interior (i.e. non archetype root) nodes, although this probably should be prevented in archetypes. Multiple `LINKs` can be attached to the root object of any archetyped structure to give the effect of a 1->N link. 1:1 and 1:N relationships between archetyped content elements (e.g. `ENTRYs`) can be expressed by using one, or more than one, respectively, `LINKs`. Chains of links can be used to see problem threads or other logical groupings of items. Links should be between archetyped structures only, i.e. between objects representing complete domain concepts because relationships between sub-elements of whole concepts are not necessarily meaningful, and may be downright confusing. Sensible links only exist between whole `ENTRYs`, `SECTIONs`, `COMPOSITIONs` and so on. "/> <min value="0"/> <max value="*"/> <base> <path value="Base"/> <min value="0"/> <max value="*"/> </base> <isModifier value="false"/> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element id="LINK.meaning"> <path value="LINK.meaning"/> <short value="Used to describe the relationship, usually in clinical terms, such as in response to (the relationship between test results and an order), follow-up to and so on."/> <definition value="Used to describe the relationship, usually in clinical terms, such as in response to (the relationship between test results and an order), follow-up to and so on. Such relationships can represent any clinically meaningful connection between pieces of information. Values for meaning include those described in Annex C, ENV 13606 pt 2 under the categories of generic , documenting and reporting , organisational , clinical , circumstancial , and view management ."/> <min value="1"/> <max value="1"/> <base> <path value="LINK.meaning"/> <min value="1"/> <max value="1"/> </base> <type> <code value="http://openehr.org/fhir/StructureDefinition/DV-TEXT"/> </type> <isModifier value="false"/> </element> <element id="LINK.type"> <path value="LINK.type"/> <short value="The type attribute is used to indicate a clinical or domain-level meaning for the kind of link, for example problem or issue ."/> <definition value="The type attribute is used to indicate a clinical or domain-level meaning for the kind of link, for example problem or issue . If type values are designed appropriately, they can be used by the requestor of EHR extracts to categorise links which must be followed and which can be broken when the extract is created."/> <min value="1"/> <max value="1"/> <base> <path value="LINK.type"/> <min value="1"/> <max value="1"/> </base> <type> <code value="http://openehr.org/fhir/StructureDefinition/DV-TEXT"/> </type> <isModifier value="false"/> </element> <element id="LINK.target"> <path value="LINK.target"/> <short value="The logical to object in the link relation, as per the linguistic sense of the meaning attribute."/> <definition value="The logical to object in the link relation, as per the linguistic sense of the meaning attribute."/> <min value="1"/> <max value="1"/> <base> <path value="LINK.target"/> <min value="1"/> <max value="1"/> </base> <type> <code value="http://openehr.org/fhir/StructureDefinition/DV-EHR-URI"/> </type> <isModifier value="false"/> </element> </snapshot> <differential> <element id="LINK"> <path value="LINK"/> <short value="The `LINK` type defines a logical relationship between two items, such as two `ENTRYs` or an `ENTRY` and a `COMPOSITION`."/> <definition value="The `LINK` type defines a logical relationship between two items, such as two `ENTRYs` or an `ENTRY` and a `COMPOSITION`. Links can be used across compositions, and across EHRs. Links can potentially be used between interior (i.e. non archetype root) nodes, although this probably should be prevented in archetypes. Multiple `LINKs` can be attached to the root object of any archetyped structure to give the effect of a 1->N link. 1:1 and 1:N relationships between archetyped content elements (e.g. `ENTRYs`) can be expressed by using one, or more than one, respectively, `LINKs`. Chains of links can be used to see problem threads or other logical groupings of items. Links should be between archetyped structures only, i.e. between objects representing complete domain concepts because relationships between sub-elements of whole concepts are not necessarily meaningful, and may be downright confusing. Sensible links only exist between whole `ENTRYs`, `SECTIONs`, `COMPOSITIONs` and so on. "/> <min value="0"/> <max value="*"/> <isModifier value="false"/> </element> <element id="LINK.meaning"> <path value="LINK.meaning"/> <short value="Used to describe the relationship, usually in clinical terms, such as in response to (the relationship between test results and an order), follow-up to and so on."/> <definition value="Used to describe the relationship, usually in clinical terms, such as in response to (the relationship between test results and an order), follow-up to and so on. Such relationships can represent any clinically meaningful connection between pieces of information. Values for meaning include those described in Annex C, ENV 13606 pt 2 under the categories of generic , documenting and reporting , organisational , clinical , circumstancial , and view management ."/> <min value="1"/> <max value="1"/> <type> <code value="http://openehr.org/fhir/StructureDefinition/DV-TEXT"/> </type> <isModifier value="false"/> </element> <element id="LINK.type"> <path value="LINK.type"/> <short value="The type attribute is used to indicate a clinical or domain-level meaning for the kind of link, for example problem or issue ."/> <definition value="The type attribute is used to indicate a clinical or domain-level meaning for the kind of link, for example problem or issue . If type values are designed appropriately, they can be used by the requestor of EHR extracts to categorise links which must be followed and which can be broken when the extract is created. "/> <min value="1"/> <max value="1"/> <type> <code value="http://openehr.org/fhir/StructureDefinition/DV-TEXT"/> </type> <isModifier value="false"/> </element> <element id="LINK.target"> <path value="LINK.target"/> <short value="The logical to object in the link relation, as per the linguistic sense of the meaning attribute."/> <definition value="The logical to object in the link relation, as per the linguistic sense of the meaning attribute."/> <min value="1"/> <max value="1"/> <type> <code value="http://openehr.org/fhir/StructureDefinition/DV-EHR-URI"/> </type> <isModifier value="false"/> </element> </differential> </StructureDefinition>