pub struct SubscriptionInner {Show 42 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 identifier: Vec<Option<Identifier>>,
pub identifier_ext: Vec<Option<FieldExtension>>,
pub name: Option<String>,
pub name_ext: Option<FieldExtension>,
pub status: String,
pub status_ext: Option<FieldExtension>,
pub topic: String,
pub topic_ext: Option<FieldExtension>,
pub contact: Vec<Option<ContactPoint>>,
pub contact_ext: Vec<Option<FieldExtension>>,
pub end: Option<Instant>,
pub end_ext: Option<FieldExtension>,
pub managing_entity: Option<Reference>,
pub managing_entity_ext: Option<FieldExtension>,
pub reason: Option<String>,
pub reason_ext: Option<FieldExtension>,
pub filter_by: Vec<Option<SubscriptionFilterBy>>,
pub filter_by_ext: Vec<Option<FieldExtension>>,
pub channel_type: Coding,
pub channel_type_ext: Option<FieldExtension>,
pub endpoint: Option<String>,
pub endpoint_ext: Option<FieldExtension>,
pub parameter: Vec<Option<SubscriptionParameter>>,
pub parameter_ext: Vec<Option<FieldExtension>>,
pub heartbeat_period: Option<u32>,
pub heartbeat_period_ext: Option<FieldExtension>,
pub timeout: Option<u32>,
pub timeout_ext: Option<FieldExtension>,
pub content_type: Option<String>,
pub content_type_ext: Option<FieldExtension>,
pub content: Option<SubscriptionPayloadContent>,
pub content_ext: Option<FieldExtension>,
pub max_count: Option<NonZero<u32>>,
pub max_count_ext: Option<FieldExtension>,
/* private fields */
}Expand description
The subscription resource describes a particular client’s request to be notified about a SubscriptionTopic.
Subscription v5.0.0
Notification about a SubscriptionTopic
The subscription resource describes a particular client’s request to be notified about a SubscriptionTopic.
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.
identifier: Vec<Option<Identifier>>Additional identifiers (business identifier)
A formal identifier that is used to identify this code system when it is represented in other formats, or referenced in a specification, model, design or an instance.
identifier_ext: Vec<Option<FieldExtension>>Extension field.
name: Option<String>Human readable name for this subscription
A natural language name identifying the subscription.
name_ext: Option<FieldExtension>Extension field.
status: StringSubscriptionStatusCodes; requested | active | error | off | entered-in-error
The status of the subscription, which marks the server state for managing the subscription.
A client can only submit subscription resources in the requested or off state. Only the server can move a subscription from requested to active, and then to error. Either the server or the client can turn a subscription off.
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
status_ext: Option<FieldExtension>Extension field.
topic: StringReference to the subscription topic being subscribed to
The reference to the subscription topic to be notified about.
topic_ext: Option<FieldExtension>Extension field.
contact: Vec<Option<ContactPoint>>Contact details for source (e.g. troubleshooting)
Contact details for a human to contact about the subscription. The primary use of this for system administrator troubleshooting.
contact_ext: Vec<Option<FieldExtension>>Extension field.
end: Option<Instant>When to automatically delete the subscription
The time for the server to turn the subscription off.
The server is permitted to deviate from this time but should observe it.
end_ext: Option<FieldExtension>Extension field.
managing_entity: Option<Reference>Entity responsible for Subscription changes
Entity with authorization to make subsequent revisions to the Subscription and also determines what data the subscription is authorized to disclose.
managing_entity_ext: Option<FieldExtension>Extension field.
reason: Option<String>Description of why this subscription was created
A description of why this subscription is defined.
reason_ext: Option<FieldExtension>Extension field.
filter_by: Vec<Option<SubscriptionFilterBy>>Criteria for narrowing the subscription topic stream
The filter properties to be applied to narrow the subscription topic stream. When multiple filters are applied, evaluates to true if all the conditions applicable to that resource are met; otherwise it returns false (i.e., logical AND).
filter_by_ext: Vec<Option<FieldExtension>>Extension field.
channel_type: CodingSubscriptionChannelType; Channel type for notifications
The type of channel to send notifications on.
channel_type_ext: Option<FieldExtension>Extension field.
endpoint: Option<String>Where the channel points to
The url that describes the actual end-point to send notifications to.
For rest-hook the end-point must be an http: or https: URL; for websockets, ws: or wss:; for email, a mailto: url; and for message the endpoint can be in any form of url the server understands (usually, http/s: or mllp:). The URI is allowed to be relative; in which case, it is relative to the server end-point (since there may be more than one, clients should avoid using relative URIs).
endpoint_ext: Option<FieldExtension>Extension field.
parameter: Vec<Option<SubscriptionParameter>>Channel type
Channel-dependent information to send as part of the notification (e.g., HTTP Headers).
Exactly what these mean depend on the channel type. They can convey additional information to the server or recipient and/or meet security requirements; for example, support of multiple headers in the outgoing notifications for rest-hook type subscriptions. Note that names are not required to be unique, but channel definitions can impose restrictions.
parameter_ext: Vec<Option<FieldExtension>>Extension field.
heartbeat_period: Option<u32>Interval in seconds to send ‘heartbeat’ notification
If present, a ‘heartbeat’ notification (keep-alive) is sent via this channel with an interval period equal to this elements integer value in seconds. If not present, a heartbeat notification is not sent.
heartbeat_period_ext: Option<FieldExtension>Extension field.
timeout: Option<u32>Timeout in seconds to attempt notification delivery
If present, the maximum amount of time a server will allow before failing a notification attempt.
timeout_ext: Option<FieldExtension>Extension field.
content_type: Option<String>MimeType; MIME type to send, or omit for no payload
The MIME type to send the payload in - e.g., application/fhir+xml or application/fhir+json. Note that:
-
clients may request notifications in a specific FHIR version by using the FHIR Version Parameter - e.g.,
application/fhir+json; fhirVersion=4.0. -
additional MIME types can be allowed by channels - e.g.,
text/plainandtext/htmlare defined by the Email channel.
content_type_ext: Option<FieldExtension>Extension field.
content: Option<SubscriptionPayloadContent>SubscriptionPayloadContent; empty | id-only | full-resource
How much of the resource content to deliver in the notification payload. The choices are an empty payload, only the resource id, or the full resource content.
Sending the payload has obvious security implications. The server is responsible for ensuring that the content is appropriately secured.
content_ext: Option<FieldExtension>Extension field.
max_count: Option<NonZero<u32>>Maximum number of events that can be combined in a single notification
If present, the maximum number of events that will be included in a notification bundle. Note that this is not a strict limit on the number of entries in a bundle, as dependent resources can be included.
max_count_ext: Option<FieldExtension>Extension field.
Trait Implementations§
Source§impl Clone for SubscriptionInner
impl Clone for SubscriptionInner
Source§fn clone(&self) -> SubscriptionInner
fn clone(&self) -> SubscriptionInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more