UPI (unique person identifier) query interface. Schema for UPI related query requests and response messages. $Id: eCH-0085-1-2.xsd,v 1.3 2009-12-10 16:00:24 dbn Exp $ Searches a person in the UPI without his ID as input. Response to a "searchPerson" request. Gets the informations stored under a given persons ID Response to a "getInfoPerson" request. Gets the latest Ahvvn for "any" given person identifier Response to a "getAhvvnRequest" request. Gets the cancelled and inactive Ahvvn during a given time interval Cannot be longer than one year Beginning of the time interval (inclusive). Cannot be before 2008-07-01. End of the time interval (inclusive). Cannot be in the future. Response to a "getCancelledAndInactiveAhvvnRequest" The time, when the response was generated. Echo of the requested parameters Is present, if the request did not comply with the required XML Schema or other constraints. The reason for refusing is: 1 = not valid against XSD or an other formal reason (time interval in the future for instance), or 2 = the beginning of the time interval cannot be before 2008-07-01, or 3 = the end of the time interval cannot be in the future, or 4 = the time interval cannot be longer than one year or 5 end of time interval befor beginning or 10 = service not available (DB down for instance). Starts with the detailed error code followed by a short standard text. Is present, if the query has been processed successfully. The presence of this element means that the last update in the database has been made before the end of the selected time interval (tag "timeInterval/until"). There are 3 possible reasons: 1) the value of "timeInterval/until" is the current day, 2) the service accesses a mirror DB that is only synchronized every 24 hours, 3) nobody modified the reference DB recently (possible during the night or the week-end, almost impossible during a working day). Timestamp of cancellation Ahvvn which has been cancelled, this number does not point anymore on a person The presence of this sequence means that two physical persons where sharing the same AHV-VN (oldAhvvn), this number has been cancelled and exactly two new numbers (newAhvvnCandidate) have been generated. If this sequence is missing, you should try to find the person with the searchPersonRequest of eCH-0085 (or UPIViewer). Be careful! You can not decide automatically which new Ahvvn candidate corresponds to the old Ahvvn. This operation has to be done manually Timestamp of inactivation Ahvvn which has been inactivated. This number still points on a person, but the new number (newAhvvn) should be used New Ahvvn number which should be used instead of the old "oldAhvvn" Multiple "searchPersonRequest" In practice the number of request is limited, see documentation www.zas.admin.ch Response to a "listOfSearchPersonRequest" To link the request to the response use the itemId Multiple "getInfoPersonRequest" In practice the number of request is limited, see documentation www.zas.admin.ch Response to a "listOfGetInfoPersonRequest" To link the request to the response use the InputAhvvn tag Multiple "getAhvvnRequest" In practice the number of request is limited, see documentation www.zas.admin.ch Response to a "listOfGetAhvvnRequest" To link the request to the response use the personIdentification tag Can for instance be used for an Ahvvn with 11 positions, or the STAR Number. The reason is for refusing is: 1 = not valid against XSD, (or 2 = reserved), or 5 = maximum amount of items for request exceeded, or 10 = service not available, try later. Starts with the detailed error code followed by a short standard text. Mandatory Mandatory Mandatory The time, when the response was generated. Is present, if the query has been processed successfully. The presence of this tag means that exactly on person matches the search criteria This element 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. The presence of this tag means that one or several candidates match (eventually only roughly) the search criteria. Please check if one candidate is the person you search. Listed by decreasing order of likeliness. This element 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 ahvvn. In chronological order (oldest first). The presence of this element makes it possible to find a person on the basis of old attibute values. The presence of this tag means that no person matching the search criteria has been found in the UPI. Is present, if the query contained an error (or to few search criteria) and has not been processed normally. The reason is for refusing is: 1 = not valid against XSD or an other formal reason (not self consistent), or 2 = one "almost match" found, more search criteria needed, 3 = more than one match found, more search criteria needed, or 10 = service not available, try later. Starts with the detailed error code followed by a short standard text. Manually added free form comment. The time, when the response was generated. Ahvvn sent as query parameter. Is present, if the query has been processed successfully. If a person has more that one ahvvn than the latest one is sent. This element 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 latestAhvn. Is present, if the query contained an error (or that the person ID "ahvvn" sent as query parameter was not found in the UPI) 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 = person id not found, or 4 ahvnn no more valid, or 10 = service not available. Starts with the error code followed by a short standard text. The time, when the response was generated. Person id sent as query parameter. Is present, if the query has been processed successfully. If a person has more that one ahvvn than the latest one is sent. Is present, if the query contained an error (or that the person ID "ahvvn" sent as query parameter was not found in the UPI) 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 = person id not found, or 4 ahvnn no more valid, or 10 = service not available. Starts with the error code followed by a short standard text.