Generated Narrative: StructureDefinition profile-RequestGroup Name Flags Card. Type Description & Constraints RequestGroup 0..* RequestGroup(4.0.1) A group of related requests #xD; Documentation for this format
Cross-version Profile for R4B.RequestGroup for use in FHIR R4
This cross-version profile allows R4B RequestGroup content to be represented via FHIR R4 RequestGroup resources.
A group of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one".
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. 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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Allows a service to provide a unique, business identifier for the request.
Allows identification of the request as it is known by various participating systems and in a way that remains consistent across servers.
Instantiates FHIR protocol or definition
A canonical URL referencing a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this request.
Instantiates external protocol or definition
A URL referencing an externally defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this request.
A plan, proposal or order that is fulfilled in whole or in part by this request.
Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon.
Completed or terminated request(s) whose function is taken by this new request.
The replacement could be because the initial request was immediately rejected (due to an issue) or because the previous request was completed, but the need for the action described by the request remains ongoing.
Allows tracing the continuation of a therapy or administrative process instantiated through multiple requests.
A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form.
Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.
Some business processes need to know if multiple items were ordered as part of the same "prescription" or "requisition" for billing or other purposes.
draft | active | on-hold | revoked | completed | entered-in-error | unknown
The current state of the request. For request groups, the status reflects the status of all the requests in the group.
This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
Codes identifying the lifecycle stage of a request.
proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
Indicates the level of authority/intentionality associated with the request and where the request fits into the workflow chain.
Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.
This element changes the interpretation of all descriptive attributes. For example "the time the request is recommended to occur" vs. "the time the request is authorized to occur" or "who is recommended to perform the request" vs. "who is authorized to perform the request
Codes indicating the degree of authority/intentionality associated with a request.
Indicates how quickly the request should be addressed with respect to other requests.
If missing, this request should be performed with normal priority
Identifies the level of importance to be assigned to actioning the request.
A code that identifies what the overall request group is.
This element can be used to provide a code that captures the meaning of the request group as a whole, as opposed to the code of the action element, which captures the meaning of the individual actions within the request group.
The subject for which the request group was created.
Describes the context of the request group, if any.
Indicates when the request group was created.
Device or practitioner that authored the request group
Provides a reference to the author of the request group.
Describes the reason for the request group in coded or textual form.
Indicates another resource whose existence justifies this request group.
Provides a mechanism to communicate additional information about the response.
The actions, if any, produced by the evaluation of the artifact.
Must have resource or action but not both
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
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.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
User-visible prefix for the action (e.g. 1. or A.)
The title of the action displayed to a user.
A short description of the action used to provide a summary to display to the user.
Static text equivalent of the action, used if the dynamic aspects cannot be interpreted by the receiving system
A text equivalent of the action to be performed. This provides a human-interpretable description of the action when the definition is consumed by a system that might not be capable of interpreting it dynamically.
Indicates how quickly the action should be addressed with respect to other actions.
Code representing the meaning of the action or sub-actions
A code that provides meaning for the action or action group. For example, a section may have a LOINC code for a section of a documentation template.
Supporting documentation for the intended performer of the action
Didactic or other informational resources associated with the action that can be provided to the CDS recipient. Information resources can include inline text commentary and links to web resources.
An expression that describes applicability criteria, or start/stop conditions for the action.
When multiple conditions of the same kind are present, the effects are combined using AND semantics, so the overall condition is true only if all of the conditions are true.
Applicability criteria are used to determine immediate applicability when a plan definition is applied to a given context. Start and stop criteria are carried through application and used to describe enter/exit criteria for an action.
An expression that returns true or false, indicating whether or not the condition is satisfied.
The expression may be inlined, or may be a reference to a named expression within a logic library referenced by the library element.
A relationship to another action such as "before" or "30-60 minutes after start of".
The element id of the action this is related to.
before-start | before | before-end | concurrent-with-start | concurrent | concurrent-with-end | after-start | after | after-end
The relationship of this action to the related action.
Defines the types of relationships between actions.
A duration or range of durations to apply to the relationship. For example, 30-60 minutes before.
An optional value describing when the action should be performed.
The participant that should perform or be responsible for this action.
The type of action to perform (create, update, remove).
visual-group | logical-group | sentence-group
Defines the grouping behavior for the action and its children.
Defines organization behavior of a group.
any | all | all-or-none | exactly-one | at-most-one | one-or-more
Defines the selection behavior for the action and its children.
Defines expectations around whether an action is required.
Defines expectations around whether an action or action group is required.
Defines whether the action should usually be preselected.
Defines selection frequency behavior for an action or group.
Defines whether the action can be selected multiple times.
Defines behavior for an action or a group for how many times that item may be repeated.
The resource that is the target of the action (e.g. CommunicationRequest).
The target resource SHALL be a [Request](http://hl7.org/fhir/R4/request.html) resource with a Request.intent set to "option".