| PD | PD-001 | to be reviewed | Testable |
1
|
0
| | In the Patient Discovery request, LivingSubjectName Parameter: Both family and given elements are required. | 10 | Section 3.1.5 | 5/17/17 3:23:18 PM by aberge |
|
| PD | PD-002 | to be reviewed | Testable |
3
|
0
| | If patients are known by multiple names or have had a name change, the alternative names shall be specified as multiple instances of LivingSubjectName in the Patient Discovery request. | 10 | Section 3.1.5 | 5/24/17 8:59:18 AM by aberge |
|
| PD | PD-003 | to be reviewed | Testable |
1
|
0
| | In the Patient Discovery request, LivingSubjectAdministrativeGender Parameter: Is required. | 10 | Section 3.1.5 | 5/17/17 3:23:18 PM by aberge |
|
| PD | PD-004 | to be reviewed | Testable |
1
|
0
| | In the Patient Discovery request, the LivingSubjectAdministrativeGender parameter shall be coded using the HL7 coding for AdministrativeGender; namely code equal to one of M (Male) or F (Female) or UN (Undifferentiated) | 10 | Section 3.1.5 | 5/17/17 3:24:01 PM by aberge |
|
| PD | PD-005 | to be reviewed | Testable |
2
|
0
| | In the Patient Discovery request, LivingSubjectBirthTime Parameter: Is required. | 10 | Section 3.1.5 | 5/30/18 4:17:56 PM by aberge |
|
| PD | PD-006 | to be reviewed | Testable |
2
|
0
| | In the Patient Discovery response, Person.name element: Both family and given elements are required. | 10 | Section 3.1.5 | 5/30/18 4:17:51 PM by aberge |
|
| PD | PD-007 | to be reviewed | Testable |
4
|
0
| | If patients are known by multiple names or have had a name change, the alternative names shall be specified as multiple Patient.name elements of the Patient Discovery response message. | 10 | Section 3.1.5 | 5/24/17 8:59:21 AM by aberge |
|
| PD | PD-008 | to be reviewed | Testable |
3
|
0
| | Person.AdministrativeGenderCode element: Is required in the Patient Discovery response message | 11 | Section 3.1.5 | 5/17/17 3:42:28 PM by aberge |
|
| PD | PD-009 | to be reviewed | Testable |
3
|
0
| | Allowed values for Person.AdministrativeGenderCode element of the Patient Discovery response messages are M (Male) or F (Female) or UN (Undifferentiated). | 11 | Section 3.1.5 | 5/17/17 3:42:30 PM by aberge |
|
| PD | PD-010 | to be reviewed | Testable |
3
|
0
| | Person.BirthTime Parameter: Is required in the Patient Discovery response. | 11 | Section 3.1.5 | 5/17/17 3:42:32 PM by aberge |
|
| PD | PD-011 | to be reviewed | Testable |
4
|
0
| | In both the Patient Discovery request and response, if the Address is shared, The streetAddressLine, city, state, postalCode shall be used for elements of the address. | 11 | Section 3.1.5 | 5/24/17 8:57:20 AM by aberge |
|
| PD | PD-012 | to be reviewed | Not testable |
0
|
0
| | In both the Patient Discovery request and response, if the Address is shared, Multiple streetAddressLine elements may be used if necessary and are specified in order of appearance in the address. | 11 | Section 3.1.5 | 9/13/17 1:29:56 PM by aberge |
|
| PD | PD-013 | to be reviewed | Testable |
3
|
0
| | In both the Patient Discovery request and response messages, if the PatientTelecom is present it shall contain a single phone number. | 11 | Section 3.1.5 | 5/17/17 3:42:36 PM by aberge |
|
| PD | PD-014 | to be reviewed | Testable |
3
|
0
| | Social Security Number SSN is specified in a LivingSubjectId element potentially one of several. | 11 | Section 3.1.5 | 5/17/17 3:42:43 PM by aberge |
|
| PD | PD-015 | to be reviewed | Testable |
3
|
0
| | When specified within the response, the SSN is specified in an OtherIDs element. SSN is designated using the OID 2.16.840.1.113883.4.1. | 11 | Section 3.1.5 | 5/17/17 3:42:45 PM by aberge |
|
| PD | PD-016 | to be reviewed | Testable |
3
|
0
| | Telephone number support MUST be implemented in a "tel" URI as specified in the Internet Engineering Task Force's (IETF) RFC3966 and as further defined in the International Telecommunications Union's E.123. | 11 | Section 3.1.5.1 | 5/17/17 3:42:50 PM by aberge |
|
| PD | PD-017 | to be reviewed | Testable |
3
|
0
| | The response to IHE XCPD Cross Gateway Patient Discovery Transaction [ITI-55] may contain multiple entries, but only a single entry per assigning authority is allowed. | 11 | Section 3.1.6 | 5/17/17 3:42:53 PM by aberge |
|
| PD | PD-018 | to be reviewed | Testable |
3
|
0
| | It is recommended that if the responding gateway has more than one close match it should return the special error condition, described in Section 4 Error Handling. | 12 | Section 3.1.6 | 5/17/17 3:34:26 PM by aberge |
|
| PD | PD-019 | to be reviewed | Testable |
2
|
0
| | In the Patient Discovery response, the assigning authority is specified as the root attribute of the Patient id element. | 12 | Section 3.1.6 | 5/17/17 3:26:12 PM by aberge |
|
| PD | PD-020 | to be reviewed | Testable |
3
|
0
| | In the Patient Discovery response, each Registration Event element is required to have a unique value in the Patient id root attribute element. | 15 | Section 3.1.6 | 5/17/17 3:43:01 PM by aberge |
|