Generated Narrative: StructureDefinition ext-R5-Requirements.statement Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.0.1) R5: Actual statement as markdown (new) #xD; Slices for extension 2..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:key 1..1 Extension R5: Key that identifies this statement (new) #xD; url 1..1 uri "key" #xD; value[x] 1..1 id Key that identifies this statement #xD; extension:label 0..1 Extension R5: Short Human label for this statement (new) #xD; url 1..1 uri "label" #xD; value[x] 0..1 string Short Human label for this statement #xD; extension:conformance 0..* Extension R5: SHALL | SHOULD | MAY | SHOULD-NOT (new) #xD; url 1..1 uri "conformance" #xD; value[x] 0..1 code SHALL | SHOULD | MAY | SHOULD-NOT Binding: R5ConformanceExpectationForR4 (0.1.0) (required) #xD; extension:conditionality 0..1 Extension R5: Set to true if requirements statement is conditional (new) #xD; url 1..1 uri "conditionality" #xD; value[x] 0..1 boolean Set to true if requirements statement is conditional #xD; extension:requirement 1..1 Extension R5: The actual requirement (new) #xD; url 1..1 uri "requirement" #xD; value[x] 1..1 markdown The actual requirement #xD; extension:derivedFrom 0..1 Extension R5: Another statement this clarifies/restricts ([url#]key) (new) #xD; url 1..1 uri "derivedFrom" #xD; value[x] 0..1 string Another statement this clarifies/restricts ([url#]key) #xD; extension:parent 0..1 Extension R5: A larger requirement that this requirement helps to refine and enable (new) #xD; url 1..1 uri "parent" #xD; value[x] 0..1 string A larger requirement that this requirement helps to refine and enable #xD; extension:satisfiedBy 0..* Extension R5: Design artifact that satisfies this requirement (new) #xD; url 1..1 uri "satisfiedBy" #xD; value[x] 0..1 url Design artifact that satisfies this requirement #xD; extension:reference 0..* Extension R5: External artifact (rule/document etc. that) created this requirement (new) #xD; url 1..1 uri "reference" #xD; value[x] 0..1 url External artifact (rule/document etc. that) created this requirement #xD; extension:source 0..* Extension R5: Who asked for this statement (new) #xD; url 1..1 uri "source" #xD; value[x] 0..1 Reference(Cross-version Profile for R5.CareTeam for use in FHIR R4(0.1.0) | CareTeam | Cross-version Profile for R5.Device for use in FHIR R4(0.1.0) | Device | Cross-version Profile for R5.Group for use in FHIR R4(0.1.0) | Group | Cross-version Profile for R5.HealthcareService for use in FHIR R4(0.1.0) | HealthcareService | Cross-version Profile for R5.Organization for use in FHIR R4(0.1.0) | Organization | Cross-version Profile for R5.Patient for use in FHIR R4(0.1.0) | Patient | Cross-version Profile for R5.Practitioner for use in FHIR R4(0.1.0) | Practitioner | Cross-version Profile for R5.PractitionerRole for use in FHIR R4(0.1.0) | PractitionerRole | Cross-version Profile for R5.RelatedPerson for use in FHIR R4(0.1.0) | RelatedPerson) Who asked for this statement #xD; url 1..1 uri "http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.statement" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R5: `Requirements.statement` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `Requirements.statement` as defined in FHIR R5 in FHIR R4. The source element is defined as: `Requirements.statement` 0..* `BackboneElement` Across FHIR versions, the element set has been mapped as: * R5 `Requirements.statement` 0..* `BackboneElement` Following are the generation technical comments: Element `Requirements.statement` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `Requirements.statement` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
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
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
R5: Key that identifies this statement (new)
R5: `Requirements.statement.key` (new:id)
Element `Requirements.statement.key` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.key` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.key` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Refer directly to the statement by {url}#{key}
Element `Requirements.statement.key` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.key` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.key` has no mapping targets in FHIR R4. 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 manageable, 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.
Key that identifies this statement (unique within this resource).
Refer directly to the statement by {url}#{key}
R5: Short Human label for this statement (new)
R5: `Requirements.statement.label` (new:string)
Element `Requirements.statement.label` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.label` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.label` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The key is intended for computers, while this is intended for humans. In its absence, the key should be convenient for a human to say (e.g. not a UUID)
Element `Requirements.statement.label` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.label` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.label` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
A short human usable label for this statement.
The key is intended for computers, while this is intended for humans. In its absence, the key should be convenient for a human to say (e.g. not a UUID)
R5: SHALL | SHOULD | MAY | SHOULD-NOT (new)
R5: `Requirements.statement.conformance` (new:code)
Element `Requirements.statement.conformance` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.conformance` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.conformance` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The conformance code is extracted from the requirement to make indexing and display easier. The requirement needs to express the conformance verbs directly in the markdown content. It's not unusual to mix verbs in a single sentence (e.g. System SHALL do X and SHOULD do Y)
This element is allowed to repeat because a single requirements statement might contain multiple conformance words and thus need to be indexed under multiple conformance categories. Element `Requirements.statement.conformance` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.conformance` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.conformance` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The conformance code is extracted from the requirement to make indexing and display easier. The requirement needs to express the conformance verbs directly in the markdown content. It's not unusual to mix verbs in a single sentence (e.g. System SHALL do X and SHOULD do Y)
R5: Set to true if requirements statement is conditional (new)
R5: `Requirements.statement.conditionality` (new:boolean)
Element `Requirements.statement.conditionality` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.conditionality` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.conditionality` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). There is no intent that the conditional statement by evaluatable
Element `Requirements.statement.conditionality` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.conditionality` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.conditionality` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Set to true if requirements statement is conditional
This boolean flag is set to true of the text of the requirement is conditional on something e.g. it includes lanauage like 'if x then y'. This conditionality flag is introduced for purposes of filtering and colour highlighting etc.
There is no intent that the conditional statement by evaluatable
R5: `Requirements.statement.requirement` (new:markdown)
Element `Requirements.statement.requirement` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.requirement` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.requirement` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The actual requirement for human consumption.
R5: Another statement this clarifies/restricts ([url#]key) (new)
R5: `Requirements.statement.derivedFrom` (new:string)
Element `Requirements.statement.derivedFrom` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.derivedFrom` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.derivedFrom` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This can be just a key, if there is only one matching statement in the requirements statements referenced in Requirements.derivedFrom. If there is more than one, it should be in the format ```url#key```
Element `Requirements.statement.derivedFrom` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.derivedFrom` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.derivedFrom` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Another statement this clarifies/restricts ([url#]key)
Another statement on one of the requirements that this requirement clarifies or restricts.
This can be just a key, if there is only one matching statement in the requirements statements referenced in Requirements.derivedFrom. If there is more than one, it should be in the format ```url#key```
R5: A larger requirement that this requirement helps to refine and enable (new)
R5: `Requirements.statement.parent` (new:string)
Element `Requirements.statement.parent` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.parent` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.parent` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Follows the same convention as statement.derivedFrom, where a reference is the canonical of the Requirements followed by '#' and the 'key' of the specific requirement.
Allows requirements to be organized compositionally. E.g. Epic/Story/Task. Element `Requirements.statement.parent` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.parent` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.parent` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
A larger requirement that this requirement helps to refine and enable
A larger requirement that this requirement helps to refine and enable.
Follows the same convention as statement.derivedFrom, where a reference is the canonical of the Requirements followed by '#' and the 'key' of the specific requirement.
R5: Design artifact that satisfies this requirement (new)
R5: `Requirements.statement.satisfiedBy` (new:url)
Element `Requirements.statement.satisfiedBy` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.satisfiedBy` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.satisfiedBy` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This is for use when the requirement is met be a pre-existing artifact e.g. a rule that's met by the base FHIR spec, or a national implementation guide.
Element `Requirements.statement.satisfiedBy` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.satisfiedBy` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.satisfiedBy` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Design artifact that satisfies this requirement
A reference to another artifact that satisfies this requirement. This could be a Profile, extension, or an element in one of those, or a CapabilityStatement, OperationDefinition, SearchParameter, CodeSystem(/code), ValueSet, Libary etc.
This is for use when the requirement is met be a pre-existing artifact e.g. a rule that's met by the base FHIR spec, or a national implementation guide.
R5: External artifact (rule/document etc. that) created this requirement (new)
R5: `Requirements.statement.reference` (new:url)
Element `Requirements.statement.reference` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.reference` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.reference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
External artifact (rule/document etc. that) created this requirement
A reference to another artifact that created this requirement. This could be a Profile, etc., or external regulation, or business requirements expressed elsewhere.
R5: `Requirements.statement.source` (new:Reference(CareTeam,Device,Group,HealthcareService,Organization,Patient,Practitioner,PractitionerRole,RelatedPerson))
Element `Requirements.statement.source` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.source` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.source` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Who asked for this statement to be a requirement. By default, it's assumed that the publisher knows who it is if it matters.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).