pub struct SubscriptionStatusInner {Show 22 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 status: Option<SubscriptionStatus>,
pub status_ext: Option<FieldExtension>,
pub type: SubscriptionNotificationType,
pub type_ext: Option<FieldExtension>,
pub events_since_subscription_start: Option<Integer64>,
pub events_since_subscription_start_ext: Option<FieldExtension>,
pub notification_event: Vec<Option<SubscriptionStatusNotificationEvent>>,
pub notification_event_ext: Vec<Option<FieldExtension>>,
pub subscription: Reference,
pub subscription_ext: Option<FieldExtension>,
pub topic: Option<String>,
pub topic_ext: Option<FieldExtension>,
pub error: Vec<Option<CodeableConcept>>,
pub error_ext: Vec<Option<FieldExtension>>,
/* private fields */
}Expand description
The SubscriptionStatus resource describes the state of a Subscription during notifications. It is not persisted.
SubscriptionStatus v5.0.0
Status information about a Subscription provided during event notification
The SubscriptionStatus resource describes the state of a Subscription during notifications.
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.
status: Option<SubscriptionStatus>SubscriptionStatus; requested | active | error | off | entered-in-error
The status of the subscription, which marks the server state for managing the subscription.
status_ext: Option<FieldExtension>Extension field.
type: SubscriptionNotificationTypeSubscriptionNotificationType; handshake | heartbeat | event-notification | query-status | query-event
The type of event being conveyed with this notification.
type_ext: Option<FieldExtension>Extension field.
events_since_subscription_start: Option<Integer64>Events since the Subscription was created
The total number of actual events which have been generated since the Subscription was created (inclusive of this notification) - regardless of how many have been successfully communicated. This number is NOT incremented for handshake and heartbeat notifications.
events_since_subscription_start_ext: Option<FieldExtension>Extension field.
notification_event: Vec<Option<SubscriptionStatusNotificationEvent>>Detailed information about any events relevant to this notification
Detailed information about events relevant to this subscription notification.
notification_event_ext: Vec<Option<FieldExtension>>Extension field.
subscription: ReferenceReference to the Subscription responsible for this notification
The reference to the Subscription which generated this notification.
subscription_ext: Option<FieldExtension>Extension field.
topic: Option<String>Reference to the SubscriptionTopic this notification relates to
The reference to the SubscriptionTopic for the Subscription which generated this notification.
This value SHOULD NOT be present when using empty payloads, MAY be present when using id-only payloads, and SHOULD be present when using full-resource payloads.
topic_ext: Option<FieldExtension>Extension field.
error: Vec<Option<CodeableConcept>>SubscriptionError; List of errors on the subscription
A record of errors that occurred when the server processed a notification.
Recommended practice: clear errors when status is updated.
error_ext: Vec<Option<FieldExtension>>Extension field.
Trait Implementations§
Source§impl Clone for SubscriptionStatusInner
impl Clone for SubscriptionStatusInner
Source§fn clone(&self) -> SubscriptionStatusInner
fn clone(&self) -> SubscriptionStatusInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more