Fundamental types that should be used in different kind of messages, webservice- or JMS-messages for example. The name or ip-number of a machine. Holds information to be able to make integrity logging in the frameworks. The PNR (Personnummer) for the insured person that the information is about. This must be set it the information I viewed by an administrator to make sure integrity logging is made The format Is xxxxxxxxyyyy The Organizational number (Organisationsnummer) for the insured organization that the information is about. This must be set it the information I viewed by an administrator to make sure integrity logging is made The format Is xxxxxxxxyyyy Boolean is set to true if integrity logging has been taken care of in earlier steps by the caller or other application in the chain The name or ip-number of the callers machine/computer. Common message header. Contains information that can be used to track messages in backend system logs, routing of messages, identify receiver of error reports etc. Mandatory information for a call. Name/id of message sender. Example: BTP. Should always be set by the caller. Can be used to identify the receiver of error reports. If no integrity logging information must be sent to the backend service this element shall not be removed Unique id for a message. Can be used to trace a message through our internal systems. Set by the caller. Uniqe Id that corresponds to the Correlation pattern. Always set by the service in the response Name/id of business sender. Can for example be the name of the company hosting the calling service. Name of calling environment, example: tm211_dmahs. Used for information in logs and can also be used during test to route backend calls to the calling environment. If this value is stored in a properties file in a WLS-environment, the recommendation is to use the property "infrastruktur.miljonamn" in the property-file "system.properties". Used to transport metadata (correlationId etc)in the message error. Used for auditing in integrations for example.