Please use a compatible browser :Google Chrome or Mozilla Firefox
Page expired. Any change will be lost. Try to refresh the page.
Gazelle update scheduled, unsaved changes will be lost :
Your session will timeout :
Redeployed...
Logged out...
The server is restarting. Any change will be lost.
 

Integration Profile: Unique Person Identification

Integration Profile Information

Id: 361

Keyword: UPI

Name: Unique Person Identification

Description:

Status: Trial Implementation

Document Section:

None

Id
Keyword
Name
Description
Action
1313 UPI_CLIENT Unique Person Identification Client
1314 UPI_SERVICE Unique Person Identification Service
Id
Actor
Integration Profile Option
Assertions
2340UPI_CLIENT - Unique Person Identification ClientNONE - None0
2341UPI_SERVICE - Unique Person Identification ServiceNONE - None0
Assertion Id
Description
eCH0213-001 SPID creation is not possible without NAVS.
eCH0213-002 NAVS cancellation causes automatically SPID cancellation.
eCH0213-003 SPID status is not strictly connected to NAVS status.
eCH0213-004 When creating a SPID, the person's demographic attributes must be provided, in order to submit them to a plausibility check with the NAVS.
eCH0213-005 According to the agreement of the data announced with those in the UPI, the UPI generates one of the three possible answers, which are listed in the table.
eCH0213-006 When a person in the UPI has two (or more) active SPID, an UPI client can then determine, from an announcement, which SPID should be inactivated.
eCH0213-007 A UPI client can announce that an affected SPID should be canceled.
eCH0213-008 In an asynchronous announcement, if the first announcement has not been processed, the process is as usual.
eCH0213-009 In an asynchronous announcement, if the first announcement has already been processed, an error message containing a copy of the original response is returned.
eCH0213-010 Demographic attributes in accordance with eCH eCH-0011 (Data Privacy Standard), eCH-0021 (Data Standard Supplementary Personal Data) and eCH-0044 (Data Standard Person Identification Exchange) shall be delivered.
eCH0213-011 The valid dataset for first and last name is the one that is defined in the official catalog of characteristics.
eCH0213-012 The list of possible values of the actionOnSPIDType element is: "generate", "inactivate", and "cancel".
eCH0213-013 Only active NAVS or SPIDs should be sent in an announcement. Inactive NAVS and inactive SPIDs are tolerated.
eCH0213-014 The root element of a request is called request, it has a mandatory numeric attribute minorVersion, it contains the Minor Version of the XSD schema.
eCH0213-015 The header element of the request is of type eCH-0058: headerType.
eCH0213-016 The element "content" of the request contains the following element: SPIDCategory, responseLanguage, actionOnSPID, additionalInputParameterKey and additionalInputParameterValue, pidsToUPI and personToUPI.
eCH0213-017 Depending on the process that is ordered, the presence of the elements vn, SPID and personToUPI must be guaranteed according to the indications in the table
eCH0213-018 In the case of the request for an inactivation of a SPID, the calling system must send two active SPIDs. The first one that appears in the request is the one that remains active, the second one that must be disabled.
eCH0213-019 In the case where the request is correct on the bottom as on the form and that it could thus be treated, a positive response (positiveResponse) is generated.
eCH0213-020 A positive response must contain only active NAVS and SPID.

Domains

Id
Keyword
Name
Description
19 EPR Elektronische Patient Record

Tool index

    Copyright IHE 2024
  • Gazelle 7.1.7
Back to top