ReteLabMessageHeaderAck
Descrizione
Il profilo ReteLabMessageHeaderAck è stato strutturato a partire dalla risorsa generica FHIR MessageHeader e riporta le informazioni sulla fonte del messaggio, il destinatario e, in caso di errori, referenzia il dettaglio dell'errore stesso. Può essere utilizzato sia nel caso di ack applicativi (ACK^T02, ACK^T06 e ACK^R22) che nel caso di ack di commit.
Di seguito è presentato il contenuto del profilo in diversi formati. La corrispondente definizione è consultabile al seguente link: ReteLabMessageHeaderAck.
Snapshot View
| ReteLabMessageHeaderAck (MessageHeader) | C | MessageHeader | There are no (further) constraints on this element Element idMessageHeaderShort description A resource that describes a message that is exchanged between systems DefinitionThe header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle.
| |||
| id | Σ | 0..1 | string | Element idMessageHeader.idShort description ID del messaggio DefinitionCorrispondente campo HL7 secondo specifiche regionali: MSH-10 The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
| meta | Σ | 0..1 | Meta | Element idMessageHeader.metaShort description Metadati della risorsa DefinitionThe 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.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.meta.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.meta.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
| versionId | Σ | 0..1 | id | Element idMessageHeader.meta.versionIdShort description Versione della risorsa DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
| ||
| lastUpdated | Σ | 0..1 | instant | Element idMessageHeader.meta.lastUpdatedShort description Data e ora di ultimo aggiornamento della risorsa DefinitionFormato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
| ||
| source | Σ | 0..1 | uri | There are no (further) constraints on this element Element idMessageHeader.meta.sourceShort description Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
| ||
| profile | Σ | 0..* | canonical(ReteLabMessageHeaderAck) | Element idMessageHeader.meta.profileShort description Profilo al quale la risorsa si riferisce DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(ReteLabMessageHeaderAck) Constraints
| ||
| security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idMessageHeader.meta.securityShort description Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System. All Security Labels (extensible) Constraints
| ||
| tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element idMessageHeader.meta.tagShort description Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idMessageHeader.implicitRulesShort description A set of rules under which this content was created DefinitionA 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 it's narrative along with other profiles, value sets, etc.
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idMessageHeader.languageShort description Language of the resource content DefinitionThe 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). A human language.
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idMessageHeader.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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 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 | 0..* | Resource | There are no (further) constraints on this element Element idMessageHeader.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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 manageable, 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.
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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 manageable, 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
| event[x] | Σ | 1..1 | Element idMessageHeader.event[x]Short description Codice evento DefinitionCode that identifies the event this message represents and connects it with its definition. Events defined as part of the FHIR specification have the system value "http://terminology.hl7.org/CodeSystem/message-events". Alternatively uri to the EventDefinition. Drives the behavior associated with this message. The time of the event will be found in the focus resource. The time of the message will be found in Bundle.timestamp. One of the message events defined as part of this version of FHIR.
| |||
| eventCoding | Coding | Data type | ||||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.event[x].idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.event[x].extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
| system | Σ | 0..1 | uriAuto Value | Element idMessageHeader.event[x].systemShort description Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
https://fhir.siss.regione.lombardia.it/ValueSet/CodiceEventoMessageHeaderMappings
| ||
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.event[x].versionShort description Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| ||
| code | Σ | 0..1 | codeBinding | Element idMessageHeader.event[x].codeShort description Codice evento DefinitionCorrispondente campo HL7 secondo specifiche regionali: MSH-9.2 Need to refer to a particular code in the system. ValueSet relativo alla codifica del codice evento secondo standard HL7 Codice Evento Message Header (required) Constraints
| ||
| display | Σ | 0..1 | string | Element idMessageHeader.event[x].displayShort description Descrizione codice evento DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
| ||
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idMessageHeader.event[x].userSelectedShort description If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| ||
| destination | Σ | 0..* | BackboneElement | Element idMessageHeader.destinationShort description Applicazione di destinazione del messaggio DefinitionCodice identificativo applicativo di destinazione. Indicates where message is to be sent for routing purposes. Allows verification of "am I the intended recipient". Corrispondente campo HL7 secondo specifiche regionali: MSH-5, MSH-6
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.destination.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.destination.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.destination.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 manageable, 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. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
| name | Σ | 0..1 | string | Element idMessageHeader.destination.nameShort description Nome applicazione di destinazione DefinitionHuman-readable name for the target system. May be used for routing of response and/or to support audit. Corrispondente campo HL7 secondo specifiche regionali: MSH-5.1, MSH-6
| ||
| target | Σ | 0..1 | Reference(Device) | There are no (further) constraints on this element Element idMessageHeader.destination.targetShort description Particular delivery destination within the destination DefinitionIdentifies the target end system in situations where the initial message transmission is to an intermediary system. Supports multi-hop routing.
| ||
| endpoint | Σ | 1..1 | url | Element idMessageHeader.destination.endpointShort description Endpoint dell'applicativo di destinazione DefinitionIndicates where the message should be routed to. Identifies where to route the message. The id may be a non-resolvable URI for systems that do not use standard network-based addresses.
| ||
| receiver | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element idMessageHeader.destination.receiverShort description Intended "real-world" recipient for the data DefinitionAllows data conveyed by a message to be addressed to a particular person or department when routing to a specific application isn't sufficient. Allows routing beyond just the application level. Reference(Practitioner | PractitionerRole | Organization) Constraints
| ||
| sender | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element idMessageHeader.senderShort description Real world sender of the message DefinitionIdentifies the sending system to allow the use of a trust relationship. Allows routing beyond just the application level. Use case is for where a (trusted) sending system is responsible for multiple organizations, and therefore cannot differentiate based on source endpoint / authentication alone. Reference(Practitioner | PractitionerRole | Organization) Constraints
| ||
| enterer | Σ | 0..1 | Reference(Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idMessageHeader.entererShort description The source of the data entry DefinitionThe person or device that performed the data entry leading to this message. When there is more than one candidate, pick the most proximal to the message. Can provide other enterers in extensions. Need to know for audit/traceback requirements and possibly for authorization. Usually only for the request but can be used in a response. Reference(Practitioner | PractitionerRole) Constraints
| ||
| author | Σ | 0..1 | Reference(Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idMessageHeader.authorShort description The source of the decision DefinitionThe logical author of the message - the person or device that decided the described event should happen. When there is more than one candidate, pick the most proximal to the MessageHeader. Can provide other authors in extensions. Need to know for audit/traceback requirements and possibly for authorization. Usually only for the request but can be used in a response. Reference(Practitioner | PractitionerRole) Constraints
| ||
| source | Σ | 1..1 | BackboneElement | Element idMessageHeader.sourceShort description Applicazione sorgente DefinitionCodice identificativo dell'Applicativo Inviante Allows replies, supports audit. Corrispondente campo HL7 secondo specifiche regionali: MSH-3, MSH-4
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.source.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.source.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.source.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 manageable, 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. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
| name | Σ | 0..1 | string | Element idMessageHeader.source.nameShort description Nome applicativo sorgente DefinitionHuman-readable name for the source system. May be used to support audit. Corrispondente campo HL7 secondo specifiche regionali: MSH-3.1, MSH-4.1
| ||
| software | Σ | 0..1 | string | Element idMessageHeader.source.softwareShort description Nome software applicativo DefinitionMay include configuration or other information useful in debugging. Supports audit and possibly interface engine behavior.
| ||
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.source.versionShort description Version of software running DefinitionCan convey versions of multiple systems in situations where a message passes through multiple hands. Supports audit and possibly interface engine behavior.
| ||
| contact | Σ | 0..1 | ContactPoint | There are no (further) constraints on this element Element idMessageHeader.source.contactShort description Human contact for problems DefinitionAn e-mail, phone, website or other contact point to use to resolve issues with message communications. Allows escalation of technical issues.
| ||
| endpoint | Σ | 1..1 | url | Element idMessageHeader.source.endpointShort description Endpoint dell'applicativo sorgente DefinitionIdentifies the routing target to send acknowledgements to. Identifies where to send responses, may influence security permissions. The id may be a non-resolvable URI for systems that do not use standard network-based addresses.
| ||
| responsible | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element idMessageHeader.responsibleShort description Final responsibility for event DefinitionThe person or organization that accepts overall responsibility for the contents of the message. The implication is that the message event happened under the policies of the responsible party. Need to know for audit/traceback requirements and possibly for authorization. Usually only for the request but can be used in a response. Reference(Practitioner | PractitionerRole | Organization) Constraints
| ||
| reason | Σ | 1..1 | CodeableConcept | Element idMessageHeader.reasonShort description Cause of event DefinitionNecessario indicare se il messaggio è di tipo applicativo o di commit. Questo permette di discriminare il flusso di messaggi se il codice evento è ACK^T02, ACK^T06 oppure ACK^R22. Need to be able to track why resources are being changed and report in the audit log/history of the resource. May affect authorization. Unordered, Open, by coding.code(Value) BindingReason for event occurrence. ExampleMessageReasonCodes (example) Constraints
| ||
| applicationACK | Σ | 0..1 | CodeableConcept | Element idMessageHeader.reason:applicationACKShort description L'evento è un ack applicativo DefinitionL'ack applicativo è un messaggio di risposta, mandato per confermare la corretta ricezione ed elaborazione del messaggio da parte del destinatario. Need to be able to track why resources are being changed and report in the audit log/history of the resource. May affect authorization. Reason for event occurrence. ExampleMessageReasonCodes (example) Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.reason:applicationACK.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.reason:applicationACK.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
| coding | Σ | 0..* | CodingAuto Value | Element idMessageHeader.reason:applicationACK.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
{
"code": "application"
}Mappings
| ||
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.reason:applicationACK.textShort description Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| ||
| commitACK | Σ | 0..1 | CodeableConcept | Element idMessageHeader.reason:commitACKShort description ack di commit DefinitionL'ack di commit è un messaggio di risposta, mandato per confermare la corretta ricezione del messaggio, ma non la sua elaborazione. Need to be able to track why resources are being changed and report in the audit log/history of the resource. May affect authorization. Reason for event occurrence. ExampleMessageReasonCodes (example) Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.reason:commitACK.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.reason:commitACK.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
| coding | Σ | 0..* | CodingAuto Value | Element idMessageHeader.reason:commitACK.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
{
"code": "commit"
}Mappings
| ||
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.reason:commitACK.textShort description Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| ||
| response | Σ | 1..1 | BackboneElement | There are no (further) constraints on this element Element idMessageHeader.responseShort description If this is a reply to prior message DefinitionInformation about the message that this message is a response to. Only present if this message is a response.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.response.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.response.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.response.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 manageable, 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. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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 | Σ | 1..1 | id | Element idMessageHeader.response.identifierShort description ID del messaggio a cui si sta rispondendo DefinitionThe MessageHeader.id of the message to which this message is a response. Allows receiver to know what message is being responded to. Corrispondente campo HL7 secondo specifiche regionali: MSA - 2
| ||
| code | Σ | 1..1 | codeBinding | Element idMessageHeader.response.codeShort description Codice che identifica il tipo di risposta al messaggio Definition
Allows the sender of the acknowledge message to know if the request was successful or if action is needed. This is a generic response to the request message. Specific data for the response will be found in MessageHeader.focus. The kind of response to a message.
| ||
| details | Σ | 0..1 | Reference(ReteLabOperationOutcome) | Element idMessageHeader.response.detailsShort description Problemi trovati nel messaggio DefinitionReference al profilo ReteLabOperationOutcome Allows the sender of the message to determine what the specific issues are. This SHALL be contained in the bundle. If any of the issues are errors, the response code SHALL be an error. Reference(ReteLabOperationOutcome) Constraints
| ||
| focus | Σ | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idMessageHeader.focusShort description The actual content of the message DefinitionThe actual data of the message - a reference to the root/focus class of the event. Every message event is about actual data, a single resource, that is identified in the definition of the event, and perhaps some or all linked resources. The data is defined where the transaction type is defined. The transaction data is always included in the bundle that is the full message. Only the root resource is specified. The resources it references should be contained in the bundle but are not also listed here. Multiple repetitions are allowed to cater for merges and other situations with multiple focal targets.
| ||
| definition | Σ | 0..1 | canonical(MessageDefinition) | There are no (further) constraints on this element Element idMessageHeader.definitionShort description Link to the definition for this message DefinitionPermanent link to the MessageDefinition for this message. Allows sender to define the expected contents of the message.
|
Differential View
| ReteLabMessageHeaderAck (MessageHeader) | C | MessageHeader | There are no (further) constraints on this element Element idMessageHeaderShort description A resource that describes a message that is exchanged between systems DefinitionThe header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle.
| |||
| id | Σ | 0..1 | string | Element idMessageHeader.idShort description ID del messaggio DefinitionCorrispondente campo HL7 secondo specifiche regionali: MSH-10 The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
| meta | Σ | 0..1 | Meta | Element idMessageHeader.metaShort description Metadati della risorsa DefinitionThe 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.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.meta.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.meta.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
| versionId | Σ | 0..1 | id | Element idMessageHeader.meta.versionIdShort description Versione della risorsa DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
| ||
| lastUpdated | Σ | 0..1 | instant | Element idMessageHeader.meta.lastUpdatedShort description Data e ora di ultimo aggiornamento della risorsa DefinitionFormato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
| ||
| source | Σ | 0..1 | uri | There are no (further) constraints on this element Element idMessageHeader.meta.sourceShort description Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
| ||
| profile | Σ | 0..* | canonical(ReteLabMessageHeaderAck) | Element idMessageHeader.meta.profileShort description Profilo al quale la risorsa si riferisce DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(ReteLabMessageHeaderAck) Constraints
| ||
| security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idMessageHeader.meta.securityShort description Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System. All Security Labels (extensible) Constraints
| ||
| tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element idMessageHeader.meta.tagShort description Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idMessageHeader.implicitRulesShort description A set of rules under which this content was created DefinitionA 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 it's narrative along with other profiles, value sets, etc.
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idMessageHeader.languageShort description Language of the resource content DefinitionThe 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). A human language.
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idMessageHeader.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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 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 | 0..* | Resource | There are no (further) constraints on this element Element idMessageHeader.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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 manageable, 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.
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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 manageable, 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
| event[x] | Σ | 1..1 | Element idMessageHeader.event[x]Short description Codice evento DefinitionCode that identifies the event this message represents and connects it with its definition. Events defined as part of the FHIR specification have the system value "http://terminology.hl7.org/CodeSystem/message-events". Alternatively uri to the EventDefinition. Drives the behavior associated with this message. The time of the event will be found in the focus resource. The time of the message will be found in Bundle.timestamp. One of the message events defined as part of this version of FHIR.
| |||
| eventCoding | Coding | Data type | ||||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.event[x].idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.event[x].extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
| system | Σ | 0..1 | uriAuto Value | Element idMessageHeader.event[x].systemShort description Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
https://fhir.siss.regione.lombardia.it/ValueSet/CodiceEventoMessageHeaderMappings
| ||
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.event[x].versionShort description Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| ||
| code | Σ | 0..1 | codeBinding | Element idMessageHeader.event[x].codeShort description Codice evento DefinitionCorrispondente campo HL7 secondo specifiche regionali: MSH-9.2 Need to refer to a particular code in the system. ValueSet relativo alla codifica del codice evento secondo standard HL7 Codice Evento Message Header (required) Constraints
| ||
| display | Σ | 0..1 | string | Element idMessageHeader.event[x].displayShort description Descrizione codice evento DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
| ||
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idMessageHeader.event[x].userSelectedShort description If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| ||
| destination | Σ | 0..* | BackboneElement | Element idMessageHeader.destinationShort description Applicazione di destinazione del messaggio DefinitionCodice identificativo applicativo di destinazione. Indicates where message is to be sent for routing purposes. Allows verification of "am I the intended recipient". Corrispondente campo HL7 secondo specifiche regionali: MSH-5, MSH-6
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.destination.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.destination.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.destination.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 manageable, 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. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
| name | Σ | 0..1 | string | Element idMessageHeader.destination.nameShort description Nome applicazione di destinazione DefinitionHuman-readable name for the target system. May be used for routing of response and/or to support audit. Corrispondente campo HL7 secondo specifiche regionali: MSH-5.1, MSH-6
| ||
| target | Σ | 0..1 | Reference(Device) | There are no (further) constraints on this element Element idMessageHeader.destination.targetShort description Particular delivery destination within the destination DefinitionIdentifies the target end system in situations where the initial message transmission is to an intermediary system. Supports multi-hop routing.
| ||
| endpoint | Σ | 1..1 | url | Element idMessageHeader.destination.endpointShort description Endpoint dell'applicativo di destinazione DefinitionIndicates where the message should be routed to. Identifies where to route the message. The id may be a non-resolvable URI for systems that do not use standard network-based addresses.
| ||
| receiver | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element idMessageHeader.destination.receiverShort description Intended "real-world" recipient for the data DefinitionAllows data conveyed by a message to be addressed to a particular person or department when routing to a specific application isn't sufficient. Allows routing beyond just the application level. Reference(Practitioner | PractitionerRole | Organization) Constraints
| ||
| sender | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element idMessageHeader.senderShort description Real world sender of the message DefinitionIdentifies the sending system to allow the use of a trust relationship. Allows routing beyond just the application level. Use case is for where a (trusted) sending system is responsible for multiple organizations, and therefore cannot differentiate based on source endpoint / authentication alone. Reference(Practitioner | PractitionerRole | Organization) Constraints
| ||
| enterer | Σ | 0..1 | Reference(Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idMessageHeader.entererShort description The source of the data entry DefinitionThe person or device that performed the data entry leading to this message. When there is more than one candidate, pick the most proximal to the message. Can provide other enterers in extensions. Need to know for audit/traceback requirements and possibly for authorization. Usually only for the request but can be used in a response. Reference(Practitioner | PractitionerRole) Constraints
| ||
| author | Σ | 0..1 | Reference(Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idMessageHeader.authorShort description The source of the decision DefinitionThe logical author of the message - the person or device that decided the described event should happen. When there is more than one candidate, pick the most proximal to the MessageHeader. Can provide other authors in extensions. Need to know for audit/traceback requirements and possibly for authorization. Usually only for the request but can be used in a response. Reference(Practitioner | PractitionerRole) Constraints
| ||
| source | Σ | 1..1 | BackboneElement | Element idMessageHeader.sourceShort description Applicazione sorgente DefinitionCodice identificativo dell'Applicativo Inviante Allows replies, supports audit. Corrispondente campo HL7 secondo specifiche regionali: MSH-3, MSH-4
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.source.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.source.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.source.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 manageable, 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. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
| name | Σ | 0..1 | string | Element idMessageHeader.source.nameShort description Nome applicativo sorgente DefinitionHuman-readable name for the source system. May be used to support audit. Corrispondente campo HL7 secondo specifiche regionali: MSH-3.1, MSH-4.1
| ||
| software | Σ | 0..1 | string | Element idMessageHeader.source.softwareShort description Nome software applicativo DefinitionMay include configuration or other information useful in debugging. Supports audit and possibly interface engine behavior.
| ||
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.source.versionShort description Version of software running DefinitionCan convey versions of multiple systems in situations where a message passes through multiple hands. Supports audit and possibly interface engine behavior.
| ||
| contact | Σ | 0..1 | ContactPoint | There are no (further) constraints on this element Element idMessageHeader.source.contactShort description Human contact for problems DefinitionAn e-mail, phone, website or other contact point to use to resolve issues with message communications. Allows escalation of technical issues.
| ||
| endpoint | Σ | 1..1 | url | Element idMessageHeader.source.endpointShort description Endpoint dell'applicativo sorgente DefinitionIdentifies the routing target to send acknowledgements to. Identifies where to send responses, may influence security permissions. The id may be a non-resolvable URI for systems that do not use standard network-based addresses.
| ||
| responsible | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element idMessageHeader.responsibleShort description Final responsibility for event DefinitionThe person or organization that accepts overall responsibility for the contents of the message. The implication is that the message event happened under the policies of the responsible party. Need to know for audit/traceback requirements and possibly for authorization. Usually only for the request but can be used in a response. Reference(Practitioner | PractitionerRole | Organization) Constraints
| ||
| reason | Σ | 1..1 | CodeableConcept | Element idMessageHeader.reasonShort description Cause of event DefinitionNecessario indicare se il messaggio è di tipo applicativo o di commit. Questo permette di discriminare il flusso di messaggi se il codice evento è ACK^T02, ACK^T06 oppure ACK^R22. Need to be able to track why resources are being changed and report in the audit log/history of the resource. May affect authorization. Unordered, Open, by coding.code(Value) BindingReason for event occurrence. ExampleMessageReasonCodes (example) Constraints
| ||
| applicationACK | Σ | 0..1 | CodeableConcept | Element idMessageHeader.reason:applicationACKShort description L'evento è un ack applicativo DefinitionL'ack applicativo è un messaggio di risposta, mandato per confermare la corretta ricezione ed elaborazione del messaggio da parte del destinatario. Need to be able to track why resources are being changed and report in the audit log/history of the resource. May affect authorization. Reason for event occurrence. ExampleMessageReasonCodes (example) Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.reason:applicationACK.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.reason:applicationACK.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
| coding | Σ | 0..* | CodingAuto Value | Element idMessageHeader.reason:applicationACK.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
{
"code": "application"
}Mappings
| ||
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.reason:applicationACK.textShort description Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| ||
| commitACK | Σ | 0..1 | CodeableConcept | Element idMessageHeader.reason:commitACKShort description ack di commit DefinitionL'ack di commit è un messaggio di risposta, mandato per confermare la corretta ricezione del messaggio, ma non la sua elaborazione. Need to be able to track why resources are being changed and report in the audit log/history of the resource. May affect authorization. Reason for event occurrence. ExampleMessageReasonCodes (example) Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.reason:commitACK.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.reason:commitACK.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
| coding | Σ | 0..* | CodingAuto Value | Element idMessageHeader.reason:commitACK.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
{
"code": "commit"
}Mappings
| ||
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.reason:commitACK.textShort description Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| ||
| response | Σ | 1..1 | BackboneElement | There are no (further) constraints on this element Element idMessageHeader.responseShort description If this is a reply to prior message DefinitionInformation about the message that this message is a response to. Only present if this message is a response.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.response.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.response.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.response.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 manageable, 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. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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 | Σ | 1..1 | id | Element idMessageHeader.response.identifierShort description ID del messaggio a cui si sta rispondendo DefinitionThe MessageHeader.id of the message to which this message is a response. Allows receiver to know what message is being responded to. Corrispondente campo HL7 secondo specifiche regionali: MSA - 2
| ||
| code | Σ | 1..1 | codeBinding | Element idMessageHeader.response.codeShort description Codice che identifica il tipo di risposta al messaggio Definition
Allows the sender of the acknowledge message to know if the request was successful or if action is needed. This is a generic response to the request message. Specific data for the response will be found in MessageHeader.focus. The kind of response to a message.
| ||
| details | Σ | 0..1 | Reference(ReteLabOperationOutcome) | Element idMessageHeader.response.detailsShort description Problemi trovati nel messaggio DefinitionReference al profilo ReteLabOperationOutcome Allows the sender of the message to determine what the specific issues are. This SHALL be contained in the bundle. If any of the issues are errors, the response code SHALL be an error. Reference(ReteLabOperationOutcome) Constraints
| ||
| focus | Σ | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idMessageHeader.focusShort description The actual content of the message DefinitionThe actual data of the message - a reference to the root/focus class of the event. Every message event is about actual data, a single resource, that is identified in the definition of the event, and perhaps some or all linked resources. The data is defined where the transaction type is defined. The transaction data is always included in the bundle that is the full message. Only the root resource is specified. The resources it references should be contained in the bundle but are not also listed here. Multiple repetitions are allowed to cater for merges and other situations with multiple focal targets.
| ||
| definition | Σ | 0..1 | canonical(MessageDefinition) | There are no (further) constraints on this element Element idMessageHeader.definitionShort description Link to the definition for this message DefinitionPermanent link to the MessageDefinition for this message. Allows sender to define the expected contents of the message.
|
Hybrid View
| ReteLabMessageHeaderAck (MessageHeader) | C | MessageHeader | There are no (further) constraints on this element Element idMessageHeaderShort description A resource that describes a message that is exchanged between systems DefinitionThe header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle.
| |||
| id | Σ | 0..1 | string | Element idMessageHeader.idShort description ID del messaggio DefinitionCorrispondente campo HL7 secondo specifiche regionali: MSH-10 The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
| meta | Σ | 0..1 | Meta | Element idMessageHeader.metaShort description Metadati della risorsa DefinitionThe 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.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.meta.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.meta.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
| versionId | Σ | 0..1 | id | Element idMessageHeader.meta.versionIdShort description Versione della risorsa DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
| ||
| lastUpdated | Σ | 0..1 | instant | Element idMessageHeader.meta.lastUpdatedShort description Data e ora di ultimo aggiornamento della risorsa DefinitionFormato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
| ||
| source | Σ | 0..1 | uri | There are no (further) constraints on this element Element idMessageHeader.meta.sourceShort description Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
| ||
| profile | Σ | 0..* | canonical(ReteLabMessageHeaderAck) | Element idMessageHeader.meta.profileShort description Profilo al quale la risorsa si riferisce DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(ReteLabMessageHeaderAck) Constraints
| ||
| security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idMessageHeader.meta.securityShort description Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System. All Security Labels (extensible) Constraints
| ||
| tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element idMessageHeader.meta.tagShort description Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idMessageHeader.implicitRulesShort description A set of rules under which this content was created DefinitionA 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 it's narrative along with other profiles, value sets, etc.
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idMessageHeader.languageShort description Language of the resource content DefinitionThe 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). A human language.
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idMessageHeader.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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 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 | 0..* | Resource | There are no (further) constraints on this element Element idMessageHeader.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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 manageable, 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.
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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 manageable, 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
| event[x] | Σ | 1..1 | Element idMessageHeader.event[x]Short description Codice evento DefinitionCode that identifies the event this message represents and connects it with its definition. Events defined as part of the FHIR specification have the system value "http://terminology.hl7.org/CodeSystem/message-events". Alternatively uri to the EventDefinition. Drives the behavior associated with this message. The time of the event will be found in the focus resource. The time of the message will be found in Bundle.timestamp. One of the message events defined as part of this version of FHIR.
| |||
| eventCoding | Coding | Data type | ||||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.event[x].idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.event[x].extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
| system | Σ | 0..1 | uriAuto Value | Element idMessageHeader.event[x].systemShort description Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
https://fhir.siss.regione.lombardia.it/ValueSet/CodiceEventoMessageHeaderMappings
| ||
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.event[x].versionShort description Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| ||
| code | Σ | 0..1 | codeBinding | Element idMessageHeader.event[x].codeShort description Codice evento DefinitionCorrispondente campo HL7 secondo specifiche regionali: MSH-9.2 Need to refer to a particular code in the system. ValueSet relativo alla codifica del codice evento secondo standard HL7 Codice Evento Message Header (required) Constraints
| ||
| display | Σ | 0..1 | string | Element idMessageHeader.event[x].displayShort description Descrizione codice evento DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
| ||
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idMessageHeader.event[x].userSelectedShort description If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| ||
| destination | Σ | 0..* | BackboneElement | Element idMessageHeader.destinationShort description Applicazione di destinazione del messaggio DefinitionCodice identificativo applicativo di destinazione. Indicates where message is to be sent for routing purposes. Allows verification of "am I the intended recipient". Corrispondente campo HL7 secondo specifiche regionali: MSH-5, MSH-6
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.destination.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.destination.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.destination.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 manageable, 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. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
| name | Σ | 0..1 | string | Element idMessageHeader.destination.nameShort description Nome applicazione di destinazione DefinitionHuman-readable name for the target system. May be used for routing of response and/or to support audit. Corrispondente campo HL7 secondo specifiche regionali: MSH-5.1, MSH-6
| ||
| target | Σ | 0..1 | Reference(Device) | There are no (further) constraints on this element Element idMessageHeader.destination.targetShort description Particular delivery destination within the destination DefinitionIdentifies the target end system in situations where the initial message transmission is to an intermediary system. Supports multi-hop routing.
| ||
| endpoint | Σ | 1..1 | url | Element idMessageHeader.destination.endpointShort description Endpoint dell'applicativo di destinazione DefinitionIndicates where the message should be routed to. Identifies where to route the message. The id may be a non-resolvable URI for systems that do not use standard network-based addresses.
| ||
| receiver | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element idMessageHeader.destination.receiverShort description Intended "real-world" recipient for the data DefinitionAllows data conveyed by a message to be addressed to a particular person or department when routing to a specific application isn't sufficient. Allows routing beyond just the application level. Reference(Practitioner | PractitionerRole | Organization) Constraints
| ||
| sender | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element idMessageHeader.senderShort description Real world sender of the message DefinitionIdentifies the sending system to allow the use of a trust relationship. Allows routing beyond just the application level. Use case is for where a (trusted) sending system is responsible for multiple organizations, and therefore cannot differentiate based on source endpoint / authentication alone. Reference(Practitioner | PractitionerRole | Organization) Constraints
| ||
| enterer | Σ | 0..1 | Reference(Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idMessageHeader.entererShort description The source of the data entry DefinitionThe person or device that performed the data entry leading to this message. When there is more than one candidate, pick the most proximal to the message. Can provide other enterers in extensions. Need to know for audit/traceback requirements and possibly for authorization. Usually only for the request but can be used in a response. Reference(Practitioner | PractitionerRole) Constraints
| ||
| author | Σ | 0..1 | Reference(Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idMessageHeader.authorShort description The source of the decision DefinitionThe logical author of the message - the person or device that decided the described event should happen. When there is more than one candidate, pick the most proximal to the MessageHeader. Can provide other authors in extensions. Need to know for audit/traceback requirements and possibly for authorization. Usually only for the request but can be used in a response. Reference(Practitioner | PractitionerRole) Constraints
| ||
| source | Σ | 1..1 | BackboneElement | Element idMessageHeader.sourceShort description Applicazione sorgente DefinitionCodice identificativo dell'Applicativo Inviante Allows replies, supports audit. Corrispondente campo HL7 secondo specifiche regionali: MSH-3, MSH-4
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.source.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.source.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.source.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 manageable, 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. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
| name | Σ | 0..1 | string | Element idMessageHeader.source.nameShort description Nome applicativo sorgente DefinitionHuman-readable name for the source system. May be used to support audit. Corrispondente campo HL7 secondo specifiche regionali: MSH-3.1, MSH-4.1
| ||
| software | Σ | 0..1 | string | Element idMessageHeader.source.softwareShort description Nome software applicativo DefinitionMay include configuration or other information useful in debugging. Supports audit and possibly interface engine behavior.
| ||
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.source.versionShort description Version of software running DefinitionCan convey versions of multiple systems in situations where a message passes through multiple hands. Supports audit and possibly interface engine behavior.
| ||
| contact | Σ | 0..1 | ContactPoint | There are no (further) constraints on this element Element idMessageHeader.source.contactShort description Human contact for problems DefinitionAn e-mail, phone, website or other contact point to use to resolve issues with message communications. Allows escalation of technical issues.
| ||
| endpoint | Σ | 1..1 | url | Element idMessageHeader.source.endpointShort description Endpoint dell'applicativo sorgente DefinitionIdentifies the routing target to send acknowledgements to. Identifies where to send responses, may influence security permissions. The id may be a non-resolvable URI for systems that do not use standard network-based addresses.
| ||
| responsible | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element idMessageHeader.responsibleShort description Final responsibility for event DefinitionThe person or organization that accepts overall responsibility for the contents of the message. The implication is that the message event happened under the policies of the responsible party. Need to know for audit/traceback requirements and possibly for authorization. Usually only for the request but can be used in a response. Reference(Practitioner | PractitionerRole | Organization) Constraints
| ||
| reason | Σ | 1..1 | CodeableConcept | Element idMessageHeader.reasonShort description Cause of event DefinitionNecessario indicare se il messaggio è di tipo applicativo o di commit. Questo permette di discriminare il flusso di messaggi se il codice evento è ACK^T02, ACK^T06 oppure ACK^R22. Need to be able to track why resources are being changed and report in the audit log/history of the resource. May affect authorization. Unordered, Open, by coding.code(Value) BindingReason for event occurrence. ExampleMessageReasonCodes (example) Constraints
| ||
| applicationACK | Σ | 0..1 | CodeableConcept | Element idMessageHeader.reason:applicationACKShort description L'evento è un ack applicativo DefinitionL'ack applicativo è un messaggio di risposta, mandato per confermare la corretta ricezione ed elaborazione del messaggio da parte del destinatario. Need to be able to track why resources are being changed and report in the audit log/history of the resource. May affect authorization. Reason for event occurrence. ExampleMessageReasonCodes (example) Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.reason:applicationACK.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.reason:applicationACK.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
| coding | Σ | 0..* | CodingAuto Value | Element idMessageHeader.reason:applicationACK.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
{
"code": "application"
}Mappings
| ||
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.reason:applicationACK.textShort description Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| ||
| commitACK | Σ | 0..1 | CodeableConcept | Element idMessageHeader.reason:commitACKShort description ack di commit DefinitionL'ack di commit è un messaggio di risposta, mandato per confermare la corretta ricezione del messaggio, ma non la sua elaborazione. Need to be able to track why resources are being changed and report in the audit log/history of the resource. May affect authorization. Reason for event occurrence. ExampleMessageReasonCodes (example) Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.reason:commitACK.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.reason:commitACK.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
| coding | Σ | 0..* | CodingAuto Value | Element idMessageHeader.reason:commitACK.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
{
"code": "commit"
}Mappings
| ||
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.reason:commitACK.textShort description Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| ||
| response | Σ | 1..1 | BackboneElement | There are no (further) constraints on this element Element idMessageHeader.responseShort description If this is a reply to prior message DefinitionInformation about the message that this message is a response to. Only present if this message is a response.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMessageHeader.response.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.response.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idMessageHeader.response.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 manageable, 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. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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 | Σ | 1..1 | id | Element idMessageHeader.response.identifierShort description ID del messaggio a cui si sta rispondendo DefinitionThe MessageHeader.id of the message to which this message is a response. Allows receiver to know what message is being responded to. Corrispondente campo HL7 secondo specifiche regionali: MSA - 2
| ||
| code | Σ | 1..1 | codeBinding | Element idMessageHeader.response.codeShort description Codice che identifica il tipo di risposta al messaggio Definition
Allows the sender of the acknowledge message to know if the request was successful or if action is needed. This is a generic response to the request message. Specific data for the response will be found in MessageHeader.focus. The kind of response to a message.
| ||
| details | Σ | 0..1 | Reference(ReteLabOperationOutcome) | Element idMessageHeader.response.detailsShort description Problemi trovati nel messaggio DefinitionReference al profilo ReteLabOperationOutcome Allows the sender of the message to determine what the specific issues are. This SHALL be contained in the bundle. If any of the issues are errors, the response code SHALL be an error. Reference(ReteLabOperationOutcome) Constraints
| ||
| focus | Σ | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idMessageHeader.focusShort description The actual content of the message DefinitionThe actual data of the message - a reference to the root/focus class of the event. Every message event is about actual data, a single resource, that is identified in the definition of the event, and perhaps some or all linked resources. The data is defined where the transaction type is defined. The transaction data is always included in the bundle that is the full message. Only the root resource is specified. The resources it references should be contained in the bundle but are not also listed here. Multiple repetitions are allowed to cater for merges and other situations with multiple focal targets.
| ||
| definition | Σ | 0..1 | canonical(MessageDefinition) | There are no (further) constraints on this element Element idMessageHeader.definitionShort description Link to the definition for this message DefinitionPermanent link to the MessageDefinition for this message. Allows sender to define the expected contents of the message.
|
Table View
| MessageHeader | .. | |
| MessageHeader.id | .. | |
| MessageHeader.meta | .. | |
| MessageHeader.meta.versionId | .. | |
| MessageHeader.meta.lastUpdated | .. | |
| MessageHeader.meta.profile | canonical(ReteLabMessageHeaderAck) | .. |
| MessageHeader.event[x] | Coding | .. |
| MessageHeader.event[x].system | .. | |
| MessageHeader.event[x].code | .. | |
| MessageHeader.event[x].display | .. | |
| MessageHeader.destination | .. | |
| MessageHeader.destination.name | .. | |
| MessageHeader.destination.endpoint | .. | |
| MessageHeader.source | .. | |
| MessageHeader.source.name | .. | |
| MessageHeader.source.software | .. | |
| MessageHeader.source.endpoint | .. | |
| MessageHeader.reason | 1.. | |
| MessageHeader.reason:applicationACK | .. | |
| MessageHeader.reason:applicationACK.coding | .. | |
| MessageHeader.reason:commitACK | .. | |
| MessageHeader.reason:commitACK.coding | .. | |
| MessageHeader.response | 1.. | |
| MessageHeader.response.identifier | .. | |
| MessageHeader.response.code | .. | |
| MessageHeader.response.details | Reference(ReteLabOperationOutcome) | .. |
XML View
JSON View
risposta commit ok: MessageHeader
risposta commit ko: MessageHeader
risposta commit ok (ACK^R22): MessageHeader
risposta applicativa ok (ACK^R22): MessageHeader
risposta applicativa ok (ACK^T02): MessageHeader
ValueSet
Nella seguente tabella sono elencati i value set relativi al profilo ReteLabMessageHeaderAck:
| Nome | Descrizione | Riferimento al dettaglio della codifica |
|---|---|---|
| Codice Evento Message Header | Codice evento del messaggio | La codifica è definita dal ValueSet Codice Evento Message Header |