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.
 

View Transaction

View Transaction Information

Id: 438

Keyword: eCH-0214

Name: eCH-0214 - EPR PID Query

Description:

TF Reference:

Status: Trial Implementation

Referenced standards :

If there is no referenced standard the transaction will not appear in the inbound/outbound configurations supported by a system

Document Section :

None

Id
Keyword
Name
Description
Action
361 UPI Unique Person Identification
Id
Keyword
Name
Description
Action
1313UPI_CLIENTUnique Person Identification Client
1314UPI_SERVICEUnique Person Identification Service
Assertion Id
Description
eCH0214-001 A request is for a list of people, this list can also be confined to one person.
eCH0214-002 A subquery is an element of the list in the request. Each subquery must have an unambiguous identifier in the list.
eCH0214-003 The identifier of the subquery is reiterated in the response so that the response unit can be associated with the correct subquery.
eCH0214-004 A response unit is an element of the list in the response.
eCH0214-005 The request structure allows only one type of request by announcement. All subqueries in a given list must therefore be of the same type.
eCH0214-006 Each subquery contains exactly one person.
eCH0214-007 A positive response unit contains either a person or, in the case of a search of a person in the UPI who gives no relevant unambiguous result, a list of candidates.
eCH0214-008 The error messages in the response depend of the request level: global errors for the complete request, or errors at the subquery level are purely related to the given subquery and have no impact on the others subqueries.
eCH0214-009 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.
eCH0214-010 The header element of a request is of type eCH-0058: headerType.
eCH0214-011 The element "content" of the request contains the following elements: SPIDCategory, responseLanguage, getInfoPersonRequest, searchPersonRequest, compareDataRequest.
eCH0214-012 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.
eCH0214-013 A positive response must contain only active NAVS and SPID (unless it is an identical repetition of an element of the request).
eCH0214-014 In the case of an error in the request, a global error announcement (negativeReport) is returned.
eCH0214-015 The element positiveResponse of a positive response may contain those elements: SPIDCategory, globalNotice, getInfoPersonResponse, searchPersonResponse, compareDataResponse.
eCH0214-016 In the case where the sub-query is correct on the bottom as on the form and that it could thus be treated, a positive response unit is generated. Otherwise, an error message is returned at the sub-query level (negativReportOnGetInfoPerson).
eCH0214-017 The following blocks are delivered in a positive response unit: echoPidRequest, notice, pids, personFromUPI.
eCH0214-018 The negativReportOnGetInfoPerson element of type eCH-0213-commons: negativeReportType appears as soon as the subquery has an error, the impact of which is limited to the subquery only (for example when the NAVS check digit in the subquery -request is not correct).
eCH0214-019 When an error, which concerns the whole advertisement (for example when a test announcement was sent in a productive environment), was found in the request, the response contains a global error message of the type eCH-0213-commons : negativeReportType.
eCH0214-020 English name of the search algorithm (or its abbreviation in English) should be used

Tool index

  • Simulators

    Copyright IHE 2024
  • Gazelle 7.1.7
Back to top