Generated Narrative: StructureDefinition cqf-relatedRequirement Name Flags Card. Type Description & Constraints Extension 0..* Extension Extension #xD; Slices for extension Content/Rules for all slices #xD; extension:targetId 1..1 Extension What data requirement #xD; url 1..1 uri "targetId" #xD; value[x] 0..1 string Value of extension #xD; extension:targetPath 0..1 Extension What element establishes the relationship #xD; url 1..1 uri "targetPath" #xD; value[x] 0..1 string Value of extension #xD; extension:targetSearchParam 0..1 Extension What search parameter establishes the relationship #xD; url 1..1 uri "targetSearchParam" #xD; value[x] 0..1 string Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/StructureDefinition/cqf-relatedRequirement" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
HL7 International / Clinical Decision Support
Allows relationships to be established between data requirements. For example, a Medication data requirement that depends on a MedicationRequest data requirement.
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
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.
The id of a related data requirement (i.e. a data requirement that establishes context for this data requirement)
As an example, consider a query for MedicationRequest with all related Medication resources (an include query). In this case the Medication data requirement will specify a relatedDataRequirement of MedicationRequest, with a path of medication.
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.
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).
What element establishes the relationship
The path to an element in the related data requirement that establishes the relationship. The element is typically of type Reference (or in some cases canonical).
This element is exclusive with the targetSearchParam element; either the relationship is established by the path to an element, or by a search parameter defining the reference relationship to be followed.
What search parameter establishes the relationship
The name of a search parameter that establishes the relationship to the related data element.
This element is exclusive with the targetPath element; either the relationship is established by the path to an element, or by a search parameter defining the reference relationship to be followed.