Generated Narrative: StructureDefinition ext-R3-DocumentReference.con.related Name Flags Card. Type Description & Constraints Extension 0..* Extension(5.0.0) STU3: Related identifiers or resources (new) #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:identifier 0..1 Extension STU3: Identifier of related objects or events (new) #xD; url 1..1 uri "identifier" #xD; value[x] 0..1 Identifier Identifier of related objects or events #xD; extension:ref 0..1 Extension STU3: Related Resource (new) #xD; url 1..1 uri "ref" #xD; value[x] 0..1 Reference(Cross-version Profile for STU3.Resource for use in FHIR R5(0.1.0) | Resource) Related Resource #xD; url 1..1 uri "http://hl7.org/fhir/3.0/StructureDefinition/extension-DocumentReference.context.related" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
STU3: Related identifiers or resources (new)
STU3: `DocumentReference.context.related` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `DocumentReference.context.related` as defined in FHIR STU3 in FHIR R5. The source element is defined as: `DocumentReference.context.related` 0..* `BackboneElement` Across FHIR versions, the element set has been mapped as: * STU3: `DocumentReference.context.related` 0..* `BackboneElement` * R4: `DocumentReference.context.related` 0..* `Reference(http://hl7.org/fhir/StructureDefinition/Resource)` * R4B: `DocumentReference.context.related` 0..* `Reference(http://hl7.org/fhir/StructureDefinition/Resource)` Following are the generation technical comments: Element `DocumentReference.context.related` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.related` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Element `DocumentReference.context.related` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.related` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). May be identifiers or resources that caused the DocumentReference or referenced Document to be created.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
STU3: Identifier of related objects or events (new)
STU3: `DocumentReference.context.related.identifier` (new:Identifier)
Element `DocumentReference.context.related.identifier` is part of an existing definition because parent element `DocumentReference.context.related` requires a cross-version extension. Element `DocumentReference.context.related.identifier` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.related.identifier` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Order numbers, accession numbers, XDW workflow numbers.
Element `DocumentReference.context.related.identifier` is part of an existing definition because parent element `DocumentReference.context.related` requires a cross-version extension. Element `DocumentReference.context.related.identifier` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.related.identifier` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Related identifier to this DocumentReference. If both id and ref are present they shall refer to the same thing.
Order numbers, accession numbers, XDW workflow numbers.
STU3: `DocumentReference.context.related.ref` (new:Reference(Resource))
Element `DocumentReference.context.related.ref` is part of an existing definition because parent element `DocumentReference.context.related` requires a cross-version extension. Element `DocumentReference.context.related.ref` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.related.ref` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Order, ProcedureRequest, Procedure, EligibilityRequest, etc.
Element `DocumentReference.context.related.ref` is part of an existing definition because parent element `DocumentReference.context.related` requires a cross-version extension. Element `DocumentReference.context.related.ref` has a context of DocumentReference.context based on following the parent source element upwards and mapping to `DocumentReference`. Element `DocumentReference.context.related.ref` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Related Resource to this DocumentReference. If both id and ref are present they shall refer to the same thing.
Order, ProcedureRequest, Procedure, EligibilityRequest, etc.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).