UPI (unique person identifier) declaration interface. Schema for UPI related declaration request and response messages. $Id: eCH-0084-1-0.xsd,v 1.8 2009-03-20 12:55:18 tqn Exp $ Type describing the header of each message. Identifier of the institution which is sending the request (data of the declaration. In other words, a constant for each institution which can be source of data. The source ID format is compliant to the sedex participant ID. See the 'sedex Handbuch', ch. 4.9. Running number forming with sedexId a key identifying the declaration. If a second declaration is sent with the same key, it is refused. Contains information useful in case of manual clearing. For instance the case reference or the direct telephone number or the name of le clerk who has treated the record, etc... Extended person-related information element, where every single subelement is optional. The maiden name. Present only, if the maiden name is relevant. The presence of the contained element municipalityName is only allowed if the date of birth is before 1960. To delete the current value in the UPI for the mother's name at brith, set nil="true". To delete the current value in the UPI for the father's name at brith, set nil="true". To delete the current value in the UPI for the date of death, set nil="true". Declaration of a new person to the UPI (Universal Personal Identifier) DB of the Swiss social security. Before sending this declaration, you should be reasonably sure that this person is not already present in the UPI DB. Header common to all messages. Represents the person identifier in the information system of the institution sending the declaration. The cardinality 0 is only allowed for institutions belonging to the first pillar of the Swiss social security. In chronological order (oldest first). The presence of this element makes it possible to find a person on the basis of old attribute values. The presence of the element municipalityName is only allowed, if the date of birth is before 1960. Must be present in almost any case. Should be present if available true=this person has a twin brother/sister Requests the update of the person's local person ID. This element is used to modify the values of the persons attributes in the UPI DB. Header common to all messages. Requests the update of the person's current values. This element is used to modify the values of the persons attributes in the UPI DB. Header common to all messages. Represents the person identifier in the information system of the institution sending the declaration. The cardinality 0 is only allowed for institutions belonging to the first pillar of the Swiss social security. Reason for modification. Possible values: 0=unknown, 1=correction, 2=legal event. Requests an additional entry in the person’s historical values. This element is used to modify the values of the persons attributes in the UPI DB. Header common to all messages. The UPI decides wether to treat this request as a "updateCurrentValuesRequest" or as a "addEntryToHistoryRequest". Header common to all messages. Represents the person identifier in the information system of the institution sending the declaration. The cardinality 0 is only allowed for institutions belonging to the first pillar of the Swiss social security. Erasure of a person from the UPI (Universal Personal Identifier) DB of the Swiss social security. A person can only be erased if she as been entered some hours ago. Header common to all messages. The cardinality 0 is only allowed for institutions belonging to the first pillar of the Swiss social security. It represents the person identifier in the information system of the institution sending the declaration. Merging of two (or more) persons in the UPI (Universal Personal Identifier) DB of the Swiss social security. This message is used to merge two persons which appear in the UPI DB as two separate persons into one person. Header common to all messages. Represents the person identifier in the information system of the institution sending the declaration. The cardinality 0 is only allowed for institutions belonging to the first pillar of the Swiss social security. If the communication as broken down while the response was transmitted, a message with this tag allows to recall the latest response to the declaration identified with the key (sedexId, declarationNumber). This element could also be used for manually processed declarations. Header common to all messages. Response to UPI related declaration message. The time, when the response was generated. Content of header received in the request. Is present, if the declaration message has been processed successfully. This element is always present except in case the person is erased. IT contains the current values (recorded in the UPI at the moment mentioned in the element called timestamp) of the attributes of the person having the AHVN contained in the element called ahvn. Empty marker element. Is present, if the declaration message has to be processed manually. The response can be retrieved at a later point in time. Is present, if the declaration message contained an error and has not been processed normally. The reason is for refusing is: 1 = not valid against XSD or an other formal reason (wrong control number of ahvn for instance), or 3 = not valid against UPI data, or 4 = refused by the clearing service, or 10 = service (database) not available. Starts with the detailed error code followed by a short standard text. Manually added free form comment.