Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted. Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted. If the element is present, it must have either a @value, an @id, or extensions The business identifier that is used to reference the MessageDefinition and *is* expected to be consistent from server to server. A formal identifier that is used to identify this message definition when it is represented in other formats, or referenced in a specification, model, design or an instance. The identifier that is used to identify this version of the message definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the message 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. Indicates the mechanism used to compare versions to determine which is more current. A natural language name identifying the message definition. 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 message definition. A MessageDefinition that is superseded by this definition. The status of this message definition. Enables tracking the life-cycle of the content. A Boolean value to indicate that this message definition is authored for testing purposes (or education/evaluation/marketing) and no version of this resource will ever be intended for genuine usage. The date (and optionally time) when the message 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 message definition changes. The name of the organization or individual responsible for the release and ongoing maintenance of the message definition. Contact details to assist a user in finding and communicating with the publisher. A free text natural language description of the message definition from a consumer's perspective. 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 message definition instances. A legal or geographic region in which the authority that maintains the resource is operating. In general, the jurisdiction is also found in the useContext. The useContext may reference additional jurisdictions because the defining jurisdiction does not necessarily limit the jurisdictions of use. Explanation of why this message definition is needed and why it has been designed as it has. A copyright statement relating to the message definition and/or its contents. Copyright statements are notices of intellectual property ownership and can include restrictions on the use and publishing of the message definition. 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 MessageDefinition that is the basis for the contents of this resource. Identifies a protocol or workflow that this MessageDefinition represents a step in. Event code or link to the EventDefinition. The impact of the content of the message. Identifies the resource (or resources) that are being addressed by the event. For example, the Encounter for an admit message or two Account records for a merge. Declare at a message definition level whether a response is required or only upon error or success, or never. Indicates what types of messages may be sent as an application-level response to this message. Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted. The kind of resource that must be the focus for this message. A profile that reflects constraints for the focal resource (and potentially for related resources). Identifies the minimum number of resources of this type that must be pointed to by a message in order for it to be valid against this MessageDefinition. Identifies the maximum number of resources of this type that must be pointed to by a message in order for it to be valid against this MessageDefinition. Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted. A reference to the message definition that must be adhered to by this supported response. Provides a description of the circumstances in which this response should be used (as opposed to one of the alternative responses). Consequence Currency Notification If the element is present, it must have either a @value, an @id, or extensions Always Error/reject conditions only Never Successful completion only HL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message. If the element is present, it must have either a @value, an @id, or extensions