OpenEHR Base package
0.1.0 - First Draft International flag

OpenEHR Base package, published by openEHR + HL7. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/openehr-fhir/base-spec/ and changes regularly. See the Directory of published versions

Logical Model: LINK

Official URL: http://openehr.org/fhir/StructureDefinition/LINK Version: 0.1.0
Standards status: Informative Maturity Level: 3 Computable Name: LINK

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.

Original Source: specifications.openehr.org

Usages:

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. LINK 0..* Any The `LINK` type defines a logical relationship between two items, such as two `ENTRYs` or an `ENTRY` and a `COMPOSITION`.
... meaning 1..1 DV_TEXT 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.
... type 1..1 DV_TEXT The type attribute is used to indicate a clinical or domain-level meaning for the kind of link, for example problem or issue .
... target 1..1 DV_EHR_URI The logical to object in the link relation, as per the linguistic sense of the meaning attribute.

doco Documentation for this format

This structure is derived from Any

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. LINK 0..* Any The `LINK` type defines a logical relationship between two items, such as two `ENTRYs` or an `ENTRY` and a `COMPOSITION`.
... meaning 1..1 DV_TEXT 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.
... type 1..1 DV_TEXT The type attribute is used to indicate a clinical or domain-level meaning for the kind of link, for example problem or issue .
... target 1..1 DV_EHR_URI The logical to object in the link relation, as per the linguistic sense of the meaning attribute.

doco Documentation for this format

This structure is derived from Any

Summary

Mandatory: 0 element(3 nested mandatory elements)

Maturity: 3

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. LINK 0..* Any The `LINK` type defines a logical relationship between two items, such as two `ENTRYs` or an `ENTRY` and a `COMPOSITION`.
... meaning 1..1 DV_TEXT 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.
... type 1..1 DV_TEXT The type attribute is used to indicate a clinical or domain-level meaning for the kind of link, for example problem or issue .
... target 1..1 DV_EHR_URI The logical to object in the link relation, as per the linguistic sense of the meaning attribute.

doco Documentation for this format

Differential View

This structure is derived from Any

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. LINK 0..* Any The `LINK` type defines a logical relationship between two items, such as two `ENTRYs` or an `ENTRY` and a `COMPOSITION`.
... meaning 1..1 DV_TEXT 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.
... type 1..1 DV_TEXT The type attribute is used to indicate a clinical or domain-level meaning for the kind of link, for example problem or issue .
... target 1..1 DV_EHR_URI The logical to object in the link relation, as per the linguistic sense of the meaning attribute.

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. LINK 0..* Any The `LINK` type defines a logical relationship between two items, such as two `ENTRYs` or an `ENTRY` and a `COMPOSITION`.
... meaning 1..1 DV_TEXT 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.
... type 1..1 DV_TEXT The type attribute is used to indicate a clinical or domain-level meaning for the kind of link, for example problem or issue .
... target 1..1 DV_EHR_URI The logical to object in the link relation, as per the linguistic sense of the meaning attribute.

doco Documentation for this format

This structure is derived from Any

Summary

Mandatory: 0 element(3 nested mandatory elements)

Maturity: 3

 

Other representations of profile: CSV, Excel