Describes a stream of resource state changes or events and annotated with labels useful to filter projections from this topic. Describes a stream of resource state changes or events and annotated with labels useful to filter projections from this topic. If the element is present, it must have either a @value, an @id, or extensions An absolute URI that is used to identify this subscription topic 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 subscription topic is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the subscription topic is stored on different servers. Business identifiers assigned to this subscription topic by the performer and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server. The identifier that is used to identify this version of the subscription topic when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the Topic 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 are orderable. Indicates the mechanism used to compare versions to determine which is more current. A natural language name identifying the subscription topic This name should be usable as an identifier for the module by machine processing applications such as code generation. A short, descriptive, user-friendly title for the subscription topic. For example, "admission". The canonical URL pointing to another FHIR-defined SubscriptionTopic that is adhered to in whole or in part by this SubscriptionTopic. The current state of the SubscriptionTopic. A flag to indicate that this TopSubscriptionTopicic is authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage. The date (and optionally time) when the subscription topic 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 subscription topic changes. Helps establish the "authority/credibility" of the SubscriptionTopic. May also allow for contact. Contact details to assist a user in finding and communicating with the publisher. A free text natural language description of the Topic from the consumer's perspective. The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching of code system definitions. A jurisdiction in which the Topic is intended to be used. Explains why this Topic is needed and why it has been designed as it has. A copyright statement relating to the SubscriptionTopic and/or its contents. Copyright statements are notices of intellectual property ownership and can include restrictions on the use and publishing of the SubscriptionTopic. A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are restricted. (e.g. 'All rights reserved', 'Some rights reserved'). The date on which the asset content was approved by the publisher. Approval happens once when the content is officially approved for usage. The date on which the asset content was last reviewed. Review happens periodically after that, but doesn't change the original approval date. The period during which the SubscriptionTopic content was or is planned to be effective. A definition of a state change or event that triggers a notification based on the SubscriptionTopic. The criteria may be just a human readable description, or may contain a FHIRPath expression, query-based definition, or event coding. Multiple triggers are considered OR joined (e.g., an update matching ANY of the definitions will trigger a notification). Describes a stream of resource state changes or events and annotated with labels useful to filter projections from this topic. The human readable description of this trigger for the SubscriptionTopic - for example, "An Encounter enters the 'in-progress' state". URL of the key definition that is relevant to this trigger. Relative URLs are relative to the StructureDefinition root of the implemented FHIR version (e.g., http://hl7.org/fhir/StructureDefinition). For example, "Patient" maps to http://hl7.org/fhir/StructureDefinition/Patient. For more information, see <a href="elementdefinition-definitions.html#ElementDefinition.type.code">ElementDefinition.type.code</a>. The FHIR RESTful interaction which can be used to trigger a notification for the SubscriptionTopic. Multiple values are considered OR joined (e.g., CREATE or UPDATE). If not present, all supported interactions are assumed. The FHIR query based rules that the server should use to determine when to trigger a notification for this subscription topic. The FHIRPath based rules that the server should use to determine when to trigger a notification for this topic. A well-defined event which can be used to trigger notifications from the SubscriptionTopic. List of properties by which Subscriptions can be filtered. May be defined Search Parameters (e.g., Encounter.patient) or parameters defined within this SubscriptionTopic context (e.g., hub.event). List of properties to describe the shape (e.g., resources) included in notifications from this trigger. Describes a stream of resource state changes or events and annotated with labels useful to filter projections from this topic. The FHIR query based rules are applied to the previous resource state (e.g., state before an update). For `create` interactions, should the `previous` criteria count as an automatic pass or an automatic fail. If not present, the testing behavior during `create` interactions is unspecified (server discretion). The FHIR query based rules are applied to the current resource state (e.g., state after an update). For 'delete' interactions, should the 'current' query criteria count as an automatic pass or an automatic fail. If not present, the testing behavior during `delete` interactions is unspecified (server discretion). If set to `true`, both the `current` and `previous` query criteria must evaluate `true` to trigger a notification for this topic. If set to `false` or not present, a notification for this topic will be triggered if either the `current` or `previous` tests evaluate to `true`. Describes a stream of resource state changes or events and annotated with labels useful to filter projections from this topic. Description of how this filtering parameter is intended to be used. URL of the Resource that is the type used in this filter. This is the "focus" of the topic (or one of them if there are more than one). It will be the same, a generality, or a specificity of the `SubscriptionTopic.trigger.resource` if this is present. Either the canonical URL to a search parameter (like "http://hl7.org/fhir/SearchParameter/encounter-patient") or topic-defined parameter (like "hub.event") which is a label for the filter. Either the canonical URL to a search parameter (like "http://hl7.org/fhir/SearchParameter/encounter-patient") or the officially-defined URI for a shared filter concept (like "http://example.org/concepts/shared-common-event"). Comparators allowed for the filter parameter. Modifiers allowed for the filter parameter. Describes a stream of resource state changes or events and annotated with labels useful to filter projections from this topic. URL of the Data Type, Resource, or definition (e.g., logical model) that is the type used in this shape. This is the 'focus' resource of the topic (or one of them if there are more than one) and the root for this shape definition. It will be the same, a generality, or a specificity of `SubscriptionTopic.trigger.resource` when it is present. Search-style _include directives, rooted in the resource for this shape. Servers SHOULD include resources listed here, if they exist and the user is authorized to receive them. Clients SHOULD be prepared to receive these additional resources, but SHALL function properly without them. Search-style _revinclude directives, rooted in the resource for this shape. Servers SHOULD include resources listed here, if they exist and the user is authorized to receive them. Clients SHOULD be prepared to receive these additional resources, but SHALL function properly without them. Queries and codes that could be included with notifications of this shape. Servers MAY include these queries if supported and desired in the workflow. Describes a stream of resource state changes or events and annotated with labels useful to filter projections from this topic. Coded value(s) used to describe the type of information that evaluating this query will provide. Subscribers can use the values to ensure the data they request are relevant and necessary for their use. Query a subscriber can use to retrieve additional information. The exact contents of the query MAY depend on the value of the `queryType`, however this SHOULD be a query suitable for use as an HTTP GET request (either fully-qualified or partial). create update delete If the element is present, it must have either a @value, an @id, or extensions Test passes Test fails If the element is present, it must have either a @value, an @id, or extensions