OpenEHR Base package
0.1.0 - First Draft
OpenEHR Base package
0.1.0 - First Draft
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/FHIR/openehr-base-ig/ and changes regularly. See the Directory of published versions
| 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 LINK structure to give the effect of a 1→N link. 1:1 and 1:N relationships between LINK 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 LINK 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:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
| Name | Flags | Card. | Type | Description & Constraints Filter:   |
|---|---|---|---|---|
  LINK |
0..* | Base | 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 | |
| type |
1..1 | DV_TEXT | The type attribute is used to indicate a clinical or domain-level meaning for the kind of link | |
 target |
1..1 | DV_EHR_URI | The logical to object in the link relation | |
| Documentation for this format | ||||
This structure is derived from Base
| Name | Flags | Card. | Type | Description & Constraints Filter: |
|---|---|---|---|---|
| LINK |
0..* | Base | 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 | |
| type |
1..1 | DV_TEXT | The type attribute is used to indicate a clinical or domain-level meaning for the kind of link | |
| target |
1..1 | DV_EHR_URI | The logical to object in the link relation | |
| Documentation for this format | ||||
| Name | Flags | Card. | Type | Description & Constraints Filter: |
|---|---|---|---|---|
| LINK |
0..* | Base | 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 | |
| type |
1..1 | DV_TEXT | The type attribute is used to indicate a clinical or domain-level meaning for the kind of link | |
| target |
1..1 | DV_EHR_URI | The logical to object in the link relation | |
| Documentation for this format | ||||
Key Elements View
| Name | Flags | Card. | Type | Description & Constraints Filter: |
|---|---|---|---|---|
| LINK |
0..* | Base | 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 | |
| type |
1..1 | DV_TEXT | The type attribute is used to indicate a clinical or domain-level meaning for the kind of link | |
| target |
1..1 | DV_EHR_URI | The logical to object in the link relation | |
| Documentation for this format | ||||
Differential View
This structure is derived from Base
| Name | Flags | Card. | Type | Description & Constraints Filter: |
|---|---|---|---|---|
| LINK |
0..* | Base | 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 | |
| type |
1..1 | DV_TEXT | The type attribute is used to indicate a clinical or domain-level meaning for the kind of link | |
| target |
1..1 | DV_EHR_URI | The logical to object in the link relation | |
| Documentation for this format | ||||
Snapshot View
| Name | Flags | Card. | Type | Description & Constraints Filter: |
|---|---|---|---|---|
| LINK |
0..* | Base | 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 | |
| type |
1..1 | DV_TEXT | The type attribute is used to indicate a clinical or domain-level meaning for the kind of link | |
| target |
1..1 | DV_EHR_URI | The logical to object in the link relation | |
| Documentation for this format | ||||