Struct ActivityDefinitionInner

Source
pub struct ActivityDefinitionInner {
Show 106 fields pub id: Option<String>, pub meta: Option<Meta>, pub implicit_rules: Option<String>, pub language: Option<String>, pub text: Option<Narrative>, pub contained: Vec<Resource>, pub extension: Vec<Extension>, pub modifier_extension: Vec<Extension>, pub url: Option<String>, pub url_ext: Option<FieldExtension>, pub identifier: Vec<Option<Identifier>>, pub identifier_ext: Vec<Option<FieldExtension>>, pub version: Option<String>, pub version_ext: Option<FieldExtension>, pub version_algorithm: Option<ActivityDefinitionVersionAlgorithm>, pub version_algorithm_ext: Option<ActivityDefinitionVersionAlgorithmExtension>, pub name: Option<String>, pub name_ext: Option<FieldExtension>, pub title: Option<String>, pub title_ext: Option<FieldExtension>, pub subtitle: Option<String>, pub subtitle_ext: Option<FieldExtension>, pub status: PublicationStatus, pub status_ext: Option<FieldExtension>, pub experimental: Option<bool>, pub experimental_ext: Option<FieldExtension>, pub subject: Option<ActivityDefinitionSubject>, pub subject_ext: Option<ActivityDefinitionSubjectExtension>, pub date: Option<DateTime>, pub date_ext: Option<FieldExtension>, pub publisher: Option<String>, pub publisher_ext: Option<FieldExtension>, pub contact: Vec<Option<ContactDetail>>, pub contact_ext: Vec<Option<FieldExtension>>, pub description: Option<String>, pub description_ext: Option<FieldExtension>, pub use_context: Vec<Option<UsageContext>>, pub use_context_ext: Vec<Option<FieldExtension>>, pub jurisdiction: Vec<Option<CodeableConcept>>, pub jurisdiction_ext: Vec<Option<FieldExtension>>, pub purpose: Option<String>, pub purpose_ext: Option<FieldExtension>, pub usage: Option<String>, pub usage_ext: Option<FieldExtension>, pub copyright: Option<String>, pub copyright_ext: Option<FieldExtension>, pub copyright_label: Option<String>, pub copyright_label_ext: Option<FieldExtension>, pub approval_date: Option<Date>, pub approval_date_ext: Option<FieldExtension>, pub last_review_date: Option<Date>, pub last_review_date_ext: Option<FieldExtension>, pub effective_period: Option<Period>, pub effective_period_ext: Option<FieldExtension>, pub topic: Vec<Option<CodeableConcept>>, pub topic_ext: Vec<Option<FieldExtension>>, pub author: Vec<Option<ContactDetail>>, pub author_ext: Vec<Option<FieldExtension>>, pub editor: Vec<Option<ContactDetail>>, pub editor_ext: Vec<Option<FieldExtension>>, pub reviewer: Vec<Option<ContactDetail>>, pub reviewer_ext: Vec<Option<FieldExtension>>, pub endorser: Vec<Option<ContactDetail>>, pub endorser_ext: Vec<Option<FieldExtension>>, pub related_artifact: Vec<Option<RelatedArtifact>>, pub related_artifact_ext: Vec<Option<FieldExtension>>, pub library: Vec<Option<String>>, pub library_ext: Vec<Option<FieldExtension>>, pub kind: Option<String>, pub kind_ext: Option<FieldExtension>, pub profile: Option<String>, pub profile_ext: Option<FieldExtension>, pub code: Option<CodeableConcept>, pub code_ext: Option<FieldExtension>, pub intent: Option<RequestIntent>, pub intent_ext: Option<FieldExtension>, pub priority: Option<RequestPriority>, pub priority_ext: Option<FieldExtension>, pub do_not_perform: Option<bool>, pub do_not_perform_ext: Option<FieldExtension>, pub timing: Option<ActivityDefinitionTiming>, pub timing_ext: Option<ActivityDefinitionTimingExtension>, pub as_needed: Option<ActivityDefinitionAsNeeded>, pub as_needed_ext: Option<ActivityDefinitionAsNeededExtension>, pub location: Option<CodeableReference>, pub location_ext: Option<FieldExtension>, pub participant: Vec<Option<ActivityDefinitionParticipant>>, pub participant_ext: Vec<Option<FieldExtension>>, pub product: Option<ActivityDefinitionProduct>, pub product_ext: Option<ActivityDefinitionProductExtension>, pub quantity: Option<Quantity>, pub quantity_ext: Option<FieldExtension>, pub dosage: Vec<Option<Dosage>>, pub dosage_ext: Vec<Option<FieldExtension>>, pub body_site: Vec<Option<CodeableConcept>>, pub body_site_ext: Vec<Option<FieldExtension>>, pub specimen_requirement: Vec<Option<String>>, pub specimen_requirement_ext: Vec<Option<FieldExtension>>, pub observation_requirement: Vec<Option<String>>, pub observation_requirement_ext: Vec<Option<FieldExtension>>, pub observation_result_requirement: Vec<Option<String>>, pub observation_result_requirement_ext: Vec<Option<FieldExtension>>, pub transform: Option<String>, pub transform_ext: Option<FieldExtension>, pub dynamic_value: Vec<Option<ActivityDefinitionDynamicValue>>, pub dynamic_value_ext: Vec<Option<FieldExtension>>, /* private fields */
}
Expand description

This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context.

ActivityDefinition v5.0.0

The definition of a specific activity to be taken, independent of any particular patient or context

This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context.

Fields§

§id: Option<String>

Logical id of this artifact

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.

§meta: Option<Meta>

Metadata about the resource

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.

§implicit_rules: Option<String>

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 its narrative along with other profiles, value sets, etc.

§language: Option<String>

Language; Language of the resource content

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: Option<Narrative>

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 a 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.

§contained: Vec<Resource>

Contained, inline Resources

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

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.

§extension: Vec<Extension>

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 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.

§modifier_extension: Vec<Extension>

Extensions that cannot be ignored

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 managable, 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).

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.

§url: Option<String>

Canonical identifier for this activity definition, represented as a URI (globally unique)

An absolute URI that is used to identify this activity definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this activity definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the activity definition is stored on different servers.

Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions.

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.

§url_ext: Option<FieldExtension>

Extension field.

§identifier: Vec<Option<Identifier>>

Additional identifier for the activity definition

A formal identifier that is used to identify this activity definition when it is represented in other formats, or referenced in a specification, model, design or an instance.

Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this activity definition outside of FHIR, where it is not possible to use the logical URI.

§identifier_ext: Vec<Option<FieldExtension>>

Extension field.

§version: Option<String>

Business version of the activity definition

The identifier that is used to identify this version of the activity definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the activity definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active assets.

There may be different activity definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the activity definition with the format [url]|[version]. The version SHOULD NOT contain a ‘#’ - see Business Version.

§version_ext: Option<FieldExtension>

Extension field.

§version_algorithm: Option<ActivityDefinitionVersionAlgorithm>

How to compare versions

Indicates the mechanism used to compare versions to determine which is more current.

If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can’t be successfully be determined.

§version_algorithm_ext: Option<ActivityDefinitionVersionAlgorithmExtension>

Extension field.

§name: Option<String>

Name for this activity definition (computer friendly)

A natural language name identifying the activity definition. This name should be usable as an identifier for the module by machine processing applications such as code generation.

The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.

§name_ext: Option<FieldExtension>

Extension field.

§title: Option<String>

Name for this activity definition (human friendly)

A short, descriptive, user-friendly title for the activity definition.

This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

§title_ext: Option<FieldExtension>

Extension field.

§subtitle: Option<String>

Subordinate title of the activity definition

An explanatory or alternate title for the activity definition giving additional information about its content.

§subtitle_ext: Option<FieldExtension>

Extension field.

§status: PublicationStatus

PublicationStatus; draft | active | retired | unknown

The status of this activity definition. Enables tracking the life-cycle of the content.

Allows filtering of activity definitions that are appropriate for use versus not.

See guidance around (not) making local changes to elements here.

§status_ext: Option<FieldExtension>

Extension field.

§experimental: Option<bool>

For testing purposes, not real usage

A Boolean value to indicate that this activity definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.

Allows filtering of activity definitions that are appropriate for use versus not.

§experimental_ext: Option<FieldExtension>

Extension field.

§subject: Option<ActivityDefinitionSubject>

Type of individual the activity definition is intended for

A code, group definition, or canonical reference that describes or identifies the intended subject of the activity being defined. Canonical references are allowed to support the definition of protocols for drug and substance quality specifications, and is allowed to reference a MedicinalProductDefinition, SubstanceDefinition, AdministrableProductDefinition, ManufacturedItemDefinition, or PackagedProductDefinition resource.

Note that the choice of canonical for the subject element was introduced in R4B to support pharmaceutical quality use cases. To ensure as much backwards-compatibility as possible, it is recommended to only use the new canonical type with these use cases.

§subject_ext: Option<ActivityDefinitionSubjectExtension>

Extension field.

§date: Option<DateTime>

Date last changed

The date (and optionally time) when the activity definition was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the activity definition changes.

The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the activity definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.

See guidance around (not) making local changes to elements here.

§date_ext: Option<FieldExtension>

Extension field.

§publisher: Option<String>

Name of the publisher/steward (organization or individual)

The name of the organization or individual responsible for the release and ongoing maintenance of the activity definition.

Usually an organization but may be an individual. The publisher (or steward) of the activity definition is the organization or individual primarily responsible for the maintenance and upkeep of the activity definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the activity definition. This item SHOULD be populated unless the information is available from context.

§publisher_ext: Option<FieldExtension>

Extension field.

§contact: Vec<Option<ContactDetail>>

Contact details for the publisher

Contact details to assist a user in finding and communicating with the publisher.

May be a web site, an email address, a telephone number, etc.

See guidance around (not) making local changes to elements here.

§contact_ext: Vec<Option<FieldExtension>>

Extension field.

§description: Option<String>

Natural language description of the activity definition

A free text natural language description of the activity definition from a consumer’s perspective.

This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the activity definition as conveyed in the ‘text’ field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the activity definition is presumed to be the predominant language in the place the activity definition was created).

§description_ext: Option<FieldExtension>

Extension field.

§use_context: Vec<Option<UsageContext>>

The context that the content is intended to support

The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, …) or may be references to specific programs (insurance plans, studies, …) and may be used to assist with indexing and searching for appropriate activity definition instances.

When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

§use_context_ext: Vec<Option<FieldExtension>>

Extension field.

§jurisdiction: Vec<Option<CodeableConcept>>

Jurisdiction; Intended jurisdiction for activity definition (if applicable)

A legal or geographic region in which the activity definition is intended to be used.

It may be possible for the activity definition to be used in jurisdictions other than those for which it was originally designed or intended.

DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new ‘jurisdiction’ code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)

§jurisdiction_ext: Vec<Option<FieldExtension>>

Extension field.

§purpose: Option<String>

Why this activity definition is defined

Explanation of why this activity definition is needed and why it has been designed as it has.

This element does not describe the usage of the activity definition. Instead, it provides traceability of ’‘why’’ the resource is either needed or ’‘why’’ it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this activity definition.

§purpose_ext: Option<FieldExtension>

Extension field.

§usage: Option<String>

Describes the clinical usage of the activity definition

A detailed description of how the activity definition is used from a clinical perspective.

§usage_ext: Option<FieldExtension>

Extension field.

§copyright: Option<String>

Use and/or publishing restrictions

A copyright statement relating to the activity definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the activity definition.

The short copyright declaration (e.g. (c) ‘2015+ xyz organization’ should be sent in the copyrightLabel element.

§copyright_ext: Option<FieldExtension>

Extension field.

§copyright_label: Option<String>

Copyright holder and year(s)

A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. ‘All rights reserved’, ‘Some rights reserved’).

The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general ‘copyright’ element.

§copyright_label_ext: Option<FieldExtension>

Extension field.

§approval_date: Option<Date>

When the activity definition was approved by publisher

The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage.

The ‘date’ element may be more recent than the approval date because of minor changes or editorial corrections.

See guidance around (not) making local changes to elements here.

§approval_date_ext: Option<FieldExtension>

Extension field.

§last_review_date: Option<Date>

When the activity definition was last reviewed by the publisher

The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date.

If specified, this date follows the original approval date.

See guidance around (not) making local changes to elements here.

§last_review_date_ext: Option<FieldExtension>

Extension field.

§effective_period: Option<Period>

When the activity definition is expected to be used

The period during which the activity definition content was or is planned to be in active use.

The effective period for an activity definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a activity intended to be used for the year 2016 might be published in 2015.

See guidance around (not) making local changes to elements here.

§effective_period_ext: Option<FieldExtension>

Extension field.

§topic: Vec<Option<CodeableConcept>>

DefinitionTopic; E.g. Education, Treatment, Assessment, etc

Descriptive topics related to the content of the activity. Topics provide a high-level categorization of the activity that can be useful for filtering and searching.

DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new ‘topic’ code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#topic and useContext.valueCodeableConcept indicating the topic)

§topic_ext: Vec<Option<FieldExtension>>

Extension field.

§author: Vec<Option<ContactDetail>>

Who authored the content

An individiual or organization primarily involved in the creation and maintenance of the content.

§author_ext: Vec<Option<FieldExtension>>

Extension field.

§editor: Vec<Option<ContactDetail>>

Who edited the content

An individual or organization primarily responsible for internal coherence of the content.

§editor_ext: Vec<Option<FieldExtension>>

Extension field.

§reviewer: Vec<Option<ContactDetail>>

Who reviewed the content

An individual or organization asserted by the publisher to be primarily responsible for review of some aspect of the content.

See guidance around (not) making local changes to elements here.

§reviewer_ext: Vec<Option<FieldExtension>>

Extension field.

§endorser: Vec<Option<ContactDetail>>

Who endorsed the content

An individual or organization asserted by the publisher to be responsible for officially endorsing the content for use in some setting.

See guidance around (not) making local changes to elements here.

§endorser_ext: Vec<Option<FieldExtension>>

Extension field.

§related_artifact: Vec<Option<RelatedArtifact>>

Additional documentation, citations, etc

Related artifacts such as additional documentation, justification, or bibliographic references.

Each related artifact is either an attachment, or a reference to another resource, but not both.

§related_artifact_ext: Vec<Option<FieldExtension>>

Extension field.

§library: Vec<Option<String>>

Logic used by the activity definition

A reference to a Library resource containing any formal logic used by the activity definition.

§library_ext: Vec<Option<FieldExtension>>

Extension field.

§kind: Option<String>

ActivityDefinitionKind; Kind of resource

A description of the kind of resource the activity definition is representing. For example, a MedicationRequest, a ServiceRequest, or a CommunicationRequest.

The kind element may only specify Request resource types to facilitate considering user input as part of processing the result of any automated clinical reasoning processes. To support creation of event resources, such as Observations, RiskAssessments, and DetectedIssues, use a Task resource with the focus of the task set to the event resource to be created. Note that the kind of resource to be created may determine what types of extensions are permitted.

§kind_ext: Option<FieldExtension>

Extension field.

§profile: Option<String>

What profile the resource needs to conform to

A profile to which the target of the activity definition is expected to conform.

§profile_ext: Option<FieldExtension>

Extension field.

§code: Option<CodeableConcept>

ActivityDefinitionType; Detail type of activity

Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter.

Tends to be less relevant for activities involving particular products.

§code_ext: Option<FieldExtension>

Extension field.

§intent: Option<RequestIntent>

RequestIntent; proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option

Indicates the level of authority/intentionality associated with the activity and where the request should fit into the workflow chain.

§intent_ext: Option<FieldExtension>

Extension field.

§priority: Option<RequestPriority>

RequestPriority; routine | urgent | asap | stat

Indicates how quickly the activity should be addressed with respect to other requests.

§priority_ext: Option<FieldExtension>

Extension field.

§do_not_perform: Option<bool>

True if the activity should not be performed

Set this to true if the definition is to indicate that a particular activity should NOT be performed. If true, this element should be interpreted to reinforce a negative coding. For example NPO as a code with a doNotPerform of true would still indicate to NOT perform the action.

This element is not intended to be used to communicate a decision support response to cancel an order in progress. That should be done with the “remove” type of a PlanDefinition or RequestOrchestration.

§do_not_perform_ext: Option<FieldExtension>

Extension field.

§timing: Option<ActivityDefinitionTiming>

When activity is to occur

The timing or frequency upon which the described activity is to occur.

The intent of the timing element is to provide timing when the action should be performed. As a definitional resource, this timing is interpreted as part of an apply operation so that the timing of the result actions in a CarePlan or RequestOrchestration, for example, would be specified by evaluating the timing definition in the context of the apply and setting the resulting timing on the appropriate elements of the target resource. If the timing is an Age, the activity is expected to be performed when the subject is the given Age. When the timing is a Duration, the activity is expected to be performed within the specified duration from the apply. When the timing is a Range, it may be a range of Ages or Durations, providing a range for the expected timing of the resulting activity. When the timing is a Timing, it is establishing a schedule for the timing of the resulting activity.

§timing_ext: Option<ActivityDefinitionTimingExtension>

Extension field.

§as_needed: Option<ActivityDefinitionAsNeeded>

Preconditions for service

If a CodeableConcept is present, it indicates the pre-condition for performing the service. For example “pain”, “on flare-up”, etc.

§as_needed_ext: Option<ActivityDefinitionAsNeededExtension>

Extension field.

§location: Option<CodeableReference>

Where it should happen

Identifies the facility where the activity will occur; e.g. home, hospital, specific clinic, etc.

May reference a specific clinical location or may just identify a type of location.

§location_ext: Option<FieldExtension>

Extension field.

§participant: Vec<Option<ActivityDefinitionParticipant>>

Who should participate in the action

Indicates who should participate in performing the action described.

§participant_ext: Vec<Option<FieldExtension>>

Extension field.

§product: Option<ActivityDefinitionProduct>

What’s administered/supplied

Identifies the food, drug or other product being consumed or supplied in the activity.

§product_ext: Option<ActivityDefinitionProductExtension>

Extension field.

§quantity: Option<Quantity>

How much is administered/consumed/supplied

Identifies the quantity expected to be consumed at once (per dose, per meal, etc.).

§quantity_ext: Option<FieldExtension>

Extension field.

§dosage: Vec<Option<Dosage>>

Detailed dosage instructions

Provides detailed dosage instructions in the same way that they are described for MedicationRequest resources.

If a dosage instruction is used, the definition should not specify timing or quantity.

§dosage_ext: Vec<Option<FieldExtension>>

Extension field.

§body_site: Vec<Option<CodeableConcept>>

BodySite; What part of body to perform on

Indicates the sites on the subject’s body where the procedure should be performed (I.e. the target sites).

Only used if not implicit in the code found in ServiceRequest.type.

§body_site_ext: Vec<Option<FieldExtension>>

Extension field.

§specimen_requirement: Vec<Option<String>>

What specimens are required to perform this action

Defines specimen requirements for the action to be performed, such as required specimens for a lab test.

§specimen_requirement_ext: Vec<Option<FieldExtension>>

Extension field.

§observation_requirement: Vec<Option<String>>

What observations are required to perform this action

Defines observation requirements for the action to be performed, such as body weight or surface area.

§observation_requirement_ext: Vec<Option<FieldExtension>>

Extension field.

§observation_result_requirement: Vec<Option<String>>

What observations must be produced by this action

Defines the observations that are expected to be produced by the action.

§observation_result_requirement_ext: Vec<Option<FieldExtension>>

Extension field.

§transform: Option<String>

Transform to apply the template

A reference to a StructureMap resource that defines a transform that can be executed to produce the intent resource using the ActivityDefinition instance as the input.

Note that if both a transform and dynamic values are specified, the dynamic values will be applied to the result of the transform.

§transform_ext: Option<FieldExtension>

Extension field.

§dynamic_value: Vec<Option<ActivityDefinitionDynamicValue>>

Dynamic aspects of the definition

Dynamic values that will be evaluated to produce values for elements of the resulting resource. For example, if the dosage of a medication must be computed based on the patient’s weight, a dynamic value would be used to specify an expression that calculated the weight, and the path on the request resource that would contain the result.

Dynamic values are applied in the order in which they are defined in the ActivityDefinition. Note that if both a transform and dynamic values are specified, the dynamic values will be applied to the result of the transform.

§dynamic_value_ext: Vec<Option<FieldExtension>>

Extension field.

Trait Implementations§

Source§

impl Clone for ActivityDefinitionInner

Source§

fn clone(&self) -> ActivityDefinitionInner

Returns a duplicate of the value. Read more
1.0.0 · Source§

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source. Read more
Source§

impl Debug for ActivityDefinitionInner

Source§

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter. Read more
Source§

impl<'de> Deserialize<'de> for ActivityDefinitionInner

Source§

fn deserialize<__D>( __deserializer: __D, ) -> Result<ActivityDefinitionInner, <__D as Deserializer<'de>>::Error>
where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer. Read more
Source§

impl From<ActivityDefinitionInner> for ActivityDefinition

Source§

fn from(inner: ActivityDefinitionInner) -> ActivityDefinition

Converts to this type from the input type.
Source§

impl PartialEq for ActivityDefinitionInner

Source§

fn eq(&self, other: &ActivityDefinitionInner) -> bool

Tests for self and other values to be equal, and is used by ==.
1.0.0 · Source§

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.
Source§

impl Serialize for ActivityDefinitionInner

Source§

fn serialize<__S>( &self, __serializer: __S, ) -> Result<<__S as Serializer>::Ok, <__S as Serializer>::Error>
where __S: Serializer,

Serialize this value into the given Serde serializer. Read more
Source§

impl StructuralPartialEq for ActivityDefinitionInner

Auto Trait Implementations§

Blanket Implementations§

Source§

impl<T> Any for T
where T: 'static + ?Sized,

Source§

fn type_id(&self) -> TypeId

Gets the TypeId of self. Read more
Source§

impl<T> Borrow<T> for T
where T: ?Sized,

Source§

fn borrow(&self) -> &T

Immutably borrows from an owned value. Read more
Source§

impl<T> BorrowMut<T> for T
where T: ?Sized,

Source§

fn borrow_mut(&mut self) -> &mut T

Mutably borrows from an owned value. Read more
Source§

impl<T> CloneToUninit for T
where T: Clone,

Source§

unsafe fn clone_to_uninit(&self, dest: *mut u8)

🔬This is a nightly-only experimental API. (clone_to_uninit)
Performs copy-assignment from self to dest. Read more
Source§

impl<T> From<T> for T

Source§

fn from(t: T) -> T

Returns the argument unchanged.

Source§

impl<T> Instrument for T

Source§

fn instrument(self, span: Span) -> Instrumented<Self>

Instruments this type with the provided Span, returning an Instrumented wrapper. Read more
Source§

fn in_current_span(self) -> Instrumented<Self>

Instruments this type with the current Span, returning an Instrumented wrapper. Read more
Source§

impl<T, U> Into<U> for T
where U: From<T>,

Source§

fn into(self) -> U

Calls U::from(self).

That is, this conversion is whatever the implementation of From<T> for U chooses to do.

Source§

impl<T> PolicyExt for T
where T: ?Sized,

Source§

fn and<P, B, E>(self, other: P) -> And<T, P>
where T: Policy<B, E>, P: Policy<B, E>,

Create a new Policy that returns Action::Follow only if self and other return Action::Follow. Read more
Source§

fn or<P, B, E>(self, other: P) -> Or<T, P>
where T: Policy<B, E>, P: Policy<B, E>,

Create a new Policy that returns Action::Follow if either self or other returns Action::Follow. Read more
Source§

impl<T> ToOwned for T
where T: Clone,

Source§

type Owned = T

The resulting type after obtaining ownership.
Source§

fn to_owned(&self) -> T

Creates owned data from borrowed data, usually by cloning. Read more
Source§

fn clone_into(&self, target: &mut T)

Uses borrowed data to replace owned data, usually by cloning. Read more
Source§

impl<T, U> TryFrom<U> for T
where U: Into<T>,

Source§

type Error = Infallible

The type returned in the event of a conversion error.
Source§

fn try_from(value: U) -> Result<T, <T as TryFrom<U>>::Error>

Performs the conversion.
Source§

impl<T, U> TryInto<U> for T
where U: TryFrom<T>,

Source§

type Error = <U as TryFrom<T>>::Error

The type returned in the event of a conversion error.
Source§

fn try_into(self) -> Result<U, <U as TryFrom<T>>::Error>

Performs the conversion.
Source§

impl<V, T> VZip<V> for T
where V: MultiLane<T>,

Source§

fn vzip(self) -> V

Source§

impl<T> WithSubscriber for T

Source§

fn with_subscriber<S>(self, subscriber: S) -> WithDispatch<Self>
where S: Into<Dispatch>,

Attaches the provided Subscriber to this type, returning a WithDispatch wrapper. Read more
Source§

fn with_current_subscriber(self) -> WithDispatch<Self>

Attaches the current default Subscriber to this type, returning a WithDispatch wrapper. Read more
Source§

impl<T> DeserializeOwned for T
where T: for<'de> Deserialize<'de>,

Source§

impl<T> ErasedDestructor for T
where T: 'static,